TS30Content and rendering

Do the metadata describe the right page?

Essential metadata is unique, visible and consistent with the page.

Prepare evidence

In the app: Evidence import
You provide: Titles, descriptions and content
Allow for: Depends on evidence needed

Prepare evidence

Understand

What the page announces. What it contains.

Essential metadata is unique, visible and consistent with the page.

According to Google

Google builds title links automatically from multiple sources. A descriptive, page-specific title indicates your preference without dictating the displayed text.

Influencing your title links in search results Source accessed on 2026-10-26

Check

The title promises. Does the page deliver?

In TSEP Control

You import evidence for this control. The engine assesses it within the declared scope; missing items remain visible.

Your contribution

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

With your own tools

Read title and meta description in source and after rendering. Compare with the visible heading and page topic; separately record the title actually shown by Google.

Evidence to retain

Consistent topic and promise without mechanical duplication.

What this result covers

Google may rewrite the title link or snippet in search results.

Act

Precise words. Faithful to the page.

Write page-specific metadata consistent with the visible subject.

Recheck

The published words. Then the displayed result.

After correction, gather new evidence with the same scope and expectations. Retain both dated observations to compare what changed.

Your reference points

To go further.

Statuses, sources and method.

Understand the statusesC · NC · NT · NA

The same legend in guides, analysis and demo. Each status depends on the control’s evidence and rules.

C · Verified: The criterion is met within the assessed scope. Keep dated evidence for the next comparison.
NC · To correct: Write page-specific metadata consistent with the visible subject.
NT · Not established: Evidence or confirmations are insufficient to conclude. Supply what is missing; this status does not establish an SEO error.
NA · Not applicable: The control does not apply to the scope under its rules, with a retained justification. Missing evidence alone does not make it non-applicable.

Sources and references1 reference

Influencing your title links in search resultsdevelopers.google.com · new tab

Detailed method and rules2 rules

Control method and criteria

Method
Compare title, description, H1, Open Graph and main content by template.

Acceptance criteria
Present metadata describes content without contradiction; uniqueness and duplication are assessed within the declared corpus, with human review.

Non-applicability
No document with relevant editorial metadata.

Detailed rules

TS30-A01 · Metadata and duplicates in the declared corpus

Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.

Scope
Prior finite TS30 population under render-transport-v1; see docs/render-transport-evidence.md. Amendment: docs/render-transport-prerequisites-v2.md.

Evidence
Exact originals, plan and dates/context, fingerprints, diagnostics and reasoned review bound to the entire dossier. Kinds: html, content, intent.

Method
Read native title, description, H1, og:title, og:description for each page. Compare prior values and duplicates among selected pages; require a prior decision for each intentional duplicate. Separately qualify H1 and descendant-text flags; preserve native contradictions in other fields.

Acceptance criteria
Values and multiplicity agree; each observed duplicate has one reasoned decision. The corpus is limited to supplied pages.

When the result remains inconclusive
Missing source, omitted field policy, ambiguous parse or missing review: NT. null permits only an explicitly absent optional field. Hidden/unqualified H1 or descendant text: NT, without manufacturing absence.

Non-applicability
No atomic NA. Empty population or claimed absent domain without evidence remains NT in this profile.

Assumptions
Supplied unauthenticated provenance, inventory, browser state, conditions and judgment; two static HTML readings are not two navigations. TLS trust depends on supplied roots.

Limitations
No real audit inferred from synthetic cases. No indexing, ranking, global conformity, accessibility certification, exhaustive security or universal browser trust. Reviews may be wrong and captures may omit states.

TS30-A02 · Editorial coherence and main content

Protocol assessment mode : manual. App availability is shown on the control card.

Scope
Prior finite TS30 population under render-transport-v1; see docs/render-transport-evidence.md. Amendment: docs/render-transport-prerequisites-v2.md.

Evidence
Exact originals, plan and dates/context, fingerprints, diagnostics and reasoned review bound to the entire dossier. Kinds: html, content, intent.

Method
Reconcile native metadata and identified main content; require a distinct review of promise, meaning and relevant visibility. Separately qualify H1 and descendant-text flags; preserve native contradictions in other fields.

Acceptance criteria
Facts agree with the plan and the bound editorial review supports them; qualified native or human contradiction fails.

When the result remains inconclusive
Unqualified required source/rendering, hidden content, meaning without review or unbound judgment: NT. Hidden/unqualified H1 or descendant text: NT, without manufacturing absence.

Non-applicability
No atomic NA. Empty population or claimed absent domain without evidence remains NT in this profile.

Assumptions
Supplied unauthenticated provenance, inventory, browser state, conditions and judgment; two static HTML readings are not two navigations. TLS trust depends on supplied roots.

Rule version 0.3.0-draft.5 · Public protocol reference · Versioned source

Put it into practice

← Back to controls