Integrations and connected apps

Use the canonical directory of Rankability data connections, publishing workflows, collaboration apps, and developer integrations.

Use the canonical directory of Rankability data connections, publishing workflows, collaboration apps, and developer integrations.

This is the canonical directory of integrations supported by Rankability. A native connection is configured inside Rankability. An automation workflow uses Rankability's API or MCP support with another service; it is not the same as a native connector.

Before connecting anything, confirm the client, account owner, required data, and least-privilege authorization. A service name appearing in an export option, API example, Serena tool, or marketing page does not by itself mean a native two-way connector exists.

Open client integrations

1. Select a client.

2. Open Settings → Integrations.

3. Choose a service and authorize the requested access.

4. Select the correct site, property, profile, channel, or account.

Native data connections

Connection	What it provides	Setup
Google Search Console	Queries, pages, clicks, impressions, CTR, and average position.	Connect Google Search Console
Google Analytics 4	Sessions, engagement, conversions, traffic sources, and AI-referral context where available.	Connect Google Analytics 4
Google Business Profile	Authorized business and location context for supported local workflows.	Connect client Google services
Bing Webmaster Tools	Bing query and page performance used by the supported client workflow.	Connect Bing Webmaster Tools
YouTube	Authorized channel and video context for supported client and Serena workflows.	Use Serena with connected apps

Knowledge, publishing, and collaboration

• Client Sources and Google Drive provide approved client knowledge and files to the workflows that support them. See Serena knowledge and data connections.

• WordPress and other CMS destinations use the publishing or export formats available in Copywriter. See Exporting your content. An export format is not automatically a live, two-way CMS integration.

• Slack can be connected for supported Serena collaboration workflows. See Using Serena with connected apps.

• Serena with GSC and GA4 uses the connected client data within supported analysis workflows. See How Serena uses GA4 and GSC for scope and limitations.

Native task-management connections

Rankability has native project-management connections for the services shown under Settings → Organization → Integrations → Project management. Connect one provider for the organization, then map each client to its external destination.

Connection	What it provides	Setup
Asana	Sends supported Copywriter projects, Activity assignments, and monitoring alerts to a mapped Asana project. Completion sync is limited to supported linked item types.	Connect Rankability to Asana
ClickUp	Sends supported work to the selected client destination using ClickUp's workspace, space, and list hierarchy.	Configure the provider and client mapping in Rankability.
monday.com	Sends supported work to the mapped board when the connection is available for the organization.	Configure the provider and client mapping in Rankability.

A native task-management connection does not automatically assign a person, add a due date, send every project, publish content, or provide universal two-way synchronization.

Developer integrations

• Agent API — Create a scoped API key for programmatic access to supported Rankability workflows. Start with Getting started with the API.

• Model Context Protocol (MCP) — Connect a compatible AI assistant through OAuth or a scoped API key. See Connecting Rankability to AI assistants with MCP.

Automation platforms

Zapier and Make are automation options, not requirements for Rankability's native Asana connection. Where an automation platform supports webhooks or authenticated HTTP requests, you can build workflows against the Rankability API. Review API use cases and automation patterns and the other service's current capabilities before designing the workflow.

Freshness, permissions, and security

Connected data can lag its source. Confirm the selected client, property, date range, last sync, and signed-in account before treating missing data as zero. Grant only the permissions a workflow needs, keep API keys out of browser code and public repositories, and disconnect access that is no longer required.

Validate a new connection

1. Authorize with an account that already has access to the intended property or destination.

2. Select the exact site, property, profile, channel, or account.

3. Wait for the first import or status check to complete.

4. Compare one bounded result with the source service using matching dates and filters.

5. Record the owner and purpose of the connection so it can be reviewed or revoked later.

Common connection states

• Connected, no data — The property can be correct while the first import is incomplete or the selected range has no rows.

• Authorization expired — Reconnect with the authorized account and reselect the intended resource.

• Resource not listed — Confirm the external account's permission; Rankability cannot select a property the provider does not return.

• Wrong client or property — Correct it before using the data in reports or Serena. Integrations are client-scoped.

• Automation cannot authenticate — Review Authentication and API keys, scopes, base URL, and server-side secret storage.

• Publishing option is unavailable — Review Exporting your content and the current destination state; a file export does not create a live CMS connection.

• Task handoff is unavailable — Confirm that a project-management provider is connected for the organization and that the selected client is mapped to an accessible destination.

Disconnecting a service stops future authorized access but does not necessarily delete historical results already stored in Rankability. Contact support before assuming a disconnect is a data-erasure request.