iTechGuides 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
First find out whether Google has not indexed the page, or whether it is indexed but does not appear for the search you tried. Those are different problems. Use Google Search Console’s URL Inspection tool to check the exact URL, then follow the reported status: fix access or indexing issues first; if the page is indexed, investigate its relevance and visibility. A crawl request can help prompt discovery, but Google does not guarantee that or when a URL will be crawled or indexed.
First, identify what “not showing up” means
Google handles a page in stages: it may discover and crawl the URL, decide whether to index it, and then select whether it appears for a particular search. Being crawled does not guarantee indexing, and indexing does not guarantee that a page will appear for every query. Google selects results programmatically using factors that include relevance and quality. Google explains how Search works.
In Search Console, open URL Inspection and enter the exact intended URL, including its protocol, hostname, path, and trailing slash where applicable. Check the current index status, then use the live test to see whether Google can fetch the page now. Use the Page Indexing report to determine whether the issue affects one URL or many. A site-wide pattern calls for checking broader configuration, availability, or security issues; a single excluded URL needs a page-level diagnosis. Google’s URL Inspection documentation describes the tool and its results.
A search for site:example.com is not a definitive way to verify indexing. Search Console reports are the better diagnostic. If the page is indexed, its Search performance data can help distinguish no impressions from impressions that do not translate into the visibility you expected.
#1 Best Overall
Use the reported status to choose your next step
| Search Console finding | What it may indicate | What to check next |
|---|---|---|
| Google has not crawled the URL | Google may not have discovered it, may be blocked from fetching it, or may be encountering availability or capacity problems. | Check internal links, the sitemap, robots.txt, server responses, and crawl information. Page Indexing report guidance; Google’s crawl-budget guidance. |
| The live test cannot fetch or render it | There may be an access, server, robots, or resource-loading problem. | Correct the reported access or server problem, then test again in URL Inspection. URL Inspection documentation. |
| The page was crawled but is not indexed | A directive, canonical selection, content issue, or another indexing decision may be involved. | Read the specific Page Indexing reason; inspect meta and header directives and the page itself. Page Indexing report guidance. |
| The page is indexed but absent for one search | The issue is more likely visibility, relevance, quality, or serving than initial discovery. | Review the query and the page’s usefulness, then check Search performance and robots directives. How Google Search works. |
| Many pages vanish or impressions fall suddenly | A broader technical, security, manual-action, or search-related issue may be involved. | Review Page Indexing, Crawl Stats, Manual Actions, and Security Issues in Search Console. Manual Actions report; Security Issues report. |
Make sure Google can access a working page
Open the page in a private browser window or while signed out to confirm that it is available to an ordinary visitor. Check that it returns a successful HTTP 200 response and contains substantive, indexable content. A URL that has moved should redirect appropriately to its replacement; a URL that is genuinely gone should return a real 404. A page that returns success but shows an error, blank screen, or little useful content can behave like a soft 404. Google’s crawler documentation explains how Google handles responses and crawling.
Check robots.txt separately from indexing directives
Review the site’s robots.txt file for a rule that blocks the affected URL or resources needed to render it. Robots.txt controls crawling, but it is not a dependable way to keep a URL out of Google’s index: Google may know about a blocked URL through links elsewhere. Google states, “A robots.txt is not a mechanism for keeping a web page out of Google.” Google’s robots.txt documentation covers crawl controls.
If you intend to exclude a page from Search, use a noindex meta tag or an X-Robots-Tag HTTP response header, and allow Googlebot to crawl the URL so it can read the instruction. Inspect both the rendered HTML and response headers: a CMS setting may add a meta tag, while a header can apply to files such as PDFs, images, and video. If Google cannot fetch the URL, it cannot see a noindex directive. Google’s guide to blocking indexing explains the options.
Help Google discover the URL
Add the canonical, intended URL to an accurate sitemap and submit it in Search Console if you want to monitor it there. Also link important pages from other crawlable pages using ordinary HTML links. Sitemaps and links help Google find URLs; neither commands Google to crawl, index, or rank them. Repeatedly resubmitting an unchanged sitemap will not force indexing. Google’s sitemap guidance.
Rank #3
- Keep track of everything from attendance to test scores
- Spiral bound
- Measures 8-1/2" x 11"
After correcting an issue, URL Inspection can request crawling. That request is not a guarantee of a crawl or indexing, and Google says it cannot predict or promise when—or whether—every URL will be crawled or indexed. Its documentation says new pages commonly take several days minimum to be noticed, but that is not a fixed indexing deadline. Request a recrawl; Crawling and indexing FAQ.
Check rendering if the site relies on JavaScript
A JavaScript page can be available to a browser yet fail to expose its important content or links to Google as expected. Use URL Inspection’s live test or the Rich Results Test, then examine the rendered output. Confirm that the main text and links appear, required scripts and other resources load, and the browser console does not show errors or exceptions that prevent rendering. A blank or incomplete rendered page can make it harder for Google to understand the URL. Google’s JavaScript SEO guidance.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Look for site-wide manual actions or security issues
If many URLs are affected, review Search Console’s Manual Actions and Security Issues reports, as well as Page Indexing and Crawl Stats. A manual action can prevent some or all of a site from appearing in results; a security issue can trigger warnings that discourage visits. Follow the specific report’s instructions rather than applying a generic fix. Manual Actions report; Security Issues report.
If it is indexed, improve its fit for the search
When URL Inspection confirms that a page is indexed, but it does not appear for a chosen query, check whether the page clearly answers that searcher’s question. Make its purpose and substantive content clear, ensure important information is accessible to Google, and check that a robots meta rule is not limiting its appearance. Google may omit a page for a query because it is not relevant enough or does not meet its quality standards. Indexing alone does not secure a ranking, and changing a page does not guarantee a particular search result. Google’s overview of Search.
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.
