Site Health: an automated SEO audit that counts what you fix

How the audit works

Site Health starts from your sitemap, the list of pages your site asks search engines to read, and measures everything against the first audit that has read all the pages it keeps from it. Four steps run without you:

1. 1

   Your sitemap, every night

   BlogAmplify reads the sitemap you saved, or finds the one your site serves when you leave the field empty, then reads each page it lists, up to 500 addresses with your blog posts first: title, description, headings, links, images, structured data and the answer your server gives. Each page is read again every 30 days, and a page that answered with a server error or a rate limit is read again the next night.
2. 2

   The site as a whole

   Each audit also reads robots.txt, tries the http:// address and the other www form of your domain, and checks links between your pages that point outside the sitemap, up to 100 a run, reusing each answer for 14 days.
3. 3

   The audit, weekly

   The checks run nightly until every page has been read once, then every 7 days. A problem a check finds opens an issue, one it no longer finds is marked fixed with the date, and a fixed one that comes back opens again, marked as having come back.
4. 4

   Rules in code

   No AI reads your pages to judge them: the checks are rules in code, so the same page gets the same answer every time. Only the title and description suggestions are written with AI, and only when you ask for one.

What it checks

The audit runs 35 checks in six groups. Each one comes with why it matters and fix steps for Shopify, WordPress or other platforms, and a severity: errors are the most serious (pages kept out of Google, dead links, missing titles), warnings cost clicks or blur what Google shows, and notices are smaller improvements.

The local checks run only while local search applies to your business; see local search for who it applies to and what else it tracks.

The health score and your starting point

The health score runs from 0 to 100 and is counted by kind of problem, not page by page, so one broken link on the homepage isn't hidden by hundreds of clean pages. Each kind of problem with open issues costs 12 points for an error, 5 for a warning and 1.5 for a notice. On a few pages it costs part of that, rising to the full amount once it reaches 5% of the pages checked (or 5 pages on a small site). A problem with the whole site, such as robots.txt, costs the full amount. Issues you set aside and the check for pages Google hasn't indexed don't count, since Google's own backlog would move the score without anything changing on your site.

Your starting point is the first audit that has read every page Site Health keeps from your sitemap (until there is one, the first audit). Site Health shows the score now and how far it moved since then, the errors, warnings and notices open now, a small line of the daily score over the last 90 days, and how many problems were fixed since the start. A problem counts as fixed when a later audit or Validate fix finds it gone. Pages that leave your sitemap and pages read for the first time never pass for fixes, so the number only grows when something on your site improved.

Fixing what it finds

Each problem opens with why it matters, the steps for your platform and the pages it affects, with what was found on each (for example the address a redirect leads to). From there:

• Suggest a title or Suggest a description writes that one field from the page's own text: about 40 to 60 characters for a title, 120 to 150 for a description, different from your other pages. Every number in it is checked against the page, and one the page doesn't give is never offered. You copy it into your CMS. Up to 60 suggestions a day per website.
• Validate fix reads that check's open pages again (up to 50), audits them and tells you how many are fixed and how many still fail. For broken links it also reads the broken addresses again. One runs at a time, up to 30 a day, counting full re-checks and Fix it for me.
• Check again now reads your sitemap again, re-reads the pages with open issues (up to 100) and runs the whole audit, once every 6 hours.
• Set aside is for a problem you have decided to keep, such as a page you want out of Google on purpose. It leaves the score, stays set aside, and you can bring it back.

Fix it for me: links in our articles

Most fixes live in your theme or CMS, and those stay yours. The exception is an article BlogAmplify published for you on Shopify, WordPress or a webhook site: when one of its links is broken or goes through a redirect, the issue offers Fix it for me. When you press it:

1. The flagged addresses are read again first (up to 12), and only links still broken or still redirecting change. A page restored since the audit keeps its link.
2. A broken link is unwrapped: its words stay, as plain text. A redirecting link is pointed straight at where it ends.
3. Everything else in the article stays character for character. On Shopify and WordPress the article is edited as it is live, so edits you made there are kept. On a webhook site our copy is edited and sent as an in-place update, and only when it holds no changes you haven't published.
4. The page is checked again 30 seconds later (10 minutes on a webhook site, which may need to rebuild), so the issue closes on its own.

