URL Inspection Tool

About the URL Inspection tool

The URL Inspection tool provides information nearly Google's indexed version of a specific page. Information includes AMP errors, structured data errors, and indexing problems.

Common tasks:

  • See the current index status of a URL: Retrieve information about Google'due south indexed version of your page. Run into why Google could or couldn't index your page.
  • Inspect a live URL: Test whether a page on your site is able to be indexed.
  • Asking indexing for a URL: You tin request that an URL be crawled (or recrawled) by Google.
  • View a rendered version of the folio: See a screenshot of how Googlebot sees the page.
  • View loaded resources, JavaScript output, and other data: See a list of resources, page code, and more information by clicking View crawled folio (indexed result) or View tested page (live test).
  • Troubleshoot a missing page: In that location can be many reasons why a page hasn't been indexed. URL Inspection can help troubleshoot some of them.

Open URL Inspection Tool

URL Inspection Tool - Google Search Console Training

Run into the current index condition of a URL

Encounter detailed Google Index information almost a URL in your holding.

To run the URL Inspection tool to meet URL's electric current alphabetize status:

  1. Open the URL Inspection tool.
  2. Enter the consummate URL to inspect. A few notes:
    • The URL must be in the current belongings. URLs exterior the current property cannot be tested. If yous ain that other holding, you must switch properties to exam the URL.
    • AMP vs non-AMP URLs: You can audit both AMP and non-AMP URLs. The tool provides information well-nigh the corresponding AMP or non-AMP version of the page.
    • Alternate page versions: If the page has alternate/duplicate versions, the tool besides provides information nearly the canonical version, if the canonical version is in a property that y'all own.
  3. Read how to understand the results.
  4. Optionally run an indexability exam on the live URL
  5. Optionally request indexing for the URL.

There is a daily limit of inspection requests for each belongings that you own.

Agreement the results: Indexed URL

Of import notes:

  • This is not a live examination. This tool describes the nearly recently indexed version of a page, non the live version on the web. The information shown in the tool is used by Google to evaluate Search results. Your page may have inverse or become unavailable since Google last saw it. To examination the current version of the page as Google would run across it, select the Live Exam push on the page.
  • "URL is on Google" doesn't actually mean that your page is actualization in Search results. Actual appearance in Search results requires that the page and its structured data conform to quality and security guidelines. The URL Inspection tool doesn't take into account manual actions, content removals, or temporarily blocked URLs. To meet if your URL is appearing, search for your URL on Google; if your URL is missing but this tool says it was indexed, here's how to find out why.
  • The "Last crawl" appointment in the Coverage section shows the engagement when the information shown here was retrieved (if the page was successfully crawled).
  1. Read the presence status at the top of the tool to run into whether or non the URL is eligible to appear in Google Search results: URL is on Google means that the URL is eligible to appear in Search results, but is non guaranteed to be at that place. URL is not on Google means that the URL tin't announced in Search results.
  2. Aggrandize the Coverage section to see more than details:
    • Discovery: How Google establish the URL.
    • Crawl: If Google was able to crawl the folio, when it was crawled, or whatsoever obstacles that it encountered when crawling the URL. If the status is not URL is on Google, the reason why can by and large be found here.
    • Indexing: The canonical URL that Google chose for this page.
  3. Enhancements: If you accept structured data, if the page is an AMP or has an associated AMP, you will run into details in the Enhancements section. This section also includes mobile usability testing.
  4. To run into information about the request, including the HTTP request and response, and the returned HTML, click View crawled page. If this link is disabled, it is because there was a problem fetching the folio; hover over the disabled button to see the reason.

The inspection results include the post-obit expandable sections:

Presence on Google (URL status)

The top department of the study provides a summary evaluation about whether or non the URL is eligible to appear in Google Search results (with some caveats). The following values are possible:

