How to Get Indexed by Google

The right way to get pages indexed by Google — sitemaps, internal links, Request Indexing, the Indexing API and IndexNow, and why quality is the real gate.

First published: Jul 3, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #18 in Indexing#53 in How Search Works#285 in Technical SEO#381 on the site
1 evidence signal on this page

Getting indexed means Google crawled your URL, judged it worthwhile, and stored it so it can appear in results — a prerequisite for ranking, never a ranking factor. The single most useful reframe: crawling and indexing are separate steps, and the usual blocker isn't a missing button-click, it's quality. What you actually control is discovery and priority: a clean XML sitemap, real internal links so nothing is orphaned, and — for a handful of individual high-priority URLs — Request Indexing in URL Inspection (which does not guarantee or speed a quality decision, and 'no need to resubmit'). The two 'fast-index' shortcuts people reach for are narrower than advertised: Google's Indexing API is officially only for JobPosting and BroadcastEvent-in-VideoObject pages (default 200 publish requests/day), and IndexNow is a Bing/Yandex protocol that Google does not use at all. Nothing guarantees indexing. This page is the actions companion to the Page Indexing report.

TL;DR — IndexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. is crawl → judge → store, and the judgment is the hard part: Google indexes a URL only if it clears a quality/usefulness bar, so “why isn’t my page indexed” is usually a content problem, not a mechanics problem. The levers you control affect discovery and crawl priority, not the indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. decision: internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them. (no orphans), a clean XML sitemapAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags. (discovery aid, not a guarantee), and Request Indexing in URL InspectionA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version. for a few individual high-priority URLs — which explicitly does not guarantee or speed a quality decision, and “no need to resubmit.” The two “fast-index” APIs are narrower than their reputation: Google’s Indexing APIThe Google Indexing API lets site owners notify Google directly when a URL is added, updated, or removed. Google officially supports it only for pages with JobPosting or BroadcastEvent (livestream) structured data — not for general content. is officially only for JobPosting and BroadcastEvent-in-VideoObject pages (default 200 publish requests/day), and IndexNowIndexNow is an open push protocol that lets you instantly tell participating search engines (Bing, Yandex, Naver, Seznam, and Yep) which URLs you've added, changed, or removed via a simple HTTP request — and one submission is shared across all of them. Google does not use it. is a Bing/Yandex protocol that Google does not use. Nothing guarantees indexing.

Crawling ≠ indexing — the reframe the whole page hangs on

Discovery can earn a crawl; a successful crawl still does not guarantee indexing or ranking. Source: Google Search Central

The pipeline moves from crawl, where a bot discovers and downloads a URL, to index, where the engine processes the page and decides whether to store it, to serve or rank, where indexed pages may be selected for a query. Indexing is highlighted as a separate decision between crawling and ranking.

© Patrick Stox LLC · CC BY 4.0 ·

Most “why isn’t my page indexed” frustration comes from collapsing two separate steps into one. Google’s pipeline is three stages — crawl, index, serve — and, in Google’s own words, “not all pages make it through each stage.” A URL can be crawled and then not indexed. Evidence for this claim Google separates crawling, indexing, and serving and states that not every page makes it through each stage. Scope: Google Search; crawling does not guarantee indexing. Confidence: high · Verified: Google: How Search works That’s not a bug; it’s Google exercising editorial judgment.

So indexing is not a mechanical queue you can force your way into. It’s a gate with a quality bar. Getting indexed is a prerequisite for ranking, not a ranking factor: an indexed page can still rank poorly or for nothing at all, but a non-indexed page can never appear. Everything below is organized around that: the parts you control (discovery, crawl priority) versus the part Google controls (the indexing decision).

Why a page isn’t indexed — a quick diagnostic

