Unindexed Pages: How to Find and Fix Them in Search Console

How do you find unindexed pages in Search Console?

Unindexed pages are URLs that Google knows about or has crawled but has not added to its search index. You find them in the Page indexing report in Search Console, under the Not indexed section, where each reason is listed. You then test single URLs with the URL Inspection tool.

So the method has two steps. First, you read the report to see the big picture. Then you inspect the suspicious pages one by one. In this guide, we explain what each status means, which ones are real problems, and how to fix them.

If your focus is online stores, also read our guide on why product pages are not indexed. Here, we cover the general method for unindexed pages that works for any type of site.

Is every unindexed page a problem?

No, it is not. For example, carts, thank-you pages, filter combinations and admin screens should stay out of the index. However, the real problem starts when pages that earn money or answer real questions are missing from Google.

Therefore, your first job is to sort your pages into two groups. The first group holds pages you want in the index. The second holds pages you do not. Then you compare every status in the report with those two lists.

• Should be indexed: service pages, product pages, category pages and blog posts.
• Should stay out: cart, checkout, internal search results and test pages.
• Needs a decision: tag archives, paginated pages and old campaign pages.

So without this sorting, you waste time on pages that never mattered. With it, every row in the report becomes a clear yes or no. As a result, you triage unindexed pages in minutes instead of hours.

Where do you open the Page indexing report?

In Search Console, open the Indexing section in the left menu and click Pages. The report needs a verified property, so add your site first if you have not done so.

For setup steps, see our guide on what Google Search Console is and how to use it. Next, choose the right property type. For instance, a domain property shows all subdomains and both protocols in one report. A URL prefix property only shows the pages under that prefix.

This difference explains many cases of missing data. For example, if you check a URL prefix property for https://www, you will not see the non-www pages. So check which property you are reading before you draw conclusions.

What do the totals and the chart tell you?

The chart shows two series: pages that Google indexes and pages that it does not. According to Google's documentation, the indexed and not indexed totals above the chart are complete and accurate from Google's point of view. Source: Google Search Console Help.

First, use these totals as your starting point. If the total does not match the real number of pages on your site, there are two likely reasons. Either Google has not discovered some of your pages, or your site produces extra URLs that nobody needs.

When you look for a sudden drop or jump, always check the date too. A theme update, a migration or a robots.txt change often falls in the same week. Also, a growing gray area is not always bad news. Cart and filter URLs land there as well.

How do you read the table of reasons?

The report groups non-indexed pages by reason. Each row shows the reason, the source, the validation status, the trend and the number of pages. Also, start with the row that matters most for your business, not with the row that has the most pages.

The table below summarizes the most common statuses and the first action for each. The status names follow Google's official definitions.

What does Crawled, currently not indexed mean?

In this status, Google visited your page but chose not to add it to the index. Google's documentation says you need no action, because the page may get indexed later. However, if an important page stays here for weeks, you should question its quality signals.

In our experience, we see this status most often on thin pages, near duplicates and pages with no internal links. Then Google may treat such pages as unimportant. So improving the page usually works better than waiting.

• Deepen the content with original examples, data and a clear answer.
• Link to the page from related blog posts and service pages.
• Make the title and description different from similar pages.
• Merge or remove pages that add no real value.

What does Discovered, currently not indexed mean?

This status means Google found the URL but has not crawled it yet. According to Google, you can wait, or you can request indexing in the URL Inspection tool if the page is urgent.

If many pages pile up here, the cause is usually crawl priority. When a site is large, slow or full of useless URLs, Googlebot visits the pages it finds more important first. To understand this behavior better, read why Googlebot crawls less.

However, the fix is often simple. Add the important pages to your sitemap, and link to them from your main menu and related content. That way, Google notices their value sooner. Also, fast hosting helps, because a slow server makes Googlebot ask for fewer pages.

How do you spot a soft 404?

A soft 404 happens when a page shows a not found message or an empty shell to the visitor, while the server still answers with a 200 code. Google does not index these pages, because it sees no value in them.

First, open the Soft 404 row and inspect the example URLs one by one. For example, an out of stock product may leave an empty shell page behind, or an internal search may show zero results. Both cases create soft 404s.

• Return a 404 or 410 for pages that are gone for good.
• Redirect with a 301 if a replacement page exists.
• Fill the page with useful content if it really matters.
• On empty categories, show related products and alternatives.