URL is on Google

  • What it means: The URL has been indexed, can appear in Google Search results, and no problems were found with whatsoever enhancements establish in the page (structured information, linked AMP pages, and then on).
    Important: "URL is on Google" doesn't actually mean that your page is actualization in Search results. Actual appearance in Search results requires that the folio and its structured data suit to Google'southward quality and security guidelines. The URL Inspection tool doesn't accept into account manual actions, security issues, or temporarily blocked URLs. To see if your URL is appearing, search for your URL on Google; if your URL is missing merely this tool says it was indexed, find out why.
  • What to do side by side: Typically nothing, although y'all can explore what Google knows about your page by navigating into the details of the index coverage or enhancement sections.

URL is on Google, only has issues

  • What it means: The URL has been indexed and can appear in Google Search results, but there are some problems that might prevent information technology from appearing with the enhancements that you applied to the page. This might mean a problem with an associated AMP page, or malformed structured data for a rich event (such as a recipe or job posting) on the page. Read the "Important" section of URL is on Google above to run into more than caveats.
  • What to practise next: Read the warnings or errors information in the tool and endeavor to ready the problems described.

URL is non on Google: Indexing errors

  • What it ways: There was at least 1 disquisitional error that prevented the URL from being indexed, and information technology cannot announced in Google Search until those issues are fixed.
  • What to do side by side: Expand the Index coverage section to see details about the indexing endeavour. Meet the list of index coverage errors and possible fix steps.

URL is not on Google

  • What it means: This URL won't announced in Google Search results, simply nosotros recollect that was your intention. Common reasons include that the page is password-protected or robots.txt protected, or blocked by a noindex directive.
  • What to practise next: Read the details in the Index coverage department to learn more about the reason. A few possible reasons:
    • If the "User-declared approved" and "Google-selected canonical" values are different, this means that this URL is one of a prepare of like pages, and Google has chosen to index some other version of the same page. At that place's probably no need to do anything hither, though you might consider removing your explicit canonical tag, or considering why you demand another page as approved.
    • If there is a noindex or robots.txt blockage that you didn't await (see the Coverage section), you lot must remove that blockage to allow Google to access your site.
    • URL is unknown to Google: See the description in the Coverage department.
    • For other index coverage reasons, read the listing of values and possible ready instructions.

URL is an alternate version

  • What information technology means: This URL is one of a set of alternate versions of the aforementioned page. Google knows about this folio and the canonical folio, and might serve this folio in certain conditions, only will typically prefer to serve the approved page. For example, yous might have submitted is the desktop URL for a site that is mobile-beginning, or that you have submitted the URL of an AMP folio that has a canonical non-AMP version. The Crawled as value in the tool shows which crawler type (mobile or desktop) considers this to exist an alternate version. You can see the indexed URL as the Google-selected canonical value nether Alphabetize coverage.
  • What to practice: Generally at that place is aught to do, though you might check the Google-selected canonical to make sure information technology is an expected folio.

Coverage

This section provides information about whether Google could notice and index the page.

Coverage status
The section heading includes a curt, descriptive reason for the status of the URL, explaining why the URL is or isn't on Google. The following values are supported:
  • A success, alarm, failure, or excluded value listed and described here
  • URL is unknown to Google: This ways that Google hasn't indexed the URL either because it hasn't seen the URL earlier, or because it has constitute it as a properly marked alternate folio, only it can't be crawled. To fix, run a live inspection, ready any issues you might see, and submit the folio for indexing. (Hint: if this is a properly marked but uncrawlable alternate folio, if you inspect the canonical page you will meet this folio listed, with a crawl error.)
