ShipworkSite inspection
Feed check

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.

Find the products Google is rejecting

Paste your store address. You'll see every product that breaks Google Shopping's rules and what to change on each one. Free for your first 500 products, with no account, no signup and nothing installed.

Works with Shopify stores that have a public catalogue. Shipwork reads only what shoppers can already see, and stores nothing.

What the product feed check reads

This check reads up to 500 products from a Shopify store’s public catalogue, from outside your network. It evaluates the visible product data that can be compared with a product listing: title, description, price, image, brand and availability. It also checks duplicate titles and catalogue-level patterns. It does not sign in to Merchant Center or retrieve private feed attributes.

A clean result means no issue was found in the fields and rules this check can see. It does not mean Merchant Center has accepted every item. Google can reject an item for account diagnostics, missing feed-only data, policy reasons or a mismatch that is not present when Shipwork fetched the site.

  • Product title and description, including missing text or prohibited promotional wording.
  • Price, image, brand and availability as exposed by the public catalogue.
  • Duplicate titles and catalogue-level patterns that can make listings unclear.
  • The products affected, the findings per product, and a concrete suggested correction.

How to read feed check results

The summary separates products with errors from products with warnings. An error marks a product issue the report says will be rejected; a warning identifies a risk worth reviewing. Each affected product is grouped with its title and handle, followed by the reason and a suggested change. Start with errors, then decide whether each warning reflects a real catalogue problem.

If no products are affected, the check found no problems in the tested public data. If Merchant Center still shows disapprovals, compare the affected item’s destination URL and current feed values with the page. Check Merchant Center diagnostics for account, policy and attributes this public check cannot inspect.

  • Open each affected product and compare its current page with the finding.
  • Fix the product or the system generating its storefront data, then rerun the check.
  • For disapprovals that remain, inspect the item-level reason in Merchant Center.

Fix common product data issues

Write titles and descriptions for the product itself. Remove campaign language from a title; keep promotions in a supported promotion field rather than text such as SALE or FREE SHIPPING. A duplicate title should distinguish the actual products, or the products may belong as variants of one item. Do not add details that are not true of the product.

Availability needs to agree with what a customer can buy. If an item is sold out, update the inventory and the system that publishes its product data. If the public page and feed disagree, fix the source that is stale rather than repeatedly editing only one copy.

  • Example: Merino running shoe, charcoal / natural sole describes the item; SALE - Free Shipping!!! is promotional text to remove.
  • Give distinct products distinct, shopper-readable titles; represent size or color choices as variants when appropriate.
  • Check that the product image loads and represents the item, and that the displayed price and availability are current.
  • After changes reach the public page, run the product page check for reachability and the structured data check for page markup.

When to use a feed check versus a feed file validator

Use this check when you want a quick outside view of the live Shopify catalogue and its shopper-visible product details. It does not require Merchant Center access or an uploaded feed. This is useful when the storefront appears correct to you but item data may be incomplete or inconsistent from a crawler’s perspective.

Use the feed file check when you have a CSV, TSV or XML file and need its actual fields validated. A file can contain identifiers and categories that are not publicly visible, so the live storefront check cannot infer them. For Google’s final decision, the Merchant Center diagnostics page remains authoritative.

Errors this check finds, and their fixes

Questions

What does the feed check look at?
Your whole public catalogue: title, description, price, image, brand, availability and duplicate titles: the data-level reasons Google Merchant Center rejects products.
Do I need Merchant Center access?
No. Shipwork reads only what shoppers can already see. Feed-only fields like GTIN are not visible publicly, so it does not guess at them.
How is this different from a feed validator?
Validators parse a file you upload. This reads your live catalogue from outside your network, catching the “looks fine to me” cases, including landing-page mismatches.
Can I check a Google Shopping feed without Merchant Center access?
Yes. This check reads a Shopify store’s public product catalogue, so it does not need Merchant Center credentials. That also limits what it can verify: private or feed-only attributes such as GTIN are not visible on the page and are not guessed. Use Merchant Center diagnostics to investigate account-level issues and the feed file check to inspect attributes in an exported file.
Why are my products disapproved when the page looks fine?
A working page is only one part of eligibility. The feed may be missing a required field, the page and submitted price or availability may differ, or an account or policy issue may apply. The feed check reviews public product data it can read; compare its findings with the exact item-level reason shown in Merchant Center, which has the authoritative account diagnostics.
Does the feed checker validate GTINs?
No. A GTIN is generally a feed attribute, not something reliably visible in a public product page. This checker does not log in to Merchant Center or invent identifiers. To validate fields such as GTIN, use a feed file that includes them and inspect Merchant Center’s item diagnostics for errors in the submitted identifier.
What does duplicate product title mean in Google Shopping?
It means the public catalogue contains more than one product with the same title. Identical titles make it harder to distinguish listings and can indicate duplicate products rather than meaningful variants. Give separate products accurate, specific names. If the items differ only by options such as size or color, check whether your catalogue should represent them as variants of a single product.
How do I fix a product marked out of stock?
First confirm whether the item is actually available for purchase. If it is available, correct inventory or availability settings in the store system that publishes the product data, then allow the public page and feed to update. If it is genuinely unavailable, do not claim that it is in stock; follow the platform’s normal handling for sold-out products and review Merchant Center diagnostics.

Related: product-page crawl check · product markup check · Merchant Center requirements, explained

Each rejection, in plain words: Missing description · Promotional text in title · Gratuitous capitalisation · Title over 150 characters · Missing brand · Price missing or zero · Missing image · Duplicate titles · all guides