How to Fix “Not Indexed” Pages in Google Search Console

You log into Google Search Console and in the Indexing report, you find a list of URLs under “Not indexed” – pages Google found but didn’t add to its search index. One of the most annoying situations in SEO is when the content is there, Google knows it’s there, but searchers can’t find it.

The good news is that most “Not Indexed” issues are fixable. The bad news is there are dozens of potential reasons a page might not be indexed, and each needs its own cure. Whether you’re a site owner, developer or SEO pro facing this for the first time or the tenth time, this session takes you thru every key “Not Indexed” state in Google Search Console, what it really means and what you can do about it.

Importance of Indexing for SEO

If a page is unindexed, Google acts as if it doesn’t exist. It can’t rank for keywords. It can’t produce organic traffic. It can’t establish topical authority for your site. If firms are dependent on search engine optimization for leads and profits, they are costing themselves money directly with unindexed pages.

The first approach to remedy this is to understanding how Google indexes. Googlebot will visit your site, find URLs, fetch the information at those URLs, and then determine if it wants to include that URL in the index or not. Any of these steps can be a point of rejection – and Google Search Console’s Page Indexing report will tell you exactly where each URL was rejected, and why.

How to View Pages Not Indexed in Google Search Console

Navigate to:

Google Search Console > Indexing > Pages

The report contains two tabs, “All page statuses” and “Why pages aren’t indexed.” The second item gives you all the reasons Google has detected for your pages not being indexed, and how many URLs are affected by each cause. Click on a cause to see the affected URLs.

The bottom line from this report: Google-selected canonical means Google believes another URL is the “primary” version of a page. Crawled – presently not indexed means that Google crawled but didn’t index. These demand quite different therapies.

Common “Not Indexed” Statuses & How to Fix Them

1. Crawled – Currently not indexed

Basically, Google has crawled the page, seen the content and opted to not index it. This is not a technology block, it’s a discretionary assessment. Google crawled the info but decided it’s not worth indexing.

Common reasons include:

• Low value or shallow material which adds little value to what is already in the index
• Duplicate information that is remarkably identical to other pages on your website or anywhere on the web
• Google deems the following to be low quality: gateway pages, auto-generated material, and pages that are built on a template with little original content
• Very fresh webpages that Google has not indexed yet (sorts itself out sometimes)
• Pages with weak E-E-A-T (experience, expertise, authoritativeness, trustworthiness)

How to fix it: The main concern here is whether the page should be indexed at all. Not every page has to be indexed by Google. As a rule of thumb, pagination pages, filtered e-commerce views, and thin utility pages are not worth indexing. If the page needs to rank, then the fix is to raise the quality of the material.

• Expand article: Add original research, expert perspective, concrete examples, multimedia and anything else. If your stuff is too identical to your competitor’s, theirs will be indexed and yours won’t.
• Thin pages consolidation: If you have dozens of short, similar pages, you might want to consolidate them into comprehensive resource pages that Google is more likely to index and rank.
• Request Indexing with URL Inspection: After you’ve changed the content, you can use the URL Inspection tool to request Search Console to crawl the page again. Note: this does not ensure indexing, but starts a new crawl.
• Build internal links: Put a link to that page from within your own website – internal links are a sign of importance to Google. The lack of internal links to the page may cause it to be flagged as an orphan page and reduce its priority in the index.

2. Not Yet Indexed – Available

What it means: Google has info on the URL (by sitemap or link) but hasn’t crawled it yet. This is a crawl budget or priority problem: Google knows the URL but hasn’t fetched the material yet.

Common reasons:

• Large sites where Googlebot prioritizes pages with more authority over ones with less, or fresher pages
• Google detected orphan pages (pages with no internal links) only thru the sitemap
• Googlebot is crawling slowly and inefficiently due to server speed concerns
• Pages newly published on low crawl frequency sites

How to fix it:

• Build Internal Links: Link to affected pages from high authority pages on your site. Google then crawls the pages with the most internal links.
• Submit using Google Search Console URL Inspection: Manually submit the URL for crawling using the URL Inspection feature. This is especially helpful for single crucial pages.
• Keep your sitemap up to date: Ensure your XML sitemap is up to date and accurate, then submit it to Search Console. Remove URLs from sitemap you don’t want crawled.
• Improve server performance: If a server is faster, then Googlebot can crawl more pages in one session, which can assist new content get indexed faster.
• Build external links: The backlink from another site increases the crawl priority for your pages supplied by Google.

3. Duplicate without user-selected canonical

Meaning: Google has located lots of sites with the same or very similar material, and has chosen one as the canonical (main) version – but you didn’t tell Google which page you wanted them to use with a canonical tag. That’s up to Google and may not be the same as yours.

Causes include:

• Same page at different URLs (e.g., www vs non-www, HTTP vs HTTPS, trailing slash vs no trailing slash)
• Multiple Category Paths on E-Commerce Product Pages
• Print pages
• Duplicate URLs with Session ID Parameters

How to correct this:

