You opened Google Search Console, or an email from it landed in your inbox, and there it is: a red number of pages marked "not indexed." Underneath sit reasons that read like error codes, such as "Crawled, currently not indexed," "Page with redirect" and "Server error (5xx)." It can look as if your website is broken and customers cannot find you. A page not indexed report is often far less alarming than it looks, because a lot of those rows are URLs Google is supposed to leave out. A few of them, though, can point at a real problem on a page that brings in calls and leads. The trick is telling the two apart, and you can do most of that yourself in a few minutes. By the end of this post you will know which rows to leave alone, which ones to fix first, and what Google will and will not do after you fix them.
Key Takeaways
Google's own help page says "Not indexed is not necessarily bad," and it tells you not to expect every URL on your site to be indexed.
Redirects, correct canonical alternates, duplicates where Google picked the right page, noindex pages you meant, and 404s for pages you removed are normal.
Server errors, redirect errors, an accidental noindex or robots.txt block, a soft 404 on a real page, and a 404 where the page should exist are worth fixing.
Validate fix typically takes up to about two weeks, and neither it nor Request indexing guarantees Google will index the page.
What does "page not indexed" mean in Google Search Console?
In Google Search Console, "page not indexed" means Google knows about a URL but has not put that URL in its search index. Some reasons are expected, such as redirects, duplicates and pages you told Google to skip. Others, such as server errors or an accidental block on an important page, need fixing. Check the reason and the affected URLs before you assume you are losing traffic.
It helps to know what "indexed" means. Google finds a URL, crawls it (its crawler, Googlebot, fetches the page), processes what it finds, and then decides whether to add the page to its index. A page in the index is eligible to appear in search results. It is not promised a spot, and it is not promised a ranking. Google's URL Inspection tool documentation says the same thing about an inspected URL that is on Google: it can appear, not that it will.
The report itself lives under Indexing, then Pages. The "Why pages aren't indexed" table lists every URL Google knows about that is not in the index, grouped by reason. That list includes old addresses, redirect sources, duplicate versions of the same page and anything else Google has run into. So, a big number does not mean a big problem. Google's Page indexing report help page says it plainly: "Don't expect every URL on your site to be indexed." The goal it sets is to get the canonical version of each important page indexed, meaning the one main version of each page you want people to find.
Which "not indexed" reasons can you usually leave alone?
A good share of the rows in a typical report describe URLs that should not be in Google's index at all. They are there because Google found them and is telling you what it decided. Each meaning below comes from Google's Page indexing report help page, with a plain verdict for what it means to you. The one question to ask of every example URL is simple: is this a page I want customers to land on from Google?
Page with redirect
Google's meaning: the URL is not the main version of the page, and it redirects to another page, so it is not indexed. This is what a working redirect looks like from Google's side. If you moved a page and the old address forwards to the new one, the old address belongs here. Check that the page it redirects to is the right one and is indexed, then leave the row alone.
Alternate page with proper canonical tag
Google's meaning: the page is an alternate of another page, and it correctly points to the version Google indexed. A canonical tag is a small line in a page's code that says "this is the main version." When Google follows it, the alternate stays out of the index and the main page stays in. Google describes this as a good result, and there is nothing to fix.
Duplicate without user-selected canonical
Google's meaning: Google thinks the page is a duplicate of another, the page did not say which version is the main one, and Google chose a different page as the canonical. This is often harmless, for example when the same page is reachable with and without a tracking code on the end of the address. Use URL Inspection to see which page Google picked. If Google picked the page you want, you can leave it. If it picked the wrong one, that moves into the "fix" group below. Google's guide to what canonicalization is explains how it chooses one page among near copies.
URL marked "noindex" or blocked by robots.txt, when you meant it
The noindex label (older reports called it "Excluded by noindex tag") means Google found a noindex instruction on the page and did not index it. The robots.txt label means your site's robots.txt file blocked Google from crawling the page. If these are pages you meant to keep out, such as a thank-you page after a form, a login page or a test page, the report is showing your own instructions working.
Not found (404), for pages you removed
Google's meaning: the URL returned a 404 error when Google requested it. A 404 is the standard "this page does not exist" response. If you deleted a page on purpose and there is no close replacement, a 404 is the correct answer. A removed page does not need to be forced back into the index.
Which Google Search Console errors can cost you customers?
The same labels become a real problem when the example URLs include a page you need customers to reach: your home page, a core service page, a product, a location or your contact page. One of these rows is not proof of lost traffic by itself, but it is worth fixing because it can keep Google, and sometimes visitors, from reaching that page. The reasons below are the ones to look at first. The table after them sums up every common reason in one place.
Google Search Console error 5xx: server errors
Google's meaning: your server returned a 500-level error when the page was requested. That means the site failed to answer, whether because of a host outage, a broken update, a firewall rule or a resource limit. One short blip can clear on its own. A repeated pattern on important pages needs fixing at the host or in the site's code, because a visitor who arrives at that moment may see an error too. If the pattern keeps coming back, it can be a web hosting problem more than a search problem.
Page not indexed redirect error
Google's meaning: Google ran into a redirect loop, a redirect chain that was too long, a final address that was too long, or a bad or empty redirect address. In everyday terms, the forwarding went in circles or never arrived. The fix is one permanent redirect that goes straight from the old address to the correct final page. This often shows up after a redesign or a platform change, when old addresses were forwarded in several hops.
An accidental noindex or robots.txt block
The same noindex and robots.txt labels from the "leave it" group are a problem when they sit on a page you want found. A noindex setting left over from a test version of the site, or a checkbox in a site builder that hides pages from search engines, can keep an entire service page out of Google. Remove the instruction, then test the live page. Note one difference Google points out in its guide to blocking indexing with noindex: robots.txt blocks crawling, but Google may still index a blocked address if other pages link to it, so noindex is the tool for keeping a page out of results.
Page cannot be indexed: soft 404
Google's meaning: the page shows a friendly "not found" style message but does not send an actual 404 response. Google is saying the page looks empty or like an error, even though the server says it is fine. If the page really is gone, make it return a real 404 (or 410). If it is a real page you want found, it needs enough real content to be worth indexing, since an empty template or a page that only says "coming soon" can land here.
Google Search Console error 404 on a page that should exist
A 404 is only a problem when the page is supposed to be there, or when an old page moved and a close replacement exists. In that case, either restore the page or redirect the old address to its successor. If you changed platforms, for example after a website builder shut down or changed its plan, old addresses without redirects are a common place for these to pile up.
Duplicate, Google chose different canonical than user
Google's meaning: your page said which version is the main one, and Google picked a different page anyway. When this touches an important page, check that your canonical tags, internal links and sitemap all point to the same version. Mixed signals, where a template or plugin creates several versions of one page, are the usual thing to clean up.
Google's report also lists a few access reasons: "Blocked due to unauthorized request (401)," "Blocked due to access forbidden (403)" and "URL blocked due to other 4xx issue." These mean Googlebot was asked for a login, refused, or given another client error. They matter only when they hit a public page, often because a security setting is turning Googlebot away.
| Reason in the report | What Google says it means | Usually | What to do |
|---|---|---|---|
| Page with redirect | The URL redirects to another page | Normal | Check the destination is right and indexed |
| Alternate page with proper canonical tag | Correctly points to the indexed main version | Normal | Nothing |
| Duplicate without user-selected canonical | A duplicate with no main version declared; Google chose one | Often normal | Confirm Google picked the right page |
| URL marked "noindex" | Google found a noindex instruction | Normal if intended | Remove it only from pages you want found |
| URL blocked by robots.txt | robots.txt blocked crawling | Normal if intended | Unblock pages you want found |
| Not found (404) | The URL returned a 404 | Normal for removed pages | Restore or redirect if a page should exist |
| Soft 404 | Looks like a "not found" page without a 404 response | Problem on a real page | Add real content or return a true 404 |
| Server error (5xx) | The server returned a 500-level error | Problem if repeated | Fix at the host or in the site's code |
| Redirect error | Loop, long chain, overlong or empty redirect | Problem | One direct permanent redirect |
| Crawled, currently not indexed | Crawled but not indexed; may be indexed later | Depends on the page | Check important pages; no need to resubmit |
| Discovered, currently not indexed | Found but not crawled yet | Depends on the page | Wait; check important pages |
Is "Crawled, currently not indexed" bad?
Not by itself. Google's meaning for "Crawled, currently not indexed" is that the page was crawled but not indexed, and it may or may not be indexed in the future. Google also says there is no need to resubmit the URL. The label does not mean a penalty, and Google does not publish a single cause or a guaranteed fix for it.
"Discovered, currently not indexed" is one step earlier. Google found the URL but has not crawled it yet. Google says it typically put the crawl off because crawling at that moment might have overloaded the site, so the last crawl date is often blank.
Both labels matter only when the sample URLs include pages you need found, and those pages stay out over time. If that happens, look at the page with a customer's eye. Is it clearly different from your other pages, and does it answer something a visitor would search for? Improve it only if it genuinely deserves a place, make sure other pages on your site link to it, then give Google time to come back.
One thing you can set aside for a normal small business site is "crawl budget." Google's crawl budget guide is written for very large sites that change often. For a site without a large number of fast-changing pages, Google says keeping your sitemap up to date and checking the Page indexing report is enough.
How do you check your own report in fifteen minutes?
You do not need to clear every row. You need to find out whether any important page is caught up in a real problem. This short pass, all inside Search Console, answers that.
- Open Indexing, then Pages: Write down each reason in the "Why pages aren't indexed" table and its count.
- Start with the big or rising rows: Open the reasons with the largest count or a sudden jump.
- Read the example URLs: Flag any page you want customers to find, such as your home page, service pages, products, locations and contact page.
- Inspect one flagged page: Paste it into URL Inspection and note the status, the last crawl, whether crawling and indexing are allowed, the canonical you declared and the one Google selected.
- Test the live page if something changed: Use Test live URL when you have just fixed something or suspect an access problem, since the report can reflect an older crawl.
- Sort each flagged URL: Meant to be excluded, removed with no replacement, moved to a new page, or an important page that should be available. Only the last group, plus any repeated technical failure, goes on your fix list.
If nothing on your fix list is a page that matters, you are done. The red number can stay red. If something does matter, you now know exactly which page, which reason and what Google saw, which makes the fix, or the conversation with whoever builds your site, much shorter. A fix can be small, such as unticking a hide-from-search setting or correcting one redirect. It can also be larger, such as a canonical rule a template repeats across hundreds of pages or a string of server errors. The report alone cannot tell you the size of the job; the inspected URL and the pattern behind it can.
Does Validate fix make Google index the page?
No. Validate fix is how you tell Google you have fixed a reported issue. After you fix every instance of one reason, open that reason's detail page and choose Validate fix. Google checks some examples right away, queues checks for the rest, stops if it finds an instance still broken, and emails you the result. According to Google's validation details help page, validation "typically takes up to about two weeks, but in some cases can take much longer."
A passed validation means Google no longer finds that issue on the URLs it knows about. It does not mean the pages will be indexed, rank or bring in more calls. Google also updates the counts during normal crawling, whether or not you validate.
Request indexing, in URL Inspection, is the other button people reach for. It is reasonable for a single important page you just published or fixed. It puts the page in a queue, and Google says it does not guarantee the page will be included. For many changed pages at once, submitting an up-to-date sitemap is the better route. There is no need to press either button over and over, and for "Crawled, currently not indexed" Google says there is no need to resubmit at all.
When is it worth paying someone to fix it?
Often, it is not. If your example URLs are redirects, deliberate noindex pages, correct canonical alternates, duplicate variants or deleted pages returning a proper 404, the report is not evidence that anything is broken, and you do not need to buy a fix. Be wary of any offer to "get every page indexed," because Google itself does not expect that, and nobody can promise Google will index or rank a page.
Help is worth paying for when the fifteen-minute check turns up something real on pages that matter: repeated server errors, redirect loops after a redesign, service pages hidden by an accidental noindex, soft 404s on real pages, or Google choosing the wrong version across a whole group of pages. Those take technical diagnosis, a fix at the source, a live test and follow-up in Search Console. Ongoing website maintenance can also catch server errors and broken redirects before they pile up in the report.
Can you read your Page indexing report?
Pick an answer to begin.
1. Your report shows 40 URLs under "Page with redirect." What should you usually do?
2. What does passing Validate fix confirm?
3. Your main service page is listed under "URL marked 'noindex'." What is the most likely next step?
Frequently Asked Questions About page not indexed
What does page not indexed mean?
It means Google knows about the URL but has not added it to its search index. Some reasons are expected, like redirects, duplicates and pages you chose to hide. Others, like server errors on important pages, need fixing.
Do I need to fix every page not indexed by Google?
No. Google says not indexed is not necessarily bad and that you should not expect every URL to be indexed. Focus on the main version of each important page.
Is Crawled, currently not indexed bad?
Not by itself. Google crawled the page and did not index it, and that may change later. Google says there is no need to resubmit it. Look closer only if important pages stay out.
Is Page with redirect an error?
Usually not. The address redirects, so it is not indexed. Check that the page it forwards to is the right one and is indexed.
How long does Validate fix take?
Google says validation typically takes up to about two weeks, and sometimes much longer. A pass confirms the issue is gone, not that the pages will be indexed or rank.
Does Request indexing guarantee Google will index my page?
No. It puts the page in a queue for Google to look at. Google decides whether the page goes into its index.
What This Means for You
A red "not indexed" number in Search Console is a list of URLs and Google's reason for each, not a score for your website. Many of those rows, such as redirects, correct canonical alternates, deliberate noindex pages and removed pages returning a 404, are Google doing what it should. The rows worth your time are the ones that touch pages customers need to reach, especially server errors, redirect errors, accidental blocks and soft 404s. Fixing them removes a barrier, and Google still decides what goes into its index.
Once you know which rows matter, the report stops being a source of worry and becomes a quick monthly check. You fix real problems on the pages that bring in business, leave the rest alone, and stop spending time on URLs that were never meant to be found.
If your check turns up something you would rather hand off, Web Leveling can look at your report with you, confirm which rows affect important pages, and fix the causes we can verify. Our search engine optimization work includes this kind of indexing review, followed by a live test and a Search Console check. If your report shows nothing that needs paying for, we will tell you that too. We work with small and medium businesses across the country and overseas. Send us what your Page indexing report shows, and we will help you sort it.
Terms
Search Console indexing words in this post
Tap a term to see what it means.
Index. Google's store of pages that are eligible to appear in search results.
Crawl. When Googlebot, Google's crawler, fetches a page to read it.
Canonical. The main version of a page when several addresses show the same or similar content.
Redirect. An instruction that sends visitors and Google from one address to another.
Noindex. An instruction on a page that tells Google not to include it in search results.
Robots.txt. A file on your site that tells crawlers which addresses they may not crawl.
Soft 404. A page that looks like "not found" to Google but does not send a real 404 response.
