Confirm the page isn’t blocked by robots.txt or a noindex tag, submit an XML sitemap through Google Search Console, then use the URL Inspection tool’s “Request Indexing” feature on your priority pages. Google’s own documentation states crawling “can take anywhere from a few days to a few weeks” and explicitly warns that requesting a crawl “does not guarantee that inclusion in search results will happen instantly or even at all.” In 2026, most indexing problems aren’t a missing button to click, they’re a crawl-access issue or a content-quality issue hiding behind a request that keeps getting ignored.
1. Is Google actually able to reach the page?
Check this before anything else. Google’s own guidance on the noindex directive states plainly: “If the page is blocked by a robots.txt file or the crawler can’t access the page, the crawler will never see the noindex rule, and the page can still appear in search results.” That’s counterintuitive and worth reading twice: a blocked page can still show up in search with no description, which confuses people into thinking indexing is working when access is actually broken. Check your robots.txt file directly, check for a stray <meta name="robots" content="noindex"> tag or an X-Robots-Tag: noindex HTTP header, and confirm Googlebot can load the same CSS and JavaScript your browser does, since Google’s Search Essentials guidance notes hidden or blocked resources can prevent it from understanding the page at all.
2. Are your internal links doing the discovery work?
Google’s own SEO Starter Guide is direct about this: “Google primarily finds pages through links from other pages it already crawled… the vast majority of the new pages Google finds every day are through links, making links a crucial resource.” A sitemap and a manual request both help, but neither replaces a page being linked to from somewhere Google already crawls. An orphan page, one with no internal links pointing to it, is the single most common reason a page sits in “Discovered, currently not indexed” for weeks.
Curious whether your own site has pages stuck exactly like this right now? Get a free audit.
3. Have you submitted a sitemap, and does it meet Google’s actual limits?
Google states directly that “pages from your site can be discovered by Google without this step,” but that “submitting a sitemap using Search Console might speed up your site’s discovery.” Submit it through the Search Console Sitemaps report, the Search Console API, or by adding a Sitemap: line to your robots.txt file, which supports an unlimited number of sitemap references. The hard technical limits: 50MB uncompressed or 50,000 URLs per sitemap file; use a sitemap index to split a larger site. Every URL must be absolute and UTF-8 encoded. Google is explicit that a sitemap submission “is merely a hint,” not a guarantee your URLs get crawled or indexed.
4. Should you use the Indexing API to speed this up?
No, and this is where a lot of advice online gets it wrong. Google’s Indexing API documentation is unambiguous: it “can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject.” It is not a general-purpose fast-indexing tool for ordinary content pages, despite how it’s sometimes marketed. For everything outside job postings and livestream video pages, the correct tools are the sitemap and the URL Inspection tool’s manual request feature, not the Indexing API.
5. Are you requesting indexing correctly, and how long should it actually take?
Use the URL Inspection tool, which requires being an owner or full user on the property in Search Console, and note there’s a daily quota on requests. Google states directly: “Requesting a recrawl multiple times for the same URL won’t get it crawled any faster.” One request per URL is enough; repeating it does nothing. On timing, Google’s own words: crawling “can take anywhere from a few days to a few weeks,” and our systems “prioritize the fast inclusion of high quality, useful content.” That last clause matters: speed of indexing is tied to Google’s own read on content quality, not just the mechanical act of requesting a crawl.
Gary Illyes of Google Search Central published new detail on this in March 2026: Googlebot currently fetches up to 2MB of any individual URL’s HTML, excluding PDFs, and if a page exceeds that, “Googlebot doesn’t reject the page. Instead, it stops the fetch exactly at the 2MB cutoff.” Anything past that point “aren’t fetched, they aren’t rendered, and they aren’t indexed.” Each linked resource loaded during rendering, scripts and stylesheets included, gets its own separate 2MB allowance. A bloated page can silently lose content from Google’s view without ever throwing an error.
6. Why is a page still not indexed after doing everything above?
Google’s own FAQ on crawling and indexing states plainly: “The most common reason that a site is not indexed is because it’s just too new.” Beyond that, Google names poor site connectivity (few or no inbound links), technical crawl blocks, Search Essentials violations, and a domain’s problematic prior history as common causes. This is the step most guides underweight: indexing isn’t purely mechanical. A thin or duplicate page can sit in “Crawled, currently not indexed” indefinitely because Google has decided it isn’t worth adding to the index, not because of any technical block at all.
It’s also worth knowing indexing reports can simply glitch. John Mueller of Google confirmed on Bluesky in September 2026 that a wave of “not indexed” scares was a short reporting bug: “I double-checked with the team, and it was a short blip that was resolved quickly in the night… It’s good that it’s easy to double-check things like the indexing of the homepage.” Before assuming a real problem, re-check the URL Inspection tool a day later.
Crawl budget, the idea that Google limits how much of your site it’ll crawl, only applies at real scale. Google’s own Crawl Budget Management documentation names the sites that should actually think about it: those with 1 million-plus unique pages, or 10,000-plus pages updated daily, or sites where a large share of pages sit in “Discovered, currently not indexed.” Google calls these “rough estimates,” not hard thresholds, and states directly that crawl budget “is not something most publishers have to worry about.” If your site has a few hundred pages, this almost certainly isn’t your problem.
Bing Webmaster Tools offers a comparable sitemap submission and URL inspection flow, and Bing is the primary backer of the IndexNow protocol described below. If your traffic sources include Bing or Bing-powered surfaces (including Microsoft Copilot’s web results), it’s worth setting up Search Console’s counterpart there rather than assuming Google coverage is enough. Most sites still see the overwhelming majority of organic traffic from Google, which is why this guide focuses there, but a five-minute Bing Webmaster Tools setup is close to free insurance.
The ordered checklist
- Confirm the page isn’t blocked by robots.txt, a noindex tag, or a blocked resource.
- Link to the page internally from at least one already-indexed page.
- Submit or update your XML sitemap in Search Console.
- Use URL Inspection to request indexing once, not repeatedly.
- Check the Page Indexing report in Search Console a few days to a few weeks later, not the same afternoon.
- If it’s still not indexed, treat it as a content-quality question, not a technical one: is this page genuinely worth Google adding to its index?
Want to know exactly which of your pages Google, or an AI engine, actually sees right now? Run a free visibility audit.
There’s a genuine alternative worth knowing about too: IndexNow, a protocol backed by Bing and Microsoft, lets a site push instant notification of new or changed URLs rather than waiting to be crawled. Amazon and Shopify both adopted it in 2025. It doesn’t replace Google’s own process, Google doesn’t currently participate in IndexNow, but it’s worth setting up alongside your sitemap since it covers Bing’s index at essentially no extra cost. Bing Webmaster Tools offers its own comparable sitemap submission and URL inspection flow, worth a five-minute setup even if Google remains the overwhelming majority of your organic traffic, since it costs nothing and covers Bing-powered surfaces like Microsoft Copilot’s web results.
Getting indexed and getting cited by an AI engine are related but not identical problems: an indexed page is a prerequisite, but AI visibility work goes further than making sure Google can find the page at all, since being indexed only means a page is eligible to show up, not that anything is actually surfacing it.
FAQ
Why is my site not indexed by Google?
The most common reason, per Google’s own FAQ, is that the site is simply too new. After that, check for robots.txt blocks, noindex tags, thin or duplicate content, and whether any other page on your site links to it. A site with no inbound links pointing to a page gives Google no path to discover it.
How long does Google indexing take?
Google states directly that crawling “can take anywhere from a few days to a few weeks.” There’s no official average published beyond that range, and any specific number you see elsewhere, like “Google indexes new pages within 48 hours,” is an estimate, not a Google-confirmed figure.
How do I check if a page is indexed?
Use the URL Inspection tool in Search Console for a definitive, current status, or the Page Indexing report for a site-wide view. A site:yourdomain.com/page-url search in Google is a quick but less reliable check, since it can lag behind the actual index and sometimes returns stale results for pages that were indexed and later dropped.
How do I submit a sitemap to Google?
Add your sitemap’s URL in the Sitemaps report inside Search Console, or reference it directly in your robots.txt file with a Sitemap: line, which supports multiple sitemap references. Keep each file under 50MB uncompressed and 50,000 URLs, using a sitemap index if you exceed that.
Does the Google Indexing API help get pages indexed faster?
Only for job posting and livestream video pages. Google’s own documentation restricts it to JobPosting and BroadcastEvent-in-VideoObject content specifically, and using it for ordinary blog posts or product pages doesn’t work the way some SEO advice implies. For every other type of page, the sitemap and the URL Inspection tool’s request-indexing feature remain the correct, Google-supported path.
Why does my page say “Discovered, currently not indexed”?
This status usually means Google knows the page exists but hasn’t decided it’s worth crawling and indexing yet, often tied to crawl budget prioritization or Google’s assessment of the page’s likely quality. Improving internal links to the page and making sure it offers something genuinely distinct from your other content are the two most effective fixes. Adding the page to your sitemap and linking to it from a page Google already crawls frequently, like your homepage or a high-traffic blog post, tends to resolve this faster than repeated manual indexing requests.
Tagged