Your Product Feed Says Your Store Is Somewhere It Isn't

The seller fields in a product feed are the ones nobody checks. A store URL that doesn't resolve, or that disagrees with your own product links, produces a feed that delivers perfectly and can't be verified by anything on the other end. Here's how to catch it.

A merchant wrote to us last week. Their ChatGPT feed, they said, wasn't connecting to their website. It was going somewhere else entirely — their parent company's corporate domain, which had never been attached to their Shopify store.

We checked both domains. Their storefront answered normally and was served by Shopify, exactly as it should be. The corporate domain had no DNS record at all. Not misconfigured — absent. Nothing on the internet could reach it.

Their feed was, in effect, introducing them as a shop at an address that doesn't exist.

Why this class of bug is invisible

Every part of the pipeline reports success.

Your feed tool validates the file: all required columns present, prices formatted, images resolvable. Pass. The delivery runs: file written, bytes transferred, no errors. Pass. Your dashboard shows a green checkmark and a row count.

And then nothing happens, for weeks, because the one field describing who is selling points into the void — and no validator checks whether a seller URL is a real place, because that's a question about the world rather than about the file.

Product feeds are unusual this way. A broken product URL costs you one row. A broken seller URL costs you the whole file's credibility, and it fails silently, because the file itself is perfectly well-formed.

The three ways seller identity goes wrong

1. The domain doesn't exist. Usually a typo, or a domain that was planned and never registered, or one that lapsed. DNS resolution is a yes/no fact — and it's worth checking, because nothing else in the pipeline does.

2. The domain exists but isn't your store. A corporate domain, a holding company, an old domain from before a replatform. This is the case we hit. The feed is internally inconsistent: seller_url names one place, every product link points at another. Anything trying to verify that you are who you say you are has two different answers.

There is a legitimate version of this — some merchants genuinely sell under a separate storefront — so it isn't automatically wrong. But it should be a decision you made, not a value you inherited from a form you filled in once.

3. The field is empty. Seller name is required on every row by the spec; seller URL usually isn't. "Optional" gets read as "ignorable", and an empty column helps nobody. Worse, some tools fall back to your myshopify handle, so shoppers see quickstart-72eb4431 where your brand should be.

The check that takes thirty seconds

Open your feed settings and read the store URL out loud. Then:

• Does it resolve? Paste it in a browser. If you get a DNS error, that's your bug and nothing downstream will work until it's fixed.
• Is it the same host your products link to? Open any product row in your feed and compare. If seller_url says example-corp.com and the product links say example-shop.com, decide which is true and make them agree.
• Does it match the domain on your ads account? Whatever platform you're feeding will have its own notion of who you are, set when the account was created. That's a third place the same fact lives, and the one people forget.
• Is your seller name your brand, not a slug?

Why we're writing this down

Because the merchant who reported it had done everything right on their side. Every store-side field was filled in correctly, including their store URL. The mismatch lived in their ads account, set up months earlier under a corporate domain, and there was no screen anywhere that showed the two values side by side.

That's the real lesson. Your store identity is stored in at least three places — your Shopify domain settings, your feed configuration, and your ads platform account — and nothing reconciles them for you. When they drift apart, everything keeps reporting success.

If your feed has been delivering for weeks and nothing is happening downstream, check the seller fields before you touch the product data. It's a thirty-second check that's saved us more time than any amount of catalog work.

FoundGPT refuses to deliver a feed whose store URL doesn't resolve, and flags one that disagrees with your product links rather than shipping it silently. Format validity was never the hard part.