10 common Google indexing issues and how to fix them

According to a study of 16 million pages by IndexCheckr, 61.94% of pages were not indexed by Google. For most of those pages, the problem was not that Google disliked the content. It was that the site gave Google a reason to skip it.

This guide covers the 10 most common reasons Google does not index pages and what to do about each one. Whether you manage a 20-page site or a 200,000-URL ecommerce platform, these are the issues that show up most often in audits. Fix them and you remove the barriers between your content and the search results that drive traffic, leads, and revenue.

How to find indexing issues before you start fixing them

Google Search Console is the starting point for every indexing investigation. Open the Page Indexing report under Indexing and look at the "Not indexed" section. Every entry in that list tells you a specific reason Google skipped a page. Use the URL Inspection Tool for individual pages when you need to see exactly how Googlebot last crawled and rendered a URL.

The Page Indexing report groups issues by type. The two status labels you will see most often are "Crawled, currently not indexed" and "Discovered, currently not indexed." The first means Google visited the page but chose not to add it. The second means Google found the URL but has not yet prioritized it for crawling.

What to check first

Start with the issues affecting the most pages. Click each issue type in the report to see a list of affected URLs and a short description of the problem. Use the URL Inspection Tool on a representative URL from each group to understand what Googlebot actually sees.

For site-wide audits, tools like Screaming Frog SEO Spider, Ahrefs, or Semrush help you surface patterns across thousands of URLs at once, including redirect chains, orphan pages, and duplicate content that Search Console may not fully expose.

A note on timelines

Fixing an indexing issue does not produce instant results. Pages that meet Google's quality and technical requirements after a fix typically re-enter the index within four to eight weeks. Requesting indexing via the URL Inspection Tool speeds up the process for individual pages, but it does not guarantee rapid crawling at scale. Pair every request with a fresh sitemap submission.

Issue 1: Accidental noindex tags blocking important pages

A noindex tag tells Googlebot not to include a page in the index. This is useful for admin pages and checkout flows. It is damaging when it appears on blog posts, product pages, or landing pages you want to rank. Developers often add noindex tags during staging and forget to remove them before launch.

This is one of the most common and most damaging indexing mistakes. A single noindex directive in a page template can silently remove thousands of pages from Google's index. The problem often goes unnoticed for weeks because traffic drops gradually rather than overnight.

In December 2024, Google updated its JavaScript SEO documentation to clarify that Googlebot may skip JavaScript execution entirely when it encounters a noindex tag in the original HTML. This means you cannot rely on JavaScript to remove a noindex tag dynamically. If the tag is present in the original page code, the page may never be indexed regardless of what your CMS or JavaScript logic does afterward.

How to fix it

1. In Google Search Console, go to the Page Indexing report and filter for "Excluded by noindex tag"
2. Export the list of affected URLs
3. Crawl the site with Screaming Frog and filter for pages returning a noindex directive
4. Review your CMS template settings and any plugins that control meta robots output
5. Remove the noindex tag from any page you want indexed
6. Use the URL Inspection Tool to request indexing after each fix
7. Add an automated check to your deployment pipeline to catch noindex tags before they reach production

Common pitfall

Developers building on WordPress sometimes install SEO plugins that include a global "discourage search engines" setting. This adds a noindex to every page on the site. Always verify this setting is off before any site launch.

Issue 2: Robots.txt errors blocking crawling

A robots.txt error prevents Googlebot from visiting pages at all. Unlike a noindex tag, which prevents indexing of pages Googlebot can reach, a robots.txt disallow rule stops the crawler before it even reads the page. The page will not appear in the "not indexed" section of Search Console because Google never saw it.

Robots.txt errors are particularly dangerous because they are silent. Search Console flags pages it tried to crawl and found blocked, but it cannot report on pages it never discovered. Tools like Screaming Frog or WebSite Auditor are needed to identify pages that exist on the site but are blocked at the crawl level.

How to fix it

