What permissions does RankOut request from Google?

Read-only access to Search Console and Analytics data. It never requests write access to Google properties. Every authorisation is recorded in the project's authorization log.

Can I disconnect an integration?

Yes — each has a Disconnect action on the Connections tab. For the WordPress Connector, disconnecting also revokes the grant on the site's own plugin.

Connect your data

How to connect the WordPress Connector, Google Search Console and Analytics, Google Business Profile, Google Tag Manager, GitHub, PageSpeed and Jira — and what each one enables.

Connections are managed per project. Open the project on the Clients screen and choose Edit, then the Connections tab — or click any Set up button on the Setup page to land there directly. RankOut only ever shows data for connections you've actually made.

WordPress Connector (recommended for WordPress sites)

The RankOut Connector is a WordPress plugin that gives RankOut a scoped, revocable connection to the site. It's the deepest integration: RankOut can read pages and settings, apply approved changes, read the value back to validate them, and roll a change back from WordPress's own revision history.

1
Install the plugin
Install and activate the RankOut Connector plugin on the WordPress site.
2
Start the connection
On the Connections tab choose Connect next to WordPress Connector. RankOut opens the site's authorisation screen.
3
Approve on the site
Sign in to WordPress as a user with the capabilities you want RankOut to act with, and approve. The grant acts as that user — its permissions cap what RankOut can change.
4
Confirm
The Connections tab shows Connected, the WordPress user, and the granted scope.

The connector's scope is the WordPress user's own capabilities. If a proposal you approve fails on WordPress's side, it usually means that user can't perform that action — connect as a user with broader capabilities.

Easy MCP (legacy)

Older projects may be connected through the Easy MCP AI plugin instead. It still works as a website-access path, but new projects should use the RankOut Connector — it's the path that supports validation read-back and one-click rollback.

Google Search Console + Google Analytics

One Google authorisation covers both. After authorising you pick which Search Console property and which Analytics property belong to this project.

Search Console unlocks: Query and page performance history, indexability signals, and per-change measurement — RankOut compares the target query's clicks, impressions, CTR and position before and after a change.
Analytics unlocks: Sessions, engagement and conversion baselines, used in outcome measurement and in reports.

1
Authorise Google
On the Connections tab choose Connect next to Google. Sign in and grant read access.
2
Pick the Search Console property
Choose the exact property (domain or URL-prefix) that matches this site.
3
Pick the Analytics property
Choose the GA4 property for this site.

If Setup shows Search Console or Analytics as Action needed, Google is authorised but the property hasn't been selected — finish it on the Connections tab.

GitHub

For codebase-backed sites, connect GitHub so RankOut can prepare changes as pull requests instead of applying them directly. RankOut browses and reads the repo to draft a change, then opens a PR for a human to review and merge.

1
Install the GitHub App
Choose Connect next to GitHub and install the RankOut GitHub App on the repository.
2
Pick the repository
If the installation covers more than one repo, select the one for this project.

Google Business Profile

Optional. Connect for local and near-me visibility: ratings, reviews and profile insights feed reports and the local view. Authorise Google Business Profile, then choose which business location to link.

Google Tag Manager

Optional. Provides tag and measurement-configuration evidence. It needs both the container ID and a GTM OAuth credential for this project — add both on the Connections tab.

PageSpeed API key

Optional. A Google PageSpeed Insights API key raises the rate limit for performance checks used in the crawl baseline and the Performance view. Add the key on the Connections tab.

Jira

Optional. Jira is a one-way sync target, never the system of record. Set a Jira project key (and, for API sync, Jira credentials) so work items can be mirrored into a Jira board for teams that run delivery there.