Use URL Inspection to diagnose one page and Crawl Stats to spot site-wide crawling or availability problems. Neither tool can guarantee that Google will index a URL or say exactly when it will happen; together, however, they help distinguish a page-specific eligibility issue from a broader crawl problem.
What each Search Console report can tell you
| Tool or view | Scope | Best question to answer | Important limit |
|---|---|---|---|
| URL Inspection: Google Index | One URL, based on information in Google’s index | What does Google know about this URL, and when was it last crawled? | It reflects the version Google processed; changes made afterward may not appear. |
| URL Inspection: live test | One URL as currently served | Can Google fetch the current page, and does it appear eligible for indexing? | A successful test does not establish that Google has indexed the page. |
| Crawl Stats | Site-level crawl history for eligible root-level properties | Are crawl volume, response times, host availability, or response patterns changing? | It is an advanced report, its example URLs are not a complete log, and it has no crawl-rate control. |
| Page Indexing report | Site-wide summary of known URLs | Are indexing totals or exclusion categories changing across the site? | Reporting can lag several days, and URLs Google does not know about are not included. |
Google describes URL Inspection’s index data and live test as distinct views: the first reports stored index information, while the second checks the current page. Google’s URL Inspection guide explains how to interpret them. The Crawl Stats report provides crawl history and representative examples rather than a complete record of every request. The Page Indexing report helps identify patterns across URLs known to Google.
As an Amazon Associate I earn from qualifying purchases.
Inspect the URL in Google’s index first
- Open Google Search Console and paste the complete page URL into the URL Inspection search field. Confirm you are viewing a property that includes the URL’s scheme, host, subdomain, and path.
- Read the Google Index result before testing the live page. Check whether the URL is indexed or excluded, its last crawl date, whether Google could fetch it, whether crawling and indexing are allowed, and the Google-selected canonical.
- If Google selected a different canonical, investigate whether that other URL is the version you intend to appear in search. A page that is indexed is not guaranteed to appear for every query or receive a search appearance.
- Use the last crawl date to judge whether Google could have seen your recent edit. The index view describes stored information from Google’s processing; changes after that crawl may not yet be reflected.
A known URL excluded from the index is a different situation from a URL Google has not discovered. Check the reported status and eligibility details rather than treating both cases as simply “not indexed.” Google’s single-page inspection guide describes the index and live-test workflow.
Run Test live URL to check the current page
In URL Inspection, choose Test live URL to check the page as it is currently served. Use the result to find current fetch, availability, robots.txt, or noindex problems and address them before asking Google to try again. A live test is a technical check, not proof that the tested version has been added to Google’s index, and it does not cover every indexing condition.
#1 Best Overall
If the live test succeeds but the indexed view shows an older crawl date or an excluded status, treat those as separate facts: Google can access the current page now, while the stored index information may reflect an earlier crawl or another eligibility issue. URL Inspection’s index and live views are not interchangeable.
Check Crawl Stats for site-wide patterns
- In Search Console, open Settings > Crawl stats on a root-level Domain property or root URL-prefix property.
- Review crawl request volume and trends alongside average response time, host status, and response categories. A change in one metric alone is a clue to investigate, not a complete diagnosis.
- When useful, segment the report by Googlebot type, file type, or crawl purpose, such as discovery versus refresh. A rise in discovery requests may follow a substantial content addition or sitemap submission.
- Use example URLs to understand the kinds of requests Google made, not as a complete request log. The absence of a particular URL from the examples does not show that Google never requested it.
Google characterizes Crawl Stats as an advanced report and says most sites with fewer than 1,000 pages generally do not need this level of crawl detail. Its Crawl Stats documentation describes the report’s metrics and limits.
Connect crawl changes to plausible causes
A drop in crawl activity does not by itself explain why a specific page is missing. Compare the timing of crawl changes with access, response, and content changes on your site. In particular, check:
Free tools Windows power users keep installed
One-click scans. No signup required.
- Robots.txt changes: A broad or newly changed rule may prevent Googlebot from crawling relevant pages.
- Resources needed to render the page: Check whether Google can access important CSS or JavaScript files.
- Slow responses or server errors: Google says it may reduce requests to avoid overloading a slow or erroring server.
- Host availability: Use Crawl Stats host-status information to look for availability problems that coincide with reduced crawling.
Google also notes that pages that change less often or are not considered high quality may be crawled less often. That general guidance does not establish why Google crawled any particular URL less frequently. Crawl Stats offers no setting to raise the crawl rate; Google’s crawl-rate guidance explains why slow responses and server errors can lead to reduced requests.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix the issue, request another crawl, and allow time
- Resolve the diagnosed cause. Correct any relevant crawl block, indexing restriction, fetch failure, server problem, or canonical mismatch. If the change affects how Google receives the page, run Test live URL again.
- For one important page, request indexing. In URL Inspection, submit an indexing request after the page is ready. This asks Google to consider the URL; it does not guarantee indexing or a particular search position.
- For many pages, use a sitemap. Submit or update a sitemap rather than sending individual requests for a large batch. Keep last-modified dates accurate where applicable.
- Wait, then check the relevant reports. Google says processing an indexing request may take up to a week or two. Its missing-page guidance recommends allowing at least a week after a sitemap submission or indexing request before assuming there is a problem. Google gives a broader possible range of a day or two to a few weeks for discovering and indexing a new page, depending on many factors.
- Look for site-wide patterns separately. Use the Page Indexing report to monitor known URL totals and issue categories, keeping in mind its several-day reporting lag and that it omits URLs Google does not know.
These are timing ranges in Google’s missing-page guidance and URL Inspection guidance, not a deadline or promise that a page will be indexed.
Quick Recap
Rank #4
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.
