Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A website can be missing from Google for two very different reasons: Google may not have indexed the page, or it may have indexed it but not show it for the search you care about. Start by checking the page’s index status in Google Search Console, then investigate access and technical issues before assessing relevance, site changes, and demand. These are diagnostic leads, not a guaranteed ranking checklist.
First, work out what “not ranking” means
Identify which situation you are seeing before changing the page:
- The URL is absent from Google: It may not have been discovered, crawled, or included in the index.
- The URL is indexed but does not appear for a target query: Google may consider it irrelevant to that search, or it may not be selected prominently among competing results.
- The page used to get traffic and now gets less: This is a traffic decline; possible explanations include a site change, a policy issue, or changing search demand.
Search results can vary by query, location, language, and device. A site:example.com search can offer a quick clue, but Google warns that this operator does not necessarily show every indexed URL. For a site-specific check, use Google Search Console.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Check whether Google can access and index the page
Google’s technical requirements are a baseline for eligibility, not a promise of inclusion or ranking. Check the specific URL in Search Console’s URL Inspection tool, and use the Page Indexing and Crawl Stats reports to look for broader patterns.
#1 Best Overall
- Confirm that the page is public and does not require a login or other access restriction.
- Check that Googlebot is not blocked from crawling the URL or resources needed to render it.
- Verify that the server returns HTTP 200 rather than an error.
- Review indexing controls, including meta directives and other sources of
noindex. - Make sure the page contains useful text and that its important content is available to Google after rendering.
A noindex instruction tells Google not to include a page in Search. By contrast, robots.txt controls crawling; blocking a URL there does not reliably remove an already known URL from results. Google explains these technical requirements in its technical requirements documentation.
Investigate discovery, crawling, and delays
1. The site or URL is new, or Google has not discovered it
Google says a site being too new is the most common reason it is not indexed. Discovery, crawling, and indexing depend on many factors, and Google does not guarantee whether or when a URL will be indexed. Check whether Google knows the URL and give the process time rather than assuming that a submission will produce an immediate result. See Google’s guide to getting a site on Google.
2. A sitemap has not been submitted or does not list the page
A sitemap can help Google discover URLs, especially on a new or reorganized site. It does not guarantee indexing or improve rankings by itself. Keep the sitemap current and submit it through Search Console, but investigate access and content quality separately if a listed URL remains absent.
Rank #2
3. Robots.txt or another crawl control blocks Googlebot
Check the actual page URL and any resources it needs to render. A crawl block can prevent Google from fetching content, but robots.txt is not a substitute for noindex when the goal is to keep a page out of Search.
4. The server is unavailable or limiting crawls
Look for outages, slow or failed responses, and access limits that affect Googlebot. Google may reduce crawling when a server struggles to respond. A site-wide availability issue can affect more URLs than a single-page problem.
5. Low-value URL patterns are consuming crawl attention
Crawl-budget concerns are not universal. They matter for particular sites and URL inventories; they are not a reason to assume every small site has a crawl-budget problem. If valuable pages are not being crawled, check whether Google knows their URLs, whether crawl controls block them, whether the server can handle requests, and whether large numbers of low-value URLs complicate discovery. Google’s crawl-budget guidance discusses when this issue is relevant. Efficient crawling alone does not make a low-value page rank.
Rank #3
Review the page’s relevance and usefulness
6. The page does not match the searcher’s query or intent
An indexed page may not be served for a particular query if Google considers it irrelevant. Compare the page with what the query asks for: does it answer the actual question, serve the likely purpose behind the search, and make its subject clear? Indexing is not the same as visibility for every search.
Free tools Windows power users keep installed
One-click scans. No signup required.
7. The content offers too little value or distinction
Assess whether the page fulfills a clear purpose and helps its intended audience, rather than mainly repeating or lightly rephrasing other pages. Google’s people-first content guidance encourages publishers to consider whether readers will find the page useful, whether it provides appropriate depth and first-hand expertise, and whether readers leave satisfied.
Do not treat word count as a ranking lever: Google says it has no preferred word count. E-E-A-T describes qualities Google’s systems seek to identify through a mix of factors; Google says E-E-A-T itself is not a specific ranking factor.
Check policy issues, security, and site changes
8. A spam-policy issue affects visibility
Review Search Console’s Manual Actions report and check the page and site against Google’s spam policies. Google says policy violations may cause pages to rank lower or disappear from results. A drop in traffic alone does not establish that a policy violation occurred.
9. A security issue affects the site
Check Search Console’s Security Issues report for notices that may affect how the site appears in Search. Treat this as a distinct diagnostic branch from relevance or indexing: the report provides evidence to investigate, rather than a reason to infer a security problem from low rankings alone.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
10. A migration or URL change disrupted discovery or consolidation
If the site moved domains, changed URL structures, or replaced important pages, review redirects and migration handling. Google may need to recrawl and reindex changed URLs, and fluctuations can occur during that process. A site move is a plausible explanation for a decline, not proof that it caused one.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Consider experience, competition, and demand
11. Page experience is a weakness, but scores are not a ranking guarantee
Google’s core ranking systems consider a variety of page-experience signals, including Core Web Vitals. Good scores do not guarantee a top position, and Google cautions against pursuing perfect scores solely for SEO. Page experience is considered alongside relevance and other factors; a highly relevant result may appear even when its experience is subpar. See Google’s page-experience guidance.
12. The apparent decline reflects competition or changing demand
Compare affected queries and dates in Search Console’s Performance report. Check whether the change is limited to one URL, a directory or template, or the wider site. Use Google Trends to see whether interest in the topic also declined across the wider web. A change in demand or the results competing for a query can affect visibility without a single technical fault. Google’s guide to debugging Search traffic drops recommends checking query-level patterns and broader demand.
Choose the next check from the evidence
Use the pattern of the issue to narrow the investigation instead of applying every possible fix at once.
Recommended Free Tools
| What you observe | Where to investigate |
|---|---|
| URL is unknown, not crawled, or excluded | URL Inspection and Page Indexing; then check discovery, access, crawl controls, server responses, and indexing directives. |
| URL is indexed but absent for a target query | Check query relevance and usefulness; remember that indexing does not guarantee serving for that query. |
| One page is affected | Inspect that URL’s access, status, directives, rendered content, and query fit. |
| A directory, template, or whole site is affected | Look for shared technical controls, server problems, site-wide changes, and Search Console policy or security notices. |
| Traffic fell after a migration | Review URL changes, redirects, and recrawling patterns; compare affected dates and queries. |
| Traffic fell without a clear site change | Compare Search Console queries and dates, then check Google Trends for wider demand changes. |
Google Search works through discovery and crawling, rendering and indexing, and then serving results. A failure or delay at one stage calls for a different investigation than an indexed page that simply is not competitive for a particular query. Search Console reports help identify which branch to follow; none of these checks guarantees a ranking outcome.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
