Navigation

English market

Language

Blog

Case study: this site. What we keep from AMP, and what Google no longer rewards

I built WebsiteScorer.com as AMP HTML on purpose. Small JS budget. One layout that still works on a phone. Googlebot still reads <html amp>. That is detection, not a prize.

Until 2021 AMP could get you into Top Stories. That door is open to any page that is a real news page. In July 2026 Google stopped serving AMP from its own cache. A click in Search now lands on my URL, like any other site.

What this site already does

HTTPS, HSTS, a decent CSP. One URL per language, canonical and hreflang. A public methodology page. A sitemap. Open Graph with a 1200x630 image. JSON-LD for the organisation and the web app.

That is hygiene. It is not a secret format.

What was missing

A named person. Search still likes to know who stands behind a tool. For a long time the About page said Local Business Sites and stopped there. That is the company. I am the author: Sławek Kusy.

The JSON-LD on some locale pages pointed at the English URL and said the language was English. That is a bug, not a strategy. Those templates now use the page canonical and the HTML language.

The homepage FAQ is visible HTML. I dropped FAQPage JSON-LD because Google almost never shows FAQ rich results for a commercial tool. The questions stay on the page. I do not treat that markup as a ranking lever.

What I am not inventing

I will not publish fake client scores. If a later case study uses a real site, it will be a site I am allowed to name, with numbers from a dated report. This first note is about our own marketing pages, because I can stand behind every sentence.

If you run an audit on websitescorer.com, you will see AMP: yes. Read that as a technical fingerprint. Do not read it as "Google likes this more".