Google Search Console: Why Your Pages Are Not Indexed

You published a new page. It looks good, it loads correctly, and you even submitted your sitemap to Google Search Console. But when you check a few days later, the page is still missing from Google Search.

Then you open the Page indexing report and see a worrying message: Not indexed.

Did you do something wrong? Does Google dislike your website? Should you keep requesting indexing until the page appears?

Not necessarily. A page can remain unindexed because Google has not crawled it yet, because a technical instruction prevents indexing, because Google selected a different canonical URL, or because the page does not currently appear useful enough to include. Some excluded URLs, such as redirects and intentionally deleted pages, should not be indexed at all.

This guide explains how to identify the actual cause, fix what you can control, and avoid wasting time on harmless exclusions.

What does “not indexed” mean in Google Search Console?

A page marked not indexed is not currently included as an indexed URL in Google’s search index according to the report. That generally means the page cannot appear as its own result in ordinary Google Search. It does not automatically mean your whole website has a problem.

It helps to understand three different steps:

1. Discovery: Google learns that a URL exists, perhaps through a link or an XML sitemap.
2. Crawling: Googlebot requests the URL and attempts to retrieve its content.
3. Indexing: Google processes the content and decides whether to store a version in its search index.

Being discovered does not guarantee a crawl. Being crawled does not guarantee indexing. And being indexed does not guarantee rankings, impressions, or traffic.

Google describes these stages in its official How Search Works: Crawling and indexing documentation (opens in a new tab).

The practical rule: Start by finding out which stage your page has reached. The solution to “Discovered - currently not indexed” is not always the solution to “Crawled - currently not indexed.”

First, find the exact reason your page is missing

Before editing your website, investigate one specific URL.

Step 1: Open the Page indexing report

1. Sign in to Google Search Console (opens in a new tab).
2. Select the correct website property. Be careful if you manage both a main domain and a subdomain.
3. In the left navigation, open Indexing > Pages.
4. Review the summary of indexed and not-indexed pages.
5. Open a reason to see affected example URLs.

The report groups URLs by why Google currently treats them as indexed or not indexed. It is a diagnostic tool, not a score. A website with many intentionally redirected, canonicalized, or deleted URLs can have plenty of non-indexed URLs without having a serious SEO problem.

For Google’s explanation of this report, see its Page indexing report help (opens in a new tab).

Step 2: Inspect the individual URL

Copy the full page address and paste it into the URL Inspection bar at the top of Search Console.

Check these details when Search Console provides them:

• Whether the URL is on Google or is not on Google.
• The reason for the current indexing status.
• Whether a crawl has been recorded and the last crawl date.
• Whether crawling and indexing are allowed.
• The user-declared canonical and, when available, the Google-selected canonical.
• Whether a referring page or sitemap is listed under discovery information.

Then use Test live URL when you need to check the page’s current accessibility. A live test is useful after fixing a technical issue, but passing that test is not a promise that Google will index the page.

The URL Inspection tool can show Google’s recorded information, which may reflect an earlier crawl, while the live test checks the current page. These are different views and can disagree temporarily after a recent fix.

Step 3: Confirm that the URL should actually be indexed

Ask yourself: Is this the final, public, useful URL that you want someone to find in search results?

A product filter URL, a duplicate tracking-parameter URL, an old URL that redirects, or an outdated post you intentionally removed may not need to appear in Google’s index.

Do not try to make every URL in the report turn green. Concentrate on important pages that should be eligible for Google Search.

Common Google Search Console indexing statuses and what to do

This table is a quick diagnostic starting point. The correct response depends on whether the URL is supposed to be a public, searchable page.

Search Console reason	What it usually means	What to check or do
Discovered - currently not indexed	Google knows the URL but has not crawled it yet.	Verify internal links, sitemap accuracy, server access, and whether the page is important enough to prioritize.
Crawled - currently not indexed	Google fetched the page but did not index it.	Review originality, usefulness, duplication, canonical signals, rendering, and the actual page content.
Excluded by ‘noindex’ tag	An indexing directive tells Google not to index the page.	Remove the directive only if the page should be searchable.
Blocked by robots.txt	Robots rules prevent crawling.	Check the blocking rule and whether it is intentional.
Alternate page with proper canonical tag	This URL points to another preferred version.	Usually no fix is necessary when the preferred page is correct.
Duplicate, Google chose different canonical than user	Google preferred a different version from the one you indicated.	Compare content, links, redirects, sitemaps, and canonical signals.
Page with redirect	The URL redirects to a different destination.	Check the destination; the redirecting URL normally should not be indexed.
Not found (404)	The requested URL does not exist.	Restore it if removal was accidental, redirect only when there is a relevant replacement, or leave the 404 if removal was intentional.
Soft 404	The page looks like an error or effectively empty page despite its response.	Return the appropriate status for a missing page, or improve the real content if the URL should exist.
Server error (5xx)	Google’s request encountered a server problem.	Investigate logs, hosting availability, timeouts, and intermittent failures.

