Where they click
A relative grid, not pixels: the same button lands in the same cell on a 390 phone and on a 2,560 monitor.
Against your domain, not against our database. Plus: where people click, where they come from and how long it really takes to load for them.
The stars come from that listing's published reviews. The title, from what your site declares.
No setup fee. Monthly, no lock-in.
No reading our own configuration and approving ourselves. It requests the public URL, follows the redirects and judges the HTML, the headers and the resources an actual visitor receives.
If a check can pass by looking at the database, that check is worth nothing.
And when something cannot be checked, it says so. A JavaScript-mounted site does not expose its alt text in the served HTML: it warns instead of silently passing the check.
Not over a grey rectangle: the background is a capture of your own page, requested at the width of the device you are looking at. Painting mobile clicks over a desktop photo puts them where they are not.
A relative grid, not pixels: the same button lands in the same cell on a 390 phone and on a 2,560 monitor.
Per element, with the label sanitised twice — on the server too, because the intake is public.
Which sections nobody sees, by the deepest band reached.
It is aggregated as it is written, so the trail never comes into being: no identifier, no IP, no session, no timeline to reconstruct. It honours Global Privacy Control and Do Not Track, and stores nothing on the device.
Visits today, over 7 and over 30 days, distinct people, countries, pages, device and campaign. Plus performance in the visitor's browser, not in a test of ours.
One stuck 30 s load drags the average and makes it look like the site is bad for everyone. You get the median and the p75, which is the threshold Google judges page experience by.
The referrer is sent from the client. Read from the header it came out as the site itself: with 8,000 people a month, only 3 visits showed as direct.
4g, 3g or wifi. Without it, a high LCP could be the site or could be the visitor's coverage.
Two beacons per load: one on arrival that counts the visit and one on leaving that completes it. Counting on leaving would lose exactly the ones that bounce.
The app declares what it publishes — the table, the slug, the price, the stock, the reviews — and from that same declaration come the sitemap, the indexable listings, the Google Merchant feed and the Meta one. A shop, an estate agency or an academy, with no per-client code.
They used to serve the home page's title and a canonical pointing at it: 160 pages telling Google they were a different one.
A shop with 40 categories had ONE page for Google, because the filter lived in memory and never changed the URL.
Only reviews with a published status and a 1-to-5 score count. With none published, nothing is sent, instead of inventing an average.
Google demands the currency next to the price. Assuming euros on a site that charges in pounds is handing false data to a search engine that shows it to a buyer.
And a bad declaration is caught on publish: every declared column is contrasted against the real schema and comes out as a warning with its name. It does not block publishing — a typo cannot drop a shop out of the index.
There are no rank-tracking reports here, no keyword audit, no bought links, no «page one guaranteed». Where you land on Google is not decided by whoever sells you the software.
What we can do: make sure what the search engine looks at is in place, check it against your domain and not against our database, surface the failure by name, and let you know who arrives and what they do. From there on, the content is yours.
The audit runs against your domain exactly as it is today, and we tell you what comes out — the good and the bad.
We answer the same working day.