Why won't Google index your pages? It usually comes down to one of three things: Google can't reach the page properly, Google reached it and decided it wasn't worth adding, or the page is stuck waiting in line to be crawled at all.
Most advice treats indexing like a checklist: submit a sitemap, click "request indexing," wait. That's only half the picture. Google actually decides whether to index a page after weighing its technical setup, its content quality, and how the rest of the site is linked together. Miss one of those and the page stays invisible, no matter how many times you resubmit it.
Below is how to tell which of the three is actually happening on your site, using what Google Search Console shows you, and what to fix once you know.
First, Confirm You Actually Have an Indexing Problem
Before troubleshooting anything, separate two situations that look identical to a business owner but are not the same problem. A page can be indexed and simply not ranking for the terms you care about, or a page can genuinely be missing from the index. Search Engine Journal's "Ask An SEO" column makes this the first diagnostic step for a reason: if you search site:yourdomain.com/page-url and the page appears, it is indexed and the issue is ranking, competition, or relevance, not indexing. If it does not appear, move on to Search Console.
This distinction matters because the fixes are completely different. A ranking problem is solved with better content depth, links, and relevance signals. An indexing problem is solved by removing whatever is stopping Google from adding the page to its database in the first place.
Crawling, Indexing, and Ranking Are Three Different Events
Crawling is when Googlebot visits a URL and downloads its content. Indexing is the separate decision Google makes afterward: does this page qualify to be stored in Google's index and made eligible to appear in search results. Ranking only applies to pages that clear indexing, and it decides position, not eligibility.
Google's own crawl budget documentation is direct about this: not everything that gets crawled is guaranteed a place in the index, because each page still has to be evaluated and assessed for indexing after the crawl happens. That single sentence is the part most site owners skip, and it changes how you should troubleshoot.
This matters because most troubleshooting starts in the wrong place. A page can be perfectly crawlable and still sit unindexed because Google decided the page was not worth adding. That is a content and value judgement, not a technical fault, and resubmitting the URL in Search Console repeatedly will not change Google's assessment of how useful the page is to searchers.
What Google Search Console Is Actually Telling You
Every unindexed page in the Page Indexing report carries a specific status. Reading that status correctly saves weeks of guessing.
Google's own page indexing report documentation is worth reading directly on this point: a duplicate page must genuinely resemble its canonical, and a non-canonical URL that redirects will never be indexed on its own, only the redirect's target might be, depending on Google's assessment of that target.
Why Pages Get Stuck at "Discovered, Currently Not Indexed"
This status confuses more people than any other because Search Console does not explain it in plain language. It means Google added the URL to its crawl queue but has not yet spent time fetching it. Google frames this as a resourcing decision: a site's crawl budget is the combination of its crawl capacity limit (how much load the server can take without degrading) and its crawl demand (how much Google actually wants to crawl a given URL, based on its popularity and freshness).
For a new domain, or a newly launched section of a large site, crawl demand starts close to zero because there is no track record of value yet. This is why individual new pages linked only from an XML sitemap, with no internal links pointing to them from pages Google already trusts, can sit in this state for weeks. The sitemap tells Google the URL exists. It does very little to tell Google the URL matters.
The fix is two-sided: reduce how much low value crawling Google is doing elsewhere on the site so more of the available budget reaches new pages, and increase the internal link equity pointing at the pages that actually need to be found. Sites built around faceted navigation, tag archives, or bulk location or listing pages are the most common budget drains we see across real estate, ecommerce, and directory style websites.
Crawled But Rejected: The Content Value Problem
"Crawled, currently not indexed" is the harder problem to fix because it is not a technical error. Google visited the page and made a judgement call. Gary Illyes, who works on Google's Search team, has said plainly that quality is the biggest driver behind most indexing and crawling decisions, more than any single technical setting. Reporting on Google's 2023 and 2024 core updates estimated that those updates removed roughly 45% of what Google considered low quality content from search results, which is a useful reminder that "crawled, not indexed" is frequently a quality signal dressed up as a technical one.
The recurring causes we see in audits:
The page duplicates or closely overlaps content already indexed elsewhere on the same domain, or on a competitor's domain.
The content answers the underlying question too thinly to be more useful than what is already ranking.
The page was generated at scale, such as bulk location or service variants, without enough unique detail per page to justify a separate URL.
Structured data on the page claims more than the visible text actually supports.
This is where E-E-A-T (experience, expertise, authoritativeness, trust) stops being an abstract acronym and becomes a practical filter. Google's Search Quality Rater Guidelines define what "helpful" looks like to a human evaluator, and the live ranking systems are trained to approximate that judgement automatically. A page written to fill a template, rather than to answer a specific reader's question, tends to read as low effort to both.
Technical Directives That Quietly Block Indexing
Beyond content quality, a short list of technical settings accounts for most avoidable indexing failures:
A noindex meta tag or X-Robots-Tag header left over from staging, often applied through a CMS SEO plugin default.
robots.txt rules written broadly enough to block an entire folder rather than the handful of URLs they were meant to stop.
Canonical tags pointing to the wrong URL, or missing entirely on pages that should self reference.
Conflicting hreflang annotations on multi language sites, which can cause Google to consolidate or drop variant pages.
Content rendered only through client side JavaScript, which Googlebot may queue for a second rendering pass rather than index immediately.
Mobile-first indexing adds a layer most teams overlook. Google now uses the mobile version of a site's content, crawled with a smartphone agent, as the primary basis for indexing and ranking. If the mobile version of a page is missing content, internal links, or structured data that exist on the desktop version, the page can be indexed with an incomplete picture, or fail to qualify at all if the mobile version errors out or carries a stricter robots rule than the desktop version.
Site Architecture and Internal Linking: The Overlooked Lever
A flat architecture, where every important page sits within two or three clicks of the homepage, gives Googlebot a clear, high value path to follow. A deep architecture, where product or blog pages sit seven or eight clicks in, buries them behind low authority intermediate pages and signals lower importance regardless of how good the content actually is.
This is also where topical authority intersects with indexing. Search engines increasingly evaluate content clusters together rather than isolated pages, so a page published on its own, without a pillar page and supporting internal links tying it to related content, gives Google less contextual reason to prioritise it. Our own approach to explaining what SEO actually involves treats internal linking as a structural decision made during planning, not a task added after a page goes live.
Page Experience and Crawl Efficiency
Page speed is not a direct indexing signal, but it shapes crawl efficiency in a way that indirectly affects indexing timelines. Google's own mobile speed research found that 53% of mobile visits are abandoned when a page takes longer than three seconds to load. That figure describes human behaviour, but the same server latency that drives a visitor away also slows Googlebot, because Google deliberately throttles its crawl rate to avoid overloading a slow server.
In effect, a slow site gets crawled less thoroughly per visit, which lengthens the time it takes new pages to reach the index in the first place. We cover this relationship between Core Web Vitals, crawl efficiency, and AI citation in more detail in our guide to Google AI Mode optimization, since the same underlying signals now feed both classic indexing and generative search visibility.
Very Large Sites Play By Different Rules
Everything above assumes a typical small or mid-sized business site. Sites with 500,000 or more URLs run into a different problem: the site can genuinely be too large for Google to fully index, independent of quality, simply because crawl limitations cap how much of a monster site gets fetched in a given window. If your site falls into this range (large marketplaces, classifieds, multi-location franchises), the diagnostic priority shifts from "is this page good enough" to "is my crawl budget being spent on the right fraction of the site," which usually means aggressively pruning low value URL patterns (filters, sort orders, thin tag pages) so the budget concentrates on pages that matter.
The Data Behind Indexing Decisions
These figures come from Google's own documentation, Google's own public statements, and independent large scale research. Each one changes how a business should plan its indexing and content strategy.
A Practical Diagnostic Sequence
Work through this order rather than jumping straight to fixes. Each step narrows the likely cause before you spend time on the wrong one.
Run a site:yourdomain.com/page-url search to confirm the page is genuinely missing, not just ranking poorly.
Open the Page Indexing report in Search Console and note which status accounts for most of the affected pages.
Run URL Inspection on three to five representative pages within that status, not the whole batch.
Check robots.txt, the robots meta tag, and the X-Robots-Tag header for each sampled page.
Compare the mobile rendered version of the page against the desktop version for missing content or links.
Review server response times and, where available, server log activity from Googlebot.
Assess how many internal links, and from which pages, point to the affected URLs.
Evaluate the content itself against pages already ranking for the same intent: is it genuinely more useful, or a variation of what already exists.
Fix the root cause categories in priority order, then request indexing for a small representative sample rather than the entire set.
Common Mistakes We See Across Client Audits
Bulk-submitting "request indexing" for hundreds of URLs without addressing the underlying cause. Search Console can move a URL up the crawl queue; it cannot override Google's value judgement about the page.
Treating XML sitemap submission as a substitute for internal linking, rather than a supplement to it.
Blocking staging or filtered URLs at scale, then discovering the same noindex rule was carried over into production during launch.
Assuming the desktop site is what matters because "it looks fine there," while the mobile version, which Google actually indexes from, has missing sections.
Panicking over a normal ranking fluctuation as if it were mass deindexing. Search Engine Journal's mid-2026 reporting on a wave of deindexing complaints found that many cases were pages moving between "excluded" states during a core update, or ranking drops being misread as removal from the index entirely, rather than genuine, permanent deindexing.
Indexing Is the Entry Ticket. Citation Is the New Finish Line
Being indexed used to be the finish line. It is now the entry requirement. Google AI Mode and AI Overviews summarise answers before a searcher ever scrolls to the organic results, so structuring content for direct extraction, defining key terms early, using genuinely useful tables, and marking up FAQ schema now serve two audiences at once: the classic ranking algorithm, and the generative layer sitting in front of it. Businesses evaluating a technical SEO partner should ask specifically how indexing health and AI search visibility are being tracked as separate, connected metrics, not folded into one generic "rankings" report.
How Long Should Indexing Actually Take
On an established, healthy domain, new pages that are internally linked from already-indexed pages are typically crawled within hours to a few days. On new domains, or for pages with weak internal signals, two to six weeks is common and not automatically a sign of a problem.
Escalate to a full technical audit when a page has been live for more than 60 days with solid internal linking, no no index or canonical conflict, adequate content depth, and it is still showing as "Discovered, currently not indexed." At that point, the constraint is almost always crawl demand tied to overall site authority, not a single setting that can be toggled off.
Frequently Asked Questions
Why is Google not indexing my website at all?
Usually a combination of factors rather than one cause: weak internal linking to new pages, a no index or canonical issue, thin or duplicate content, or a domain that has not yet built enough crawl demand. Start with the Page Indexing report in Search Console to see which status applies to most of the affected pages.
What does "Discovered, currently not indexed" mean?
Google knows the URL exists but has not yet spent crawl resources fetching it. This is a queueing and prioritisation state, not an error message, and it is common for new pages on newer or lower authority domains.
How long does it normally take Google to index a new page?
On an established site with strong internal linking, often within a few days. On a new domain or a page with few internal links pointing to it, two to six weeks is typical.
Does submitting a sitemap guarantee indexing?
No. A sitemap tells Google a URL exists; it does not tell Google the page is worth prioritising. Internal links from already-indexed, relevant pages carry far more weight for both discovery and crawl demand.
Can a slow website prevent pages from being indexed?
Indirectly, yes. Slow server response times reduce the crawl capacity limit Google allocates to a site, which means fewer pages get crawled per visit and new pages take longer to reach the index.
Does duplicate content stop pages from being indexed?
Often. When a page closely overlaps content already indexed on the same domain or elsewhere, Google may crawl it and still choose not to index it, or may index a different URL as the canonical version instead.
Will requesting indexing manually in the Search Console speed things up?
It can move a URL into the priority crawl queue, but it does not change Google's underlying assessment of the page's value. If the root cause is content quality or a technical directive, resubmitting the same URL will not fix it.
Does mobile-first indexing affect which content gets indexed?
Yes. Google primarily indexes the mobile version of a page's content. If the mobile version is missing text, links, or structured data that the desktop version has, that gap is effectively what Google evaluates for indexing.
Is being indexed enough to show up in Google AI Overviews?
No. Indexing makes a page eligible, but citation in AI Overviews and AI Mode depends further on how clearly the content answers a question, whether it is structured for extraction, and how well it demonstrates E-E-A-T signals.
What is the crawl budget, and does it matter for small websites?
Crawl budget is the combination of how much load Google's crawler will put on a server (crawl capacity) and how much Google wants to crawl a site (crawl demand). Google's own guidance notes that small to medium sites that publish new content at a normal pace usually do not need to manage it actively; it becomes relevant mainly for large sites with tens of thousands, or hundreds of thousands, of URLs.




