Google may leave a page out because it can’t access it, sees an indexing restriction, considers it a duplicate, or hasn’t selected it for inclusion. Not every exclusion needs fixing, so start by identifying whether the missing page should appear in search.
For a small business or agency, Google indexing issues matter most when they affect service pages, location pages and contact routes. Begin with those pages, then follow the evidence in Google Search Console.
Key takeaways
- Check individual URLs before changing site-wide settings. An excluded thank-you page is usually expected; an excluded service page needs investigation.
- Fix access problems, indexing restrictions and conflicting canonical signals before requesting indexing.
- Sitemap submission and indexing requests don’t guarantee inclusion. Measure recovery through indexed pages, search activity and real enquiries.
Diagnose Google indexing issues in Search Console
Separate crawling, indexing and ranking
Crawling is when Googlebot fetches a page. Indexing is when Google processes its content and selects a version for its index. Ranking determines where an indexed page appears in search results.
A page can be indexed but attract no visits. If the URL Inspection tool says it’s indexed, check search demand, relevance and competition in Performance > Search results.
Also check that you’re viewing the right property. A URL-prefix property for a non-www address doesn’t cover the separate www version. Our Google Search Console setup guide explains the property options.
Inspect an important missing URL
Open Indexing > Pages, sometimes labelled Index > Pages. Select Not indexed and review “Why pages aren’t indexed”. The Page indexing report lists these statuses. Google’s Page indexing report guidance explains each one.
Don’t confuse “Improve page appearance” notices with reasons for exclusion.
- Enter the full page address in the URL Inspection tool.
- Review its indexing status, last crawl and selected canonical.
- Select Test live URL to check current access.
- Open the tested page details and rendered screenshot.
The indexed record shows Google’s previous findings. A successful live test doesn’t prove the page is indexed or guarantee future inclusion.
Fix robots.txt access blocks and server failures first
Remove unintended noindex and robots.txt restrictions
Google indexing issues often stem from access restrictions or server failures.
An accessible page with a noindex instruction won’t enter Google’s index once Google processes it. Check the HTML robots meta tag and the HTTP X-Robots-Tag header.
Remove unintended restrictions from pages that should appear. In WordPress, check Settings > Reading and your SEO plugin’s page settings. Keep pages marked noindex out of the XML sitemap.
robots.txt controls crawling, not guaranteed exclusion. Google can discover a blocked address through links and report “Indexed, though blocked by robots.txt”.
Google must be allowed to crawl a page to read its
noindexinstruction. A robots.txt block can prevent Google from seeing the exclusion you intended.
Restore pages returning server or access errors
A 5xx response means the server couldn’t fulfil Google’s request. Use URL Inspection to check the response Googlebot receives, then investigate application errors, resource limits, timeouts and recent updates with your web hosting provider.
For 401 or 403 responses, inspect authentication, firewall and security-plugin rules. Public service pages shouldn’t require a login or block legitimate Googlebot requests.
After the page loads reliably, run another live test and request indexing. Google’s crawl-error troubleshooting guidance helps distinguish server availability problems from other failures.
Avoid changing titles or canonical tags while the underlying server failure remains unresolved.
Resolve missing pages and redirect errors
Distinguish genuine 404s from soft 404s
A genuine 404 error is appropriate when a page no longer exists and has no relevant replacement. Google treats 410 responses the same as 404s and groups them together in its report.
These exclusions don’t normally require repair. Restore an accidentally deleted service page, and remove obsolete addresses from internal links and sitemaps.
A soft 404 returns 200 OK but appears empty, missing or unavailable. Broken JavaScript can leave Google seeing a blank page even when your browser displays content.
Restore meaningful content or return a real 404 or 410. Redirecting every removed page to the homepage can also cause soft 404 problems.
Repair faulty redirects without unnecessary chains
“Page with redirect” is usually expected: Google indexes the destination rather than the old address.
“Redirect error” needs action. Causes include excessive chains, loops, overlong destination URLs, and bad or empty addresses within the chain.
Replace chains with a direct 301 redirect. Make the 301 redirect permanent and point it to the closest relevant replacement. Then update internal links and sitemap entries to use that destination.
After a migration, update links in your Google Business Profile, email marketing and social media profiles too. Consistent digital branding won’t prevent broken journeys if those channels still send clients to retired addresses.
Correct duplicate and canonical signals
“Duplicate without user-selected canonical” means Google found similar pages without a clear preferred version. “Duplicate, Google chose different canonical than user” means Google selected another URL despite your preference.
Inspect both addresses. If they contain substantially the same information, choose the version customers should reach.
Set the appropriate canonical signal, then use that URL consistently in internal links and the XML sitemap. Redirect redundant versions that no longer need to exist. The preferred URL should match the canonical tag, since conflicting links and redirects can weaken your preference.
If two service pages genuinely deserve separate indexing, give each a distinct purpose and useful content. A page about web design and another about ongoing web development should answer different buying questions.
“Alternate page with proper canonical tag” usually needs no action when the chosen canonical is correct.
Handle discovered and crawled exclusions differently
Discovered, currently not indexed
Google knows the URL exists but hasn’t crawled it. This can happen when Google postpones fetching pages to avoid overloading a server.
First, check how Google found the page. An orphan page has no internal links, so connect it through relevant navigation and established pages that receive traffic. Our website navigation guidance explains how to connect related services.
Submit an updated, working XML sitemap with your preferred, indexable URLs.
On larger sites, including those exceeding 10,000 pages, check for duplicate URL generation and server capacity if crawl budget may be a concern. The 10,000-page figure isn’t a universal crawl budget threshold. Google’s Crawl Stats report can reveal availability problems and changes in crawling activity.
Crawled, currently not indexed
Google fetched the page but hasn’t indexed it. This status doesn’t mean indexing is guaranteed after a waiting period, and you don’t need to resubmit an unchanged page.
Review what the page contributes. Near-identical service-area pages, empty categories and generic copy may offer little reason for Google to index each page separately.
For local SEO, explain your genuine service coverage and add relevant project evidence where available. Avoid swapping place names across otherwise identical pages.
If you use AI for small-business content, review its accuracy and usefulness before publishing. Producing more repetitive pages won’t resolve weak content.
Also inspect Google’s rendered view. Missing main content can point to a technical problem rather than an editorial one.
Validate fixes and monitor recovery
After fixing a shared cause behind Google indexing issues, test representative URLs from each affected template. A correction on one page doesn’t prove that every service page is free of indexing issues.
Use Validate Fix when it’s available for the issue. Google says validation typically takes up to about two weeks, but some cases take several weeks or longer.
Request indexing for important corrected pages where appropriate, rather than repeatedly submitting unchanged URLs. There’s no guaranteed indexing deadline.
Compare the repair date with Google’s last crawl date and the report’s update date. The Page indexing report may still show an older exclusion until Google revisits the page and refreshes its records.
For sudden site-wide changes, compare recent deployments, server logs, manual actions and security warnings. Google’s Search Status Dashboard can help identify a confirmed wider incident before you make disruptive site changes.
Build these checks into regular website maintenance, especially after launches, migrations and major plugin updates.
For agencies needing technical support across client sites, See how we collaborate with creative agencies.
Frequently asked questions
How do I stop Google indexing a page?
For a public page that should stay out of search, allow crawling and apply noindex. For confidential material, use authentication rather than relying on search-engine instructions.
Search Console’s temporary Removals tool hides results for about six months, not 90 days. Permanent exclusion still requires an appropriate noindex instruction, deletion or access restriction. A relevant redirect suits content that has moved.
Why is an indexed page still getting no enquiries?
Indexing only makes a page eligible to appear. Review impressions, queries and clicks in Search Console, then compare visits with tracked enquiries.
This separates digital marketing and lead generation problems from technical exclusions. Conversion optimisation also requires a mobile-responsive page and a working contact route. Test any systems and automation handling the enquiry afterwards, because a lost submission can look like a traffic problem.
Keep the focus on pages that bring in work
Google indexing issues are easier to resolve when you start with one important URL and its reported status. Fix the underlying cause, test the live page and allow time for Google to revisit it.
Review key reports monthly and after major changes. Recovery means useful pages can appear in search and customers can complete their enquiry, not that every excluded URL disappears from Search Console.
