How to Trace Google Ads Feed Drift by Layer: Merchant Centre, Product Feed or Live Site?
If Google Shopping performance has slipped but you cannot see an obvious error, the problem may be Google Ads feed drift. That usually means the product shown in Merchant Centre no longer matches the feed source, or the feed source no longer matches the live product page.
The mistake many teams make is treating this as one general feed issue. In practice, drift usually happens in one of three layers: Merchant Centre rules, feed generation, or live site data. If you do not isolate the layer first, you can waste time fixing the wrong thing and still leave the mismatch in place.
This guide is a practical triage approach for UK ecommerce teams, founders, commercial managers and marketers who suspect hidden product-data mismatch is affecting Google Shopping. The aim is not to audit everything at once. It is to find where the drift starts, then decide where the fix belongs.
What feed drift looks like in practice
Feed drift is when the same product has different facts in different places. It may be a price mismatch, an availability mismatch, a title mismatch, or a variant mismatch. The page still loads. The feed still exports. Merchant Centre still shows products. But the data is no longer aligned.
Common signs include:
- a product is live on the site but appears out of stock in Merchant Centre
- the shopping ad shows a sale price that no longer exists on the live page
- colour, size or bundle variants do not match between feed and product page
- Merchant Centre applies a rule that rewrites or suppresses the source data
- product titles, descriptions or categories differ enough to affect Shopping relevance
If those symptoms sound familiar, the next step is not to guess. It is to trace the drift layer by layer.
Start with the three-layer model
For a useful product feed audit, think in three layers:
- Layer 1: Merchant Centre - rules, diagnostics, feeds, supplemental feeds and feed processing
- Layer 2: Feed source - your ecommerce platform, PIM, ERP, export logic or middleware
- Layer 3: Live site - the product page, variant state, price display and stock messaging
Each layer can drift on its own. Merchant Centre may alter the imported data. The feed source may export the wrong value. The live site may show one thing while the feed captures another. The goal is to identify which layer is telling the truth last.
Trace Google Ads feed drift in the right order
Do not start with the CMS, and do not start with Merchant Centre rules. Start with the data as the shopper sees it, then work backwards.
Step 1: Check the live product page
The live site should be your first reference point because it is the customer-facing source of truth. Open the product page on desktop and mobile, then record:
- product title
- price
- sale price, if any
- availability
- variant details
- image used for the default variant
- shipping or delivery notes if they affect the listing
If the live page is already wrong, Merchant Centre is not the first problem. The feed is probably reflecting a bad upstream value or a stale product state.
Step 2: Compare the raw feed output
Next, inspect the feed export before Merchant Centre has a chance to process it. This may be a CSV, XML, API feed, scheduled export or platform-generated file. Compare the feed values directly to the live page.
Look for:
- price differences
- missing identifiers
- variant values that no longer match the product page
- titles that have been truncated, rewritten or simplified
- stock states that differ from the site
If the feed already differs from the site, the issue is likely in the feed source or export logic. If the feed matches the site but Merchant Centre shows something else, the drift is happening after import.
Step 3: Inspect Merchant Centre processing
Once the raw feed is confirmed, review the Merchant Centre layer. This is where Google Merchant Centre feed issues often appear because of feed rules, supplemental feeds, diagnostics, or processing settings.
Check whether Merchant Centre is:
- rewriting titles or attributes
- applying rules that alter price, availability or labels
- rejecting variants or products silently
- merging data from supplemental feeds in a way that changes the final output
- flagging warnings or disapprovals that point to a data mismatch
If Merchant Centre changes the data after import, the source feed may be fine. The fix then belongs in Merchant Centre rules, feed mapping or supplemental data logic.
A simple decision tree for fixing the right layer
Once you have compared the three layers, use this decision tree.
- If the live site is wrong, fix the product page, pricing logic, stock state or variant data first.
- If the live site is right but the raw feed is wrong, fix feed generation, source mapping, sync timing or export logic.
- If the raw feed is right but Merchant Centre is wrong, fix Merchant Centre rules, supplemental feeds, import settings or processing errors.
- If all three disagree, you may have more than one issue. Treat it as a layered data mismatch, not one bug.
This is the quickest way to stop feed drift from turning into a week-long guessing exercise.
How to tell which layer is drifting
Different symptoms usually point to different layers. That makes triage much easier if you know what to look for.
1. Merchant Centre drift
If Merchant Centre shows data that does not match the feed file, the drift is probably happening inside Google Merchant Centre. Typical causes include:
- feed rules rewriting attributes
- supplemental feeds overriding source values
- processing delays or import errors
- disapprovals caused by missing or mismatched attributes
This is where Google Merchant Centre feed issues often surface because the source is correct, but the imported output is no longer what you expected.
2. Feed source drift
If the feed file itself is wrong, the issue is upstream. The problem may sit in the ecommerce platform, PIM, ERP, export rule or middleware. Common causes include:
- field mapping changes
- stale product data
- variant logic that no longer matches the catalogue
- scheduled exports using old values
- price or stock sync delays
This is where a product feed audit needs to look beyond Merchant Centre and into the data pipeline.
3. Live site drift
If the feed and Merchant Centre match each other but both disagree with the live site, the problem may be on the website itself. This can happen when:
- the product page shows cached or outdated values
- variant selection updates the visible page but not the exported feed
- stock labels are generated separately from the commerce data
- promotional logic updates the site but not the channel feed
In that case, shopping feed optimisation alone will not solve it. The website data needs to be brought back into sync.
What to compare in your audit
For each product you test, compare the same fields across all three layers. Keep the list small and repeatable.
- Title - does it match in the site, feed and Merchant Centre?
- Price - does the current price align everywhere?
- Availability - is stock status consistent?
- Variant - are the right child products connected?
- Image - is the correct image used for the chosen variant?
- Category or product type - does the classification make sense in the channel?
- Identifier - are SKU, GTIN or MPN values correct where required?
If even one of these is off, note where the first mismatch appears. That is often enough to find the right owner for the fix.
Common causes of hidden product-data mismatch
Many teams think feed drift is a single technical fault. In reality, it is usually a chain of small decisions that no longer line up.
Feed source causes
- ERP updates arriving late
- PIM fields renamed without export updates
- variant attributes missing from the source record
- manual edits on the site not reflected in the feed
Merchant Centre causes
- rules that overwrite source values
- supplemental feeds that conflict with the main feed
- attribute mapping errors
- processing warnings that were not reviewed
Live site causes
- cached product data
- sale price display that differs from feed logic
- variant pages that show one default but export another
- mobile and desktop templates showing different states
When any one layer changes on its own, Google Ads feed drift becomes more likely.
A practical triage checklist for ecommerce teams
If you suspect a mismatch, use this quick process.
- Pick one product that is underperforming or being disapproved.
- Record the live page data.
- Extract the raw feed entry for the same product.
- Check the Merchant Centre version of the product.
- Compare the same fields side by side.
- Mark the first point where the values stop matching.
- Assign the fix to the layer that first drifted.
This process is simple, but it prevents a lot of unnecessary back-and-forth between marketing, ecommerce and development.
When Merchant Centre is not the place to start
It is tempting to open Merchant Centre and assume the problem sits there because that is where the disapproval or visibility issue appears. But the visible failure is not always the source of the failure.
If the live page and raw feed already disagree, changing Merchant Centre rules may only hide the symptom. The same applies if the feed source is stale or the website is exporting the wrong variant. Fixing the wrong layer can create more drift, not less.
That is why a good diagnostic order matters. Start with the page, then the feed, then Merchant Centre.
Where HOFK can help
HOFK works across ecommerce, SEO, Google Ads support, full stack development and website monitoring, which is useful when feed drift sits between systems rather than inside one obvious tool. In these cases, the value is often in tracing the data path clearly: from live site to feed source to Merchant Centre import.
That can help when the issue is a product data mismatch, a broken export, a Merchant Centre rule conflict or a website template that is showing something different from what the feed sends. In more complex setups, the right fix may involve feeds, APIs, monitoring and operational software rather than just one channel setting.
Conclusion
Google Ads feed drift is easiest to solve when you stop treating it as one generic feed problem. Trace it by layer instead. Check the live site first, then the raw feed, then Merchant Centre. That order tells you whether the fix belongs in website data, feed generation or Merchant Centre rules.
Once you know where the drift begins, you can make a narrower and more useful change. That saves time, reduces Google Shopping product data mismatch issues and makes shopping feed optimisation much more manageable. If your feed, Merchant Centre setup or live site needs a more technical review, HOFK can help with ecommerce support, SEO and Google Ads, full stack development and website monitoring.
Frequently asked questions
What is Google Ads feed drift?
It is when the product data shown in your live site, feed source and Merchant Centre no longer matches. The mismatch can affect price, availability, variants, images or product titles.
What is the best place to start diagnosing feed drift?
Start with the live product page, then compare it with the raw feed, and only then check Merchant Centre. That order makes it easier to spot where the data first diverged.
How do I know whether the issue is in Merchant Centre or the feed source?
If the raw feed file is correct but Merchant Centre shows different values, the issue is likely in Merchant Centre rules or processing. If the raw feed is already wrong, the source or export logic needs attention.
Can live site changes affect Google Shopping performance?
Yes. If the website shows one price, stock state or variant while the feed exports another, Google Shopping can surface inconsistent or outdated information.
Why is a product feed audit useful?
A product feed audit helps you compare the live site, source feed and Merchant Centre output so you can fix the right layer instead of guessing.