Page Checks

Catch price mismatches before Google does

Google disapproves products whose page shows another price or availability than the feed, and suspends stores it can't trust. Page Checks reads a sample of your product pages every day, compares each with the row your feed sends, and checks your store for what Google's misrepresentation policy looks for.

Standard and up For Google Merchant Center, Microsoft and Meta feeds.

The comparison

The feed's own row against the page

A check compares what the channel receives with what a shopper sees — so it catches the mismatches Google would find.

  • Each sampled product goes through the feed's mapping and rules first, so the link, price, sale price and availability are exactly what the file sends.
  • On the page, FeedManager reads the offer from Product structured data (JSON-LD) first, then microdata, product meta tags, and finally the visible price — skipping struck-through old prices.
  • A price more than 1% away from what the shopper pays according to the feed, another currency, or "in stock" against "out of stock" is a mismatch. So is a page that answers 404 or 410.
  • A sale price counts while the feed's sale dates include today.
Checked pages Today · 50 pages
  • Matches Linen shirt — 49.90 in the feed and on the page 44
  • Differs Page 59.90, feed 49.90 — the sale ended on the site 3
  • Page not found 404 — product removed from the store 1
  • Not checkable No price in the HTML — drawn by JavaScript 2
An example of a day's pass. Each row shows what the feed sends, what the page shows and the likely cause.

Likely causes

Not only "differs", but why

Most mismatches have one of a handful of causes. Each differing page comes with the one that fits best.

VAT

The difference is about one VAT rate: one side has the price with tax, the other without. In most countries Google wants the price with VAT.

Sale timing

A sale is on in one place but not in the other. Check the sale price and its dates in the feed against the store's sale.

Another variant

The page shows the default variant's price. Link each variant to an address that preselects it, such as ?variant=…

Stale structured data

The visible price matches the feed, but the page's JSON-LD has another one — often a cached template. Google reads both.

Currency

The page shows another currency than the feed. Show the feed's currency to that country's shoppers, or send the feed in the store's currency.

Stock

Page and feed disagree on stock, often because it changed after the last sync. Sync more often, or send stock changes through the Product API.

The daily sample

The pages that matter most, every day

Each account gets a number of pages a day from its plan, shared between its Google Merchant Center, Microsoft and Meta feeds.

Landing pages checked a day per plan
PlanPages checked a day
Free —
Standard 25
Pro 50
Premium 100
Enterprise 200
  • Half the sample is your most viewed products (from Google Analytics), a quarter those that changed in the last two days, the rest picked at random.
  • Every feed gets at least five pages; when the day's budget is too small for that, feeds take turns.
  • A pass runs once a day by itself. Check Now spends what is left of the last 24 hours' pages.
  • An alert when 5% or more of a feed's checked pages differ or are missing — in the panel and by email. The feed's page shows the latest pass.
  • Results are kept for 30 days.
Compare plans

Store trust

Ten checks for Google's misrepresentation policy

Google suspends stores when it can't see who sells, at what price or on what terms. Once a week — and when you click Check Again — FeedManager reads your home page, its contact page and robots.txt, and explains every check in plain words.

Who you are

  • Secure connection — the whole store on HTTPS; http:// redirects to https://
  • Contact page — linked from the home page, best in the footer
  • Phone number — on the home or contact page
  • Email at your domain — [email protected], not a free mailbox
  • Business address — on the site or in Organization structured data

Your terms and pages

  • Return policy — linked in the footer, as Google requires
  • Shipping policy — costs and times, matching Merchant Center
  • Privacy policy — wherever the store collects personal data
  • Googlebot may read product pages — robots.txt doesn't block the home page or product pages
  • Product structured data — JSON-LD with price and availability on 80% or more of the pages read

Pass, check or fix

A link in the footer passes; the same link elsewhere on the page is marked "check". Link words are recognised in the languages of FeedManager's markets, from "İade" to "Widerruf". With Merchant Center connected, Google's own account issues come with a checklist too — and the article Merchant Center misrepresentation and price mismatches walks through both.

Only where you allow it

A careful visitor on your own store

  • Nothing is read until a manager confirms the store's domain and that FeedManager may read its pages. Up to ten domains per account; the www and bare twin count as one.
  • Only pages on confirmed domains are read. A product link to another site is counted as "other domain" and never contacted; a redirect elsewhere is refused before it is followed.
  • robots.txt is honoured for the user agent FeedManager and for every bot, and at most one page is read every three seconds per store.
  • It is a check, not a crawler: nothing read on a page goes into your products.

What it can't check

Pages that draw the price with JavaScript are marked "not checkable": FeedManager reads the HTML and its structured data, without a browser. Adding Product structured data (JSON-LD) fixes that, and Google relies on it too.

Pages are read with the language of your account's currency, not from inside each country, so a store that changes prices by the visitor's location may differ from what Google sees.

Page Checks

Questions about Page Checks

Which pages does FeedManager read?

Only pages on store domains a manager confirmed, and only the product pages your active Google Merchant Center, Microsoft and Meta feeds link to — plus, for the store-trust checklist, the home page, its contact page and robots.txt. Links to other domains are counted, never visited.

How many pages are checked?

Standard checks 25 pages a day, Pro 50, Premium 100 and Enterprise 200, shared between the feeds; each feed gets at least five. The Free plan has no page checks.

How is the price compared?

With the price shoppers pay according to the feed — the sale price while the feed's sale dates include today — after the feed's mapping and rules. More than 1% (and more than 0.01) apart is a mismatch, as is another currency or in stock against out of stock.

Will the checks slow down my store?

No. FeedManager reads at most one page every three seconds per store, honours robots.txt for the user agent FeedManager, and reads a few dozen pages a day. You can block it in robots.txt at any time; those pages are then shown as blocked.

Why is a page "not checkable"?

Its HTML has no price and no Product structured data, so the price is probably drawn by JavaScript. FeedManager doesn't run a browser. Adding Product structured data (JSON-LD) with price and availability makes the page checkable, and Google relies on it too.

Does it fix the mismatches?

No. It tells you which pages differ and the likely cause — VAT, sale timing, a default variant, stale structured data, currency or stock — so you can fix the feed, the source or the store. Nothing read on a page goes into your products.

Find the pages that don't match your feed

Confirm your store's domain on Standard or above, then click Check Now.

Private beta — accounts by invitation.