We see this error most often on store and listing sites. Also, the template builds an empty page when the stock ends. So fix it at the template level for a lasting result.

How do you tell noindex and robots.txt blocks apart?

First, the two methods do different jobs. Then robots.txt stops Googlebot from crawling a page. Noindex is a directive that Google reads while crawling, and it asks Google to keep the page out of the index. For details, read the Google Search Central guide to noindex.

Here is the key point. Google cannot see a noindex tag on a page that robots.txt blocks. So to remove a page from the index, you first open it to crawling and then add noindex. Google's documentation also notes that a blocked URL can still appear in the index through external links.

We collected the usual mistakes in our post on common robots.txt mistakes. To write the file from scratch, use our robots.txt generator.

Are canonical related statuses real problems?

However, most of the time they are not. The status Alternate page with proper canonical tag means the page points to the right canonical, and Google says it needs no action. The problem starts only when the canonical tag points to the wrong page.

Two cases need more care. The first is Duplicate without user-selected canonical. Here, Google noticed a duplicate, but you never declared your preference. The second is Duplicate, Google chose different canonical than user. In other words, Google disagrees with your choice.

In both cases, then, compare the two URLs. If the content is really the same, pick one canonical and link to it consistently. If the content differs, separate the pages clearly. Also keep your internal links and sitemap in line with your preferred URL, because a canonical tag is a hint, not a command.

How do you fix server, 404 and redirect errors?

This group holds technical errors, and most have a clear fix. A server error (5xx) means Google got a 500 level response. Google's documentation says you should check your host and the Crawl Stats report.

For a 404, first ask if you deleted the page on purpose. If so, leave it alone. Otherwise, if you deleted it by mistake, restore the content or add a 301 redirect.

For redirect errors, look for chains and loops. Our post on redirect chains explains the fix in detail. To test a single URL fast, our redirect checker does the job.

Also treat each error group as its own work item. Server errors go to the hosting team, 404s go to the content team, and redirects go to the developer. That way, no unindexed pages stay without an owner.

How do you test a single page with the URL Inspection tool?

The URL Inspection tool shows the index status of one address. First, you paste the full URL into the search bar at the top of Search Console. The tool reports the last crawl date, the user and Google selected canonicals, and whether the page is on Google. See the URL Inspection tool documentation for details.

Also, the live test option shows the page as Google sees it right now. So you can confirm that your fix works without waiting for the index to update.

• Whether the page is on Google or not.
• Which URL Google picked as the canonical.
• Whether crawling is allowed and whether a noindex exists.
• The rendered HTML and a screenshot in the live test.

A request for indexing can speed things up, but it does not guarantee quality. So solve the cause first.

Is the site: search enough to find unindexed pages?

No, it is not enough alone. Also, typing site:yourdomain.com in Google gives a rough idea, but the result count is not exact, and it does not show the status of a specific URL. Use it only as a quick first look.

For a reliable answer, you need Search Console. The URL Inspection tool covers single pages, and the Pages report covers the big picture. In practice, we suggest this combination: a fast check with site:, then a confirmation in Search Console.

You can also search for a full sentence from the page in quotes. If the page does not appear, confirm with URL Inspection. Sometimes a page is in the index but does not show in a site: query, so never decide on one query alone.

How do you find missing pages with the sitemap filter?

The Pages report has filter options: all known pages, all submitted pages, unsubmitted pages only, and a specific sitemap. Google recommends a sitemap with only your important pages, then filtering the report by it.

In practice, this works well. A page that sits in your sitemap but stays out of the index is a question mark, because you recommended it to Google yourself. So review this list every week.

• Submitted but not indexed: your priority review list.
• Indexed but not submitted: a sign of useless URL generation.
• Split sitemaps: track service, blog and product groups on their own.

For setup, our XML sitemap generator and our guide to the sitemap lastmod tag help.

How does the Validate fix button work?

After you fix an issue, then you press Validate fix on the issue page. However, Google rechecks only the known affected URLs, not the whole site. According to the documentation, validation can take up to two weeks.

During validation, the status moves through these steps: Not started, Started, Looking good, Passed or Failed. If the issue remains on a threshold of pages, validation fails and you get an email.

So before you press the button, fix every example of the issue. If you fix only a few pages and start validation, it fails, and you lose two weeks. When it does fail, check the failed URLs, fix the cause and start again.

