Rabbot
Blog

Some Shopify problems never announce themselves.

August 23, 2026

  • shopify
  • seo
  • product-feed

You’ve read one of those threads. A store owner posts that their traffic went to zero overnight, or that Google stopped showing their product pages at all, and nobody in the replies can quite explain why. You read the whole thing, then open your own store in a new tab. It looks exactly the way it looked yesterday. That’s the unsettling part. A store looking fine tells you almost nothing about whether it actually is.

I read stories like these for a living now, and the ones that worry me are almost never the ones a merchant expects.

The short version: most of the ways a Shopify store breaks without warning turn out to announce themselves fairly fast. An app throws an error, or Search Console emails you, usually within days. There’s one class that doesn’t come with any of that built in, a tag or a feed field that reverts or breaks with nothing attached to say so, and it can cost you for weeks before a sales dip or a traffic report makes the case for you. That’s the one worth an actual habit. The other two stories below, you can read for what they are and then set down.

Start with the tags that live in a page’s own code, the ones Google reads to decide what to show. The meta title is the blue headline text Google displays for a page in its results. A related one is the canonical tag, the line that tells Google which of several near-identical pages is the real one to rank. Tags like these are the kind of thing you set once, in an app or a theme setting, and never look at again. They can also be overridden by that same theme or app later, and nothing on the storefront looks any different when it happens.

Take the meta title first. Universal Auto Spares, a car-parts shop on Shopify, had a proper meta title set on the homepage and every collection page. Google showed a generic, truncated version of the shop’s name on the homepage instead, and on a collection page it showed the collection’s own name, “Tools & Storage”, rather than the title the owner had set. The theme was overriding the custom titles behind the scenes, and Shopify support confirmed it by running the site through the store’s default theme, where the tags worked fine. By then, in the owner’s own words, “this issue has been going on for months now!”

A different owner watched their Search Console alerts become a pattern. “The last couple of weeks I have started the week with error messages from the Google search console,” they wrote. Search Console is Google’s own free dashboard for site owners, the place indexing problems turn into an email rather than a mystery. In this case, 103 product pages had been flagged as excluded by noindex, the instruction that tells Google not to show a page in search at all. One merchant further down the thread guessed at a cause, an app they suspected of writing noindex onto pages nobody had touched, but another merchant said that was a different problem on different pages, and the thread never settled on a confirmed answer for the 103. Either way, it’s one you can mostly let go of. If a tag like that lands on your pages, Search Console tends to be the one that tells you, often straight to your inbox.

Then there’s the case the community took four and a half years to explain, even once everyone had already spotted the symptom. A merchant running Shopify’s Dawn theme, plus the Shopify Product Reviews app, found each product page carrying two overlapping sets of star ratings and price data in Google’s results. The cause, worked out much later in the same thread, was that Dawn’s theme code already writes structured data, the extra bit of code behind a product page that tells Google things like price and rating so it can display them directly in the search result, for every product. The reviews app writes a second copy on top, and neither checks whether the other has already done it. I’d put this one lower on your worry list than it first looks. A community contributor in that same thread made a fair point: Google generally picks the better of two overlapping datasets and ignores the redundant one. The real risk is a slightly confusing-looking listing, not lost sales, and you can check it in a couple of minutes with Google’s own Rich Results testing tool.

The feed case is the one that deserves a little worry. Google Merchant Center is the system that turns your product catalogue into Google Shopping ads. A merchant found it kept pulling in their Shopify brand value in a way they didn’t want, so they edited a Shopify feed rule, the setting that maps your product data into the file Google reads, and set the brand field to clear across the whole catalogue. They came back to find, in their own words, “450 products are disapproved because of no BRAND.” Brand is one of the identifying details Google expects on a shopping listing, alongside things like a GTIN, the barcode number for a product, or a manufacturer part number, and a missing one puts a product at real risk of losing its place in shopping results.

Line those four stories up and a pattern falls out. Two of them come with a working alarm already wired in. A noindex tag shows up in Search Console’s own alerts, and duplicate structured data shows up the first time you run a testing tool, assuming you ever go looking. The other two don’t work quite the same way. Nobody at Google emails you to say your meta title or your canonical tag got overridden. Merchant Center does send a warning email when it flags a data problem, but it arrives with examples of what’s wrong rather than the full list, so the specific products affected still sit in a dashboard you have to go and open. Both add up to a similar result. Weeks can pass before you’ve pieced together the full picture, and the first place it often shows up is your own sales figures.

It’s a bit like a slow puncture on a bike tyre. A blowout stops you on the spot. You feel it, you get off, you deal with it there and then. A slow puncture doesn’t work that way. You ride to work fine on Monday, fine again on Tuesday, and by Thursday you’re pumping the tyre up every morning before you’ve worked out why. The tag or the feed field that breaks with nothing attached to say so is the slow puncture of your store. Everything else in this piece behaves like the blowout, the kind you notice straightaway, without needing a habit built around it.

Two of these four stories, the app-injected noindex tag and the duplicate structured data, tend to surface on their own, given a little time. You don’t need to carry them. The meta title and the feed rule are really the same worry told twice: a small setting breaks, nothing tells you the specifics in time, and your own sales figures end up doing the reporting. That’s the slow puncture. It earns one honest check, on purpose, not a daily worry.

That’s the specific gap I built Rabbot to catch. It watches your SEO tags and cross-checks your product feed for the kind of drift that puts you at disapproval risk, so you’re not left waiting three weeks for a sales report to break the news. The one-time feed cross-check is free forever, no card required. Checking every day from there, so a new gap gets caught the same day it opens, is the paid upgrade. Go and look at what’s already drifted, then decide what’s worth fixing.

Sources