Sitemaps
Whatsoever known sitemaps that betoken to this URL. Note : This includes simply sitemaps submitted using the Sitemaps written report or listed in the robots.txt for this site. Sitemaps discovered through other ways won't be listed. For larger or new sites, it is a good practice to provide a sitemap to help Google know which pages to crawl. See known issues.
Referring page
A page that Google possibly used to discover this URL. The referring page might direct link to this URL, or it might be a grandparent or neat-grandparent of a page that links to this URL. If this value is absent information technology doesn't hateful that no referring page exists, just that this data might not be available to the URL Inspection tool at this time. If you see "URL might be known from other sources that are currently not reported", it means that Google found this URL through some means other than a sitemap or referring folio, but the referring information currently isn't available to this tool.
Final crawl
The last time this folio was crawled past Google, in your local time. All information shown in this tool is derived from this last crawled version.
Crawled every bit
The user agent type used for the crawl (desktop or mobile).
Crawl immune?
Indicates whether your site allowed Google to crawl (visit) the page or blocked it with a robots.txt rule. If you did not intend to block Google, you should remove blocking rule from robots.txt. Read how to fix a blocked page. Note that this value is not the same equally allowing indexing, which is given by the "Indexing allowed?" value.
Page fetch
Whether or not Google could actually get the page from your server. If crawling is not immune, this field will testify a failure. If crawling is allowed, page fetch might still fail for various reasons. Come across explanations of fetch failures. "Clamber allowed?" indicates whether you want the folio to exist reachable; "Page fetch" indicates whether, if immune, Google could really reach the page.
Indexing immune?
Whether or non your folio explicitly disallowed indexing. If indexing is disallowed, the reason is explained, and the page won't appear in Google Search results. Of import If your page is blocked by robots.txt (see Crawl allowed?), then Indexing immune? will e'er be "Aye" because Google tin can't meet and respect whatsoever noindex directives. Because of this, your page might announced in Search results.
User-declared approved
If your folio explicitly declares a approved URL, it will exist shown here. If your page is not an alternate page, the value None is fine here. If your page is one of a set of alternate pages, we recommend explicitly declaring the canonical URL. You can declare a canonical URL in several ways: a <link rel="canonical"> tag, an HTTP header, a sitemap, or a few other methods. There is no guarantee that Google volition choose your preferred canonical, merely nosotros will take this into consideration. For AMP pages, the canonical should be the non-AMP version (unless it is a self-canonical AMP).
Google-selected canonical

The page that Google selected every bit the canonical (authoritative) URL, when information technology establish similar or duplicate pages on your site. Google might select the user-declared approved, but sometimes Google might cull some other URL that it considers a better canonical example. If the page has no alternate versions, the Google-selected canonical is the inspected URL. If you lot find an unexpected page here, consider explicitly declaring a approved version.

The canonical URL is not always the one shown in Search results: for example, if a page has both a desktop canonical and a mobile version, Google volition probably prove the URL appropriate for your current device.

Notation that this value can be a few hours backside the value in our alphabetize.

If the inspected page is not the canonical URL, y'all can inspect the Google-selected canonical URL by selecting Inspect (merely only if the URL is in a property that y'all manage).

Enhancements (Mobile usability, AMP, and more than)

This department describes any Search enhancements detected by Google on your URL the final time it was indexed. If the URL could not exist indexed, or no enhancements were detected, this section will be empty.

This tool does non nonetheless show all possible enhancements. Hither are the enhancements supported by this tool:

Mobile Usability

Discover whether your page is easy to use on a mobile device. Not all pages are tested for mobile usability.

The following verdicts are possible:

  • Page is not mobile friendly: The page won't piece of work well on a mobile device because of a few issues. See descriptions of the possible errors.
  • Page is mobile friendly: The page should probably work well on a mobile device. More details.
  • No data available: For some reason nosotros couldn't retrieve the page or test its mobile-friendliness. Please wait a bit and try again.

Click the verdict row to get more details about mobile usability for this URL.

AMP

If the page has a linked AMP version, you can see data about information technology past selecting the row in the tool. Use this information to help find and troubleshoot AMP-specific indexing and other issues.

Details shown here apply to the AMP version referenced by the electric current page; they practise not utilise to the current page.

In addition to standard AMP errors, you might see these Google-specific AMP errors.

To come across other pages on your site affected by a specific event, select the issue description row, then select Open Written report.

