Why isn't this page indexed?

Google fetched the page, looked at it, and decided not to add it to the index — for now. If the checker shows no technical blockers, the cause is almost always quality-side: thin or duplicate content, weak internal linking, or Google rationing crawl resources on your site. It is a judgment, not an error message.

Anywhere from hours to several weeks. Established sites with strong internal linking often see new pages indexed within a day; new domains or pages buried deep in the architecture can wait weeks — or never get picked up. A sitemap entry and an internal link from an already-indexed page are the two biggest accelerators.

It gets the page crawled faster, but it does not override Google's quality judgment. Requesting indexing for a page Google already declined usually changes nothing — fix the reason it was declined first, then request.

Then no technical blocker exists and Google is choosing not to index the page. The usual suspects: content too similar to other pages (yours or competitors'), no internal links pointing at it, too many low-value URLs competing for crawl budget, or site-level quality signals dragging individual pages down. That diagnosis needs a full audit — crawl data, log analysis, and content review together.

Yes, and it happens constantly. SEO plugins set noindex on archives and templates by default, staging-site settings survive migrations (the WordPress “Discourage search engines” checkbox), and hosts or CDNs can inject an X-Robots-Tag header at server level that never appears in your page source. That last one is exactly why this checker reads the HTTP headers, not just the HTML.

Not strictly — Google can discover pages through links alone. But a sitemap speeds up discovery, helps on large sites where crawl budget is rationed, and is the cheapest indexing aid that exists. Every modern SEO plugin generates one automatically; the checker verifies it's actually reachable.