ShipworkSite inspection
Checks
Every error, explainedGuides →
Pricing Learn Guides

What does Google itself say about this page?

Every other check infers from the outside. This one reads the other side: whether Google indexed the URL, why not if it did not, when it was last crawled, which queries the site appears for, and whether the sitemap Google holds has errors. It needs the owner to grant read-only access once.

Runs the free audit, which includes this check where it applies to your site. Nothing is stored.

What this check inspects

When a Search Console property is connected, Shipwork runs a URL inspection for the page and a 28-day search analytics query and sitemap list for the property. From the inspection it reads the verdict, the coverage state, the robots.txt state, the indexing state, the last crawl time, the Google-chosen canonical, the user canonical and the page fetch state. From analytics it reads the top ten queries with clicks, impressions, click-through rate and position, and the totals. From the sitemap list it reads up to five sitemaps with their warning and error counts, and the last downloaded time.

What a failure means

A verdict other than PASS is an error: Google reports the URL as excluded, and the coverage state says why. Google choosing a different canonical from the one on the page is a warning, as is a URL Google has not crawled for more than sixty days. A connected property with no query data in twenty-eight days is a warning, since the site is getting no impressions. Sitemap errors are an error and sitemap warnings are a warning. With no Search Console configured, or no property connected for the host, the check reports that plainly rather than guessing.

How to fix it

  1. Work the coverage state on any URL Google did not index, which names the exact reason such as crawled but not indexed or discovered but not indexed.
  2. Align the page canonical with the one Google chose, or correct the page so Google stops choosing a different address.
  3. Request indexing for a URL Google has not crawled for two months, and check that it is not blocked.
  4. Fix the sitemap errors Search Console reports, then resubmit the sitemap.

A typical failure, worked through

The setupA store connects Search Console read-only. The account shows an indexed home page and a set of product URLs that Google reports as crawled but not indexed, with no query data across the property.

What the check reportsThe check reports the negative verdict for the product URLs with the coverage state, the absence of query data in twenty-eight days as a warning, and two errors in the sitemap Google holds.

The pointThis is the one check that reads the Google side rather than guessing it, which is why its findings are the ones to trust over an inference from outside.

Questions

Do I have to connect Search Console?
To read data, yes, with read-only access. Without a connection the check says so instead of inventing a verdict, and the free audit still infers from public signals.
Why does it report a different canonical?
Google sometimes chooses a canonical that differs from the one on the page. Seeing the Google-chosen address is the clearest signal that the page canonical is being overridden.
What do the query numbers mean?
They are the top ten queries the site appeared for over twenty-eight days, with clicks, impressions, click-through rate and average position, plus the totals across all rows.

Related checks and guides