An URL folio inspected with URL Inspection tool every bit an AMP can have the post-obit possible statuses:

  • AMP page is valid / Web Story is valid: The AMP is valid and indexed.
  • AMP page is invalid / Web Story is invalid: The AMP has an error that will prevent it from existence indexed.
  • AMP folio isn't indexed / Web Story isn't indexed (indexed version) or AMP page cannot be indexed / Web Story cannot be indexed (live inspection): The page is blocked from indexing, typically because of a robots.txt rule or a noindex directive.
  • AMP page is valid with warnings / Web Story is valid with warnings: AMP can be indexed, but there are some issues that might prevent it from getting full features, or it uses tags or attributes that are deprecated, and might become invalid in the future.
  • Not an AMP page: The folio inspected was not an AMP page.

Various rich effect types

You can run into data about whatever rich result types (structured data) found on the folio. Information includes the number of valid items found on the URL, descriptions of each item, and details nearly any warnings or errors found. The following rich effect types are supported:

  • Breadcrumb
  • Dataset
  • Event
  • FAQ
  • Fact check
  • Guided recipe
  • How-to
  • Epitome License
  • Chore posting
  • Logo
  • Production
  • Q&A page
  • Recipe
  • Review snippet
  • Sitelinks searchbox
  • Special Announcement
  • Video

My rich result isn't hither! Not all rich event types are supported past the tool yet. Unsupported types might be nowadays and valid on the folio, and can appear in Search results, but won't appear in the tool.

Additional response data

Boosted fetch information is only available in tests with a status of URL is on Google or URL is on Google, but has issues.

To see additional response data such every bit the raw HTML returned, the HTTP headers, JavaScript console output, and any folio resources loaded, click View crawled folio. A screenshot of the rendered page is available but in a live exam.

Alive URL test

You lot tin can examination a live URL in your property to see whether information technology is capable of being indexed past Google. This will run a exam against the live page for information like to the indexed URL. It is useful when you lot want to examination changes in the page against the currently indexed version of the folio.

To exam a live URL for potential indexing errors:

  1. Inspect the indexed URL. Note: it's fine if the page hasn't been indexed yet, or has failed indexing, but it must be accessible from the cyberspace without whatever login information.
  2. Click Exam live URL on the alphabetize results page.
  3. Read understanding the live test results to empathize what you lot're looking at.
  4. You tin toggle between the live test results and the indexed results by selecting Google Index or Live Test on the page.
  5. To rerun a live test, select the Reload (reload) button on the page.
  6. To see details about the page, including a screenshot and HTTP response headers, select View crawled page.

In that location is a per-belongings daily limit of live inspections.

Understanding the results: Live exam

Important notes:

  • This is a alive test. This tool fetches and examines the URL in real time. The information shown in the alive test can differ from the indexed URL for reasons described beneath.
  • The live test does not cheque for the presence of the URL in any sitemaps or whatever referring pages.
  • The Indexable status in the live URL can be different from the Index coverage status on the indexed URL for these reasons:
    • You have inverse or fixed something in the live URL, such every bit removing (or adding) a noindex tag or a robots.txt cake, and the changes were non yet indexed. Examine the divergence in the Indexed and Live tests, or cheque the page version history on your site to observe the differences betwixt the indexed version and the alive version.
    • The live examination does not support all the alphabetize states in the indexed version. Some states in the indexed version aren't tested or don't make sense in a alive examination, and volition exist reported differently in the live exam. See the indexable section details to learn the unsupported states.

Does a valid result mean that my page will be indexed?

No. This test just confirms that Googlebot can access your page for indexing. Even if yous get a valid or warning verdict in the live examination, your folio must however fulfill other conditions in social club to be indexed. For instance:

  • The page cannot be field of study to any manual deportment or legal issues.
  • The page cannot be a duplicate of another indexed page; it must either be unique, or selected as the canonical version of a set of similar pages.
  • The page quality must exist high plenty to warrant indexing.

The inspection results include the following expandable sections:

URL status (live test)

The pinnacle section of the report gives a general evaluation of whether or not the live URL can be indexed. A positive result is not a guarantee that information technology will appear in Search results, but it means that the URL can be crawled and parsed. The URL Inspection tool doesn't take into business relationship transmission actions, content removals, quality and security issues, or temporarily blocked URLs.

