Why isn’t Google indexing my page? 10 causes and how to fix them

Guessing wastes time. Open Google Search Console, paste the URL into the inspection bar at the top and read the Page indexing section. It tells you whether the page is on Google, and if it is not, which reason Google gives.

The wording of that reason points straight at one of the causes below. How to read the URL Inspection tool explains every state.

A page that answers with 404 (not found), 410 (gone) or a 5xx server error will not be indexed. Google also treats some pages that look empty or say “not found” while returning 200 as soft 404s.

• Open the URL in a private window and confirm it loads the real content.
• Check the HTTP status with your browser’s network tab or curl -I.
• Fix server errors and broken routes, and return a real 404 or 410 only for pages that should not exist.

A noindex rule in a robots meta tag or in an X-Robots-Tag HTTP header is a direct instruction not to index the page. It often arrives by accident: a staging setting that reached production, a CMS option such as “discourage search engines”, or an SEO plugin’s per-page switch.

How to find and fix noindex tags and robots.txt blocks shows where to look.

If robots.txt disallows the URL, Googlebot will not fetch it. Search Console reports this as Blocked by robots.txt. A broad rule such as Disallow: / left over from development is a classic cause.

A rel="canonical" tag tells Google which version of a page is the main one. If it points at a different URL, Google will usually index that one and leave yours out. Search Console shows this as “Alternate page with proper canonical tag” or “Duplicate, Google chose different canonical than user”.

• Make sure every indexable page has a canonical that points to itself.
• Check that redirects, http/https and www/non-www versions agree on one preferred URL.
• If Google picked another canonical on its own, the pages are probably too similar. Make them distinct or merge them.

Thin, repetitive or near-duplicate pages are often crawled and then left out. Search Console calls this Crawled – currently not indexed. It is a judgement about the page, not an error you can switch off.

See Crawled – currently not indexed: what it means and how to fix it.

A page with no internal links and no sitemap entry may simply be unknown to Google. Search Console says URL is unknown to Google, or Discovered – currently not indexed when Google knows the URL but has not crawled it yet.

• Link to the page from pages that are already indexed, such as your home page, a category page or a related article.
• List it in your XML sitemap and make sure the sitemap is submitted. See how to create and submit a sitemap.
• Read Discovered – currently not indexed if Google knows the URL but is not crawling it.

Google can render JavaScript, but rendering is slower and can fail. If the main content is injected by scripts that error, time out or depend on a login, Google may see an empty page.

In URL Inspection, use Test live URL and then View tested page to compare what Google rendered with what you see. Server-side rendering or pre-rendering the important content avoids the problem.

If the scripts or stylesheets a page needs are blocked in robots.txt, or the server answers slowly or intermittently, Googlebot may give up early and crawl less. Keep server response times low and let Google fetch the resources your pages depend on.

New sites, sites with little authority and sites with a very large number of low-value URLs get crawled less. Check Security & Manual Actions in Search Console for penalties, look for a flood of parameter or faceted URLs that waste crawling, and make sure the site is reachable and stable.

A new page can take days or even weeks to appear, particularly on a young site. If the page is technically sound, linked from somewhere indexed and listed in your sitemap, patience is part of the fix.

Pressing Request indexing over and over does not speed things up. It has a daily limit and does not override Google’s own judgement about the page.

Causes 1 to 4 and 7 are mechanical, so a tool can find them for you. IndexMeNow’s pre-flight scan fetches each URL the way a crawler would and flags error statuses, noindex, robots.txt blocks, redirects, canonical mismatches and thin content before you spend a credit. What it cannot decide is whether Google thinks the content is worth indexing: that part is up to the page.