TS18Sitemaps and links
Sitemaps and linksWhich pages are too deep or isolated?
Depth and orphan pages are measured within an explicit scope.
Prepare evidence
- In the app
- Evidence import
- You provide
- Inventory, starting points and links
- Allow for
- Depends on evidence needed
In the app
You provide
Allow forUnderstand
How many links to get there?
Depth and orphan pages are measured within an explicit scope.
According to Google
Internal links help discover and understand pages. Starting points, scope and depth thresholds assessed here are defined in your TSEP plan.
Check
Expected pages. Discovered pages.
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 toolsCrawl from identified starting points and compare discovered URLs with the complete expected inventory. Date the paths and justify depth thresholds; a crawl alone can miss orphan pages.
Evidence to retain
Dated fingerprinted original inventories, declared production/dependencies, prior plan, original HTTP/source/DOM, pairs and bounds, per-inventory dates and supplied reviews bound to exact dossiers.
What this result covers
Declared graph only: no completeness, site-wide orphan, universal SEO depth, authenticated acquisition/reviews, observed interaction, indexing or ranking. HTTP200 does not verify expected content or soft404s. The reader does not adjudicate supplied rationale.
Act
Connect the isolated. Bring priorities closer.
Bring priority pages closer and connect isolated pages within the studied scope.
Recheck
Same starting points. New pathways?
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
- Bring priority pages closer and connect isolated pages within the studied scope.
- 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 rules3 rules
Control method and criteria
Method
Reconcile original reference, crawl, CMS and sitemap inventories; compute native bounded graph links/distances; verify supplied reviews bound to family and difference measurements.
Acceptance criteria
Three complete layers within supplied scope: qualified reconciliation, qualified native measurements and bound documentary reviews. An evidenced reviewed defect remains NC despite another unknown.
Non-applicability
No relevant navigation graph, with a justification; a missing inventory means NT.
Detailed rules
TS18-A01 · Prior scope and reconciled original inventories.
Protocol assessment mode : automatic. App availability is shown on the control card.
Scope
Population, roots, families and boundaries declared before captures; bounded supplied-graph-reconciliation-v1 profile.
Evidence
Dated fingerprinted original inventories, declared production/dependencies, prior plan, original HTTP/source/DOM, pairs and bounds, per-inventory dates and supplied reviews bound to exact dossiers.
Method
Read explicitly declared formats and lineage; ordered reference bound to plan, crawl following links from roots only, native CMS and sitemap with explicit optional dependency.
Acceptance criteria
Pass if all originals, dates, families and declarations are qualified; otherwise inconclusive. Matching lists do not establish completeness. Mixed or list seeding is inconclusive in this profile.
When the result remains inconclusive
Missing, ambiguous, out-of-profile, misbound or out-of-window plan/original/surface/review; required runtime absent. Unknowns remain explicit and independent defects survive.
Non-applicability
No automatic NA; missing proof is inconclusive.
Assumptions
Exact origins/documents, prior plan, captures within at most24hours; unauthenticated production and no-interaction declarations.
Limitations
Declared graph only: no completeness, site-wide orphan, universal SEO depth, authenticated acquisition/reviews, observed interaction, indexing or ranking. HTTP200 does not verify expected content or soft404s. The reader does not adjudicate supplied rationale.
TS18-A02 · Depths and incoming degrees within the bounded graph.
Protocol assessment mode : automatic. App availability is shown on the control card.
Scope
Population, roots, families and boundaries declared before captures; bounded supplied-graph-reconciliation-v1 profile.
Evidence
Dated fingerprinted original inventories, declared production/dependencies, prior plan, original HTTP/source/DOM, pairs and bounds, per-inventory dates and supplied reviews bound to exact dossiers.
Method
Read each pair from source under two hypotheses or qualified no-interaction DOM; compute lower/upper distances and counts of distinct incoming sources, excluding self-links.
Acceptance criteria
Pass if roots and every pair are qualified; otherwise inconclusive even if one depth is exact. A no-incoming candidate requires an upper degree of0. No universal depth threshold.
When the result remains inconclusive
Missing, ambiguous, out-of-profile, misbound or out-of-window plan/original/surface/review; required runtime absent. Unknowns remain explicit and independent defects survive.
Non-applicability
No automatic NA; missing proof is inconclusive.
Assumptions
Exact origins/documents, prior plan, captures within at most24hours; unauthenticated production and no-interaction declarations.
Limitations
Declared graph only: no completeness, site-wide orphan, universal SEO depth, authenticated acquisition/reviews, observed interaction, indexing or ranking. HTTP200 does not verify expected content or soft404s. The reader does not adjudicate supplied rationale.
TS18-A03 · Supplied documentary qualification of families and differences.
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Population, roots, families and boundaries declared before captures; bounded supplied-graph-reconciliation-v1 profile.
Evidence
Dated fingerprinted original inventories, declared production/dependencies, prior plan, original HTTP/source/DOM, pairs and bounds, per-inventory dates and supplied reviews bound to exact dossiers.
Method
Derive subjects only from native measurements; check one review for each family, known difference, no-incoming candidate and unreachable document, bound to plan, originals, dates and measurements.
Acceptance criteria
Pass if every qualified subject has a correctly bound supplied explanation; fail if a supplied defect binds an evidenced subject; otherwise inconclusive. Reviews cannot cure unknown measurements and are never software-created human approval.
When the result remains inconclusive
Missing, ambiguous, out-of-profile, misbound or out-of-window plan/original/surface/review; required runtime absent. Unknowns remain explicit and independent defects survive.
Non-applicability
No automatic NA; missing proof is inconclusive.
Assumptions
Exact origins/documents, prior plan, captures within at most24hours; unauthenticated production and no-interaction declarations.
Limitations
Declared graph only: no completeness, site-wide orphan, universal SEO depth, authenticated acquisition/reviews, observed interaction, indexing or ranking. HTTP200 does not verify expected content or soft404s. The reader does not adjudicate supplied rationale.
Rule version 0.2.0-rc.1 · Public protocol reference · Versioned source
Put it into practice
An inventory, starting points and links.