There are two ways in. Type the full URL into the inspection bar at the top of any Search Console screen, or click the Inspect link beside a page URL in most reports. You may need to hover over the URL to reveal that link.

• The URL must belong to the property you currently have open.
• To check a URL on a site you do not own, use a non-owner test such as the Rich Results Test.
• Both AMP and non-AMP URLs can be inspected.

Tip: include the full address, with protocol and hostname exactly as it appears in the property.

The first screen shows what Google has stored from its most recent crawl. It is not a live test, so the page may have changed or disappeared since Google last saw it.

• URL is on Google: eligible to appear in Search results, but not guaranteed to appear.
• URL is on Google, but has issues: indexed, though an enhancement such as structured data or a linked AMP page has a problem.
• URL is not on Google: the page cannot appear in Search results until the cause is found.
• URL is an alternate version: the URL is an alternate of a canonical page, so the canonical is the one to check.

To confirm that a page really appears in Google, search for its URL on Google. The tool does not check every condition for appearing in results.

Expand the Page indexing section to see how Google found, fetched and indexed the page. When a page is not indexed, the reason is usually in this section.

• Discovery: the sitemaps and referring page Google knows about for this URL.
• Last crawl and crawled as: when Google last visited, and whether it used the mobile or desktop crawler.
• Crawl allowed? whether a robots.txt rule blocked Google from crawling.
• Page fetch: whether Google could actually retrieve the page from your server.
• Indexing allowed? whether a noindex tag or header prevents indexing.

If robots.txt blocks the page, Google cannot see a noindex directive, so Indexing allowed? will show Yes even though the page may still be restricted by your own settings.

Check the user-declared canonical beside the Google-selected canonical. The user-declared value is the one your page states. The Google-selected value is the one Google actually chose as the representative version.

• A declared canonical can come from a rel="canonical" tag, an HTTP header or a sitemap.
• If the page has no alternate versions, the Google-selected canonical is the inspected URL itself.
• An unexpected Google-selected canonical is a sign to declare your preferred version more clearly.
• Google’s choice can only be read from the indexed data, never predicted by a live test.

Select Test live URL to have Google fetch the page in real time. This is the right way to check a fix before you wait for the next crawl. The page does not need to be indexed already, but it must be reachable without a login.

• Switch between the Google Index and Live Test views to compare what changed.
• Use the re-run button to repeat the test after another change.
• The test follows redirects first and does not tell you which final URL it tested.
• Live results are available, available with issues, or not available to Google.
• Each property has a daily limit of live inspections.

A positive live result means Google can access and parse the page. It does not guarantee indexing.

Some indexing conditions only exist at indexing time, so a live test can say the page is available even when indexing will still fail.

• Duplicate and alternate-page decisions, including which URL Google picks as canonical.
• Statuses such as Crawled – currently not indexed and Discovered – currently not indexed.
• Whether the URL appears in a sitemap or has a referring page.
• Quality and security guidelines, manual actions, content removals and temporary blocks.
• Whether a detected video is actually indexed.

Use View crawled page on the indexed result or View tested page on a live test to inspect what Google received from your server.

• Raw HTML returned for the page.
• HTTP request and response headers.
• JavaScript console output and loaded page resources.
• A screenshot of the rendered page, available only after a successful live test.

If the button is disabled, Google had a problem fetching the page. Hover over it to see the reason.

After a page is new or has changed meaningfully, you can ask Google to crawl it. The page must pass a quick check for immediate indexing errors, and a page that the live test treats as non-indexable cannot be submitted.

• Indexing can take anywhere from about a day to a couple of weeks.
• A request is not a guarantee that the page will enter the index.
• There is a daily limit on indexing requests.
• For many new or updated pages, submit a sitemap with accurate lastmod dates instead.

Below the indexing details, the tool lists the enhancements Google detected on the page the last time it was indexed.

• Rich results: detected structured data, valid item counts, warnings and errors, with the problem code highlighted where possible.
• AMP: validity and indexing status of the page or its linked AMP version.
• Video indexing: shown only when a video is detected, and only one video per watch page can be indexed.

Not every rich result type is supported by the tool yet. A type that is missing from the report can still be valid on the page.

Start by inspecting the URL, then follow the status Google reports.

• If the status starts with URL is on Google, search for the URL on Google, then check the Manual actions and Security issues reports and look for a temporary block.
• If the label says URL is unknown to Google, request indexing and allow a few days.
• If Crawl allowed? is No, find and remove the robots.txt rule that blocks Google.
• If Indexing allowed? is No, remove the noindex tag or header.
• If the page has changed since the last crawl, run a live test of the current version.