How to Fix Indexing Issues in Google Search Console: A Step-by-Step Guide

You spent hours creating that perfect landing page. It looks beautiful. The copy's compelling. You've triple-checked it's live on your website.

But in Google Search Console, it says "Discovered – currently not indexed."

It's still not showing up in search results weeks later.

And you have no idea why.

This is one of the most common issues I see in our technical SEO audits—and honestly, it's more frustrating than ranking issues because the problem feels invisible. Your page exists. It's on your server. But Google won't touch it.

The thing is, there's usually a reason. And once you understand what that reason is, the fix is straightforward.

I've helped fix over 800 indexing problems for UK businesses, and most fall into a handful of predictable categories. This guide covers exactly what causes indexing issues and the step-by-step process to fix them.

Understanding Google's Indexing Process

Before we get into fixes, you need to understand how Google indexing actually works. Most people get this wrong, which is why they waste time on the wrong solutions.

Google's indexing process has three stages:

Stage 1: Discovery – Google's crawler (Googlebot) finds your page through links, sitemaps, or manual submission. The page is "discovered."

Stage 2: Crawling – Googlebot actually visits your page, reads the HTML, CSS, and JavaScript, and understands what it's about. At this point, Google can index it.

Stage 3: Indexing – Google adds the page to its index, meaning it's eligible to appear in search results.

When you see "Discovered – currently not indexed" in Google Search Console, you're stuck between stages 2 and 3. Google found your page but decided not to index it. Understanding why is the key to fixing it.

The 8 Most Common Causes of Indexing Issues

1. Noindex Tag Present

This is the most common cause I see, and it's usually accidental.

If you have a <meta name="robots" content="noindex"> tag on your page, Google won't index it. This is completely intentional—you're telling Google "don't index this"—but many businesses add it during development and forget to remove it.

How to check:

Right-click on your page and select "View Page Source"
Press Ctrl+F and search for "noindex"
If you find <meta name="robots" content="noindex"> or <meta name="googlebot" content="noindex">, that's your problem

How to fix it:

Remove the noindex tag from your page
If you have it in your WordPress settings or site-wide configuration, update that
For WordPress, go to Settings → Reading and ensure "Discourage search engines from indexing this site" is unchecked
Request indexing again in Google Search Console

Why this happens: Developers add noindex tags to prevent staging sites from being indexed, then move the code to production by mistake.

2. Blocked by Robots.txt

Your robots.txt file tells Google which pages it can and cannot crawl. If you're accidentally blocking your important pages here, Google won't even try to index them.

How to check:

Visit yoursite.com/robots.txt
Search for "Disallow:" entries
If your disallowed paths include your new pages, that's the issue

How to fix it:

Edit your robots.txt file
Remove or modify the Disallow entries blocking your pages
Ensure important directories like /blog or /services are NOT blocked
Submit your updated robots.txt in Google Search Console
Request indexing again

Example of a problem robots.txt:

User-agent: *
Disallow: /blog/
Disallow: /services/

This blocks ALL pages in these directories. Usually, you want:

User-agent: *
Disallow: /admin/
Disallow: /private/
Disallow: /temp/

3. Duplicate Content and Canonical Tag Issues

If Google thinks your page is a duplicate of another page, it won't index both. Canonical tags tell Google which version to index.

If your canonical tag points to the wrong page, Google indexes that instead—or skips both.

How to check:

Right-click → View Page Source
Search for <link rel="canonical"
If the canonical URL is different from the page you're viewing, Google indexes the canonical URL instead
If the canonical is broken or points to a deleted page, Google gets confused

How to fix it:

Every page should have a self-referential canonical tag (pointing to itself)
If you have multiple versions of the same content (HTTP and HTTPS, www and non-www), use canonical to point to the preferred version
Ensure canonical URLs are absolute (not relative)
Avoid canonical chains (page A → page B → page C)

Correct canonical tag:

<link rel="canonical" href="https://yoursite.com/page-name/" />

4. New Pages Not Submitted or Linked

Google doesn't automatically crawl brand new pages. It needs a reason to visit them. If your page isn't linked from anywhere and you haven't submitted it to Google Search Console, Google might not find it for months.

How to check:

In Google Search Console, go to Coverage
Filter by "Discovered – currently not indexed"
Look at the date discovered. If it's recent but you created the page weeks ago, you never submitted it

