Deploy TrackingFeature

See which release moved your search traffic

When clicks fall, the first question is what changed. Deploy Tracking keeps a dated record of every release, checks the site right after it, and connects new problems to the files and signals that changed.

Book a DemoSee Pricing

Every Way You Ship

A CLI step in CI, a GitHub Action, a GitLab template, a read-only GitHub App or GitLab token, a webhook, or a manual entry in the dashboard.

Checked Right After

Each deploy queues a Site Check and a crawl, so a broken robots.txt or a stray noindex is caught the day it ships.

Before and After

Search Console clicks for the days before and after each deploy, side by side, so a release that hurt traffic stands out.

Likely Cause

From a new problem to the change that probably caused it

The CLI reads your diff on your own machine and sends only file paths and the names of the SEO signals that changed, never your code. When a check finds a new noindex, a changed canonical or a robots.txt rule, we match it to the deploys and files that touched that signal.

  • Detects changes to noindex, nofollow, canonical, hreflang and robots meta
  • Detects changes to titles, meta descriptions and structured data
  • Detects redirects, 404 and 410 handling, trailing slash and base path changes
  • Detects robots.txt rule changes
  • Source code never leaves your machine; only paths and signal names do
Your History

A release timeline you can search months later

Most traffic investigations start long after the drop. Because deploys are stored with their dates and signals, you can go back to any week and see what shipped, what the checks found afterwards, and how clicks moved.

  • Repository connections backfill recent releases when you connect them
  • Deploys appear in the digest email and in the agent’s answers
  • API keys can be scoped to record deploys and nothing else
Explore

More in RankDebug

Site Check

Catches robots.txt, sitemap, host and noindex breaks within a day

Site Crawl

A polite crawler that finds page-level issues and diffs every run

Opportunities

Near-wins, low CTR, decay and cannibalisation, ranked by clicks at stake

AI Readiness

Whether AI crawlers can reach your pages and read your content

Agent

Ask questions about your search data and get answers with evidence

Reports

Written analysis from our team, with live charts and comments

Deploy Tracking: questions and answers

Do you need access to our source code?

No. The CLI analyses the diff locally and sends only file paths and signal names. The optional GitHub App asks for read-only access to deployments and metadata, and nothing in the product writes to a repository.

We deploy many times a day. Is that a problem?

No. Every deploy is recorded. Checks are queued per deploy, and the before-and-after comparison uses daily Search Console data, so frequent releases are compared over the same days.

Can we record a deploy without changing our pipeline?

Yes. Connect GitHub or GitLab and releases are picked up on their own, or post to a webhook, or add a deploy by hand in the dashboard.

Does it show search engine updates on the same timeline?

Not yet. Today the timeline holds your own deploys and the checks that followed them. Search engine events are on our roadmap.

See Deploy Tracking on your own site

In a short call we connect your site, show you what RankDebug finds, and agree a plan that fits it.

Book a Demo