The SEO Deployment Guard, on every pull request.
RankSage's GitHub App checks a pull request's built pages for changes that would stop them being indexed or cited, and reports on the pull request before it merges. The regressions that usually surface in Search Console weeks later surface in code review instead.
What GitHub gives RankSage
- A check on each pull request's rendered pages for indexing regressions, reported on the PR.
- Coverage limited to repositories that build a website — libraries and services are recognised and skipped.
- Findings that land in the same ranked action queue as everything else.
How to connect
- 1
Install the RankSage GitHub App
Choose the repositories it may read. Installation is scoped to those and nothing else.
- 2
Map a repository to a site
RankSage classifies the repository and only guards ones that produce a website.
- 3
Open a pull request
The guard runs on the preview build and posts its findings before merge.
What it does not do
- Read access to the repositories you install it on; RankSage never pushes commits or changes settings.
- Disconnecting uninstalls the App from those repositories.
- Only repositories RankSage recognises as building a website are checked.
Questions
What counts as an indexing regression?
A change in the built pages that would stop a page being indexed or cited the way it was — the guard compares the pull request's rendered output against what is live and reports the difference.
Does it block merges?
It reports on the pull request. Whether a finding blocks the merge is your branch-protection choice.
Start with the two that matter.
Google Analytics and Search Console, read-only, about five minutes. Add GitHub whenever it earns its place.