1. Visit yoursite.com/robots.txt to review your current rules
2. Use the robots.txt tester in Google Search Console under Settings to test specific URLs against your current file
3. Look for any Disallow rules that cover important directories like /blog/, /products/, or /services/
4. Remove or narrow any rules that are blocking content you want indexed
5. If you are running a JavaScript app, confirm your main JavaScript and CSS files are not blocked, as Googlebot needs them to render your pages
6. Submit the updated robots.txt to Search Console and monitor for changes in the Page Indexing report

Robots.txt vs. noindex: which to use

Issue 3: Duplicate content without canonical tags

When two or more URLs on your site return the same or very similar content, Google must decide which one to index. It often picks the wrong one, or skips both. Canonical tags solve this by explicitly telling Google which version is the authoritative page. Without them, duplicate content silently fragments your indexing and ranking signals.

Ecommerce and multi-location sites face this problem most often. A product page with filter parameters like /shoes?color=red and /shoes?color=blue may each return nearly identical content. Google's September 2025 Spam Update targeted this pattern specifically, flagging businesses that used identical location page templates across multiple cities, which led to direct indexing losses.

How to fix it

1. Crawl your site with Screaming Frog or Semrush and filter for duplicate page titles and duplicate body content
2. For parameter-generated duplicates, add a canonical tag on each variant pointing to the main URL
3. For near-identical location pages, rewrite each page with unique, location-specific content covering local details, team information, or service context specific to that area
4. Confirm all canonical tags in your page source match the URLs you are linking to internally
5. Avoid pointing canonicals to redirected or non-200 URLs

John Mueller has stated that "consistency is the biggest technical SEO factor." Mismatched canonical tags and conflicting internal links send opposing signals that confuse Google's indexing decisions.

Issue 4: Thin or low-quality content

Google uses content quality as a signal to decide whether to crawl and index a page. Pages with too little useful information, copied text, or content that does not serve a clear user need are deprioritized or removed from the index entirely. This is not a soft ranking preference. It is a hard filter.

Google's Gary Illyes confirmed this directly, stating: "The most important is quality. It's always quality. And I think externally, people don't necessarily want to believe it, but the quality, that's the biggest driver for most of the indexing and crawling decisions that we make." Google's combined core updates from 2023 and 2024 removed approximately 45% of low-quality content from search results.

What counts as thin content

• Pages under 300 words with no substantive information
• Product descriptions copied directly from a manufacturer or supplier
• Auto-generated or templated pages with only a few words of unique text
• Blog posts that summarize other articles without adding original perspective, data, or examples
• Tag archives and paginated category pages with little unique content

How to fix it

1. Run a content audit using Screaming Frog or Semrush to identify low word count pages
2. For each thin page, decide whether to expand, merge, or remove
3. Merge thin, closely related pages into one comprehensive piece
4. Delete pages that cannot be improved and set up 301 redirects to the closest relevant page
5. For pages you keep, add original research, examples, specific data, or first-hand commentary that competitors do not have
6. Ensure every page has a clear author attribution, particularly for content in YMYL (your money, your life) categories

"The fastest way to recover indexing coverage is to remove the pages dragging down your domain's quality signal. Merging five thin posts into one well-cited article consistently produces faster re-indexing than trying to pad each one individually."

Tanner Medina, Co-Founder and Chief Growth Officer, Launchcodex

Issue 5: JavaScript rendering blocking Googlebot

Googlebot can render JavaScript, but it does so in a second pass that may take days or weeks. If your site relies on JavaScript to load the main content, key navigation, or important page text, Googlebot may index a nearly empty page on its first pass. Sites built on React, Vue, or Angular with client-side rendering are most at risk.

Google's Martin Splitt has explained the crawl impact directly: each JavaScript API request a page makes counts against the site's crawl budget. Sites that load content through multiple JavaScript API calls burn through crawl allocation faster than sites that serve the same content server-side.

How to identify the problem

In Google Search Console, use the URL Inspection Tool and click "Test Live URL." Then compare the rendered page to your actual page in a browser. If the Search Console version shows less content, JavaScript rendering is likely the blocker.

How to fix it

