How to Fix Indexing Issues in Google Search Console

To fix indexing issues in Search Console, open the Page indexing report, read the reason Google gives for each group of unindexed pages, and decide whether each reason is expected or a problem. Then inspect an example URL, fix the cause on your site, and ask Google to validate the fix. Statuses such as "Crawled - currently not indexed" usually point to a page quality or duplication issue, not a technical block. This guide is part of our technical SEO guide.

You'll need access to the site's Search Console property and to the pages or templates involved. If your site has only a few hundred pages, Google suggests a site: search for your key URLs may tell you enough before you open the report.

First, decide whether the page should be indexed

Not every URL on your site should be in Google's index, and Google says not to expect all of them to be. Redirects, duplicates, filtered views, deliberately noindexed pages and removed pages are meant to stay out. A long "Not indexed" list is often a sign that Google has correctly ignored the copies and indexed the main versions.

So the goal isn't a perfect score. It is to get the canonical version of every important page indexed. Start with a short list of the pages that matter, such as the homepage, service pages and your best guides, and check those first.

Page indexing statuses at a glance

These are the reasons you'll see most often in the "Why pages aren't indexed" table, with the first thing to check for each.

Steps

1. 01
   Open the Page indexing report.

   In Search Console, go to Indexing, then Pages. The chart shows indexed and not indexed counts, and the "Why pages aren't indexed" table lists each reason with the number of affected URLs. Note the Source column: Google says you can generally fix only the reasons where the source is "Website".

2. 02
   Separate expected reasons from real problems.

   Go through the table row by row. Redirects, alternates with a proper canonical, and pages you deliberately noindexed or removed are usually fine. Mark the rows that contain pages you want indexed. Those are your work list, in order of how important the affected pages are.

3. 03
   Inspect an example URL.

   Click a reason, then click an example URL and open it in URL Inspection. Read the crawl date, whether crawling and indexing were allowed, and the user-declared and Google-selected canonicals. The result shows what Google saw at its last crawl, which may be older than your most recent change.

4. 04
   Run a live test.

   Click Test live URL to see how Google fetches the page now. This confirms whether a block or error still exists, and shows the rendered page. Google notes that the live test doesn't check everything: it can't tell you whether the page will be treated as a duplicate, and it doesn't check sitemaps or manual actions.

5. 05
   Fix the cause on the site.

   The fix depends on the reason; the troubleshooting section below covers the most common ones. Fix the template or rule behind the problem, not one URL at a time, so every affected page is corrected together. Check that the fix shows in the live page source, not just in your CMS.

6. 06
   Make important pages easy to find.

   Make sure every page you want indexed has contextual links from related pages, as covered in our internal linking strategy, and appears in your sitemap. Google needs to find a page through a link or a sitemap before it can crawl it.

7. 07
   Request indexing for key URLs.

   For your most important fixed pages, click Request indexing in URL Inspection. Requests are limited by a quota, so save them for pages that matter. A request asks Google to recrawl; Google still decides whether to index the page.

8. 08
   Validate the fix and watch the trend.

   Back in the report, open the reason you fixed and click Validate fix. Search Console checks the affected URLs and emails you the result. Then watch the indexed count over the following weeks. A steady rise in indexed pages, with the problem rows shrinking, means the fix worked.

If you'd rather have indexing problems diagnosed and fixed for you, our in-house SEO team handles technical SEO, from site structure to metadata and performance.

How long fixes take to show

Google says validation typically takes up to about two weeks, and sometimes much longer. When pages have been grouped as duplicates, Google may hold them in that cluster for up to two weeks after you make them different. New content can take a few days to be indexed.

During that time, the report may still show the old status. Check the crawl date in URL Inspection before assuming a fix failed. If the page hasn't been recrawled since the change, the report simply hasn't caught up. Our guide on how to read Search Console explains the other reports to watch.

Troubleshooting

Crawled - currently not indexed

Cause: Google crawled the page and decided not to index it, at least for now. There is no technical block. Usually the page doesn't add enough compared with other pages, on your site or elsewhere: it is thin, very similar to another page, or answers a question better covered by another URL.

Fix: compare the page with the pages that rank for its main query and with your own similar pages. Add what's missing, such as specific detail, examples or first-hand information, or merge it into a stronger page and redirect it. Add contextual internal links from related pages. Google says there is no need to resubmit the URL for crawling, so focus on the page itself and give Google time to recrawl it.

Discovered - currently not indexed

Cause: Google knows the URL exists but hasn't crawled it yet. Google says this typically happens when crawling was expected to overload the site, so it rescheduled. On larger sites it can also mean Google is spending its crawling on other URLs, such as duplicates or filter pages.

Fix: check server response times in the Crawl stats report, under Settings, and fix slow pages or server errors. Reduce wasted crawling by consolidating duplicate and parameter URLs, as covered in our guide to crawl budget. Make sure the discovered pages are linked from pages Google already crawls, not only listed in a sitemap. Then request indexing for the most important few.

Duplicate, Google chose different canonical than user

Cause: your page declares itself canonical, but Google thinks another URL is the better main version. Either the two pages look the same to Google, or your signals conflict, such as a canonical tag that disagrees with your sitemap, redirects or internal links.

Fix: inspect the URL and compare your declared canonical with Google's choice. If Google's choice really is the same content, accept it and point your links there. If the pages should be separate, make their main content clearly different. Make sure your canonical tag, sitemap and internal links all name the same URL. Our explainer on canonical tags and duplicate content covers the signals in detail.

Soft 404

Cause: the page tells visitors something like "not found" or "no results", but the server returns a 200 success code. Google treats it as an error page in disguise. Empty category pages, expired listings and pages with almost no content are common causes.

Fix: if the page is truly gone, make the server return a 404 or 410 status, or a 301 redirect if there is a close replacement. If the page should exist, add real content so it no longer looks empty, for example by listing related services or explaining what the page offers. Then inspect the URL with a live test to confirm the status code and content, and validate the fix in the report.

Excluded by noindex, or blocked by robots.txt

Cause: the page carries a noindex meta tag or header, or a robots.txt rule stops Google from crawling it. Both are often left behind by mistake after a site launch, a plugin setting or a staging setup copied to the live site.

Fix: if the page should be indexed, remove the noindex tag or header, or narrow the robots.txt rule, then run a live test and request indexing. If the page should stay out of search, use noindex and make sure robots.txt doesn't block it: Google can't see a noindex rule on a page it isn't allowed to crawl. Our robots.txt and sitemap guide covers the rules.