- Informational
Why Google Hasn't Indexed Your Page: A Practical Checklist
Editorial responsibility: SearchCub
A page can be missing from Google's index because Google has not discovered it, has not crawled it, cannot index it, or has chosen another version. Check the specific URL in Google Search Console before changing the page or repeatedly requesting indexing. Publishing a page and making it eligible for search are different milestones.
1. Confirm the exact URL and reported state
Open your site's property in Google Search Console, then paste the full URL into URL Inspection. Check the hostname, path and protocol; a redirecting address and its destination are different URLs.
Read the indexed information first, including the reported reason and last crawl where available. Then use the live test when you need to check the current page. Google's URL Inspection documentation explains that the initial report describes Google's indexed information, while a live test fetches the page now. A successful live test does not prove that the page is indexed or guarantee future inclusion.
For several affected pages, use the Page indexing report to look for a shared pattern:
Reported situation | What to investigate next |
|---|---|
URL unknown to Google | Whether Google can discover links to it |
Discovered, currently not indexed | Google knows the URL but has not crawled it yet |
Crawled, currently not indexed | Access has happened; examine the page's value and possible duplication |
Excluded by a noindex rule | Whether exclusion is intentional |
Alternate or duplicate URL | Whether the intended canonical version is indexed |
Server or access error | Whether Google can retrieve a working public page |
The label describes the observed state. It does not prove that a crawled page is “too short,” that a new site needs paid backlinks, or that a particular waiting period will solve the issue.
2. Check access before rewriting content
Open the page while signed out. It should load its intended content without requiring an account, and the final page should return a successful HTTP response. Ask your developer or host to investigate access errors, redirect loops, or an error page served with a misleading success status.
Google's technical requirements include crawler access, a working response, and indexable content. Meeting these requirements makes a page eligible; it does not compel Google to index it.
SearchCub's Page optimisation checks can help inspect fetched HTML, metadata and the response: open Page research and choose Check this page. Fresh checks use research credits. Read the observation's date and any unavailable fields. These checks do not verify Google index status, robots.txt, or the fully rendered JavaScript page; use Search Console for Google's view.
3. Resolve conflicting instructions
Check whether the page is meant to appear publicly in search. An account page or a duplicate filter URL may be correctly excluded.
For a public article you want indexed, investigate an accidental noindex rule in the page or HTTP headers. Separately check whether robots.txt blocks crawling. Google's noindex guidance explains the distinction: Google must be able to crawl a page to see its noindex rule. Blocking crawling is not a reliable way to remove a URL from search.
Check the canonical too. If an alternate URL points to your preferred article and Google has indexed that article, there may be nothing to repair. If an unrelated page was selected, inspect the content and conflicting URL signals before changing tags blindly.
4. Give the page a useful place on the site
Link to the article from a relevant, accessible page and include the preferred URL in your sitemap. Confirm that the links lead to the final address.
For an illustrative example, a new shipping guide hidden behind a search form is harder to discover than one linked from your delivery-information page. A guide repeating the same shipping text as five existing pages also gives you a separate duplication question to resolve.
If Google has already crawled the page, review its actual contribution: does it answer a distinct customer question, contain the promised information, and work without missing content? Extend it only where the answer needs more detail. A word-count target is not an indexing fix.
5. Request review after fixing the relevant issue
Retest the changed page. For an important new or materially updated URL, use Request indexing if available. For many URLs, submit an accurate sitemap. Google's recrawl guidance says requests do not guarantee indexing and repeated requests do not make crawling faster.
Keep a small record: URL, reported state, change made, test result and review date. Revisit the state after Google processes the page. Once it is indexed, low traffic becomes a different investigation; use the Keyword Research Guide to check whether the page addresses a useful search opportunity.
For the wider site check, compare website SEO performance and choose the next page to investigate.