Know what your deploy broke before Google does.
Automatic SEO checks after you deploy. Alerts to the people who need them. Proof the fix worked.
How it works.
-
1
Add your site and show it's yours
Connect Google Search Console, if you're an owner or a full user of the site there. Or ask your developer, who can do it from the dashboard in minutes.
-
2
We watch it
We check your key pages, the ones that must stay in Google, every day. The rest of the site is checked on a schedule, up to your plan's size. Once your developer adds one step to your deploy, we also check within minutes of a deploy: your key pages, a few pages of each main kind, such as products or articles, and newly added pages. If we're ever down, your deploy carries on as normal.
-
3
You hear about it, and the fix is proven
If something broke, your developer sees it right in the deploy: what broke, on which pages, and why. Fix it yourself, or hand our fix instructions to an AI coding tool such as Claude Code or Cursor. After the next deploy we check the pages we found it on again: Verified, Partly verified or Still there.
What your developer adds
# Under jobs:, after the job that deploys.
seo-uptime:
needs: deploy
runs-on: ubuntu-latest
timeout-minutes: 7
steps:
- name: Check the deploy with SEO Uptime
uses: codenyra/seo-uptime@v1
with:
token: ${{ secrets.SEO_HOOK_TOKEN }}Alerts in plain words, to the people who need them.
Alerts need no accountWhen something can take pages out of Google, an alert by email or Slack says what broke and on which pages. We check twice first, so a deploy still rolling out wakes nobody.
With Search Console connected, an alert also goes out when Google drops a key page from its index, can't fetch one, or picks another page as the main version. Those are sent as Google reported them, without our second check.
Everything else waits for the weekly digest, an email in plain words: what is new, what was fixed and what came back.
Add anyone to the site's alerts by email address or Slack channel. An address outside your team confirms once, and every email has a link to stop them.
What Google itself says.
Connect your Search Console, read-only, and every day we ask Google about your pages, key pages first. Its answer sits beside ours: whether the page is in Google, and if not, Google's own reason. If Google drops a key page, an alert goes out.
Every problem comes with proof.
Every problem says what's wrong, on which page and when, in plain words first, with the technical proof underneath: the tag, the header or the status code, quoted as your server sent it.
Rules decide, not AI: the same page always gets the same answer.
Problems Google reports quote Google's answer and the date we asked, and close when Google says so.
Anyone you invite to your team sees each fix verified in the dashboard.
- What we saw
- A robots meta tag in the page head
<meta name="robots" content="noindex">
- Where
- /products/linen-overshirt, on the template
/products/{slug} - When
- 14:05:12, and again at 14:07:12
- Fixed when
- The page answers with no noindex in its meta tags or its X-Robots-Tag header
What we don't do.
Rankings, keywords and backlinks
We say whether your pages can be found, never where they rank.
Changes in your Search Console
Our access is read-only, and we never ask Google to index a page for you. The dashboard links each page to Search Console, where you can request indexing yourself.
Plans
Both plans have every feature, for any number of team members, and differ only in size. Prices are in US dollars, before any VAT or sales tax.
-
Free
1 site
$0 no card every account starts here
- Site size we check
- 500 pages
- Monthly page allowance
- 5,000
- Whole-site check
- Weekly
- Key pages
- 10
- Checked after a deploy
- 20 deploys a month
- History kept
- 30 days
-
Pro
10 sites
$19 a month, or $190 a year, two months free
- Site size we check
- 10,000 pages
- Monthly page allowance
- 500,000
- Whole-site check
- Up to daily
- Key pages
- 100
- Checked after a deploy
- Every deploy
- History kept
- 12 months