Guide
How the parts of RankDebug fit together, and where to find each one in the dashboard.
RankDebug answers one question for a website: when search traffic moves, what caused it and what is worth fixing first. It gets there by keeping three kinds of record side by side.
The first is what search engines and visitors did. Search Console, Google Analytics, Cloudflare and Bing are pulled into the workspace on a schedule and kept as history. The second is what changed on the site. Deploys arrive from your CI or from a connected repository, and every production deploy is followed by a site check and a site crawl that compare the site against how it looked before. The third is what the data says you could gain: opportunities scored from Search Console, ranked by clicks at stake.
Because all three share one timeline, a finding can carry the clicks the affected pages earned, and a drop can be lined up against the deploy that came before it.
Where things live
The left sidebar of the dashboard follows the same split:
- Overview shows Search Console clicks, impressions, CTR and position with deploys marked on the chart, the top pages and queries, and the Google Analytics and Cloudflare views when those are connected.
- Opportunities lists the scored opportunities.
- Deploys lists every deploy with its site check, and holds the latest check of the site.
- Crawl shows the latest site crawl, its findings, AI readiness and what changed since the crawl before.
- Web Vitals shows real-visitor speed by device and by page type.
- Connections is where every data source is connected.
- Reports holds the reports shared with the workspace.
- Agent is a chat over all of the above.
Under Workspace in the sidebar you find Team, API Keys, Webhooks and Logs. Settings holds your profile, security and notifications, the workspace list, the workspace context, the agent's task history, and billing.
Every finding is ranked by clicks
Site check and crawl findings are ordered by severity, and within a severity by the Search Console clicks the affected pages earned over the last 28 days, so a broken page nobody visits sorts below a broken page that brings in traffic. Opportunities are ordered by the clicks they could add. The findings reference explains every finding kind.
Related documentation
- Connections
How data sources connect to a workspace, how often they sync, and what happens when you disconnect one.
- Search Console
Connect Google Search Console with read-only access. What RankDebug pulls and what it is used for.
- 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.