TS17Sitemaps and links
Sitemaps and linksCan your essential links actually be crawled?
Essential links use an a element with a resolvable href.
Prepare evidence
- In the app
- Evidence import
- You provide
- Essential links: HTML and rendering
- Allow for
- Depends on evidence needed
In the app
You provide
Allow forUnderstand
A visible link. A crawlable link?
Essential links use an a element with a resolvable href.
According to Google
Google can generally crawl a link when it uses an anchor element with an href attribute. A JavaScript interaction alone does not provide that assurance.
Check
An a element. A real destination.
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 toolsInspect HTML and DOM for menus, cards and essential links. Check for an anchor element with href, then open the destination to confirm it resolves.
Evidence to retain
Original HTTP bytes, bound DOM v2 tree, prior plan and separate source/render diagnostics; provider-declared states.
What this result covers
C only within the declared strategy. No established visibility, interaction, editorial importance, authenticity, Google visit, indexing or ranking. Source presence is not a universal Google requirement.
Act
Make the link. Resolvable and useful.
Use an a element with a resolvable href for each essential destination.
Recheck
Read the source again. Follow the 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
- Use an a element with a resolvable href for each essential destination.
- 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
Compare HTML a/href links in source and every declared DOM state; separate stages and exact document URLs.
Acceptance criteria
Each declared destination has a resolvable a/href in both required stages within essential-document-links-v1.
Non-applicability
No relevant navigation, with a justified scope.
Detailed rules
TS17-A01 · Essential links present in supplied source.
Protocol assessment mode : automatic. App availability is shown on the control card.
Scope
Declared essential destinations under the prior source-and-rendered strategy, on supplied captures.
Evidence
Original HTTP bytes, bound DOM v2 tree, prior plan and separate source/render diagnostics; provider-declared states.
Method
Read native source under both static scripting hypotheses; require their agreement.
Acceptance criteria
Every destination in the qualified stage: pass; established absence in complete inventory: fail; otherwise inconclusive.
When the result remains inconclusive
Missing/incomplete/out-of-profile plan or stage, active base, ambiguous reading or missing runtime. Independent contradictions remain.
Non-applicability
No automatic NA in this profile.
Assumptions
Prior plan, population, scenarios and completeness supplied; checked HTTP/DOM association but unauthenticated acquisition.
Limitations
C only within the declared strategy. No established visibility, interaction, editorial importance, authenticity, Google visit, indexing or ranking. Source presence is not a universal Google requirement.
TS17-A02 · Essential links present in declared rendered states.
Protocol assessment mode : automatic. App availability is shown on the control card.
Scope
Declared essential destinations under the prior source-and-rendered strategy, on supplied captures.
Evidence
Original HTTP bytes, bound DOM v2 tree, prior plan and separate source/render diagnostics; provider-declared states.
Method
Check each complete HTTP-bound tree and disclose repeated snapshots; scenarios are unauthenticated.
Acceptance criteria
Every destination in the qualified stage: pass; established absence in complete inventory: fail; otherwise inconclusive.
When the result remains inconclusive
Missing/incomplete/out-of-profile plan or stage, active base, ambiguous reading or missing runtime. Independent contradictions remain.
Non-applicability
No automatic NA in this profile.
Assumptions
Prior plan, population, scenarios and completeness supplied; checked HTTP/DOM association but unauthenticated acquisition.
Limitations
C only within the declared strategy. No established visibility, interaction, editorial importance, authenticity, Google visit, indexing or ranking. Source presence is not a universal Google requirement.
Rule version 0.2.0-rc.1 · Public protocol reference · Versioned source
Put it into practice
Source HTML and rendered essential links.