Lab component 21

Every page, showing its own working

One script tag, no configuration, and no cost until someone opens it. The passport runs identity, structure, schema, retrieval, and delivery checks against whatever page it is attached to. It is on this page right now.

Page Passport

Live on this page One script tag Zero cost until opened

The passport is already on this page. Scroll to the bottom of the content, or open it directly, and it will run the full set of checks against the document you are currently reading. It is present on every page in this lab, and every one of them reports different results because every one is a different document.

0Checks run until opened
0Network requests
0Dependencies
~11kB deferred
5Analysis surfaces
<!-- the entire integration --> <script src="/assets/page-passport.js" defer></script> <!-- optional: place it somewhere specific --> <div data-page-passport></div>
Tab 01

Identity

Title and description lengths, canonical target and whether it self references, indexability, language, and Open Graph completeness.

Tab 02

Structure

H1 count, the full heading outline with skipped levels flagged, word count, anchor text quality, and image alt and dimension coverage.

Tab 03

Schema

Every JSON-LD block parsed, nested nodes walked, required properties checked per type, and the proportion of nodes carrying a resolvable identifier.

Tab 04

Retrieval

Passages counted, each tested for whether it survives being lifted out of context, and the sentence most likely to be cited surfaced directly.

Tab 05

Delivery

Time to first byte, request count, bytes transferred, and live largest contentful paint and cumulative layout shift from your actual session.

Designed around the constraint, not the feature list

A component that ships on four hundred pages is a different engineering problem from one that lives on a single demo. Almost every decision here follows from that.

01

Nothing runs until it is opened

Closed, the passport costs one deferred script parse and a single DOM insertion. Every check, every parse, and every measurement happens on click. An SEO tool that degraded the performance of the site it reports on would be an embarrassing thing to publish.

02

It cannot break the page

Initialisation is wrapped end to end. If a check throws, the passport quietly does not appear and the page is untouched. Styles are prefixed and scoped so they cannot leak into the document being measured.

03

It reports honestly, including on itself

The passport measures the page it is attached to, flaws included. Publishing a panel that grades your own work in public only means anything if it is allowed to return a failure.

What it deliberately does not do

It has no access to Search Console, analytics, backlinks, rankings, or competitor data, because none of that is available to a script running in a visitor's browser. It sees exactly what a crawler landing on this URL sees, which is a narrower question than whether the page is any good. A passing passport means the page is technically well formed. It does not mean the content is worth reading, and no client should be told otherwise.