Important: The live test does non embrace all possible indexing atmospheric condition. Issues marked "no" in this tabular array are not checked in the live test, and tin can occur when the page is indexed, no matter what the live URL status is.

The post-obit values are possible:

URL is available to Google

  • What it ways: The URL isn't blocked and doesn't have any detectable errors to prevent total indexing. If Google indexes the URL it can appear in Google Search results, provided that it conforms to quality and security guidelines, and is not field of study to manual actions, content removals, or temporarily blocked URLs. See which issues are not checked.
  • What to practise next: If the page is different from the indexed version, you can request indexing by selecting the button on the page. Alternatively you could submit a sitemap, or wait for it to be crawled naturally.

URL is bachelor to Google, but has problems

  • What it means: The URL can be indexed by Google, only there are some problems that might prevent it from appearing with the enhancements that you tried to implement. This might mean a trouble with an associated AMP page, or malformed structured data for a rich consequence (such equally a recipe or job posting) on the folio. See which problems are not checked.
  • What to do next: Read the warnings or errors data in the tool and effort to fix the problems described.

URL is non available to Google

  • What it means: This URL tin't appear in Google Search results due to a critical issue.
  • What to do adjacent: Read the details in the Availability section to learn more near the reason.

URL is an alternating version

  • What it means: The URL is not considered the canonical version of this page, so it is non indexed, only this is non an error.
  • What to exercise next: Probably nothing. Google has a canonical URL for this page that should be indexed. The current index data will show the canonical URL in Coverage > Google-selected canonical.

Availability (alive test)

This section of the tool describes whether the folio tin can exist indexed past Google. However, a positive upshot is no guarantee that information technology will appear in Search results.

The page and its structured data must accommodate to Google's quality and security guidelines. The live URL inspection too doesn't have into business relationship manual deportment, security issues, content removals, or temporarily blocked URLs.

Availability status
The department heading includes a short, descriptive reason for the condition of the URL, explaining why the URL is or isn't on Google. This will be "URL can be indexed" if the URL is able to be indexed, or a warning or failure value similar to (but not exactly the same equally) those listed and described here. Run into details.
Time
The time of the live test.
Crawled every bit
The user agent blazon used for the live exam.
Crawl immune?
Indicates whether your site will permit Google to crawl (visit) the page, or block it with a robots.txt rule. If you don't want to block Google, you should remove the robots.txt block. Note that this is non the aforementioned as allowing indexing, which is given past the "Indexing allowed?" value. Read how to gear up a blocked page.
Page fetch
Whether or non Google could really get the page from your server. If crawling is non allowed, this field will show a failure. If crawling is allowed, folio fetch might still fail for diverse reasons. Come across explanations of fetch failures. "Crawl allowed?" indicates whether you want the page to be reachable; "Page fetch" indicates whether, if allowed, Google could actually reach the page.
Indexing allowed?
Whether or not your page explicitly disallows indexing. If indexing is disallowed, the reason is explained, and the page won't appear in Google Search results. Of import If your folio is blocked by robots.txt (come across "Crawl immune"), then "Indexing allowed" will always be "Yes" because Google tin't come across and respect any noindex directives. Because of this, your folio might appear in Search results.
User-alleged approved
If your page explicitly declares a canonical URL, it volition be shown hither. If your page is not a duplicate, None is fine hither. If your page is one of a set of similar or duplicate pages, nosotros recommend explicitly declaring the canonical URL. You can declare a canonical URL in several ways: a <link rel="approved"> tag, an HTTP header, a sitemap, or a few other methods. At that place is no guarantee that Google volition choose this URL, but we will have this into consideration. For AMP pages, the canonical should be the non-AMP version (unless it is a self-canonical AMP).

Which index coverage issues are tested in the live test

The alive test tin't detect all page conditions, or predict indexing success with 100% confidence. This is because some types of issues are non, or cannot be tested in real time, such as canonical selection or whether a URL was submitted in a sitemap. If a condition is not checked, the live test result might exist URL is available to Google, when in fact indexing will neglect due to the status not tested in the live test.