Search Console may show additional reasons, and its interface wording can change. Always read the actual status for the URL rather than relying on a screenshot from a different website.

Why “Discovered - currently not indexed” happens

This status means Google is aware of the URL but has not crawled it. For a newly launched website, this can be especially confusing because the page may open perfectly in your own browser.

Common factors to investigate include:

• The page is newly published and has not reached its turn for crawling.
• Few useful internal links point to it, so it is difficult to discover or appears less important within the site.
• The sitemap contains many outdated, duplicate, or low-value URLs.
• The website responds slowly or inconsistently when crawlers request pages.
• Google has decided to postpone the crawl based on its assessment of the site and available resources.

A sitemap can help Google discover URLs, but it does not command Google to crawl them immediately. Google explains this in its sitemap documentation (opens in a new tab).

What to do

First, open the page yourself and verify that it is public and returns a successful response. Next, make sure there is a normal internal link to it from a relevant indexed page or a well-organized article archive.

Review your XML sitemap. Important pages should be listed with their preferred, final URLs, not obsolete redirects or accidental duplicates. Check for persistent hosting problems.

Finally, give a recently published page reasonable time to be crawled. You can request indexing through URL Inspection for an important URL, but repeated requests do not make crawling faster.

glimpzai

Why “Crawled - currently not indexed” happens

This status is different: Google has already visited the URL, but the URL is not currently indexed.

There is no single guaranteed explanation for every URL in this group. Possible contributing factors include:

• The content largely repeats another page.
• The page offers little helpful information beyond what is already available elsewhere.
• Multiple URLs serve substantially similar content.
• Important content is missing from the version Google can render or access.
• The page is weakly connected to relevant parts of the website.
• Google has chosen not to index the page for now, even though it is technically accessible.

Do not interpret this status as definitive evidence of a “quality penalty.” Search Console does not provide a complete, page-by-page explanation of Google’s indexing decisions.

A practical content improvement example

Imagine two articles on the same site:

Article A: “How to Fix Website Indexing,” with a short introduction and generic advice to submit a sitemap.

Article B: “How to Fix Website Indexing,” with the same advice plus a clear explanation of crawl versus index, a status-to-action table, examples of correct canonical tags, and instructions for verifying specific errors.

Article B gives readers more opportunities to solve their problem. That does not guarantee Google will index it, but it is a much stronger page to offer visitors.

Review whether your page answers a distinct search need, provides accurate and useful detail, and fits naturally into your site. Merge genuinely overlapping articles when that is more useful than maintaining near-duplicates.

Also review Google’s guidance on creating helpful, reliable, people-first content (opens in a new tab).

glimpzai

Technical problems that can prevent indexing

Some issues are not solved by rewriting the article. They require a change to your site’s configuration or response.

1. A noindex directive is present

A page can explicitly ask search engines not to index it. A common HTML example is:

<meta name="robots" content="noindex" />

This directive may come from a CMS setting, a staging configuration, a page template, or an HTTP X-Robots-Tag header.

If an important public page is accidentally marked noindex, remove the directive and verify the updated page. If the page is a private utility page or an intentionally excluded page, leaving it in place may be correct.

Important: Google generally needs to crawl the page to see its noindex directive. Blocking the same page in robots.txt can prevent Google from seeing that directive.

See Google’s blocking indexing guidance (opens in a new tab).

2. Your robots.txt rules block crawling

A robots.txt file contains instructions about which paths compliant crawlers can request. For example:

User-agent: *
Disallow: /private/

This blocks crawling of URLs under /private/ for compliant crawlers. That may be appropriate for certain non-public sections, although robots.txt is not a security or confidentiality measure.

Check the site’s root robots.txt file and confirm that important public pages are not covered by unintended Disallow rules.

Also remember that blocking crawling is not the same as guaranteeing a URL will never appear in search results. For details, see Google’s robots.txt documentation (opens in a new tab).

3. Canonical URLs send mixed signals

A canonical tag tells search engines which URL you prefer when multiple pages contain the same or very similar content.

For example, if these URLs show substantially the same article:

https://example.com/guide/
https://example.com/guide/?ref=newsletter

You might indicate the first URL as the preferred version:

