Google Search Console Indexing Verdicts: The Fix Cheat Sheet
Search Console tells you exactly why Google will not index your page. It just says it in language that sounds like a status rather than an instruction. Here is every verdict, what it actually means, and the specific fix for each one.
Most people inspect a URL, read "URL is not on Google", and stop there. The genuinely useful part of the tool is two clicks deeper, and it will tell you what Googlebot saw, what failed to load, and which specific verdict applies to the page.
The Three Clicks to the Hidden View
Open Search Console and type any URL from your property into the inspection box at the top. Once the result loads, do not stop at the summary.
- Click Test Live URL on the right. This fetches the page as it exists right now rather than the version sitting in Google's index.
- Wait for the test to finish, usually around 30 seconds.
- Click View Tested Page. You get three tabs: HTML, Screenshot, and More Info.
The HTML tab shows the rendered source after JavaScript has run, which is the version Google actually evaluates. If your main content is missing here but visible in your browser, you have found your problem. The Screenshot tab shows how the page painted for the crawler. The More Info tab is the one almost nobody opens: HTTP response headers, every page resource that failed to load, and the JavaScript console errors Googlebot hit while rendering.
Separately, the main inspection result for the indexed version breaks down into Discovery, Crawl, and Indexing sections. The Indexing section is where you find the two canonical values that explain most confusing verdicts: the canonical you declared, and the canonical Google actually chose.
The Verdict Cheat Sheet
These are the verdicts you will see in the Page indexing report and in URL Inspection. Each one has a specific cause and a specific fix. Treating them all as one generic "indexing problem" is why they take hours instead of minutes.
| Verdict | What Google Means | Most Likely Cause | The Fix |
|---|---|---|---|
| Crawled, currently not indexed | Google fetched the page, read it, and decided it was not worth adding to the index. | Thin, templated, or near-duplicate content. Often a page that repeats what a stronger page on your own site already says. | Rewrite the page so it answers something no other page of yours answers. Merge it into the stronger page and redirect if it has no separate job. |
| Discovered, currently not indexed | Google knows the URL exists but has not spent a crawl on it yet. | Crawl budget, a slow server, or the page sitting too deep in your internal link structure. | Link to it from a page that already gets crawled often. Fix server response time. Do not just resubmit the sitemap and wait. |
| Duplicate, Google chose different canonical than user | You declared one canonical. Google overruled you and picked another URL. | The two pages are too similar for Google to treat as distinct, or your internal links point at the version Google picked. | Differentiate the content, or accept Google's choice and point your canonical there. Make sure internal links and the sitemap agree with whichever URL you want to win. |
| Duplicate without user-selected canonical | Google found duplicates and no canonical tag to guide it. | Missing canonical tags, usually on parameter URLs, filtered category pages, or print views. | Add a self-referencing canonical to the primary version and a canonical pointing to it on every variant. |
| Alternate page with proper canonical tag | Working as intended. This is not an error. | The page correctly canonicalises to another URL. | Nothing. Stop treating this row as a problem to solve. |
| Excluded by 'noindex' tag | A meta robots or X-Robots-Tag header is telling Google to stay out. | A staging tag that shipped to production, a CMS toggle, or a plugin default. | Remove the tag, then use Test Live URL to confirm it is gone before requesting indexing. |
| Blocked by robots.txt | Google was not allowed to crawl the URL at all. | An over-broad disallow rule. A single line can take out a whole directory. | Narrow the rule. Remember robots.txt blocks crawling, not indexing, so a blocked URL can still appear in results without a description. |
| Indexed, though blocked by robots.txt | The URL is in the index but Google cannot read it. | You blocked crawling on a page that other sites link to. | Unblock it in robots.txt and add a noindex tag if you genuinely want it out. Blocking alone cannot remove it. |
| Soft 404 | The page returns HTTP 200 but looks empty or like an error page to Google. | Empty search result pages, out of stock products, or a client-rendered page that shows nothing without JavaScript. | Return a real 404 or 410 if the page is genuinely gone. If it should exist, put real content on it server-side. |
| Page with redirect | The URL redirects, so the destination gets indexed instead. | Normal on any site that has ever changed a URL. | Nothing, unless the redirect is wrong. Check for chains longer than one hop. |
| Not found (404) | The URL returns a 404. | A deleted page, or a typo in a link or sitemap. | If it was deleted on purpose, remove it from your sitemap and internal links. If it had traffic or links, redirect it to the closest live equivalent. |
| Server error (5xx) | Your server failed while Google was crawling. | Timeouts under crawl load, a bad deploy, or aggressive rate limiting that catches Googlebot. | Check server logs for the exact timestamp Google reports. This is an infrastructure fix, not an SEO fix. |
| Redirect error | Google could not follow the redirect. | A redirect loop, a chain that is too long, or a redirect to an invalid URL. | Trace the chain with curl. Collapse it to a single hop to the final destination. |
| Blocked due to unauthorized request (401) / access forbidden (403) | Google hit an authentication or permission wall. | Password protection left on, or a firewall or bot rule blocking Googlebot's IP range. | Allowlist Googlebot and verify with Test Live URL, which crawls from Google's own infrastructure. |
| Page indexed without content | Google indexed the URL but could not extract readable content. | Content rendered entirely client-side, or cloaking-like behaviour where the crawler receives something different from users. | Check the rendered HTML in the inspection tool. If your text is missing there, server-render it. |
The Three Verdicts People Get Wrong Most Often
Crawled, currently not indexed. This is a quality verdict, not a technical one. Google read the page and passed. Requesting indexing again will not change its mind, because nothing about the page changed. The honest question is whether the page does a job no other page on your site already does. If it does not, merge it and redirect.
Discovered, currently not indexed. This one looks similar and is completely different. Google has not crawled the page yet. That is usually a crawl budget or internal linking problem, not a content problem. Link to the page from somewhere that gets crawled frequently, and check whether your server is slow enough that Google is throttling itself.
Alternate page with proper canonical tag. This is not an error. It appears under "Not indexed" and people panic and try to fix it. It means your canonicals are working. Leave it alone.
How to Verify a Fix Actually Worked
After you change something, run Test Live URL again. The live test should come back clean while the indexed version still shows the old verdict. That gap is the proof your fix deployed. Only then is it worth requesting indexing.
For a single URL, Request Indexing usually updates within a few days. There is no way to jump the queue, and clicking it repeatedly on the same URL does nothing. For a whole class of pages, use Validate Fix in the Page indexing report. Google re-crawls a sample over roughly a couple of weeks and either confirms the fix or fails the validation and tells you which URLs still break.
The Traps Worth Knowing
- The live test and the indexed version are different things. The default view can be weeks old. Comparing the two is the whole technique, not a footnote.
- You can only inspect URLs inside a property you own. There is no competitor inspection, whatever a tutorial tells you.
- The Page indexing report samples. The example URLs are a sample, not the full list, so fixing only the examples shown does not fix the issue.
- Blocking in robots.txt does not remove a page from the index. It only stops Google reading it. To remove a page, allow the crawl and serve a noindex tag.
- A 5xx or 403 verdict is usually not an SEO problem. It is a server or firewall problem, and the fix lives with whoever owns your infrastructure.
If you want the wider context, our SaaS SEO strategy guide covers where indexing sits in a full organic plan, and the SEO glossary defines the terms used above.
Frequently Asked Questions
Where is the hidden feature in Google Search Console's URL Inspection tool?
It is behind two extra clicks that most people never make. Inspect a URL, click Test Live URL on the right, wait for the test to finish, then click View Tested Page. That opens a panel with HTML, Screenshot, and More Info tabs. The More Info tab shows the HTTP response headers, every page resource that failed to load, and any JavaScript console errors Googlebot hit while rendering the page.
What does 'Crawled, currently not indexed' actually mean?
It means Google fetched the page, evaluated it, and chose not to index it. It is a quality judgment, not a technical error, which is why resubmitting the URL rarely changes anything. The usual cause is content that duplicates or barely adds to a page you already have. The fix is to give the page a job no other page on your site is already doing, or to merge it into the stronger page and redirect.
What is the difference between 'Discovered' and 'Crawled' not indexed?
Discovered means Google knows the URL exists but has not crawled it yet, which usually points to crawl budget, slow server responses, or the page being buried deep in your internal linking. Crawled means Google did fetch it and then decided against indexing, which points to content quality. Discovered is a crawling problem. Crawled is a content problem. They need completely different fixes.
How long does it take for a fix to show up in Search Console?
Requesting indexing on a single URL typically updates within a few days, though there is no guarantee and no way to jump the queue. Validate Fix on a whole issue in the Page indexing report runs over a couple of weeks as Google re-crawls a sample of the affected URLs. Neither is instant, and repeatedly requesting indexing on the same URL does not speed it up.
Does the live test show the same result as the indexed version?
No, and confusing the two is the most common mistake. The default view shows the version Google has in its index, which may be weeks old. Test Live URL fetches the page right now. After a fix, the live test should be clean while the indexed version still shows the old problem. That difference is how you confirm the fix landed before you request indexing.