What do you check in the content when a page stays out?

First, if no technical block exists, the problem is usually the content. Google does not have to index every page, and it drops pages that give readers no clear value. So read the page again as a reader would.

• Is the page the same as, or very close to, another page?
• Does the first paragraph answer the visitor's question?
• Does it hold original information, examples or experience?
• Is it linked from other parts of your site?
• And do the title, description and H1 make it unique?

If you answer no to several of these, improve, merge or remove the page. This decision often changes more than any single technical setting. Also, add examples from your own work, because original contribution separates your page from similar ones.

How do unindexed pages hurt organic traffic?

A page that is not in the index cannot appear in search results at all. So your traffic for every search that page targets is zero. If a key service page is in this state, the loss turns into lost calls and sales.

A quieter effect concerns internal link value. Links that point to non-indexed pages waste part of their value. Also, many weak pages can lower the general quality view of your site.

So connect your list of unindexed pages with traffic. Find the pages that once earned traffic and have now dropped out. For drop diagnosis, our post on diagnosing traffic drops in Search Console guides you.

How long does a new page need to get indexed?

However, Google gives no fixed time. A page may enter the index in a few days, or it may take longer. Your site's authority, crawl frequency and internal link strength all affect the time.

To help Google notice a new page fast, follow a simple order. Add it to the sitemap, link to it from the home page or a related category, and request indexing in the URL Inspection tool.

• Keep it in the sitemap with an accurate lastmod date.
• Give it links from at least two related pages.
• Make sure it returns 200, has no noindex and no robots.txt block.
• Point its canonical tag at itself.

Then wait a few days. If it still does not show, check its status in the Pages report.

What does a sample diagnosis look like?

This is a made up example scenario, not real client data. Imagine that new service pages on a corporate site stay out of the index. Then you start the diagnosis in the report.

1. In the Pages report, the pages show as Discovered, currently not indexed.
2. Also, in the sitemap you notice the pages are missing.
3. Instead, the pages get only one link from a sub menu.
4. You add them to the sitemap and link to them from related blog posts.
5. After a few weeks, the status changes to Indexed.

Notice that the fix was not a technical bug. It was an internal link and sitemap change that raised the crawl priority. In real sites, simple fixes like this solve most cases.

How do you handle the 1,000 row limit on large sites?

According to Google's documentation, the list of example URLs in the report is limited to 1,000 items, and it may not show every URL for a status. The totals, however, are complete. So on large sites, this difference matters.

The answer is to slice your data. Build sitemaps that split the site into sections, then filter the report by each one. That way, each filter stays under 1,000 rows, even with thousands of unindexed pages, and the examples are more representative.

Also think in templates. If a hundred pages with the same template stay out for the same reason, one fix solves them all. So look for a shared pattern in the example URLs. For instance, with separate sitemaps for blog, service and product, you see at a glance which section is weak.

How do you build a monthly index check routine?

If you check indexing on a calendar instead of after an incident, you catch problems early. We suggest the order below. In practice, each step takes fifteen to thirty minutes.

1. Look at the trend of total indexed pages.
2. Mark new status rows and rows that are growing.
3. List the submitted pages that are not indexed.
4. Inspect your newly published key pages with URL Inspection.
5. Track the issues that wait for validation.

Also, turn the routine into a checklist and share it with the team. Also keep notes: write down what grew, what shrank and what you changed. After six months, these notes tell the real story of your unindexed pages. For the wider audit, see our technical SEO tips.

Which mistakes do we see most often?

Most mistakes in this area come from chasing the symptom and skipping the cause. First, the list below sums up what our team meets most in audits.

• Treating every unindexed page as a problem and wasting time.
• Trying to solve everything with an indexing request.
• Adding noindex to a page that robots.txt already blocks.
• Forgetting to remove noindex after a test launch.
• Putting redirecting or 404 URLs in the sitemap.

All of these share one thing: acting before reading the report. So read the status first, then make a single change, and then measure the result.

When do you need professional help?

Still, you can solve most statuses with this guide on your own. However, a big migration, a growing Crawled status or an unexplained traffic loss justifies an expert view.

As a team, we diagnose these cases by combining Search Console, server logs and content analysis. As a result, you get a list that shows which page stays out, why it does, and in which order to fix it.

If you want such an audit, reach us through our SEO consulting page. Before you decide, try the checklist in this post on your own site once.