<link rel="canonical" href="https://example.com/guide/" />

Canonical tags are signals, not absolute commands. Google can choose another canonical when other evidence points elsewhere.

Check whether your sitemap, redirects, internal links, and canonical tags consistently favor the same public URL. Do not point every article to the homepage. That would imply unrelated pages are duplicates.

Google documents these signals in its canonicalization guidance (opens in a new tab).

4. The page returns the wrong status or fails intermittently

A page that returns a 404 response is telling Google that it does not exist. A 500-series response suggests a server problem. A redirect can correctly send crawlers to the current URL.

Check whether the final URL returns a normal success response, whether unnecessary redirect chains exist, and whether security or anti-bot rules interfere with Googlebot. A page loading on your computer does not prove Google’s earlier request succeeded.

If Search Console shows persistent server errors, investigate hosting logs and infrastructure before spending time changing meta descriptions or adding more keywords.

5. JavaScript rendering hides important content

Modern websites sometimes deliver an almost empty HTML document and rely on JavaScript to populate the main content later. Google can render JavaScript, but rendering problems, resource blocks, or application errors can still affect what it processes.

This matters for single-page applications, custom frameworks, and certain client-only widgets.

For important articles, make sure the meaningful content and crawlable links are available in the rendered page, preferably with useful server-delivered HTML when your framework supports it. Test the exact URL in Search Console and inspect what Google can access.

See Google’s JavaScript SEO basics (opens in a new tab).

6. AI Crawler Blocks Fragment Your Site’s Visibility

With the rise of Generative AI engines, many sites have added strict agent rules to their robots.txt files to protect content from machine learning training models:

User-agent: GPTBot
Disallow: /

While this prevents background model training, over-restrictive setups can accidentally block conversational, real-time search agents (OAI-SearchBot, PerplexityBot) from accessing and citing your live links. If your technical pages are successfully indexed on Google but fail to appear in conversational answers, verify that your optimization rules distinguish between training scraping and real-time user retrieval.

For a complete breakdown of managing these crawlers, see our guide on How to Get Your Website Mentioned in ChatGPT and Google AI Search.

Does submitting an XML sitemap guarantee indexing?

No. Submitting an XML sitemap helps Google discover your preferred URLs, but it does not guarantee crawling or indexing.

A sitemap is like handing Google a list of rooms in a building. It helps Google know which rooms exist, but Google still decides which ones to visit and include.

A sensible sitemap should:

• Include important, canonical pages that you want indexed.
• Use the correct public domain, protocol, and final URL paths.
• Avoid intentionally deleted URLs, redirects, and pages marked noindex.
• Use a truthful <lastmod> value if you include one, reflecting a significant content update rather than an automatic timestamp change.
• Stay updated when articles are added, updated, moved, or removed.

Submit your sitemap in Search Console > Sitemaps and check for processing errors. If it is accepted, that is a useful discovery signal, not confirmation that every listed article has entered Google’s index.

For how to create one, see Google’s sitemap creation documentation (opens in a new tab).

What about old pages that still appear in Search Console?

Suppose your website used to publish articles at:

https://example.com/old-topic/

You later remove that topic and focus on something different. Search Console may continue reporting the old URL for a while because Google previously discovered it. That does not mean the URL must be restored.

The right action depends on what happened:

Situation	Sensible response
The article moved to a new URL covering the same topic	Use a permanent redirect to its relevant new location.
The article was permanently removed and has no replacement	Return 404 or 410; removal from search processing takes time.
Two live URLs show the same content	Choose a preferred canonical URL and align site signals.
An old URL accidentally still appears in your sitemap	Remove it from the sitemap and fix internal links.
A URL redirects correctly and Search Console lists it as “Page with redirect”	Usually no action is needed for the old URL.

Avoid redirecting every missing article to the homepage. If the homepage is unrelated to the removed article, that redirect may confuse users and be treated like a soft 404.

The purpose of fixing indexing is not to make Google forget every historical URL immediately. It is to keep the current site clear, accessible, and useful.

A realistic example: five indexed pages and twenty not indexed

Imagine a new technology blog has published ten valuable articles, along with category pages, tag pages, pagination, and several old addresses from an earlier site structure.

Search Console reports:

• 5 indexed URLs
• 20 not-indexed URLs

At first glance, it looks as though most of the website has failed. But look more closely:

URL group	Example count	What it suggests
New articles, discovered but not crawled	6	Check discovery and crawl access, then allow time.
Articles crawled but not indexed	4	Inspect content, canonical signals, and rendering.
Old URLs that redirect	5	Often expected exclusions.
Duplicate query-parameter URLs	3	Usually fine if Google indexes the correct canonical version.
Intentionally removed pages returning 404	2	Usually fine if those URLs are no longer needed.