Articles published before BlogAmplify kept their id in your CMS are matched again by their address each night (by handle on Shopify, by slug on WordPress), so they can be fixed in place too. Articles on Notion can't be changed in place. Smaller edits that keep articles current are automatic article updates.

Google index status

With Google Search Console connected, Site Health asks Google's URL Inspection about up to 25 pages each night, one at a time, in this order: the articles we published, pages never asked about, pages not indexed (asked again after 3 days, or every night for our own articles), then indexed pages (after 30 days). Google allows 2,000 inspections a day per site (Search Console API usage limits), so this uses a small share of it.

• The index card shows how many of the pages asked about Google has indexed and, for our articles, how many are on your site, how many Google has answered for and how many are indexed.
• Pages Google hasn't indexed become a check with Google's reason and the date it last crawled each page, once the page has been in your sitemap 14 days. It is listed but left out of the score.
• Request indexing is yours to press in Search Console; BlogAmplify can't press it for you, and the fix steps say where it is. After an update adds to or rewrites one of our articles, the next night's check asks Google about that article again.
• Our articles on your site: each article we publish is read at its own address a few minutes after it goes live and again on later nights, so one deleted or moved in your CMS is noticed and left out of rankings and traffic alerts.

Rankings for our articles

Each week, after the first Search Console sync of the week, Site Health records where each article we published ranks for its main search: its average position for that search on that page over the 28 days ending 3 days ago. The table shows the latest week with 26 weeks of history, the change since Google first showed the article, its best position and its clicks, and how many articles sit in the top 3 and top 10 and how many moved up since they were first seen. Articles published to Notion or to another website aren't tracked.

Articles losing traffic

Search Console's weekly clicks and impressions for each article we published are stored (the first read goes back up to 16 months). Once an article has been live 12 weeks, its last 4 full weeks are compared with its usual level before. It is flagged when the drop is larger than normal week-to-week swings and:

• clicks fell by at least 40%, from at least 20, losing at least 10;
• for an article with few clicks, impressions fell by at least 40%, from at least 500;
• or its main search ranks at least 5 places worse in each of the last 3 weekly readings than it used to.

An article isn't flagged when the rest of your site fell about as much, since then the drop isn't the article's alone. Up to 10 flagged articles are shown, worst first, each with plain sentences and its numbers, and two buttons: Update this article, which starts an article update, and Not now, which hides it for 90 days. When the data is too new or too far behind to judge, the section says so instead of showing an all-clear.

Domain Rating by Ahrefs against competitors

About once every 7 days, Site Health records your website's Domain Rating by Ahrefs and that of up to 5 competitors from your business profile. Ahrefs describes it as showing "the strength of a website's backlink profile compared to the others in our database", on a 100-point scale (Ahrefs Help Center).

Your first reading is your starting point, so you see where you began, where you are now and where you stand next to the competitors in your business profile. A new domain starts a new starting point. Domain Rating is display only: the audit and the health score never use it.

What Site Health doesn't do

• ×Never: Change pages BlogAmplify didn't write. Your theme, products and pages are yours to fix, with steps for your platform; it changes only articles it published for you, through Fix it for me and article updates.
• ×Never: Request indexing in Google for you. The fix steps show where to press it in Search Console.
• ×Never: Measure loading speed or Core Web Vitals, or audit the links other websites give you.
• ×Never: Run JavaScript. It reads the HTML your server sends, so text or links a page adds with scripts after loading aren't checked.
• ×Never: Check links to other websites, or audit pages outside your sitemap. Broken-link checks cover links between your own pages.
• ×Never: Promise rankings. It shows what is wrong, what you fixed and what changed in Google.

Plans

Site Health is part of every plan, and each website gets its own. The audit, the score and the competitor comparison work without Search Console; index status, rankings and Articles losing traffic need it.

Growth, $99/mo

Site Health for one website

Growth + AI Visibility, $199/mo

The same Site Health, plus AI visibility tracking

Extra website, $75/mo

Its own Site Health, next to a main plan

Extra website + AI Visibility, $150/mo

Its own Site Health, with AI visibility

Both main plans start with a 3-day trial; a card is required. Prices are per website, per month, before local tax; see pricing. Site Health is also part of the wider picture in what SEO automation can and can't do.

For a single check without an account, the free robots.txt tester, SERP snippet preview and schema markup generator run in your browser. All of them are on the free tools page.