1. Switch to server-side rendering (SSR) for critical content such as product descriptions, pricing, and page headings
2. Alternatively, implement static site generation (SSG) for content that does not change frequently
3. Use dynamic rendering as a short-term workaround, serving pre-rendered HTML to Googlebot and JavaScript-rendered pages to browsers
4. Ensure your robots.txt does not block the JavaScript or CSS files Googlebot needs to render your pages
5. Test rendering regularly with the URL Inspection Tool after any front-end framework updates

"When we audit SaaS products with indexing gaps, JavaScript rendering is the most overlooked root cause. Pricing pages, feature sections, and dynamic CTAs often load entirely through API calls, which means Googlebot sees a blank container and indexes nothing useful."

Derick Do, Co-Founder and Chief Product Officer, Launchcodex

Issue 6: Crawl budget waste from URL parameters and faceted navigation

Crawl budget is the number of URLs Googlebot will process from your site within a given period. When that budget is spent on duplicate or low-value URLs generated by filters, session IDs, or pagination, your most important pages get crawled less frequently or not at all. This is the primary indexing risk for large ecommerce and content-heavy sites.

Faceted navigation and URL parameters can multiply crawlable URLs tenfold. A clothing site with 5,000 products could generate 50,000 or more unique parameter combinations through color, size, and sort filters. Googlebot crawler traffic grew 96% from May 2024 to May 2025 according to Cloudflare data, and AI crawlers like GPTBot grew 305% over the same period. More bots competing for server resources makes crawl budget management more consequential than it was two years ago.

How to fix it

1. Audit your URL patterns in Google Search Console under Settings, crawl stats
2. Review server logs to identify which parameter-generated URLs Googlebot is spending time on
3. Add canonical tags on filtered and sorted pages pointing to the base URL
4. Use robots.txt to block URL patterns that generate no unique content, such as /products?sort=price
5. Configure your CMS or reverse proxy to stop generating parameter URLs for non-essential variations
6. Remove or consolidate paginated pages beyond page two or three where content value drops sharply
7. Set 410 status codes for permanently deleted pages so Googlebot stops requesting them

Issue 7: Orphan pages with no internal links

An orphan page is a page that no other pages on your site link to. Googlebot discovers most pages by following links. An orphan page may exist in your CMS, even in your sitemap, but Googlebot has no link path to reach it. Without discovery through internal links, it will sit at the bottom of the crawl queue indefinitely.

Orphan pages are common on large sites where content is published regularly without a structured internal linking strategy. Blog posts, campaign landing pages, and product pages added in bulk are the most frequent offenders.

How to fix it

1. Crawl your site with Screaming Frog and cross-reference crawled URLs against your XML sitemap to find URLs in the sitemap with zero internal links pointing to them
2. Create contextual internal links from related pages, blog posts, or hub pages to the orphaned URL
3. Add orphan pages to relevant navigation elements or category listings where appropriate
4. For new content, build an internal linking checklist into your publishing process before any page goes live

Issue 8: Slow page speed and poor Core Web Vitals

A slow-loading page gives Googlebot fewer pages to crawl per session. Google has confirmed that page speed affects crawl rate. It also influences the Page Indexing report, where poor Core Web Vitals appear in the "improve page experience" section. While speed alone rarely prevents indexing, sites with persistently slow response times see lower crawl frequency and, on competitive sites, indexing delays.

Core Web Vitals cover three performance signals: Largest Contentful Paint (LCP) for loading speed, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. Poor scores in competitive niches can contribute to deindexing when combined with other quality signals.

How to diagnose speed issues

Use Google PageSpeed Insights for page-level diagnostics and the Core Web Vitals report in Search Console for a site-wide view. Pay particular attention to LCP on mobile, as Google's mobile-first indexing means the mobile performance score carries more weight.

Quick fixes that reduce load time

• Compress and properly size images using modern formats like WebP
• Enable lazy loading for images below the fold
• Minify CSS and JavaScript files
• Use a Content Delivery Network to serve pages from servers closer to the user
• Eliminate or defer third-party scripts that block rendering
• Upgrade hosting if server response time is consistently above 200 milliseconds

Issue 9: Missing or broken XML sitemaps

