How to use Shopify SEO check | Checkout Club¹⁰¹

The pass

Paste a public Shopify URL. Open Shopify SEO check and do it in this order.

Paste the hero product, the collection you advertise, or a page you just rebuilt. The homepage is a weak sample of product schema.
Compare the name, price, and availability in the result with the buy box. If they differ, fix that before you write more content.
Check whether robots.txt blocks Googlebot or OAI-SearchBot. Blocking Googlebot affects Google Search. Blocking OAI-SearchBot is how you opt out of ChatGPT search. Those are different decisions. ChatGPT and Google on a Shopify store separates them.
Use the links on the result to open an assistant and ask about that URL yourself. The check does not return a citation, and an answer that never mentions you is not a defect in the checker.

The mistake that wastes the pass

Celebrating a matched price while a second Product node, often from a review or bundle app, still says something else. View the source if the result looks too clean.

How you know it worked

The name, price, and availability in the result match the buy box, and they still match after you publish the theme. If an app adds schema, check once more. A matched price is the pass. A ranking is not.

Which URL to paste into a Shopify SEO check

Paste the product you advertise, or the collection page that is supposed to rank, or the page you rebuilt today. A homepage without a product offer will not teach you much about product schema. A password page or an unpublished product will teach you that the public web cannot see it, which you already know if you set it up that way.

If the store uses markets, decide which country you are checking. Open the URL in a browser and note the currency. Then run the check and compare against that same presentation. A result in euros is not a failure of a dollar price you saw on a US VPN. It is a different market.

Check one URL, fix it, then sample a second template. Products that share a template share a schema pattern. Products with an app block only on one template do not. Two samples catch both cases. Twenty samples before the first fix just delay the publish.

How to change robots.txt without blocking Search by accident

Read the existing robots.txt before you add a line. Shopify serves it from the online store. A theme that contains robots.txt.liquid replaces the generated file, so the liquid file has to include the rules you still want, not only the new disallow.

If the goal is to keep a filter URL or a search results URL out of the index, disallow that pattern, not the product path. If the goal is to opt out of a training crawler, name that token. Do not paste a list of every bot you have ever seen in a server log. A log is full of fetchers that are not the ones you mean, and a broad disallow can include Googlebot if you copy a block you did not read.

After you publish, open https://your-store/robots.txt in a browser and read it. Then run the check again. Confirm Googlebot is still allowed on the product URL unless you intended otherwise. Confirm the training token you meant to change is the one that changed.

A bot challenge in front of the store can block a crawler that the file allows. If the check or Search Console says the page could not be fetched and robots.txt looks open, the next place to look is the challenge, the firewall, or an app that gates the storefront. The liquid file is not the only door.

How to correct a product schema mismatch

Write down the name, price, currency, and availability from the buy box, for the variant you care about. Write down the same four from the check. Circle the one that differs. That circle is the task. Do not start by rewriting the product description.

In the theme code, product structured data usually lives in the product template or a snippet the theme vendors maintain. Prefer fixing the product data in admin when the theme is printing the product faithfully and the admin value is wrong. Prefer a theme or app fix when the admin value is right and the HTML is wrong.

App blocks that add schema often have a setting named something like “output structured data” or “SEO snippet.” Turn off the duplicate before you delete the app. If you cannot find the setting, disable the embed, reload the product, and see whether the extra node disappeared. That isolates the author.

When the page matches, check the variant the campaign uses and one sold-out variant. Availability is where a “fixed” product still lies. Then leave it, and check once more after the next theme update. Theme updates replace snippets.

What to confirm outside the check

Search Console tells you whether Google indexed the URL and whether it reports a rich-result error. The Shopify SEO check does not. Use Console when the question is indexing. Use the check when the question is the offer in the HTML you just published.

Ask an assistant about the product only as a curiosity, and do not treat the answer as a test you can pass by editing a sentence. If you want to see what a fetch of your URL returns to a person using ChatGPT, that is a user-initiated fetch, which depends on their product and on whether the page is public. It is not proof of search inclusion.

Keep a note: URL, date, mismatched field, fix, and the rerun. The next app you install will be easier to debug if you know the page was clean on that date.

Theme updates and app updates undo schema quietly

A theme update replaces snippets. If your product structured data lived in a snippet you or an app had changed, the update can restore the theme’s version or drop the custom one. The page will still look like your product. The data may not. Run the Shopify SEO check on the hero URL the day you update the theme, even when the changelog did not mention SEO.

An app update can turn schema back on. Review apps and bundle apps do this because the feature is useful when it is the only source, and harmful when the theme already prints a correct Product node. After the update, search the page source for the type Product. Two blocks means you are back to the mismatch you already fixed. Turn the extra one off again, and note the app version so you recognize the pattern next time.

Translations add another copy of the same risk. A translated title in the buy box and an untranslated name in the structured data are not always a defect, but a translated price format that breaks the currency field is. If you just published a language, check one product in that language. Look at the currency code, not only the symbol the theme paints on the button.