How to fix it:

Submit the URL directly: In Google Search Console, use the "Inspect URL" tool and click "Request indexing"
Link to the page internally: Add links from your homepage or other high-authority pages on your site
Add to your sitemap: Ensure new pages are included in your XML sitemap and the sitemap is submitted to Google Search Console
Wait 3-7 days: After requesting indexing, it typically takes a week for pages to be indexed

5. Low-Quality or Thin Content

Google sometimes doesn't index pages it deems low-quality or thin. If your page has very little content—say, under 300 words with no real value—Google might deprioritise it.

How to check:

Look at your page content word count
Is there real value here, or is it a duplicate of content elsewhere on your site?
Does the page match the user's search intent?

How to fix it:

Expand your content to at least 800 words
Add real value (data, insights, examples)
Ensure your content answers the user's actual question
Reduce internal duplicate content (don't create similar pages targeting the same keywords)

6. Redirect Chains

If your page redirects to another page, which redirects to another, Google gets confused and stops indexing.

How to check:

Visit your page in a browser
Does it redirect somewhere? Use this tool: https://redirect-checker.org/
Does the destination redirect again? That's a chain.

How to fix it:

Use direct redirects only (Page A → Final Destination, not A → B → C → Final)
Update any links pointing to intermediate redirects
Use 301 redirects for permanent moves, not 302 temporary redirects

7. Server Issues and Crawl Errors

If your server returns errors when Google tries to crawl, indexing stops.

How to check:

In Google Search Console, go to Coverage
Look for "Error" status pages
Click through to see what errors Google encountered

Common crawl errors:

404 (Page not found) – the page was deleted
500, 502, 503 (Server errors) – your server is down
Timeout errors – your server is too slow

How to fix it:

For 404 errors: Either restore the page or use a 301 redirect to a relevant page
For server errors: Contact your hosting provider
For timeouts: Optimise your page (reduce database calls, compress images, enable caching)
Request Google to re-crawl after fixing

8. JavaScript Rendering Issues

Modern websites use JavaScript to load content. If your page content is loaded via JavaScript and Google can't render it properly, the page won't index.

How to check:

In Google Search Console, use the URL Inspection tool
Under "Inspect URL," click "View crawled page"
Compare what you see to what your browser shows
If they're different, Google didn't render your JavaScript

How to fix it:

Use server-side rendering for important content
Ensure important text and structured data load in the initial HTML (not via JavaScript)
Test your page with the URL Inspection tool in Search Console
For dynamic content, use <noscript> tags to provide fallback content

Step-by-Step Process to Fix Indexing Issues

Now you know the common causes. Here's the process to diagnose and fix your specific problem:

Step 1: Identify Which Pages Aren't Indexed

Go to Google Search Console → Coverage tab.

Filter by status:

"Excluded" (intentionally not indexed)
"Discovered – currently not indexed" (found but not indexed)
"Error" (technical problems preventing indexing)

Focus on pages you want indexed but show as excluded or not indexed.

Step 2: Use the URL Inspection Tool

Click on your problem page URL and open it in Google Search Console's URL Inspection tool.

This shows:

What Google actually sees when it crawls your page
Any blocking issues
Why Google isn't indexing it

Look for the message "URL is available to Google" or error messages explaining why it's not.

Step 3: Check for Common Technical Issues

Work through this checklist:

Noindex tag? View page source, search "noindex" → Remove if present
Robots.txt blocking it? Check yoursite.com/robots.txt
Canonical tag pointing elsewhere? View source, check <link rel="canonical"
Server errors? Are there 4xx or 5xx responses?
Redirect chains? Use a redirect checker tool
Thin content? Is the page under 300 words?

Step 4: Request Indexing

Once you've fixed the issue:

Go to Google Search Console
Use "Inspect URL" tool
Click "Request indexing"
Google will re-crawl and re-index

Note: Just because you request indexing doesn't guarantee it. If the underlying issues remain, the request fails.

Step 5: Monitor Progress

After requesting indexing:

Check back in 3-7 days
Use Google Search Console's Coverage report to confirm the page moved from "not indexed" to "indexed"
Search for the page on Google with site:yoursite.com/page-url (might take up to 2 weeks to appear in regular searches)

Pages That Should Be "Not Indexed" (Intentionally)

Not all "not indexed" pages are problems. Some should NOT be indexed:

Intentionally exclude these pages:

Login/registration pages
Private customer dashboards
Thank you pages after form submissions
Admin pages
Duplicate product pages with different parameters
Staging/test pages
PDF download pages that shouldn't rank

For these, use the noindex tag intentionally. It's not a problem.

Quick Wins to Boost Indexing

Beyond fixing issues, here's how to accelerate indexing:

1. Improve internal linking: New pages index faster when linked from your homepage or high-authority pages.

2. Add to XML sitemap: Ensure all new pages are in your sitemap.xml file.

3. Update frequently: Fresh content indexes faster. Add an update date to important pages.

4. Use Google Search Console sitemap submission: This isn't automatic. You must submit your sitemap in GSC.

5. Get external links: Pages with backlinks index faster. One quality external link speeds up indexing significantly.

FAQs: Indexing Issues Explained

How long does it take to index a page after requesting it? Usually 3-7 days, but can take up to 2 weeks. Some pages index in hours, others take a month. This depends on your site's authority and crawl frequency.

Will removing noindex tag cause previously unindexed pages to suddenly index? Yes, typically within 7 days. Google will re-crawl those pages and add them to the index.

What's the difference between "Discovered" and "Not indexed"? "Discovered" means Google found the page but hasn't indexed it. "Crawl anomaly" or "Not found" usually means technical issues. Both prevent ranking.

Can I force Google to index a page? Not really. You can request indexing, but if the page has quality issues or blocking issues, Google will decline. The page must be worth indexing.

Does submitting my sitemap guarantee indexing? No. Sitemap submission tells Google where your pages are, but Google still decides independently whether to index each one. A good sitemap + request indexing + quality content = best results.

Why does Google Search Console say "indexed" but the page doesn't show in search results? Indexed ≠ ranking. Your page might be indexed but not ranking for your target keyword. This is a different issue (usually content quality or keyword relevance). Work on optimising for your target keyword if it's indexed but not ranking.

Should I worry about pages in "Excluded" status? Only if you want them indexed. Excluded pages are intentionally kept out (usually due to robots.txt, noindex, or canonicalisation). If they should be indexed, investigate why.

Common Mistakes People Make (And How to Avoid Them)

Mistake 1: Requesting indexing for the wrong URL Don't request indexing for yoursite.com/page. If your site uses www, request www.yoursite.com/page. URL format matters.

Mistake 2: Waiting too long to check Check your Coverage report within a week of publishing. The longer you wait, the harder it is to diagnose why something didn't index.

Mistake 3: Creating too many similar pages If you create 10 pages targeting the same keyword, Google indexes one and marks the others as duplicates. Focus on one primary page per topic.

Mistake 4: Forgetting to remove noindex tags before launch Always double-check your staging site didn't accidentally get indexed with noindex tags included in production.

Mistake 5: Ignoring server-side errors A page returning 500 errors or timing out won't index, no matter what else you do. Fix server issues first.

Get Expert Help with Your Indexing Issues

If you've worked through this guide and still have pages not indexing, it's time for a proper technical SEO audit. Most indexing issues have a root cause that a trained SEO professional can identify within minutes—something that might take you days to figure out alone.

At NetTrackers, we specialise in diagnosing and fixing indexing problems for UK businesses. We can:

Audit your entire Google Search Console Coverage report
Identify exactly why each problematic page isn't indexing
Fix the issues (or provide clear instructions for your developer)
Get your pages indexed and ranking faster

We offer a complimentary technical SEO audit for UK business owners who want an expert review of their indexing issues and a clear action plan to fix them.

Book Your Free Technical SEO Audit – 30 minutes, no obligation, exactly what's holding your pages back.

Your Next Action

Don't let pages you've worked hard to create stay hidden in Google Search Console.

Go to Google Search Console now – Check your Coverage report
Identify 1-3 pages that should be indexed but aren't – Write down their URLs
Work through the checklist above – 90% of the time, one of these 8 causes applies
Request indexing after fixing – Give Google a week to re-index

If you get stuck or want an expert review of your entire site's indexing health, that's what we're here for.

Get a Free Technical SEO Audit – Identify Your Indexing Issues Today