Help Docs

Index Health Check

See how Google indexes your sitemap pages and fix gaps with Google Search Console.

The Index Health Check tab shows how well Google can find, read, and index the pages on your site. It's the fastest way to spot pages that aren't showing up in search results — and figure out why.

Why Sitemap Health Matters

Your sitemap is how you tell Google which pages on your site exist and matter. If your sitemap has errors, is out of date, or is missing pages, Google may not discover or index your content — which means those pages won't appear in search results at all.

Regularly checking sitemap health helps you:

  • Catch indexing gaps early — find pages that aren't showing up in search before they become a long-term blind spot.
  • Keep your sitemaps error-free — errors and warnings can slow down or prevent Google from processing your sitemap entirely.
  • Stay on top of freshness — a sitemap that hasn't been checked by Google in over a week could signal a crawling issue.

What You'll Need

Before you can use Index Health Check, make sure:

  1. Your website URL is set in Brand Core (Averi uses it to find your sitemap).
  2. Google Search Console is connected in Integrations.
  3. You've selected a Google Search Console property to track.

If any of these aren't in place yet, the tab will walk you through what's missing when you open it.

Where to Find It

In the left sidebar under Foundations, click Sitemap. The page opens on AI Discoverability by default — switch to the Index Health Check tab for Google indexing data.

At the top of the Index Health Check tab you'll see a banner showing which domain Averi is tracking. If you need to switch to a different Google Search Console property, click Change.

How to Check Indexing

Open the Index Health Check tab

Go to Sitemap in the sidebar, then select Index Health Check.

Run an indexing check

Click Check indexing to scan your sitemap URLs against Google's index. Averi queues your pages for inspection and processes them in the background — you don't need to stay on the page.

While the check runs, you'll see Processing on the button and a note that it's running in the background. Once it finishes, results update automatically.

Averi also runs indexing checks automatically in the background on a daily basis, so your data stays fresh even if you don't manually trigger a check.

Review your results

After the check completes, you'll see score cards at the top of the tab (see below).

If new pages are added to your sitemap after your first scan, you'll see an alert letting you know how many pages haven't been checked yet. Click Check indexing again to scan the new ones.

Understanding Your Results

Once a scan completes, you'll see summary cards at the top of the tab.

Overall Health Score

A score from 0 to 100 that combines three factors:

  • Indexing rate — the percentage of your pages that Google has indexed.
  • Freshness — how recently Google checked your sitemaps (within the last 7 days is ideal).
  • Errors and warnings — sitemap-level issues reported by Google Search Console.

The score falls into one of four labels:

  • Excellent (90–100) — everything looks great.
  • Good (70–89) — in solid shape with minor room for improvement.
  • Needs Improvement (50–69) — some issues worth addressing.
  • Poor Health (below 50) — significant issues that need attention.

Indexed Pages

Shows how many of your scanned pages are confirmed indexed by Google (e.g. 42 / 50), along with when the data was last refreshed.

Sitemaps Health

The percentage of your sitemaps that are free of errors. You'll see something like 2 of 3 healthy — meaning two of your three sitemaps have no issues reported by Google.

Sitemap Details

Below the score cards, the Sitemap Details section lists each sitemap individually. For every sitemap you'll see:

  • The sitemap URL — click to view it directly.
  • Discovered Pages — how many pages Google found in that sitemap.
  • Status badgeHealthy, an error or warning count, Pending (Google is still processing it), or Couldn't fetch (Google wasn't able to read it).
  • Submitted and Last checked dates.

If Averi detects sitemaps for both the www and non-www version of your domain, you'll see a warning: Multiple sitemaps detected for the same domain. Submitting sitemaps for only your canonical domain (the one version of your URL you want Google to use) avoids duplicate content issues.

Pages Not Indexed

If any of your pages aren't indexed, they'll appear in a Pages not indexed by Google Search Console list. Each row shows:

  • The page URL.
  • A status badge with Google's reason (e.g. "Discovered - currently not indexed" or "Crawled - currently not indexed").
  • A GSC button that opens that specific page in Google Search Console, where you can review the full status and request indexing.
  • A re-inspect button to re-check a single page. There's a 12-hour cooldown between re-inspections for each URL.

It can take several days for Google to process indexing requests and reflect changes, so don't worry if the status doesn't update right away.

What to Do with Your Results

  • Score is Excellent or Good — keep publishing consistently and check back periodically to make sure nothing slips.
  • Some pages aren't indexed — click GSC next to each URL to open it in Google Search Console and request indexing. Common reasons for pages not being indexed include thin content, duplicate content, or the page being too new for Google to have crawled it yet.
  • Sitemap errors or warnings — review the flagged sitemaps in the Sitemap Details section. The status badge tells you exactly what's wrong. You can also click through to Google Search Console to fix issues directly.
  • Duplicate sitemaps detected — submit sitemaps for only your canonical domain in Google Search Console and remove the duplicate.
  • "Couldn't fetch" on a sitemap — Google wasn't able to access that sitemap file. Make sure it's publicly accessible and that the URL is correct in Google Search Console.

Tips

  • Run a check after publishing new content. It gives you a baseline so you can catch indexing issues early rather than wondering weeks later why a page isn't getting traffic.
  • Focus on the "not indexed" list. Averi tells you why Google skipped a page — use the GSC button to dig into the details and request indexing directly from Google.
  • Don't re-inspect too often. Google needs hours to days to react after you request indexing. The 12-hour cooldown on re-inspects is there for a reason — checking sooner won't speed things up.
  • Make sure GSC stays connected. If your Google Search Console connection drops, Index Health Check will prompt you to reconnect in Integrations.

Need Help?

Reach out to us at [email protected] - you'll always get a human to talk through solutions with.