You publish a page, wait a few days, then search site:yourdomain.com/the-page and nothing comes back. I can imagine if your first instinct is to assume that Google penalized you. Well, experience has shown that chasing a penalty is hardly the case. Most times, the issue is that you need to know how to fix a website that Google won’t index, and you are good.
Yes, that’s why this guide works through indexing problems in the order they’re most likely to be the real cause. You will learn how to confirm each one in Google Search Console, and how to identify the problem on a single page or your entire site.
Quick answer
A website Google won’t index usually comes down to one of a handful of causes. Common causes include an accidental noindex tag, a robots.txt block, a canonical tag pointing elsewhere, a non-200 status code, thin or duplicate content, or the page simply not being discoverable through links or a sitemap. Read the rest of the article before changing anything.
How to Confirm An Indexing Problem
Before troubleshooting anything, you need to verify if it’s an indexing problem. Here are two ways to do that:
- Search site: yourdomain.com/the-exact-url directly in Google. If it appears, that means your page is indexed. So, your problem may be with ranking.
- Use the URL Inspection tool in Google Search Console. Paste in the exact URL, and it will tell you whether the page is fine. If it is not, it will provide the specific reason.
The URL Inspection tool is the more reliable option, since it pulls current data directly from Google’s index. However, you can always confirm through Search Console before making changes.
Is “Not Indexed” and “Not Ranking” the Same Problem?
If you are not able to identify the ideal problem, you will only be trying to fix what not. One of the misidentified problems in Search Engine Optimization (SEO) is people thinking “not indexed” is the same problem as “not ranking.”
An indexed page but not ranking has a competitive or relevance problem. A page that isn’t indexed at all has a much more basic problem. For all we know, Google hasn’t added it to the index in the first place. The easiest way to explain indexing is that something technical is blocking it or something about its quality disqualified it before ranking was ever a consideration.
If your site: search or URL Inspection check confirms the indexed page, that’s a ranking and content-quality question. You can check the Rankova blog for different topics that address the problem. If otherwise, everything below assumes the page genuinely isn’t in the index.
What Your Page Indexing Report Is Telling You
Google Search Console’s Page indexing report (in the left navigation under Indexing) groups every URL Google knows about into specific status labels. Knowing what each one means saves a lot of wasted troubleshooting:
| Status | What it means | What to do |
| Crawled – currently not indexed | Google visited the page but chose not to index it | Usually a content quality or duplication issue |
| Discovered – currently not indexed | Google knows the URL exists but hasn’t crawled it yet | Often a crawl budget or discoverability issue |
| Excluded by ‘noindex’ tag | A noindex directive is telling Google not to index it | See section 1 |
| Blocked by robots.txt | Your robots.txt file is preventing the crawl | See section 2 |
| Alternate page with proper canonical tag | Google folded this URL into a different canonical URL | See section 3 |
| Duplicate without user-selected canonical | Google sees this as a duplicate and picked its own canonical | See section 3 |
| Page with redirect | The URL redirects elsewhere, so the original isn’t indexed | Confirm the redirect target is correct and indexed instead |
| Not found (404) | The page doesn’t exist at that URL as far as Google can tell | See section 4 |
| Soft 404 | The page returns a success code but looks empty or broken to Google | See sections 4 and 6 |
How to Fix a Website That Google Won’t Index
Here is how to fix a website that Google won’t index;
- Check for an Accidental Noindex Tag
This is the single most common cause, and the easiest to miss, because it’s usually accidental. It could be a staging-site setting that you pushed to production, a plugin default, or a developer forgetting to remove a noindex tag after launch.
Check the page’s HTML <head> for:
<meta name=”robots” content=”noindex”>
You can also check the HTTP response headers for an X-Robots-Tag: noindex directive. This also achieves the same thing without appearing in the page’s visible code. If either is present and shouldn’t be, remove it.
If you are on WordPress, also check your site’s visibility setting under Settings → Reading. Note that “Discourage search engines from indexing this site” adds a sitewide noindex tag that’s trivially easy to leave switched on after a migration.
- Check Robots.txt for Accidental Blocks
Your robots.txt file, found at yourdomain.com/robots.txt, can block Google’s crawlers from ever reaching a page or an entire section of your site. Search Console’s robots.txt report shows exactly what Google sees when it checks the file.
Fix the rule so it only blocks what you intend to keep out of search (admin areas, internal search results, duplicate parameter URLs).
Note that robots.txt controls crawling and not indexing directly. So, a page blocked by robots.txt can still occasionally get indexed with no content shown, based on external links pointing to it.
- Check Your Canonical Tags
A canonical tag tells Google which version of a page is the “real” one when duplicates or near-duplicates exist. Misconfigured canonicals are a frequent and self-inflicted cause of indexing problems:
- A canonical tag pointing to a completely unrelated page
- Every page on the site canonicalizing to the homepage (a common templating mistake)
- A canonical pointing to a URL that itself redirects or 404s
Check the declared canonical in your page’s source code, then compare it against the “Google-selected canonical” field in the URL Inspection tool. When these two disagree, Google is telling you it doesn’t trust your declared canonical. This can happen because of thin or duplicate content.
- Confirm the Page Returns a Clean Status Code
A page has to return a proper 200 OK status to be indexed. Common problems here are:
- 404 or 410 errors on a page that should exist, often from a broken deployment or a URL that changed without a redirect.
- Redirect chains, where a URL redirects to another URL that redirects again, sometimes multiple times, which can cause Google to give up before reaching the final destination.
- Soft 404s, where the server returns a 200 status but the page itself displays a “not found” or empty message. These are deceptively common after a CMS migration or a broken template, and Google treats them as effectively non-existent even though the status code looks fine.
Check status codes with your browser’s developer tools (the Network tab) or a crawler tool, and fix broken links, redirect chains, and soft 404s directly at the source.
- Make Sure the Page Is Actually Discoverable
Google finds pages by following links and reading sitemaps. A page with no internal links pointing to it, missing from your XML sitemap, and with no external references is effectively invisible.
The solution is to;
- Link to the page from somewhere Google already crawls regularly, a category page, your blog index, or a relevant older article.
- Ensure you include your page in the sitemap. Submit the sitemap and ensure it’s error-free in Search Console’s Sitemaps report.
- For a brand-new page, don’t expect instant results. Even with everything correct, initial discovery and crawling can take anywhere from a few days to a few weeks.
- Address Thin, Duplicate, or Low-Value Content
This is the least technical cause and the one people resist the most, because it means the fix isn’t a settings change. Rather, it’s rewriting the page. Google increasingly declines to index pages it judges as low-value relative to what’s already indexed for similar queries.
The fix is genuinely straightforward to describe and harder to execute. Make the page say something a similar page doesn’t already say. Add real detail, original data, a distinct angle, or specific local information that can’t be copy-pasted across ten near-identical pages. If you have many thin pages of the same type, consider consolidating the weakest ones into combined pages rather than trying to rescue each individually.
If you are not sure how to go about this, contact Rankova to get the best help you need.
- Check Crawl Budget on Larger Sites
For a small site, crawl budget is rarely the issue. For a large one, it can be. Google allocates a limited amount of crawling attention to each site. If that attention gets spent crawling low-value URLs, your genuinely important pages may not get crawled as often.
- Reduce the number of low-value URLs Google has to work through. You can block the unnecessary ones in robots.txt.
- Fix slow server response times, since a slow site gets crawled less frequently.
- Clean up broken links and redirect chains, both of which waste crawl budget on dead ends.
- Rule Out Manual Actions and Security Issues
While this is rare, don’t rule it out quickly since it changes the entire fix. Check Search Console’s Security & Manual Actions section. A manual action means a human reviewer at Google flagged a violation of their guidelines. Also, it requires a specific resolution and reconsideration request. A flagged security issue will also block indexing until it’s resolved and verified clean.
- Check for JavaScript Rendering Problems
If your site relies heavily on JavaScript to load content, there’s a real risk that what a visitor’s browser renders and what Googlebot sees during its initial crawl are different things. Use the URL Inspection tool’s “View Crawled Page” feature to see a screenshot and the rendered HTML as Google’s rendering process saw it. If your main content is missing from that rendered view, that’s the problem. You may need a developer to implement server-side rendering, static generation, or dynamic rendering for the affected pages.
- Request Indexing, Last, Not First
Clicking “Request Indexing” in the URL Inspection tool is the step most people try first. It should be the step you try last. Requesting indexing on a page that still has a noindex tag, a robots.txt block, or thin content just wastes the request and teaches you nothing. Rather, fix the cause, validate the fix, then request indexing, and expect it to take anywhere from a few days to about two weeks for the change to fully register.
A Note on Brand-New Sites and Domains
If your entire domain is new, some delay is normal. Honestly, that isn’t a sign anything is broken. Google tends to crawl new sites more cautiously at first, gradually increasing crawl frequency and indexing depth as it builds confidence in the site’s structure and content quality. A brand-new site with clean technical setup and genuinely useful content should still see pages indexed within days to a few weeks. So, if you are expecting full-site indexing on day one, that is not realistic.
Mistakes That Keep Pages Stuck
Here are mistakes that keep your pages stuck;
- Repeatedly clicking “Request Indexing” without fixing anything.
- Confusing “crawled” with “indexed.”
- Using robots.txt to try to remove an already-indexed page.
- Ignoring the mobile version of the page.
- Assuming every “Excluded” status is a problem.
Frequently Asked Questions About a Website that Google Won’t Index.
Here are frequently asked questions about a website that Google won’t index;
Question 1: How long does it take for Google to index a page after fixing the issue?
Once you fix the underlying cause and you have requested indexing, it takes anywhere from a few days to about two weeks for Google to recrawl and update the page’s status.
Question 2: Does a low domain authority stop Google from indexing pages?
Domain authority and trust influence how often and how deeply Google crawls a site. A less established site with clean technical setup and genuinely useful content will still get indexed.
Question 3: Can I force Google to index a page immediately?
The URL Inspection tool’s “Request Indexing” feature asks Google to prioritize crawling the URL. However, it doesn’t guarantee immediate indexing or override an underlying quality or technical issue.
Question 4: Why does Google Search Console show conflicting indexing statuses for the same page?
The Page Indexing report and the URL Inspection tool can show different statuses because they refresh on different schedules.
Question 5: Is “Discovered – currently not indexed” the same as “Crawled – currently not indexed”?
No. “Discovered” means Google knows the URL exists but hasn’t gotten around to crawling it yet. “Crawled – currently not indexed” means Google has already visited the page and chose not to index it.
Conclusion
An indexing problem rarely means Google is punishing you. Rather, it means something specific, technical, or content-related is stopping a page from clearing a bar it would otherwise clear easily. Work through the causes in order, confirm each one directly in Search Console, and fix the cause before requesting indexing again. Most sites get this resolved faster by being methodical than by trying everything at once.
If you would rather have someone audit this for you directly, that kind of diagnostic work is what we do at Rankova. Get in touch, and we will tell you precisely why Google isn’t indexing your pages and what fixing it involves.
If you enjoyed this, read more here;
Best AEO Agency for E-commerce in Nigeria – SEO & AI Search Optimization Agency
How to Make AI Systems Recognize and Trust Your Brand – SEO & AI Search Optimization Agency
What is schema markup: a plain english guide for business owners
How to Repurpose Old Content to Recover Lost Rankings. – SEO & AI Search Optimization Agency
What Does an SEO Agency Actually Do Day-to-Day? – SEO & AI Search Optimization Agency
Internal Linking Strategy: The Most Overlooked SEO Tactic. – SEO & AI Search Optimization Agency