Google Merchant Center Feed Drift Check (Demo)
See how DriftGuard flags price and stock mismatches between a product feed and the live store, with a fix hint per item. Runs on built-in sample data; swap in your own store and feed URL.
Input
Output fields
Sign up on Apify or log in
The DriftGuard: Google Merchant Center Feed Price & Stock Checker Actor is ready to run with the inputs already set for "Google Merchant Center Feed Drift Check (Demo)". Sign up or log in and you'll land in Apify Console with a copy of this exact task.
Start the "Google Merchant Center Feed Drift Check (Demo)" task
The DriftGuard: Google Merchant Center Feed Price & Stock Checker Actor will start running based on the input automatically. You can also change all the input fields, like maximum charge per run (usd), to match your specific use case.
Receive the "Google Merchant Center Feed Drift Check (Demo)" output
Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as record type, product title, drift type, and more.
Integrate into your workflow
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Google Merchant Center Feed Drift Check (Demo)" task via API.

Integrate "Google Merchant Center Feed Drift Check (Demo)" into your workflow
Connect "Google Merchant Center Feed Drift Check (Demo)" with 100+ integrations, or run it via API or MCP.
Webhook
n8n
Make
Zapier
Airbyte
Keboola
IFTTT
Hubspot
GDrive
Gmail
Apify MCP
GitHub
Slack
LangChain
LlamaIndex
Flowise
Pinecone
OpenAI
Mastra
Clay
When your Shopify storefront price or availability no longer matches the feed Google (or Meta/TikTok) crawls — a common cause of disapprovals.
This example uses built-in demo data so you can see drift rows without connecting a store. For production, duplicate and set your storeUrl and feedUrl.
No. DriftGuard reads the public storefront and the public feed URL you already submit to Google/Meta/TikTok.
Daily is a sensible default. Repeat drifts on a schedule are deduped so you are not re-billed for the same open issue.