• Add canonical tags: Add to the <head> of your chosen page version. Do this for any duplicates linking to the same canonical.
• Implement 301 redirects: Route URL variations (www/non-www, HTTP/HTTPS) such that all versions go to a single preferred URL.
• Consistent internal linking: Always link to the canonical version of a page, and do so consistently. If internal linking is inconsistent, Google receives mixed signals regarding the target URL.
• Specify favorite domain: If you have www and non-www issues, specify your preferred domain in Search Console settings.

4. Duplicate, Google chose different canonical than user

What this means: You’ve pointed a canonical to a URL you want to be the canonical, but Google has chosen a different canonical. This is Google ignoring your stated preference – a strong clue that Google signals are strongly favoring an alternate URL.

Common causes:

• Your canonical has fewer internal links than an alternative URL
• Your stated canonical loads slower than the alternative
• Mixed signals: Canonical tag says one URL, sitemap says another, internal links say another
• The alternative URL has more external links

How to repair this:

• Align all signals: Link internally to your preferred URL, include it (and not alternatives) in your sitemap, and make sure all canonical tags are consistent.
• Manage URL parameters: Google Search Console’s parameter management tool allows you to remove or redirect options. Add noindex to non-canonical versions if you have multiple URLs with different parameters.
• Review canonical vs. actual content: If the content on your canonical site is much different than what Google is picking up, consider if your canonical preference makes sense.

5. 404 Not Found

This signifies that Google attempted to crawl the URL but your server returned 404 Not Found. That page no longer exists at that URL or never did.

Causes:

• URL changes (slug, structure) without 301 redirect of old URLs
• Migration concerns such as old URLs not linking to new URLs
• Links to misspelled URLs

How to fix:

• 301 Redirects: If a page has moved to a new URL, redirect the old URL to the new URL with a 301 (permanent) redirect. This helps Google find the new place and retains link equity.
• Page restore: If the 404 is an error (bad page removed by mistake) restore it.
• Accept and ignore: If the URL has been removed correctly and there is no replacement content, 404 is the correct response. Remove it from your sitemap and let Google forget it in due course.
• Use URL inspection: Examine how Googlebot views it compared to your server.

6. Redirect Error

Meaning: Google followed a chain of redirection from this URL and encountered a problem. This could be a redirect loop, excessively long redirect chain (usually 5 or more) or redirect to a non-existent URL.

Reasons:

• Redirect loops (URL A -> URL B -> URL A)
• Long redirect chains (A > B > C > D > E > F)
• Misconfigured HTTPS or relative path redirects

How to fix it:

• Review your redirects: Map your redirect chains and find loops using tools like Screaming Frog, Redirect Path Chrome plugin, or Ahrefs Site Audit.
• Cut redirect chains: If A redirects to B and B redirects to C, redirect A to C directly. Each hop in a chain adds latency and risk.
• Fix redirect loops: Identify the start of the loop and break it so at least one URL does not redirect to a prior URL.

7. Blocked by robots.txt

What it is: Your URL is prohibited by a Disallow rule in your robots.txt and can’t be indexed by Googlebot. Google has the URL, but is respecting the robots.txt rule not to crawl it.

Important note: If you block Googlebot in robots.txt it will stop crawling, but will NOT stop indexing if the URL is linked from other pages. Google crawls links in pages but it won’t index it properly.

Solution:

• Watch your bots: Check that your domain’s robots.txt doesn’t prevent Googlebot from crawling the URLs you’re concerned about.
• Remove conflicting rules: If you have a robots.txt rule blocking Google from crawling the page, delete or modify the rule.
• Robots.txt Tester: Use the robots.txt tester in Search Console to verify that URLs are not being banned both before and after making changes.

8. Blocked by Noindex Tag

What it means: Google does not index the page because it has a noindex meta tag (<meta name="robots" content="noindex">) or an X-Robots-Tag: noindex HTTP header on the page.

How to fix:

• Remove the tag: Delete the <meta name="robots" content="noindex"> element in the HTML <head> of the site.
• Review your CMS settings: Many CMSs (WordPress, Shopify) have a feature to disable noindex on a page level. Review SEO settings on all relevant pages.
• Check plugin settings: Some SEO plugins (Yoast, Rank Math, All in One SEO) can noindex categories, tags, or archive pages. Double verify the plugin settings.
• Request indexing: Ditch the noindex, run URL Inspection and request indexing. Just make sure that tag is gone before you submit.

9. Soft 404

What it means: Your server is giving the 200 OK response code (like the site is there) but the content is essentially blank, “no results found” or a blank page. Google is treating them as 404s even if the host doesn’t specifically state so.

Common reasons:

• Empty search result pages without noindex
• E-commerce category pages with all of the products filtered out
• Local pages for areas with no business material at all
• Pages for events or promotions that have expired, stating that the event is concluded

Here’s how to solve it:

• Send a proper 404 or 410: If the content really isn’t there, have your server return a 404 (Not Found) or 410 (Gone) status code, not a 200 with empty content.
• Add a noindex tag: For pages you want to exist but not be indexed (e.g., empty search results), use <meta name="robots" content="noindex">.
• Provide actual content: If these are pages that need to be indexed (location pages, category pages), provide valid, meaningful content so they don’t look like blank pages.

