Almost always, nothing is broken. Getting into Google takes time, and most of what Search
Console reports is normal indexing lag rather than an error on your site.
Google decides what to index and when. No platform can force it, and a brand new site or a
freshly published page routinely waits days to a few weeks. This page explains
what those Search Console statuses actually mean, and which few are worth writing to us about.
What happens after you publish
There are four stages between you making a change and that page appearing in search results. Only the first one is fast, and only the first one is ours.
From publish to search result
four stages, and only the first one is ours
Halo
Publish
Your change goes live and your sitemap updates itself
seconds
Google
Discover
Google reads your sitemap and queues the URL
days
Google
Crawl
Google actually visits the page
days to weeks
Google
Index
Google decides whether to store and show it
its own call
Stages 2 through 4 are entirely Google's.
Nobody can buy, request, or engineer their way past them. Anyone who tells you a page can be guaranteed into the index on a schedule is selling something. What you can do is make sure nothing is blocking the crawl, which is covered below, and then give it time.
Reading the Page indexing report
This is the screen most questions come from. It lists every URL Google knows about on your site and sorts them into buckets. A long list of "not indexed" pages looks alarming and usually is not.
🔒 search.google.com/search-console
Google Search Consoleyourdomain.com
Overview
Performance
URL inspection
Indexing
Pages
Sitemaps
Removals
Pages
Not indexed94
Indexed31
3 months ago2 months agolast monthtoday
Why pages aren’t indexed
ReasonPages
Crawled — currently not indexed42
Discovered — currently not indexed28
Excluded by ‘noindex’ tag14
Duplicate, Google chose a different canonical6
Not found (404)4
Open Indexing in the left menu and choose Pages. Every row under Why pages aren't indexed is a status rather than a fault, and the chart usually matters more than the totals, because a green line climbing over time is the healthy shape. The numbers here are an example, not your site.
What each status actually means
StatusWhat it meansAction
Discovered — currently not indexed
Google found the URL in your sitemap but has not visited it yet. It is in line.
Wait
Crawled — currently not indexed
Google visited the page and has not decided to index it yet. Extremely common on newer sites and on large batches of similar pages. It often flips to indexed on its own.
Wait
Excluded by ‘noindex’ tag
Usually stale. Search Console keeps reporting URLs long after they change or disappear, so this count frequently refers to pages that no longer carry the tag, or no longer exist.
Check
Duplicate, Google chose a different canonical
Two addresses show the same content and Google picked the other one. Normal for a while after moving to a custom domain, when Google still prefers your original .huzi.site address.
Wait
Not found (404)
Old URLs that no longer exist. Expected after you rename, merge, or delete pages. Google drops them over time.
Wait
Blocked by robots.txt
Something is telling crawlers to stay out. Your site ships allowing every major crawler, so a real block here is worth a look.
Check
Blocked due to access forbidden (403)
Google was actively refused. This one is not normal lag.
Write in
Server error (5xx)
The page failed to load for Google. Also not normal lag.
Write in
The count is often larger than your whole site
This trips up nearly everyone. Search Console reports on every URL it has ever seen at your domain, including ones you deleted, renamed, or never published. It is completely normal for the total in that report to exceed the number of pages your site actually has.
One member came to us because Search Console showed 38 pages excluded by a noindex tag and 82 crawled but not indexed. We checked the live site directly and found no noindex tag on a single page, no blocking header, and every page loading normally. Their entire sitemap contained 56 URLs, while Search Console was reporting on 120. Most of what it listed no longer existed.
A quick sanity check you can do yourself.
Search Google for site:yourdomain.com. That shows what is genuinely in the index right now, which is often a very different picture from the report.
What your site already does correctly
Before assuming something is misconfigured, it is worth knowing what ships turned on. Every Halo site generates and maintains these for you, and they update themselves as your site changes.
Your sitemap lives at yourdomain.com/sitemap-index.xml, and your robots.txt points search engines to it while explicitly welcoming the AI crawlers too.
# yourdomain.com/robots.txtUser-agent: *
Allow: /
# AI answer engines, named explicitlyUser-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: ClaudeBot
User-agent: PerplexityBot
User-agent: Google-Extended
# ...and others, all allowedSitemap: https://yourdomain.com/sitemap-index.xml
Nothing on our side blocks search engines or AI crawlers by default. When a member asked us to prove it, we sent live requests to their site using the real crawler identities for GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Googlebot, CCBot, and Meta-ExternalAgent. Every one came back with the full page.
Google is not the only index that matters now
ChatGPT Search and Microsoft Copilot both answer from Bing's index rather than Google's. That means a page can be missing from Google and still be found and cited by an AI assistant, and the reverse is also true. If you are watching only Google, you are watching a part of the picture.
When it is worth writing to us
Most of the report is Google being Google. These few are not, and we would rather look at them:
Pages returning 403 or 5xx to Google, particularly more than a handful.
Pages you can see are live and correct, still absent after several weeks, with nothing else in the report explaining it.
Anything Blocked by robots.txt, since your site should not be blocking crawlers.
A page in the index showing content you removed a long time ago.
Send the site address and a screenshot of the report, or just the status name and the count. We can check what your site is actually serving to Google, which is the fastest way to separate a real fault from normal lag.