Buyer proof
A public trust page gives buyers a simple place to verify score, ownership and freshness.
Verified credential
Turn your PageLens AI score into public proof.
An owner-verified, cryptographically signed badge for your domain. Embed it in your footer, README or pitch deck and link to a public trust page visitors can verify.
The goal is simple: show customers, investors and buyers that the site has been independently launch-checked instead of asking them to trust a self-awarded quality claim.
Backlink flywheel
Every embedded badge can point back to a PageLens AI verified page and grow public recognition.
Repeatable standard
The badge is backed by the same methodology, score and evidence model as the private report.
Verified, not self-graded.
The number on the badge is the same number on your dashboard — but you can only publish it after we've confirmed you control the domain. No verification, no badge.
- DNS TXT recordAdd a single TXT record on your apex domain. Best for production sites where DNS access is the source of truth for ownership.
- .well-known fileDrop a static text file at /.well-known/pagelens-verify.txt. The fastest path if you control the web server but not DNS.
- HTML meta tagAdd a <meta name="pagelens-verify" …> on your homepage. Works on platforms (Webflow, Framer, Shopify) where you can edit head HTML but not files.
Tamper-proof by design.
Every badge we serve carries an HMAC-SHA256 signature over the score, grade, domain and issue timestamp. The signature is embedded in the SVG metadata and the JSON response — anyone can confirm the badge they're looking at really came from PageLens AI.
- Score, grade and timestamp signed together — change any field and the signature breaks.
- Hot-linked from our domain — there's no way for a site owner to serve a badge image we didn't generate.
- Verifications older than 90 days are visibly flagged as stale on the public trust page.
- Scoring algorithm version is stamped on every scan, so historical badges remain truthful when our scoring evolves.
Always current
Embed once. The badge keeps itself up to date.
Every new scan you run on a verified domain refreshes the badge automatically. There's no version to bump, no SVG to re-export, no broken image when you fix something. The/verified/<your-domain> page is also evergreen — it always reflects your latest COMPLETE scan.
Drop it anywhere
We generate ready-to-paste snippets for HTML, Markdown and React — plus the bare image URL for your own wrappers.
HTML
<a href="https://www.pagelensai.com/verified/example.com" target="_blank" rel="noopener" style="display:inline-flex;min-height:24px;align-items:center">
<img src="https://www.pagelensai.com/badge/example.com" alt="PageLens AI verified" height="22" style="height:22px;width:auto" />
</a>Markdown
[](https://www.pagelensai.com/verified/example.com)JSON (Shields.io-compatible)
GET https://www.pagelensai.com/api/badge/example.com
{
"schemaVersion": 1,
"label": "PageLens AI",
"message": "92 · A",
"color": "brightgreen"
// …plus signed extras: score, grade, verifiedAt, signature
}Real snippets (with your verified domain pre-filled) live on your dashboard once you've claimed a domain. The badge renders at its native 22px height, while the link wrapper keeps the tap target at 24px for accessibility — the inline style on the snippet keeps it that size even when your site has amax-width: 100%image reset.
How verification works
- 1
Scan your site
Run any paid scan from your dashboard. The scan record is what links you to the domain — claims must come from an account that has actually scanned the site.
- 2
Claim the domain
From the dashboard's Verified domains screen, hit Claim badge for the site you want. We canonicalise to the eTLD+1 (so example.com and www.example.com are the same domain) and reserve it against your account.
- 3
Prove ownership
Pick DNS, .well-known or meta — we generate a one-time token for that method and run a probe. Probes are SSRF-hardened, never follow redirects, and time out aggressively.
- 4
Embed and forget
On success, the badge endpoint and your /verified/<domain> trust page go live immediately. We handle CDN caching and refreshing the score on every new scan.
Common questions
Do I need a paid plan to use the badge?
You need at least one paid scan on the domain — the scan record is the link between you and the site. Once that exists, badge verification, the public trust page and the embed snippets are all included at no extra cost.
What happens if my score gets worse?
The badge updates to your latest score. We don't let you pin or hide a previous high score — the whole point of a verified credential is that it's current. If you'd rather not publish at all, the badge endpoint can be set to private and your /verified/ page becomes a holding card.
What if a competitor tries to claim my domain?
They can't. Claims are reserved against the first user that successfully verifies, and any conflicting claim from another account is rejected. Until proof of ownership lands, the domain just exists as bookkeeping — no public surface advertises any score for it.
Can I rotate verification methods?
Yes. Re-verify any time — switching from .well-known to DNS, for example, just runs a fresh probe and updates the verification method on file. The badge URL stays the same.
What stops someone gaming the score?
The badge can only be issued to a verified domain owner, and we reserve the right to revoke it if the live site materially diverges from the content the score was computed against — for example, serving different HTML to our crawler than to real visitors. The score is deterministic over the audit findings, so it can't be edited; the only way to change it is to fix the underlying site.
Ready to make your score public?
Try a full audit for $1, verify the domain, embed the badge. The whole loop takes under five minutes if your DNS console is open.