Illustrative numbers, not data from a real website.

Only the first two groups clearly require attention to current articles. The other groups may reflect normal site behavior. The total count is less important than the status of pages you actually want people to find.

A sensible indexing recovery checklist

If you are looking at a long list of missing pages, work through it in this order.

Priority 1: Fix clear technical blockers

• Check accidental noindex instructions.
• Confirm important URLs are not unintentionally blocked by robots.txt.
• Fix broken responses, incorrect redirects, and persistent server failures.
• Check that each article points to the correct canonical URL.
• Make sure real article content is available to Google.

Priority 2: Improve discovery and page usefulness

• Add useful internal links from relevant articles or navigation pages.
• Clean up the XML sitemap and keep it consistent with canonical URLs.
• Make overlapping articles more distinct, or consolidate them when sensible.
• Add genuine examples, explanations, diagrams, or implementation details that help the reader.
• Keep important public articles accessible without requiring a login.

Priority 3: Verify and monitor

• Test affected URLs using URL Inspection.
• For important fixed URLs, use Request indexing when that option is available.
• Use Validate fix for issue groups where Search Console offers that workflow.
• Recheck the indexing report after Google has had a chance to recrawl and process pages.
• Track the status of your important URLs, not just the overall non-indexed total.

You can find Google’s instructions for asking Google to revisit URLs in Ask Google to recrawl your URLs (opens in a new tab).

How long does Google take to index a page?

There is no universal indexing deadline. Google’s own guidance notes that recrawling can take days to weeks, and indexing is never guaranteed. On a new or small website, some URLs may remain unindexed longer. A successful live test or an indexing request does not create a guaranteed schedule.

Try not to turn indexing checks into an hourly routine. After resolving an identified problem, give Google time to fetch and evaluate the page. If a genuinely important page is still excluded later, revisit the specific status and evidence instead of repeatedly submitting the same request.

glimpzai

Frequently asked questions

Why is my page not indexed even though it is in my sitemap?

Because a sitemap only helps Google discover URLs. Google may still need to crawl the page, resolve duplication, process its content, and decide whether to index it. Check the exact URL in the URL Inspection tool.

Should I request indexing for every page?

No. Use it selectively for important new or substantially updated pages, particularly after correcting a problem. For larger collections, accurate sitemaps and internal links are more sustainable discovery methods. Repeated requests for the same URL do not guarantee a faster result.

Does “Crawled - currently not indexed” mean Google penalized my site?

No. That status alone does not establish a manual action, algorithmic penalty, or specific content-quality judgment. It tells you the URL was crawled but is not currently indexed. Investigate the page without jumping to conclusions.

Is a site: search the best way to check indexing?

A query such as site:example.com/page/ can be a quick clue, but it is not a complete or definitive indexing audit. Use Search Console’s URL Inspection tool for a particular URL and the Page indexing report for broader patterns.

Can a page be indexed but still receive zero clicks?

Yes. Indexing and ranking are separate. An indexed page might appear for very few searches, rank poorly, or receive no clicks. Use the Search Console Performance report to evaluate impressions, clicks, queries, and pages once the URL is indexed.

Do I need to fix every “not indexed” URL?

No. Redirects, duplicates, intentionally removed pages, and other excluded URLs can be normal. Fix the exclusions that affect current, public pages you genuinely want Google to index.

Final takeaway: diagnose before you request indexing

A red or gray status in Google Search Console is not a verdict on your website. It is a starting point for investigation.

If the page has not been crawled, focus on discovery, internal linking, sitemap quality, and access. If the page has been crawled but not indexed, review its content and technical signals. If the URL is an intentional redirect, duplicate, or removed page, it may already be behaving correctly.

The goal is not to get every URL into Google. It is to make sure your important, useful pages are discoverable, accessible, and eligible for indexing, while keeping expectations realistic about Google’s independent decisions.

References and further reading

• Google Search Central: How Search Works (opens in a new tab)
• Google Search Console Help: Page indexing report (opens in a new tab)
• Google Search Console Help: URL Inspection tool (opens in a new tab)
• Google Search Central: Ask Google to recrawl your URLs (opens in a new tab)
• Google Search Central: What are sitemaps? (opens in a new tab)
• Google Search Central: Specify a canonical URL (opens in a new tab)
• Google Search Central: How to block indexing (opens in a new tab)
• Google Search Central: JavaScript SEO basics (opens in a new tab)