ShipworkSite inspection
Checks
Every error, explainedGuides →
Pricing Learn Guides

Every check, and what it actually looks at

Shipwork runs a set of inspection checks any site can be measured against. Each page below explains one check from its source: what it fetches, what a failure means, the fix, and a worked example of the failure.

Fetches public pages from outside your network the way a crawler does. Nothing is stored.

Every check Shipwork runs, one page each: what it fetches, what a failure means, how to fix it and a worked example of the failure.

Discovery and crawling

Can a crawler find, fetch and keep your pages?

Content and rendering

What a crawler actually reads once it arrives.

Markup and structured data

The machine-readable layer search engines and AI read.

Trust and delivery

The signals behind a site that is safe to serve and to buy from.

Catalogue data

The product fields that decide Google Shopping eligibility.

By platform

What the common platforms get wrong, and which checks matter most there.

By problem

Start from what you are seeing rather than from a check name.

Questions

Are these checks free?
Yes. Every check runs free and without an account. The pages here explain each one and give you a tool to run it on your own site.
Do the checks work on any platform?
Most do, because they read public HTML, response headers, DNS and the sitemap. The catalogue checks go deeper when a platform exposes a public product list, which Shopify and WooCommerce do.
Where do these checks come from?
Each one maps to a documented requirement or a standard: Google Merchant Center product data rules, the robots.txt and sitemap specifications, the JSON-LD vocabulary, and standard web security headers.

Start here