Here are a list of indexing issues from the Alphabetize Coverage report, and whether they can be tested in the live test:

Additional response data (alive examination)

Boosted fetch information is only available in the live test with a status of URL is bachelor to Google.

To meet additional response data such every bit a screenshot of the rendered page, the raw HTML returned, the HTTP headers, JavaScript console output, and any page resources loaded, click View tested page.

View the rendered folio

You can view a screenshot of the rendered page every bit Googlebot sees it. This is useful for confirming that all elements of the folio are present and appear as yous intend. Differences might be the result of resources that are blocked to Googlebot.

A screenshot is available only for the live URL test with a successful exam consequence. Screenshots are not available for the indexed URL, or for non-successful fetches of the live test. The page must be reachable to generate a screenshot. If your folio is behind a firewall, you tin expose it to the URL Inspection tool using a tunnel.

To view the rendered page:

  1. Audit the homepage of your site.
  2. Click Exam alive URL on the index results page.
  3. Click View tested page on the folio verdict card to open additional data panels. If this option is not available it is typically considering the folio cannot exist reached for the live examination.
  4. Click the Screenshot tab.

Request (re)indexing

You can request that an inspected URL be indexed past Google. Indexing can take upwards to a week or two; you can check the progress using this tool.

Some caveats when requesting indexing:

  • Indexing typically takes only a day or so, simply can accept much longer in some cases.
  • Submitting a asking does not guarantee that the page will announced in the Google Index.
  • There is a daily limit to how many index requests y'all can submit. If you desire many pages indexed, try submitting a sitemap to Google.

To asking indexing for a URL:

  1. Inspect the page URL.
  2. Click Request indexing on the inspection consequence folio for the URL. If the page passes a quick cheque to test for firsthand indexing errors, it will be submitted to the indexing queue. You cannot request indexing if the folio is considered to be non-indexable in the live examination.

To request indexing of many new or updated pages, your best choice is to submit a sitemap, with the updated pages marked by <lastmod>.

Troubleshoot a missing page

If you think your page hasn't been indexed, here's how to verify and troubleshoot the result.

  1. Check the index status of the page. Audit the URL, either past entering the URL in the inspection URL textbox, or by clicking the audit button shown next to a URL in one of the other Search Console reports (yous might need to hover over a URL to run across this button).
  2. The initial test results show you lot Google's information about the URL in the Google index. These Google index results are used to generate search results. Note: This initial page is not a alive test of the URL. Live testing is covered afterwards.
    • If the URL condition starts with "URL is on Google", then the page should be available in Google Search. You can verify this past searching for the URL in Google. If the page isn't in search results:
      • Check the Manual Actions report and Security Bug report for issues affecting that page. Problems on either report can prevent your page from appearing in search results.
      • Check to encounter if someone has temporarily blocked the page.
      • If none of the previous issues affect the folio, proceed debugging the event equally described hither.
    • If the URL condition is URL is not available to Google, then aggrandize the Availability department.
      1. The Availability section header should include a characterization describing in cursory why the URL could not exist indexed. See the list of values and possible fix instructions. If the label is URL is unknown to Google, it means that Google hasn't seen that URL before, and so you should request that the page be indexed. Indexing typically takes a few days.
      2. If Clamber allowed? is "No," that ways Google can't crawl the page because of a robots.txt rule, which prevents Google from itch the page. Read how to test and fix this outcome.
      3. If Indexing allowed? is "No", that means your site is returning a "noindex" tag or header that prevents Google from indexing the page, which enables it to appear in Google Search results. Yous'll have to remove this tag or header from the page earlier Google will alphabetize information technology.
  3. If you lot've changed the page since the crawl fourth dimension listed, you can examination your current version of the page by clicking Examination alive URL. If the status shown at the height of the folio valid, and then the page can probably be indexed (note that not all indexing issues can be detected past the live test).

Known problems

  • In a few cases, we don't written report the sitemap for a folio that was submitted in a sitemap. We are working to fix this.

Was this helpful?

How tin we improve information technology?