Why Is My Website Not Indexed by Google?
Use this when the homepage, whole site, or many important URLs are missing.
Read the article →URL Indexing
Why Is My Page Not Indexed?
Single-URL checks to diagnose why one specific page is missing from Google.
Quick overview
Summary
- Inspect the exact URL, not a similar URL, redirected URL, canonical URL, or sitemap version.
- Confirm that the page is crawlable and indexable, with a successful status, no blocking directive, and the correct canonical.
- Validate the page before requesting indexing, because Request Indexing does not fix the underlying issue.
If one page is not indexed by Google, inspect the exact URL in Search Console, test the live version, and check HTTP status, robots.txt, noindex, canonical tags, redirects, rendered content, internal links, sitemap inclusion, and page value.
- Inspect the exact URL, not a similar URL, redirected URL, canonical URL, or sitemap version.
- Confirm that the page is crawlable and indexable, with a successful status, no blocking directive, and the correct canonical.
- Validate the page before requesting indexing, because Request Indexing does not fix the underlying issue.
A page can be published, visible to users, included in the sitemap, and still not be indexed by Google. That feels unfair, but Google is not looking at the WordPress “Published” badge and politely nodding.
When one specific URL is missing, diagnose that exact URL. Do not treat it as a whole-site problem unless many similar pages share the same pattern.
For broader causes across multiple pages, see why Google is not indexing pages.
How to Check the Exact URL in Search Console
Open Google Search Console and use URL Inspection.
Inspect the final canonical URL you want indexed. Be careful with:
- HTTP vs HTTPS
- WWW vs non-WWW
- Trailing slash differences
- Uppercase and lowercase variants
- Redirecting URLs
- Parameter URLs
- Alternate canonicals
Search Console can only inspect URLs within the selected property, so make sure you are using the correct property.
Review:
- URL status
- Discovery
- Crawl status
- Page fetch
- Indexing allowed
- User-declared canonical
- Google-selected canonical, when available
- Referring sitemap
- Last crawl date
Then click Test Live URL to check the current version. The indexed report reflects Google’s stored information. The live test checks what Google can access now.
What Does “URL Is Not on Google” Mean?
“URL is not on Google” means the inspected URL is not eligible to appear in Google Search in its current indexed state.
The reason can vary. It may be:
- Google has not discovered the URL
- Google discovered but has not crawled it
- Google crawled but did not index it
- The page is blocked by robots.txt
- The page contains noindex
- The page redirects
- The page is a soft 404
- Google selected another canonical
- The page does not provide enough distinct value
- The page has not been recrawled after a fix
Open the Page Indexing details instead of guessing. Search Console often gives the first useful clue.
What Does “URL Is Unknown to Google” Mean?
“URL is unknown to Google” means Google has no known indexed information for that exact URL. In practical terms, Google may not have discovered the URL yet.
Start with discovery checks:
- Is the URL linked internally from a crawlable page?
- Is it included in the XML sitemap?
- Is the URL format consistent with the canonical?
- Is the page hidden behind a form, filter, or script?
- Does another URL canonicalize to it?
- Is the page blocked before Google can reach it?
- Is the page new?
This status is not always a noindex problem or content-quality problem. Google may simply not know the URL exists yet.
If the URL is new, strengthen internal links, confirm sitemap inclusion, test the live URL, and request indexing only after the page is accessible and indexable.
What Does “URL Is Not Indexable” Mean?
“URL is not indexable” means Google’s live test found a condition that prevents the URL from being indexed.
Common causes include:
- Noindex directive
- Robots.txt block
- Redirect
- Error status
- Unauthorized access
- Soft 404
- Canonical pointing elsewhere
- Incomplete or inaccessible content
A page can return 200 and still be not indexable if it contains noindex, declares another canonical, renders empty content, or behaves like a duplicate.
The phrase sounds dramatic, but it is a diagnostic clue, not a final sentence. Find the blocking signal, fix it, and retest.
Does the Page Return the Correct HTTP Status?
An indexable page should normally return 200 OK.
Check whether the URL returns:
200for a valid page301or308if it has permanently moved302or307if temporarily redirected404or410if removed5xxif the server failed403or401if access is blocked
Redirecting URLs are usually not indexed; the destination is the candidate. If your intended page redirects elsewhere, inspect the final destination.
For important pages, avoid redirect chains and loops. Google and users should reach the final page directly, not through a scenic route of previous redesigns.
Are Robots.txt, Noindex or Canonicals Blocking Indexing?
Check three different controls.
Robots.txt controls crawling. If blocked, Google may not fetch the page.
Noindex controls indexing. If Google crawls the page and finds noindex, the page should not be indexed.
Canonical tags indicate the preferred URL among duplicate or similar pages. If the page canonicalizes to another URL, Google may index the canonical instead.
Use the dedicated guide to robots.txt versus noindex if those controls are being mixed.
Use canonical tag best practices if the page points to a redirected, noindexed, broken, or unrelated canonical URL.
Is the Page Useful and Distinct Enough to Index?
If the technical signals are clean, evaluate the page itself.
Ask:
- Does this page satisfy a real search intent?
- Is it substantially different from other pages?
- Does it duplicate another service, product, category, or article?
- Is the content complete enough to stand alone?
- Is the page internally linked from relevant pages?
- Does the page provide useful information beyond a thin template?
- Would this URL deserve its own search result?
If Search Console shows Crawled – currently not indexed, use the dedicated guide to Crawled – currently not indexed.
If it shows Discovered – currently not indexed, use the guide to Discovered – currently not indexed.
Should You Request Indexing Again?
Request indexing after you fix or confirm the page’s current condition.
Before clicking the button:
- Test the live URL.
- Confirm it returns
200. - Confirm crawling is allowed.
- Confirm indexing is allowed.
- Check the canonical.
- Review rendered content.
- Add relevant internal links.
- Confirm sitemap inclusion if appropriate.
Request Indexing is useful for a small number of important URLs. It is not a magic button, although many website owners have understandably stared at it with hope.
Repeated requests for an unchanged URL do not fix noindex, robots.txt, duplicate content, broken canonicals, or poor internal links.
How to Confirm the Page Is Fixed
After implementation:
- Run Test Live URL.
- Confirm the blocking issue is gone.
- Request indexing for the corrected page.
- Monitor the URL Inspection result.
- Check Page Indexing.
- Search the exact URL in Google later.
- Review impressions in Search Performance.
The complete process is covered in the guide to inspect indexing issues in Google Search Console.
If the page still does not index after all signals are clean, compare it against similar indexed pages and evaluate duplication, uniqueness, and internal-link strength.
FAQ
Frequently Asked Questions
Why is this specific page not indexed by Google?
The page may be undiscovered, blocked, noindexed, redirected, canonicalized elsewhere, returning an error, rendering incomplete content, duplicating another page, or lacking enough distinct value.
What does “URL is not on Google” mean?
It means the inspected URL is not currently eligible to appear in Google Search based on Google’s indexed information. Use URL Inspection details and the live test to identify the reason.
Can a page return 200 and still not be indexed?
Yes. A 200 response only means the page loads successfully. Noindex directives, canonicals, duplication, soft 404s, weak content, or poor internal discovery can still prevent indexing.
Should I request indexing after every fix?
Request indexing after validating the live page for important URLs. Do not request indexing repeatedly before fixing the underlying issue.
What if Google has never seen the URL?
Strengthen discovery by adding internal links, including the URL in a clean sitemap, confirming crawlability, and using URL Inspection after the page is live and indexable.
Final Thoughts
When one page is not indexed, diagnose the exact URL.
Start with URL Inspection, then test the live page. Check status code, crawlability, noindex, canonical tags, redirects, rendered content, internal links, sitemap inclusion, and page value.
Only request indexing after the page is technically eligible and worth indexing. If the issue affects important business pages, page indexing diagnosis support can help identify the blocker and validate the correction.