10. 5xx Server Error

What this means: Your server produced a 5xx error (for example, 500 Internal Server Error, 503 Service Unavailable, etc.) when Googlebot crawled the page. The server returned an error and Google was not able to access the site.

Troubleshooting:

• Check server logs: Determine what is producing the 5xx responses and fix the root server error. Common causes include database connection issues, PHP memory constraints, or misconfigured server software.
• Check hosting resource limitations: A 503 error often signifies the service is overloaded. Increase hosting resources or decrease server load using caching methodologies.
• Verify via URL Inspection: Check that the status of the URL returns a 200 after fixing the issue before you request re-indexing.

Best Practices for Maintaining Healthy Indexes

Fixing present “Not Indexed” concerns is crucial, but so is preventing them going forward:

• Maintain a clean XML sitemap: Add only the URLs you want indexed and update it each time you add, change, or remove pages.
• Build strong internal links: Ensure every page you want indexed has at least one internal link from a more authoritative page. Orphan pages are always crawled and indexed with a lower priority.
• Audit Search Console monthly: Check your Page Indexing report regularly to find new indexing problems before they get out of hand.
• Focus on quality content: Google is getting more and more selective on what it indexes, so don’t publish thin material. Pages made merely as a keyword target that provide no real value won’t be indexed.
• Manage duplicates and parameters: Be aggressive about removing duplicate material, using canonical tags consistently, handling redirects during migrations, and avoiding URL parameter sprawl on e-commerce sites.
• Crawl budget management for huge sites: If you have a site with thousands of pages, ensure Googlebot spends its crawl budget on key pages. Strip sitemaps of low-value URLs and noindex pages you don’t want to rank.

Using the URL Inspection Tool

The fastest approach to contact Google about specific pages is via the URL Inspection feature in Search Console:

1. Type the URL you want to explore at the top of Search Console.
2. Test coverage status – it will tell you exactly what Google knows about this URL.
3. Test Live URL – This shows the page as it appears now, as Googlebot sees it now, regardless of whether cached data is old.
4. Request Indexing – Submit the URL for re-crawling after fixing errors. Google typically processes them in hours to days, but there is no warranty they will be indexed.

Caution: Be careful when employing Request Indexing. Useful for main pages following major changes. Doing so on dozens of poor quality pages wastes your quota and the work of Google.

Bottom Line

In Google Search Console, “Not Indexed” pages are a diagnostic indicator, not a death sentence. Each condition has a unique reason and a corresponding treatment. It’s about getting the correct answer to the appropriate problem, not delivering general counsel that has nothing to do with the actual scenario.

Go thru your Page Indexing report step by step. First, fix technical mistakes (robots.txt blocks, noindex tags, redirect errors, server errors) as they appear to have clear remedies. Then go to the content quality issues (Crawled – currently not indexed, Soft 404s) that require more judgment on whether the page actually deserves to be indexed or not. Lastly, address canonicalization so that the URL Google prefers is the one you want.

Good technical SEO is not about fooling Google. It’s about lowering the technical barriers for Google to accomplish what it wants to do, which is find, crawl and index great stuff that answers searchers’ questions.

Frequently Asked Questions

1. Why is my page “Crawled – presently not indexed” and how long will it take to be indexed?

This status signifies that Google crawled your page but elected not to put it in the index, typically because of thin, duplicate, or low-value material. There is no due date; the best fix is to improve your content quality and request indexing using URL Inspection. Some pages will never get indexed because Google still decides that the content isn’t worth indexing.

2. What’s the difference between ‘Crawled – not indexed’ and ‘Discovered – not indexed’?

“Crawled” signifies that Google has been to your website, read it, but didn’t choose to index it – a mark of content quality. “Discovered” signifies that Google has identified the URL, but hasn’t crawled it yet – a crawl priority or crawl budget issue. They are resolved differently: discovered issues are addressed with improved internal linking and site efficiency, while crawled issues require improved content quality.

3. How to submit a page to Google Search Console?

In Search Console, enter your URL in the URL Inspection tool at the top, and click “Request Indexing.” Google executes the request usually within hours to days. Requesting indexing does not guarantee it; Google still evaluates the quality of the page before it is included in the index.

4. Do I need to worry about “Not Indexed” pages?

Not necessarily. You don’t have to index every page of your website. As a general rule, you should not index pagination pages, filter pages, thank-you pages, and admin pages. The point here is not to get every single URL indexed, but to get the pages relevant to your search engine optimization efforts indexed.

5. Will Having Too Many “Not Indexed” Pages Hurt My Site’s Overall Rankings?

Yes, indirectly. Having a lot of low-quality, unindexed sites might be a signal to Google that the overall quality of your site is low, and that can affect crawl priority and the rankings of your better pages. It is better to keep the site tidy with decent quality content where most pages are worth indexing. A long-term plan is better than releasing masses of thin content.