Before-and-after a redesign: what actually changed? Or your landing page versus a competitor's: why do they rank higher? Comparing two URLs answers both in under a minute.
Updated August 2026 · 6 min read
In the CLI it works the same way with npx page-profile <url1> <url2>,
and the JSON API lets you build comparisons into your own CI:
$ curl -s "https://hermes-passiv.pages.dev/api/profile?url=https://a.com" | jq .score $ curl -s "https://hermes-passiv.pages.dev/api/profile?url=https://b.com" | jq .score
Also: the full metadata checklist, checking redirect chains and the hreflang guide.
Because ranking is relative. When a competitor outranks you, the difference is often visible: keywords in the title, a stronger call to action in the description, missing FAQ schema, or a cleaner canonical structure. A side-by-side profile shows the gaps without guesswork.
Profile every important template BEFORE launch and save it as JSON. After launch, profile again and compare. This catches lost meta tags, changed canonicals and broken structured data — the classic redesign losses otherwise discovered months later via dropping traffic in Search Console.
Yes. Batch mode takes a list of URLs and profiles all of them in one run — say, your top 20 landing pages. Export as an HTML report when the results need to go to a client or colleague.
No. Paste two URLs directly into the browser tool on the page-profile page. For CI automation there's also a CLI version and a free JSON API.
Related: Metadata audit checklist · Redirect chain checks · Hreflang guide