Choose a plan.
Start free, no card. Both plans have every feature, and Pro is bigger. Prices are in US dollars, before tax. Cancel Pro any time.
-
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
- Start one yourself
- Any time
- Key pages
- 10
- Checked after a deploy
- 20 deploys a month
- History kept
- 30 days
Every whole-site check counts toward the month, on the schedule or started by you, with the images and scripts it checks. So do the pages a check looks at, except your key pages, which never count.
Every feature, for any number of team members
Checks
- Every rule, on every check
- Key pages checked after a deploy and once a day
- One step your developer adds to the deploy, which says what it broke
- A record of what changed, deploy by deploy
- What Google reports about your pages, once you connect Search Console
Alerts
- Email, Slack, or a message to your other tools
- For anyone you invite, such as the marketing team
- Pages checked twice before an alert goes out
- An alert when Google drops a key page (with Search Console)
- A weekly digest
Fixes
- Fix instructions you can hand to an AI coding tool
- A connection it reads issues from directly (MCP)
Proof
- Proof on every issue
- Rechecks of only the pages a fix touched
- Each ends Verified, Partly verified or Still there
-
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
- Start one yourself
- Any time
- Key pages
- 100
- Checked after a deploy
- Every deploy
- History kept
- 12 months
Every whole-site check counts toward the month, on the schedule or started by you, with the images and scripts it checks. So do the pages a check looks at, except your key pages, which never count. Daily checks of every site at full size would pass it, so the month is the limit to plan by.
Every feature, for any number of team members
Checks
- Every rule, on every check
- Key pages checked after a deploy and once a day
- One step your developer adds to the deploy, which says what it broke
- A record of what changed, deploy by deploy
- What Google reports about your pages, once you connect Search Console
Alerts
- Email, Slack, or a message to your other tools
- For anyone you invite, such as the marketing team
- Pages checked twice before an alert goes out
- An alert when Google drops a key page (with Search Console)
- A weekly digest
Fixes
- Fix instructions you can hand to an AI coding tool
- A connection it reads issues from directly (MCP)
Proof
- Proof on every issue
- Rechecks of only the pages a fix touched
- Each ends Verified, Partly verified or Still there
Before monitoring starts
Show us the site is yours. If you're an owner or a full user of it in Google Search Console, connecting Search Console is enough. If not, ask your developer for a DNS record, a meta tag or a file. Until then the site gets one quick check a day, of up to 50 pages, with no schedule, no checks of its key pages (after a deploy or daily), no alerts, no digest and no rechecks.
What the numbers mean
- Sites
- How many sites the plan watches. A site covers its www and non-www addresses together, and counts from the moment you add it.
- Site size we check
- The most pages we check in one go through a verified site. A larger site is checked up to that many pages.
- Monthly page allowance
- How many pages we may check for your team in a calendar month, across all its sites. Checks of your key pages, daily or after a deploy, never count. Spend it however you like: there is no daily limit.
- Whole-site check
- How often we check the whole site on a schedule, up to the site size. A verified site is checked every week until you choose another schedule in its settings, up to this often.
- Start one yourself
- Start a whole-site check of a verified site whenever you like, from the dashboard or from an AI coding tool.
- Key pages
- The pages that must never drop out of Google, such as pricing, a product page or checkout. You name them, and your homepage always counts on top. We check them every day and after a deploy, and list their issues first.
- Checked after a deploy
- Your developer adds one step to your deploy, and it says what the deploy broke, if anything. Free checks 20 deploys a month. Pro checks every deploy.
- History kept
- How long issues, check results and the record of what changed are kept, so a check can be compared with the ones before it.
Included in both plans
- Alerts
- When something can take pages out of Google, an alert goes out by email, Slack or a message to your other tools, to anyone you add, such as your marketing team. Everything else waits for the weekly digest, an email that says what is new, what was fixed and what came back.
- Search Console
- Connect a Google account that has the site in Search Console, and we show Google's own answer about your pages beside ours. The access is read-only, and we never ask Google to index anything for you.
How each one works, in detail
- Site size we check
- We go through the site the way Google does, following its links and its sitemap, the list of pages a site gives Google. This is called a crawl. When a site is larger than the plan's size, the crawl records that it stopped at the limit rather than reaching the end of the site.
- Monthly page allowance
- Every crawl draws on it, in each calendar month (UTC): the crawls on a schedule, the ones you start, rechecks, and the pages a check looks at, except your key pages, which never count. A full crawl also counts the images, scripts and stylesheets it checks, up to 500 a crawl, and a few test requests, such as a made-up address to see how the site answers for a missing page. When it runs out, full crawls pause until the next month starts, and checks go on with your key pages only.
- Start one yourself
- An AI coding tool starts one over MCP. One runs at a time for each site.
- Key pages
- Once a day, and 30 seconds after a deploy, we fetch them along with robots.txt and your sitemaps, and tell you if one can no longer appear in Google. A noindex on one of them is a critical issue. A site that moves to a smaller plan keeps its list, and the first as many as the plan allows are checked.
- Checked after a deploy
- The dashboard gives you a job for your deploy pipeline on GitHub Actions, or a script for any other. It calls our deploy webhook, and 30 seconds later we check your key pages, a few pages of your biggest page types, such as product pages or articles, and pages new in your sitemap since the last full crawl: up to 10 of each on Free and 100 of each on Pro. Deploys close together share one check, of the newest. The job waits up to five minutes for the answer and prints what the check found. It fails only when the deploy brought a new critical problem or error. Nothing on our side ever fails it: if we cannot be reached, or the check did not run, it says so and passes. Once a month's deploy checks are used, a deploy is still accepted, the daily check still runs, and fixes waiting for an answer are still rechecked.
- History kept
- Every detail of a page, such as its full HTML and headers, is kept for each site's last two full crawls and the checks since.
- Alerts
- A site sends its alerts to up to 10 places you add in its settings: email addresses, Slack channels or webhooks. A team member's address works at once. Any other gets one email asking it to confirm, and nothing goes there until it does. An alert goes out for a new critical issue, an error on one of your key pages, or an error on many pages of one page type at once, and only after we fetch those pages again. With Search Console connected, one also goes out when Google's answer about a key page changes: Google drops it from its index, can't fetch it, or picks another page as the main version. Our fetch can't see what Google saw, so that one is sent as Google reported it. Both start once the site is verified, and every one sent by email has a link that stops them.
- Search Console
- We ask Google for its report on a page (URL Inspection), up to 1,500 a day for each site, key pages first, and show its answer with the date we asked. In the dashboard, each page links to Search Console, where its own "Request indexing" is. An owner's or full user's access also proves the site is yours.
Not sure yet? Start with your own site.
A free account, no card: one site with every feature. We run a first check once you confirm your email address. Monitoring starts once you show the site is yours.