An XML sitemap tells Google which pages exist on your site and when they were last updated. Without a sitemap, Googlebot discovers pages only through links. A broken sitemap, or one that lists redirected, noindexed, or deleted URLs, can actively mislead Googlebot and slow down indexing of new and updated content.

Sitemaps are especially important for new sites, sites with large numbers of pages, and sites with frequently updated content. Google's crawl budget guidance recommends keeping sitemaps updated and free of URLs that return error codes, redirects, or non-canonical status.

How to fix it

1. Check that your sitemap is submitted in Google Search Console under Sitemaps
2. Review the sitemap for errors. Sitemaps that list 404 or 301 URLs waste crawl budget.
3. Remove redirected URLs, noindexed pages, and deleted pages from the sitemap
4. Set a schedule to regenerate your sitemap automatically whenever content is published or removed
5. If your site has more than 50,000 URLs, split the sitemap into smaller topic-based sitemaps and reference them from a sitemap index file
6. Add a reference to your sitemap URL in your robots.txt file

Issue 10: Manual actions and site-level penalties

A manual action is a penalty applied directly by a Google reviewer when a site violates Google's spam guidelines. Unlike algorithmic filtering, manual actions are explicit. They appear in Google Search Console under Security and Manual Actions and directly suppress or remove affected pages from the index until the issue is resolved.

Common triggers include paid link schemes, hidden text, cloaking, sneaky redirects, and spammy user-generated content. Manual actions can affect individual pages or an entire domain. Either way, no amount of technical optimization will restore indexing until the root violation is addressed and a reconsideration request is submitted.

How to fix it

1. Go to Security and Manual Actions in Search Console and read the description of the action carefully
2. Identify the specific pages or patterns triggering the action
3. Remove or correct the violating content, links, or behavior
4. If the issue involves unnatural backlinks, compile a disavow file and submit it through the Search Console Disavow Links tool
5. Submit a reconsideration request through Search Console once all violations are corrected
6. Document what was changed and why in the request to give reviewers full context
7. Expect a response within several weeks, though timing varies

How to diagnose "Discovered – currently not indexed" and "Crawled – currently not indexed"

These two status labels appear more than any other in the Page Indexing report, and they require completely different responses. "Discovered – currently not indexed" is a crawl prioritization problem. "Crawled – currently not indexed" is a content quality problem. Treating one as the other wastes time and produces no improvement.

Both statuses appear in the Not Indexed section of the Page Indexing report in Google Search Console. They are not errors in the technical sense — Google is not reporting a broken tag or a blocked URL. It is reporting a judgment call. Understanding what drove that judgment is the only way to resolve it.

"Discovered – currently not indexed"

This status means Google found the URL, typically through your sitemap or an internal link, but has not yet crawled it. The page has not been visited. Google knows it exists and has put it in a queue, but it has not been prioritized for crawling.

The underlying cause is almost always crawl budget pressure or weak page authority signals. Google allocates crawl capacity based on a site's perceived value and server health. Pages with few or no internal links pointing to them, pages on sites with large volumes of low-value URLs, and pages on new domains with limited external authority all sit lower in the crawl queue.

What causes it:

• Page exists only in the sitemap with no internal links pointing to it (an orphan page)
• Site has a large number of URLs competing for crawl budget, including parameter duplicates or thin paginated pages
• Domain is new or has low external authority, so Googlebot allocates fewer crawl resources to it
• Server response times are slow, which reduces how many pages Googlebot crawls per session
• Page was recently published and has not yet been reached in the crawl cycle

How to fix it:

1. Add at least two to three contextual internal links to the affected page from higher-authority pages on your site
2. Include the URL in your XML sitemap and ensure the sitemap is submitted and error-free in Search Console
3. Use the URL Inspection Tool to request indexing for individual priority pages
4. Reduce crawl budget waste by consolidating parameter URLs, removing thin pages, and setting 410 status codes on permanently deleted pages
5. Improve server response times so Googlebot can process more pages per crawl session
6. If the page is new, allow two to four weeks before treating the status as a persistent problem — some delay after publication is normal

A page stuck in "Discovered – currently not indexed" is usually a crawl access problem, not a content problem. Fix the internal linking and reduce crawl waste first. Content improvements will not move these pages if Googlebot has never visited them.

