No, the Google Content API for Shopping never gave you competitor prices, so its retirement does not break competitor price tracking, but it does show that no official Google API will. Google's replacement, the Merchant API, manages your own product feed. To see what rivals charge, you need public-page data: a hosted scraper, a SERP data service, or a page-change monitor. This guide shows how to pick between them and what each costs to run.
What happened to the Google Content API for Shopping?
Google is replacing the legacy Content API for Shopping with the Merchant API. Several 2026 industry write-ups report that the old API was scheduled to shut down on 18 August 2026 (check Google's developer documentation for the authoritative date). Both APIs are built for merchants: you upload and manage your own products, offers and account settings.
That matters because many "competitor price API" searches assume the official API can read other sellers' prices. It cannot. Retail trade coverage of the earlier Google Shopping API shutdown made the same point: retailers who relied on Google for market prices had to look elsewhere (see Retail IT Insights).
What are the real options for tracking competitor prices?
| Option | Best for | Main weakness |
|---|---|---|
| Official Merchant API | Managing your own feed | No competitor prices at all |
| SERP / Google Shopping data APIs | Broad "who sells this" coverage | Vendor pricing varies widely, results depend on Google's page layout |
| Hosted scraper per marketplace | Exact product, seller and price per store | Covers only the stores the scraper supports |
| Page-change monitor | Watching a few competitor pricing pages | Gives diffs, not structured price tables |
| DIY scraping | Full control | You maintain proxies, selectors and bot-block workarounds |
Vendor sources describe DIY Google Shopping scraping as fragile: products load through hidden asynchronous calls, and anti-bot systems such as Cloudflare and DataDome block naive scripts (for example the guides from Decodo and Minderest). Those are vendors with products to sell, so treat their framing with care, but the maintenance burden they describe is real for anyone who has run a scraper.
How do I compare one product's price across marketplaces?
If you sell a product with a known identifier, the simplest route is to search by that identifier on each marketplace and compare. The Amazon, eBay, Best Buy and Newegg price comparison actor takes ASINs, UPCs, model numbers or plain product names and returns the highest, lowest and typical price with a source URL for each. Its AI step verifies each listing is the exact product, so accessories, bundles and refurbished units do not distort the range. Check the actor page for the current per-event rate before you size a run.
A practical workflow:
- List your top 50 to 200 SKUs with a UPC or model number.
- Run the checker on a schedule (weekly is enough for most catalogues, daily for volatile categories).
- Export to a Google Sheet and flag any SKU where the lowest competitor price sits below yours by more than a margin you choose.
How do I catch sellers advertising below my minimum price?
If you are a brand rather than a reseller, the question changes from "what do rivals charge" to "who is undercutting my minimum advertised price". The MAP violation monitor takes your products and MAP prices and returns every public offer on Amazon, eBay, Best Buy and Newegg advertised below them, with graded severity, the seller's identity and an evidence link. We cover the full process in MAP violation monitoring for unauthorized sellers.
How do I watch a competitor's pricing page?
Not every competitor sells through a marketplace. SaaS tools, agencies and local shops publish prices on their own sites. A page-change monitor is the right tool there. The Website Change Monitor returns a clean added/removed diff, supports keyword watching and sends alerts to Slack, Discord, Telegram or any webhook. For software vendors specifically, see the SaaS Price Hike Monitor.
How do I only see prices that changed?
Raw price tables get noisy. The Dataset Diff actor compares consecutive runs of any actor and returns only new, edited and removed rows with the previous values. Its published rates are $0.00002 per item compared, $0.0015 per change returned and $0.004 per alert, so checking 10,000 unchanged rows costs $0.20 according to the actor's own listing.
Is scraping competitor prices legal?
Collecting publicly visible prices is common practice, but the law varies by country and by how you collect. Court decisions in the US have increasingly turned on whether data sits behind a login. We summarise the current picture in our logged-out rule checklist. This is not legal advice: avoid logins, respect rate limits and take counsel for anything high-stakes.
What does a sensible price-tracking setup look like in practice?
Most small teams over-build this. A workable setup has four parts, and none of them needs custom code.
- A product list. One sheet with SKU, your price, UPC or model number and, if you have one, your MAP price. Clean identifiers matter more than anything else, because matching the wrong product is the main source of bad price data.
- A scheduled collection step. Run the price checker on Apify's scheduler. Start weekly. Move high-volatility SKUs to daily only after you have seen how often their prices really move.
- A change filter. Pipe results through the dataset diff step so only meaningful moves reach a human. A price that changed by a few cents is rarely worth an alert, so set a threshold such as 3 percent.
- A destination. Google Sheets for a small catalogue, Slack or Telegram for alerts, a webhook into your repricing tool for larger shops. If you prefer a no-code builder, the same actors run from n8n; see our n8n, Zapier and Make comparison for how the platforms differ.
What mistakes make competitor price data useless?
- Comparing different products. Bundles, multipacks, refurbished units and accessories share a title with the real product. Verify matches by identifier, not by name alone.
- Ignoring shipping and condition. A lower headline price with expensive delivery is not undercutting you. Record condition and seller so you can filter later.
- Treating one scrape as truth. Marketplace prices change through the day. Compare trends across several runs before you reprice.
- Repricing automatically too early. Review alerts by hand for the first month. A bad match that triggers an automatic price cut costs real margin.
- Forgetting the cost of the data. Work out cost per 1,000 results before scheduling. Our guide to what scrapers cost now shows how to do that arithmetic.
How does this differ from AI shopping assistants?
Shoppers increasingly ask AI assistants where to buy a product, so being priced competitively on the stores those assistants read matters more than before. The same public-page data that feeds your price tracker is what those assistants see. If you also want to know whether assistants recommend your products over rivals, our post on checking whether ChatGPT recommends your competitors covers that side.
How do I estimate the cost before I start?
Cost depends on three numbers: how many SKUs you track, how many marketplaces each one is checked on, and how often you run. Multiply them to get results per month, then multiply by the per-result rate shown on the actor page. For example, 100 SKUs checked weekly is roughly 400 to 450 runs of one product a month; at a rate of, say, a few cents per 1,000 results that is trivial, whereas a daily run across 5,000 SKUs is a different budget entirely. Always read the live rate on the actor page, because pay-per-event prices can change, and set a maximum spend per run in Apify so a mistake in your input cannot run up a bill.
The same arithmetic applies to any alternative you consider. A SERP data service bills per search, a hosted scraper bills per result or event, and a DIY scraper bills in proxy bandwidth and your own time. Compare them on cost per correctly matched price, not on headline price per request, because a cheap request that returns the wrong product is worth nothing.
Which approach should I choose?
- Under 200 SKUs on the big four marketplaces: the price comparison actor on a weekly schedule.
- Brand protection: the MAP violation monitor.
- A handful of competitor sites: the website change monitor.
- Thousands of SKUs across Google Shopping: a SERP data service may fit better, and our wider guide on tracking competitor prices automatically covers the trade-offs.
Browse the full set in the price monitoring hub.
FAQ
No. The Merchant API manages your own products, offers and account data. It does not return other sellers' prices, which is why competitor tracking relies on public-page data instead.
Industry write-ups report a scheduled shutdown on 18 August 2026 as Google moves merchants to the Merchant API. Confirm the exact status in Google's developer documentation, since dates can change.
Weekly suits stable categories. Daily suits fast-moving ones such as electronics. Use a diff step so you only review what changed.
Hosted actors handle proxies and page changes for you, so you do not need to run your own infrastructure. You do need an Apify account, which includes free starter credit.
Try it
Start with the price comparison actor on Apify and run it on ten of your own SKUs before scheduling anything.
Last updated: November 2026
โก Run this without building it
These actors already do what this guide describes. Free $5 credit on a new Apify account.
๐ Keep reading
Get the Free Web Scraping Toolkit
Join the newsletter and get my curated list of scraping tools, proxy comparison cheatsheet, and Python automation templates.