Search Console

Connect Google Search Console with read-only access. What RankDebug pulls and what it is used for.

Search Console is the source most of RankDebug is measured in. Connect it first.

Access

RankDebug asks Google for one scope:

https://www.googleapis.com/auth/webmasters.readonly

That is read-only access to the Search Console properties your Google account can see. RankDebug cannot submit sitemaps, change settings or add users with it.

Connecting

  1. On Connections, click Connect Search Console and approve access on Google's screen.
  2. Back in RankDebug, choose the property for this website. Only properties you have verified access to are listed. A domain property is shown by its domain, a URL-prefix property by its URL.

What is pulled

  • Clicks, impressions, CTR and average position per day.
  • The same numbers by page, by query, by page and query together, and by country and device.
  • The sitemaps Search Console reports for the property, with their warnings, errors and submitted and indexed counts.

The first pull reaches back about 16 months, the history Google keeps, one week at a time from the oldest. After that, a daily sync pulls the last four days again, because Search Console data arrives two to three days late and is revised.

What it powers

  • The Overview chart and the top pages and queries.
  • Opportunities, scored once a day from the pulled history.
  • Clicks at stake on every site check and crawl finding.
  • The pages a site check visits beyond the homepage, which are the pages that earn the most clicks.
  • The weekly site crawl, which runs for workspaces with an active Search Console connection.
  • The search impact shown on each deploy.
Related documentation
  • Guide

    How the parts of RankDebug fit together, and where to find each one in the dashboard.

  • Connections

    How data sources connect to a workspace, how often they sync, and what happens when you disconnect one.

  • Google Analytics

    Connect Google Analytics with read-only access to see what search visitors did after they landed.

  • Cloudflare

    Connect Cloudflare with a read-only API token to see which crawlers reach your site and what the edge did to them.

  • Bing Webmaster Tools

    Connect Bing Webmaster Tools with an API key to add Bing search data and crawl statistics.

  • GitHub

    Connect a GitHub repository so production deploys are recorded on their own, with the SEO-relevant files each one changed.

  • GitLab

    Connect a GitLab project with a read-only token so production deploys are recorded on their own.

  • Deploys

    Record each release from CI or a connected repository, and see what it changed on the site and in search.

Was this helpful?

On this page