A page that will not index is one of the most frustrating problems in SEO, because a page outside the index cannot rank at all. What is happening is straightforward: Google has either not found the page, chosen not to store it, or been blocked from keeping it. Who runs into this? Almost everyone, from new bloggers publishing a first post to established shops adding product pages that silently never appear.
Why it happens varies, and that is exactly why guessing wastes time. When should you worry? A brand-new page may need a few days, but a page that stays unindexed for weeks has a reason behind it. Where do you start? In Google Search Console, with the exact status Google gives that URL, and then you work through the causes below in order, from the simplest blocks to the harder quality questions. How you fix it depends entirely on which cause you find.
Open the URL Inspection tool in Search Console and enter the full address of the stubborn page. The status message is your diagnosis, not a vague hint. Different messages point to completely different fixes, so write the status down before you change anything.
Live-test the URL from inside the inspection tool as well. A live test shows what Google fetches right now, which can differ from the last recorded crawl. If the live test succeeds while the stored result fails, request indexing again.
The easiest causes to fix are deliberate-looking blocks that nobody remembers setting. Check whether the page carries a noindex directive in its meta tags or HTTP headers. Content management systems add these during development, and staging settings have a habit of surviving the move to a live site.
Next, look at your robots.txt file and at the page itself. A disallowed path prevents crawling, and an uncrawled page cannot be evaluated for indexing. Also confirm the page returns a normal 200 status code, loads at a sensible size, and does not sit behind a login or a broken redirect chain. Heavy, slow pages get crawled less patiently, especially on larger sites.
Server reliability matters more than many owners realise. If your host returns errors when Googlebot visits, Google backs off and may drop URLs it cannot fetch reliably. Google documents how different failures behave in its reference on HTTP and network errors, and it is worth matching your error type to that list before blaming your content.
Sometimes the page will not index because Google prefers another version. If a near-identical page exists, or your canonical tag points elsewhere, Google indexes the chosen version and files yours as an alternate. That is not an error to fight; it is a signal to consolidate, or to make the page clearly distinct if it truly deserves its own place.
Quality is the harder conversation. Pages that add little beyond what already ranks, such as short posts rewritten from competitors or auto-generated listings with no unique detail, are prime candidates for the crawled-but-not-indexed bucket. Google has limited storage appetite for pages that offer searchers nothing new.
Internal linking deserves special emphasis. An orphan page looks unimportant to crawlers, however good it is. One or two contextual links from strong pages often move a page from discovered to crawled faster than repeated manual requests. For more walkthroughs, our SEO blog collects practical fixes you can work through without a developer.
Work from the outside in. First confirm the page is not blocked, returns a healthy status, and appears in your sitemap with the correct URL. Then check canonicals and duplicates, and only then invest hours in improving the content itself, because rewriting a blocked page achieves nothing.
After each fix, use the inspection tool to request indexing once, then wait. Statuses can take days to update, and repeated requests do not speed the queue. Track the page in a simple list with the date of each change, so you can tell which fix actually worked instead of crediting whichever change you made last.
Page weight is part of that health check, and it is easy to overlook. Run your stubborn URL through the Page Size Checker to see how heavy it is compared with pages that index without trouble. A bloated page is not the only cause, but it is a fixable one, and the Page Size Checker gives you the number in seconds. Try it on your problem page before your next rewrite.
It varies from hours to a few weeks depending on your site's crawl rate and authority. A page on an established, frequently crawled site usually appears quickly, while a brand-new domain should expect slower and less predictable indexing at first.
No. Requesting indexing asks Google to crawl the page sooner; it does not override quality or duplication decisions. If Google crawls the page and still declines to store it, the fix lies in the page or the site, not in more requests.
Yes, and it is common. Crawling means Google fetched the page; indexing is a separate decision about whether the page earns a place in the index. Thin, duplicate, or low-value pages are often crawled and then left out.
Not immediately. First diagnose the status, fix blocks, and improve or merge weak content. Deletion makes sense only for pages with no search value and no use to your visitors, and those should also come out of your sitemap.
