TS20URLs and canonicals
URLs and canonicalsAre your URLs stable and unambiguous?
The URL structure is readable, stable and correctly encoded.
Prepare evidence
- In the app
- Evidence import
- You provide
- URL patterns and variants
- Allow for
- Depends on evidence needed
In the app
Allow forUnderstand
Different spellings. The same page.
The URL structure is readable, stable and correctly encoded.
According to Google
Google treats URL case as significant. Consistent conventions and useful parameters help limit unnecessary variants.
Check
Similar spellings. Equivalent responses?
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
With your own toolsSample site-generated URLs and compare case, encoded characters, parameters and separators. Open variants to distinguish real pages from equivalent addresses.
Evidence to retain
Documented URL patterns and no unintended variants.
What this result covers
A readable URL is not sufficient evidence of SEO performance.
Act
One convention. Stable addresses.
Stabilize path and encoding conventions, then fix unintended variants.
Recheck
The new URLs. The old links.
After correction, gather new evidence with the same scope and expectations. Retain both dated observations to compare what changed.
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
- Stabilize path and encoding conventions, then fix unintended variants.
- 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
Detailed method and rules2 rules
Control method and criteria
Method
Identify spaces, fragments, encoded characters, case and volatile identifiers.
Acceptance criteria
Encoding, case, stability and variations match declared rules; no observed unintended variant is left without a decision.
Non-applicability
No public URL in scope.
Detailed rules
TS20-A01 · URL shape under supplied policy
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Explicitly selected TS20 items; url-policy-v1 profile defined in docs/url-policy-evidence.md.
Evidence
Prior plan, original bytes and SHA-256, dates/context, atomic observations, reasoned human review bound to the entire dossier. Kinds: crawl, configuration, intent.
Method
Read the later capture and url-shape-config-v1. Check spaces/controls, backslashes, percent escapes, fragments and path case against prior choices; require human readability review.
Acceptance criteria
Configuration matches the plan and every URL satisfies its lexical axes. A qualified mismatch fails. No implicit case change or decoding.
When the result remains inconclusive
Unsupported URL/authority, unknown policy, missing capture or review: inconclusive.
Non-applicability
No atomic exemption in this profile. Empty population or absent evidence: NT, never automatic NA.
Assumptions
Supplied population and provenance; review assumes scope sufficiency and business judgment. Content, imported verdicts or hashes never prove authenticity.
Limitations
Bounded offline reading, without collection, browser execution, generated human judgment or real audit. Reviewed source scope only; no site completeness, indexing, ranking or causality inferred.
TS20-A02 · Temporal stability and variation decisions
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Explicitly selected TS20 items; url-policy-v1 profile defined in docs/url-policy-evidence.md.
Evidence
Prior plan, original bytes and SHA-256, dates/context, atomic observations, reasoned human review bound to the entire dossier. Kinds: crawl, configuration, intent.
Method
Compare two ordered url-crawl-v1 captures with matching identities; every changed URL requires one reasoned before/after decision in the reviewed plan.
Acceptance criteria
URLs match at the two dates or their variation is explicitly decided and reviewed. An observed change without a decision fails.
When the result remains inconclusive
One date, reversed/equal dates, missing identity or review: inconclusive. Future stability remains unknown.
Non-applicability
No atomic exemption in this profile. Empty population or absent evidence: NT, never automatic NA.
Assumptions
Supplied population and provenance; review assumes scope sufficiency and business judgment. Content, imported verdicts or hashes never prove authenticity.
Limitations
Bounded offline reading, without collection, browser execution, generated human judgment or real audit. Reviewed source scope only; no site completeness, indexing, ranking or causality inferred.
Rule version 0.3.0-draft.2 · Public protocol reference · Versioned source
Put it into practice
URL patterns and their variants.