Before reaching for tools, rule out the mechanical blockers. A page won’t be indexed if:

  • It carries a noindex meta tag or X-Robots-Tag header.
  • It’s blocked in robots.txt (Google can’t read the content — and a robots-blocked URL can still show up indexed without content if links point to it; see canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. for that failure mode).
  • Its rel="canonical" points at a different URL, so Google consolidates onto the canonical instead (GSCA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results.: “Alternate page with proper canonical tagA Google Search Console Page Indexing status meaning a page is a duplicate or alternate version that correctly points its canonical at another, indexed page. It's normal, healthy behavior — Google says there is nothing you need to do.” or “Duplicate, Google chose different canonical than user”).
  • It’s an orphan — nothing internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them. to it.
  • It returns a 4xx/5xx or soft-404s.
  • It depends on JavaScript for its main content or links, and Google’s renderer never successfully executes it — a blocked script/CSS file, a render error, or an app-shell page with no content in the initial HTML. GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. queues renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. as a separate step after the initial crawl, so a page can be fetched but still leave Google unable to see the real content or links inside it.
  • The content is thin, duplicate, or low-value — the most common cause of “Crawled – currently not indexed.”

If none of the first six apply, you’re almost certainly in quality territory, and no amount of resubmitting changes that.

Request Indexing (URL Inspection) — for individual, high-priority URLs

The URL Inspection toolA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version. in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. lets you ask Google to (re)crawl one URL. Google: “To request a crawl of individual URLs, use the URL Inspection tool. You must be an owner or full user of the Search Console property to be able to request indexing in the URL Inspection tool.”

Three things to internalize:

  • It’s rate-limited, and spamming it does nothing. Google: “There’s a quota for submitting individual URLs and requesting a recrawl multiple times for the same URL won’t get it crawled any faster.” Google does not publish the exact daily number, and has historically kept it opaque on purpose — it removed the on-screen “submissions remaining” counter from the old Fetch-as-Google tool back in 2018 while keeping the underlying limit. Practitioners informally cite a range around 10–15/day for lower-trust properties, but that’s observed, not official — treat any specific number as anecdotal.
  • It doesn’t guarantee anything. Google: “Requesting a crawl does not guarantee that inclusion in search results will happen instantly or even at all. Our systems prioritize the fast inclusion of high quality, useful content.” And the timeline is vague by design — crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. “can take anywhere from a few days to a few weeks.” Evidence for this claim Google's URL Inspection request is for individual URLs, has a quota, does not crawl faster when repeated, and does not guarantee inclusion. Scope: Google Search Console request indexing workflow. Confidence: high · Verified: Google: Ask Google to recrawl URLs
  • It’s for a handful of URLs, not bulk. Google’s own guidance pushes you to sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. for anything beyond a few: “If you want many pages indexed, try submitting a sitemap to Google.” And when a page is already stuck in “Crawled – currently not indexed,” Google’s status glossary is explicit: “no need to resubmit this URL for crawling.”

The through-line, which the reps have made repeatedly over the years, is to favor the non-manual channels — sitemaps and internal links — over compulsively clicking a button.

Submit and maintain a clean XML sitemap

A sitemap is a discovery aid, full stop. Google is blunt about the limit of what it buys you: “A sitemap helps search engines discover URLs on your site, but it doesn’t guarantee that all the items in your sitemap will be crawled and indexed.”

When you actually need one. Google’s rough guidance: you likely need a sitemap if your site is large, is new with few external links (Googlebot leans on already-known pages and backlinks to discover new URLs, so new sites are structurally slower to get found), or is rich in media/video/news. You likely don’t need one for a site of about 500 pages or fewer where every important page is reachable by following links from the homepage and there’s no significant media/news content.

Size limits. A single sitemap file is capped at 50MB uncompressed / 50,000 URLs; past that, split into multiple files and reference them from a sitemap indexA sitemap index is a sitemap of sitemaps — a single file that lists your other sitemap files instead of listing URLs directly. It's how large sites stay under the 50,000-URL / 50MB-per-sitemap limit while submitting just one file. file.

Audit indexing rates from it. The most useful workflow: in the Page Indexing report you can filter by sitemap to see how many of a given sitemap’s URLs are actually indexed. A big gap between submitted and indexed is a quality/architecture signal, not a reason to resubmit. And keep sitemaps lean — stuffing them with non-canonical or low-value URLs wastes crawl attention and muddies your own reporting; list only canonical, indexable URLs.

Fix your internal linking

This is the most foundational and most overlooked lever. Google’s link best-practices doc states it directly: “Every page you care about should have a link from at least one other page on your site.” Orphan pagesAn orphan page is a page on your site that no other page links to internally. Because crawlers discover pages by following links, an orphan page is effectively invisible to search engines unless it's in an XML sitemap or linked from an external site. — those with no internal links pointing at them — are a top real-world cause of non-indexing on both brand-new and very large sites.

A few specifics that matter for indexing:

  • Links must be crawlable. That means real <a href> elements, not onClick handlers or JS-only navigation. If a bot can’t extract the link, the page it points to may never be discovered.
  • Keep important pages shallow. CrawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. don’t use search boxes or interpret nav menus the way people do — important pages should be reachable within a few clicks of the homepage.
  • Link to the canonical URL, not a duplicate. Consistent internal linkingLinks between pages on the same site. to the preferred version reinforces Google’s understanding of which URL to index, and it’s one of the canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. signals.
  • Anchor textAnchor text is the visible, clickable text of a hyperlink. It tells readers what they'll find on the other end and gives search engines context about the linked page. helps. Google: “Paying more attention to the anchor text used for internal links can help both people and Google make sense of your site more easily and find other pages on your site.”

The Google Indexing API — what it’s actually for

This is the single most misunderstood tool in the indexing conversation, so be precise: the Indexing API is not a general fast-index endpoint. Google’s docs name the only two supported content types outright: “The Indexing API can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject.”

  • Scope: job-posting pages and pages with a livestream event (BroadcastEvent in VideoObject) only. A normal article, product, or category page is out of scope.
  • Quota: the default is 200 publish requests/day per project (covering both URL_UPDATED and URL_DELETED), 180 read-only requests/minute, and 380 across all endpoints/minute. Google notes “the quota may increase or decrease based on the document quality,” and quota-increase requests are gated to the two supported use cases.
  • Why using it for other content is risky. People do point it at unsupported pages and sometimes see it “work” temporarily — but Google’s Search Relations team has been clear this is unsupported and can be revoked without notice: the API may stop supporting unsupported content formats at any time, and access for non-supported verticals could be cut off overnight. Building your indexing strategy on an unsupported hack is building on sand.

If your site genuinely publishes job listings or livestreams, the Indexing API is excellent and fast for exactly those. For everything else, it’s the wrong tool.

IndexNow — real, useful, and not a Google tool

IndexNowIndexNow is an open push protocol that lets you instantly tell participating search engines (Bing, Yandex, Naver, Seznam, and Yep) which URLs you've added, changed, or removed via a simple HTTP request — and one submission is shared across all of them. Google does not use it. gets conflated with “fast Google indexing” constantly, and it’s worth being blunt: IndexNow does not include Google. It’s an open protocol launched in October 2021 by Microsoft Bing and Yandex; you ping a participating endpoint when a URL changes and the engines share that notification with each other. Bing’s own IndexNow page lists adopters like Yandex, LinkedIn, Yahoo, eBay, Etsy, GitHub, Wix, Cloudflare, Yoast, and RankMath — Google is not among them.

So submitting via IndexNow will help Bing, Yandex, and other participating engines discover changed URLs faster. It has zero direct effect on Google indexing — Google was never in scope. “I submitted via IndexNow but Google still hasn’t indexed my page” is a category error, not a bug.

Even for the engines that do participate, IndexNow is a discovery notification, not an indexing guarantee. Its own documentation is careful about what a successful response means: “The HTTP 200 response code only indicates that the search engine has received your URL.” Received, not indexed.

Should you still implement it? Yes — it’s low-effort (host a key file, ping an endpoint) and it genuinely speeds Bing/Yandex discovery. Just don’t expect it to move Google.

The real gatekeeper: content quality

Strip away the tooling and the actual bottleneck is almost always quality. Google’s own language around the not-indexed statuses is editorial, not mechanical:

  • Crawled – currently not indexedA Google Search Console Page Indexing status meaning Googlebot fetched the page but Google decided not to index it — usually a content- or site-quality signal, not a technical error.: The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling.”
  • Discovered – currently not indexedA Google Search Console Page Indexing status meaning Google knows the URL exists but hasn't crawled it yet — the Last Crawl date is empty. Often a crawl-capacity or crawl-demand (site-quality) signal.: The page was found by Google, but not crawled yet. Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl.”

The reps have consistently framed “Discovered/Crawled – currently not indexed” as a worthiness question. As John Mueller put it on the topic, moving pages from not-indexed to indexed basically means convincing Google it’s worthwhile to index more — since Google doesn’t yet have an understanding of an un-indexed URL, it pulls in the rest of the site to judge the URL’s potential context, and there’s nothing special or new about “discovered / not indexed.” His shorthand for what it takes, across several public statements, has been some variation of “awesomeness” — the page needs to be genuinely good.

In practice that means: thin contentThin content is web content that provides little or no value to users. Google's spam policies name it 'thin content with little or no added value' — and it's about value per page, not word count., near-duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling., low-effort or mass-produced pages, and pages that overlap heavily with better pages you already have are the usual suspects behind non-indexing. Consolidate or improve them rather than resubmitting them.

What about crawl budget?

For most sites, crawl budgetThe number of URLs an engine will crawl in a timeframe. is a red herring for indexing problems. Gary Illyes has said the vast majority of sites don’t need to worry about crawl budget at all — it becomes a real constraint only at large scale (roughly 1M+ pages changing weekly, or 10k+ daily). If you’re a small-to-midsize site and pages aren’t indexing, the culprit is far more likely quality or architecture than budget. (See crawl budget for the full treatment.)

How long does indexing take, and how to monitor

Honestly: a few days to a few weeks is normal, and new/low-authority sites are slower because Google relies on already-known pages and backlinks to find and value new URLs. A couple of quality backlinks and a clean sitemap matter disproportionately early on. Monitor with the Page Indexing reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason. (aggregate, property-wide) and URL Inspection (single URL) rather than re-clicking Request Indexing — patience and improvement beat the button.

Where this fits

This is the actions companion to the Page Indexing report, which explains how to read the not-indexed statuses; this page is what to do about them. It sits inside the broader indexing stage of how search worksSearch works in three stages — crawling, indexing, and serving (ranking). A page has to clear each one to appear in results: getting crawled doesn't mean you're indexed, and getting indexed doesn't mean you rank., and leans on its siblings: canonicalization decides which URL from a duplicate cluster gets indexed at all, XML sitemapsAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags. and internal linking are the discovery channels, and crawl budget is the efficiency concern that occasionally (rarely) intersects. For the whole pipeline — discovery, crawling, rendering, indexing, serving — see the How Search Works clusterSearch works in three stages — crawling, indexing, and serving (ranking). A page has to clear each one to appear in results: getting crawled doesn't mean you're indexed, and getting indexed doesn't mean you rank..

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.