Why indexing now affects your AI search visibility

A page Google has not indexed cannot appear in AI Overviews, and it is largely invisible to other generative AI systems that rely on the Google index for source material. Fixing indexing issues is the first step in any strategy to appear in AI-generated answers.

AI Overviews appeared in nearly 20% of Google searches as of September 2025. Research shows that only 7.2% of domains appear in both Google AI Overviews and LLM results from platforms like ChatGPT or Perplexity. The gap is partly an indexing problem. Pages that are not in Google's index are not available as source material for AI systems that pull from it.

Structured data is a specific element that improves both indexing eligibility for rich results and visibility in AI-generated answers. Pages with valid schema markup show 30 to 40% higher visibility in AI-generated responses compared to pages without it. If your site does not use structured data for articles, products, FAQs, or local business information, adding it is a high-return fix that costs little to implement.

The indexing and GEO connection

• Google indexes a page and adds it to its database
• AI Overviews pull from indexed pages when generating answers
• Generative AI platforms like Perplexity also pull from high-ranking indexed pages
• An unindexed page is invisible at every layer of this chain

The practice of optimizing content to appear in AI-generated answers is called GEO (Generative Engine Optimization). Indexing is the prerequisite. No GEO tactic works on a page Google has never added to its index.

Fix the foundation before anything else

Most indexing problems follow predictable patterns. A robots.txt rule that was never cleaned up. A CMS template that left noindex tags on live pages. A product catalog generating thousands of near-identical parameter URLs. These are solvable problems that produce measurable results when fixed.

Start with Google Search Console. The Page Indexing report shows you exactly what is wrong and where. Work through each issue type from most pages affected to least. Prioritize technical blocks like robots.txt and noindex errors first, because they prevent Google from seeing your content at all. Then address content quality, crawl budget, and site structure.

John Mueller stated plainly in 2025: "Consistency is the biggest technical SEO factor." Pages that send conflicting signals through mismatched canonicals, inconsistent internal links, and mixed HTTP/HTTPS status are the hardest for Google to process. Align every signal and Google's job becomes straightforward.

If your site has large-scale indexing gaps across hundreds or thousands of pages, a structured technical SEO audit paired with a content quality review is the most efficient path to recovery. At Launchcodex, this is one of the first diagnostic steps we run for clients whose organic traffic is underperforming relative to the volume of content they publish.

FAQ

How long does it take for Google to index a page after I fix the problem?

Most pages that meet Google's quality and technical requirements are indexed within four to eight weeks after fixes are applied. Pages on high-authority domains with strong internal linking may be indexed faster. Requesting indexing via the URL Inspection Tool can accelerate the process for individual pages, but it does not guarantee timing.

What is the difference between "Crawled, currently not indexed" and "Discovered, currently not indexed"?

"Crawled, currently not indexed" means Google visited the page but chose not to add it to the index, usually due to thin content or quality signals. "Discovered, currently not indexed" means Google found the URL but has not yet prioritized it for crawling, often due to crawl budget constraints or low page authority.

Do I need an XML sitemap if my site has good internal linking?

Sitemaps and internal linking work together. Good internal linking helps Googlebot discover pages through crawl paths. A sitemap ensures Google knows about every page, including those that may not be well-linked yet. Both are recommended for most sites, and required for sites with more than a few hundred pages.

Can a single low-quality section hurt indexing across my whole site?

Yes. Google evaluates site quality at a domain level. If a large portion of a site contains thin, duplicate, or low-value content, it can reduce how frequently Google crawls and indexes the rest of the site. John Mueller has confirmed this directly.

Does fixing indexing issues help with AI Overview visibility?

Yes. AI Overviews pull from Google's index. A page that is not indexed cannot appear as a source in AI-generated answers. Fixing indexing issues is the foundational step in any GEO strategy.

How do I check if my JavaScript is blocking Googlebot?

Use the URL Inspection Tool in Google Search Console. Click "Test Live URL" and review the rendered HTML. Compare it against what you see in your browser. If the Search Console version shows less content, JavaScript rendering is likely preventing Googlebot from seeing your full page.