ShipworkSite inspection
Feed finder

Crawlability

PaginationAre paginated pages set up right?Internal searchIs site search eating crawl budget?URL parametersAre parameters creating duplicates?Log analyserWhat does Googlebot actually crawl?Robots builderNeed a robots.txt file?Soft 404sAre pages “not found” but returning 200?JavaScriptCan crawlers see it without running JS?FreshnessIs my site quietly going stale?Robots.txtDoes robots.txt say what I think?

Indexing

Sitemap lastmodAre my sitemap dates valid?SitemapIs my sitemap actually fetchable?IndexingIs Google allowed to index my pages?CanonicalsIs Google indexing the wrong URL?Index signalsDo sitemap and index signals agree?Sitemap generatorNeed a sitemap.xml for my site?Bulk URL statusWhere does each of these URLs really land?Redirect builderNeed the redirect rules?RedirectsAre my URLs answering directly, over HTTPS?

On-page

Keyword ideasWhat are people searching for?SERP previewHow does my page look in Google?Content qualityAre your pages too thin or too alike?Image weightAre images slowing the page?CannibalizationAre pages competing with each other?On-page checkDoes the page use its target phrase?ImagesAre my images accessible and loading?Meta tag builderWhat should my title and share tags say?DuplicatesDo my pages compete for one query?

Links

Orphan pagesWhich pages can no link reach?Link graphHow deep do your pages sit?Anchor textDo links say what they point at?Outbound linksAre external links still alive?Broken linksAre internal links sending visitors nowhere?

Structured data

Rich resultsIs my markup eligible for a rich result?Structured dataIs my product schema valid?Schema coverageDo my key pages carry structured data?Social previewHow does my page look when shared?Schema vs pageDoes markup match the page price?Schema builderNeed valid JSON-LD?

International

Hreflang sitemapDo page and sitemap hreflang agree?HreflangDo my language versions link back?Hreflang builderNeed the hreflang tags?Page DoctorWhy is this page not doing well?Redirect planMy site has dead links — what redirects do I write?Sitemap diffIs anything missing from my sitemap?Robots simulatorWhat does my robots.txt actually block?Can Googlebot?Can Googlebot fetch this URL?
Every error, explainedGuides
Pricing Learn Error guides Run free audit

+1 free check

Welcome to Shipwork

Sign in free and your next check this month is on us.

Continue with GoogleContinue with email

We email you a 6-digit code. No password.

No card needed. Reports and watches follow you to any device.

Does your store expose a product feed?

Many checks need to read your catalogue, which requires a public product list. Shopify and WooCommerce provide one; other platforms expose products through their sitemap. This finds what your store offers.

Probes the common feed endpoints for your platform and reports what is public. Saved to your account if you are signed in to a paid plan.

How this check works

Shipwork identifies your platform, then probes the endpoints where a public product list usually lives (Shopify /products.json, WooCommerce's Store API, or the product sitemaps other platforms serve) and reports what it could read. When a feed is found, the catalogue checks run; when it is not, they honestly say so rather than guess.

What the product feed finder looks for

The finder checks whether a store exposes a public product list that the catalogue checks can read. It recognises the Shopify product list at the products JSON endpoint and the WooCommerce Store API, then reports how many products it read. If the platform is not one of those, it reports whether a public product list was found at all.

For a store with no public list, it reports that no feed was found and that catalogue-level checks cannot run. For a site that is not a store, it reports that no product feed is expected. The check reads the list itself, so it does not guess from the visible pages.

How to read a feed result

A found result means the product list answered and the checker could read products from it. The product count tells you how much of the catalogue the price, availability and image checks can see. A missing result on a store means those checks have no data, so their silence is not a clean bill of health.

The check confirms that a public list exists and can be parsed. It does not validate the fields inside it, and it does not read the private feed you send to a merchant platform. A platform that exposes the list but returns incomplete rows will be found here and then fail the catalogue checks later.

Why a public list matters

Catalogue checks such as price, availability, brand, image and description read a machine-readable list of products. Without one, the checker can only inspect the HTML of a few product pages, which is a far narrower view. A store that hides its product list makes its own problems harder to see.

Some platforms expose the list by default, and some disable it. A store that moved platform, changed a theme or restricted an endpoint can lose its list without any visible change on the site. The finder is the first check to run when the catalogue checks return nothing.

How to expose a product feed

On Shopify the product list is normally available at the products JSON path; if it is not, check whether an app or a theme has restricted it. On WooCommerce the Store API answers at its products path under the site; confirm the endpoint is public. On another platform, publish a product sitemap or export a feed file and validate it.

A public list is not the same as your merchant feed, which stays private. The list only needs to expose the fields the checks read. After enabling it, re-run the finder and confirm a product count. Then run feed check to inspect the fields, or feed file check if you export a file.

When to use related checks

Use price check and availability check once the list is found, since both depend on it. Use product page check to review a product page's own signals when no list is available, and feed check for the field-level view.

The guide feed versus page explains why the public list and the page can disagree. If you are not on Shopify or WooCommerce, the site-wide checks still run on HTML and your sitemap, so only the catalogue checks need a list.

Questions

What is a product feed?
A machine-readable list of your products and their fields. Shopify exposes /products.json; WooCommerce exposes a Store API; other platforms list products in their sitemap.
Why does Shipwork need one?
Catalogue checks like prices, availability and images read the feed. Without a public list, those checks cannot run and Shipwork says so instead of guessing.
My platform is not Shopify or WooCommerce. Can I still be checked?
Yes. The site-wide checks read HTML and your sitemap, so reachability, indexation, schema, canonicals and more run on any platform. A product sitemap lets the catalogue checks run too.
How do I find my product feed?
Run this finder on your store. It checks the known public product-list endpoints and reports whether one answered and how many products it read. On Shopify and WooCommerce the list is normally exposed by the platform. If none is found on a store, the catalogue checks have no data to read.
Why does Shipwork need a public product list?
Catalogue checks for price, availability, images and descriptions read products from a list. Without one, only the HTML of a few product pages can be inspected. If no list is found, the finder says so rather than guessing, so a clean catalogue result always means the data was actually read.
Does the finder read my merchant center feed?
No. The feed you upload to a merchant platform is private and is not read by any Shipwork check. The finder only looks for a public product list that a crawler can reach. Keep your merchant feed and your public list sourced from the same product records so they agree.

Keep reading

What this reads

  • Reads public pages from outside your network, the way a crawler does.
  • No signup, and nothing is stored on the free checks.
  • One of 83 checks across discovery, content, markup, trust and catalogue data.
83checks
0signups needed
0stored on free checks
Cool, just ran an audit and got some insights! Let’s see if I can fix them :)
Tenta Dev, @DevTenta
Whoah! this site is crazy, nothing to roast at all
Ainreek, @AinreekAI
cool as heck, tried it on my blog and the insights it gave are helpful and not bluff.
Refaat 🍉 (Mouse), @1Mouse__