Rankwell

Why Google is not indexing your page

What each Search Console indexing status means, including crawled and discovered but not indexed, and what to change for each one.

3 October 2026 · 5 min read

A page that is not in Google's index cannot rank for anything. The good news is that Google usually tells you why, if you know where to look and how to read the answer.

This guide walks through Search Console's statuses one by one, with the likely cause and the fix for each.

First, confirm the page really is missing

A site: search gives a rough answer:

site:yoursite.com/your-page

If it returns nothing, that suggests the page is not indexed, but site: results are not complete. For a reliable answer, open Search Console, paste the full URL into the URL Inspection bar at the top, and read the verdict. It says either "URL is on Google" or "URL is not on Google", followed by the reason.

Then click Test live URL. The first result describes what Google saw on its last visit. The live test shows what it would see now, which matters if you have already changed something.

For the site as a whole, the Pages report under Indexing lists every reason Google has for not indexing URLs, with examples for each.

Statuses that mean you told Google not to

These are the easiest to fix, because the cause is on your side and usually a single line.

Excluded by 'noindex' tag. The page carries <meta name="robots" content="noindex"> or an X-Robots-Tag: noindex header. Themes and CMS plugins sometimes add it to whole sections, and staging settings get carried to live sites. Remove it if the page should rank.

Blocked by robots.txt. A Disallow rule covers the URL, so Google has not fetched it. Find the matching rule and narrow or remove it. What to put in robots.txt covers how the rules are matched.

Alternate page with proper canonical tag. The page points its canonical at another URL, and Google agreed. This is correct for genuine duplicates such as tracking-parameter versions. If it appears on a page you want indexed, the canonical tag is wrong, often because a template sets it to the homepage or to page one of a series.

Page with redirect. The URL redirects elsewhere, so the destination is what gets indexed. Usually fine. Check that your sitemap and internal links point to the final URL rather than the redirecting one.

Statuses that mean the page failed

Not found (404). The URL returns 404. If it should exist, fix the route. If it was removed on purpose, this is harmless, but stop linking to it.

Soft 404. The page returns 200 but looks empty or like an error page to Google: "No products found", a nearly blank template, or a page whose content only appears after JavaScript runs. Either give the page real content or return a proper 404.

Server error (5xx). Google got a server failure when it visited. Check your logs for the time of the crawl. Repeated errors make Google slow its crawling of the whole site.

Blocked due to unauthorized request (401) or access forbidden (403). The page needs a login, or a firewall rule is refusing Googlebot. Security plugins and bot protection are the usual cause.

Redirect error. A redirect loop, a chain that is too long, or a redirect to an invalid URL. Clearing broken links and redirect chains shows how to trace them.

Duplicate statuses

Duplicate without user-selected canonical. Google found several pages it considers the same and you did not say which is the real one, so it picked one. Add a canonical tag to each version pointing at the URL you prefer.

Duplicate, Google chose different canonical than user. You named a canonical, but Google disagreed and indexed a different URL. Canonical tags are a strong hint, not an order. Google overrides them when other signals point elsewhere: internal links, the sitemap, and redirects all naming a different version. Make every signal agree on the same URL.

Crawled, currently not indexed

Google fetched the page, read it, and decided not to keep it for now. Nothing is technically broken. This is a judgement about the page.

Common reasons:

  • The page adds little that other pages, on your site or elsewhere, do not already say.
  • It is thin: a short product page with a manufacturer description copied by a hundred other shops, or a tag page listing two posts.
  • It is too similar to another page on your own site, without being an exact duplicate.
  • Google does not yet see the site as worth indexing deeply, which is common for new sites.

What helps:

  1. Make the page clearly better than the alternatives for the search it targets. Writing pages that answer the search covers what that means in practice.
  2. Merge near-duplicate pages into one stronger page and redirect the others.
  3. Link to the page from relevant, already indexed pages on your site. A page nothing links to looks unimportant.
  4. If the page genuinely does not need to rank, leave it. This status is not a penalty.

Requesting indexing again without changing the page rarely changes the outcome.

Discovered, currently not indexed

Google knows the URL exists, from a link or your sitemap, but has not crawled it yet.

On large sites this often means Google is limiting how much it crawls, either because the server responded slowly or because there are far more URLs than it wants to fetch. Filter combinations, calendar pages and session parameters can produce millions of URLs that crowd out the ones you care about.

On small sites, it usually means Google did not see the page as a priority. The URL might be listed in a sitemap with no internal links pointing at it, which is a weak signal.

What helps:

  • Link to the page from your navigation or from related pages, not only from the sitemap.
  • Block crawl traps such as endless filter parameters, so crawling goes to real pages.
  • Check server response times. A slow server gets crawled more gently.
  • Use Request indexing in URL Inspection for a few important pages, keeping in mind the daily limit.

After you fix something

Once the cause is fixed, open the matching row in the Pages report and click Validate fix. Google rechecks the affected URLs over the following days or weeks and reports the result. You do not need to request indexing for each URL individually.

For pages you have just published, the quickest route is a link from a page Google already crawls often, plus an accurate entry in your sitemap.

Rankwell's site audit checks the causes you control before Google has to report them: noindex tags, canonicals pointing elsewhere, broken pages, redirect chains, and pages reachable only from the sitemap.

Common questions

How long does Google take to index a new page?
Anything from a few hours to several weeks. Pages on established sites with good internal links are usually picked up within days. Pages on new sites that nothing links to can take much longer.
Does Request indexing guarantee the page gets indexed?
No. It asks Google to crawl the URL soon, and there is a daily limit on requests. Whether the page is then kept in the index is still Google's decision.
Should every page on my site be indexed?
No. Filtered listings, internal search results, thank-you pages and thin tag archives are often better left out. Look at whether the pages you care about are indexed, not at the total.

Read next