Why feed and landing-page prices drift apart
Most Google Shopping price mismatches come from the feed and the storefront updating on different clocks. A promotion ends, a currency or tax rule kicks in, a variant loads a different price, or cached structured data lags the live page, and suddenly the price Google read does not match what shoppers see.
- Feed and landing-page prices update on separate schedules, so a sale start or end leaves them out of sync.
- Regional pricing, currency, tax, or shipping context changes the price for some visitors but not the feed.
- Variant, personalization, or stock changes render a different price than the one Google crawled.
- Structured data (schema.org price) no longer matches the price visible on the page.
Monitor the feed and the live page side by side
You cannot fix drift you cannot see. Comptrace crawls the same landing pages Google reads and lines up the catalog or Merchant Center price against the live page price, with a scraped-at timestamp on every row. The point is not to promise approval; it is to surface the evidence your team needs to resolve a mismatch quickly and prove it stayed fixed.
- Compare feed price, live landing-page price, scraped-at timestamp, and mismatch status in one view.
- Keep the source URL attached to every finding so the price is traceable, not assumed.
- Surface coverage gaps as dated exceptions with status states instead of hiding them.
- Prioritize high-value and high-traffic products first when crawl coverage is limited.
Turn the evidence into a repeatable fix-and-verify loop
Once the monitored price, source page, and timestamp are reliable, the same evidence supports the rest of your pricing work: catalog cleanup, feed corrections, and controlled price reviews. A mismatch becomes a tracked action rather than a surprise disapproval.