TS15Sitemaps and links

Do your sitemaps respect format limits?

Sitemap size and segmentation limits are respected.

Prepare evidence

In the app: Evidence import
You provide: Sitemaps and inventory
Allow for: Depends on evidence needed

Prepare evidence

Understand

A readable sitemap. Within the limits.

Sitemap size and segmentation limits are respected.

According to Google

A sitemap is limited to 50,000 URLs or 50 MB uncompressed. Larger sets must be split across multiple files.

Build and submit a sitemap Source accessed on 2026-10-26

Check

XML and volume. The right limits.

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

Use an XML parser to check structure and count URLs. Measure uncompressed size, then check each file referenced by the index and Search Console’s Sitemaps report.

Evidence to retain

Base64/SHA-256 originals, declared URLs/dates and set plan; native-sitemap-files-v1 bounds.

What this result covers

Supplied files only, no observed server or site completeness. No full XSD, lastmod/changefreq/priority values, URL host/path/length, canonical or indexing validation.

Act

Well-sized files. A consistent index.

Split oversized files and fix the format or index references.

Recheck

The next generation. The same limits.

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: Split oversized files and fix the format or index references.
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 references2 references

Detailed method and rules3 rules

Control method and criteria

Method
Read original bytes, base XML structure, decompressed size, direct entries and index children in the declared set.

Acceptance criteria
Within the bounded profile: qualified UTF-8 and minimal structure, at most52,428,800 bytes and50,000 direct entries per file, coverage of the declared set.

Non-applicability
No sitemap used in scope.

Detailed rules

TS15-A01 · Encoding and minimal structure of supplied files.

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

Scope
Declared population of supplied native sitemap files; roots are not automatically discovered.

Evidence
Base64/SHA-256 originals, declared URLs/dates and set plan; native-sitemap-files-v1 bounds.

Method
Check strict UTF-8,0.9 root, unique nonempty loc and unique ordered leaves; DTD/unqualified extensions stay unknown.

Acceptance criteria
Every complete file passes the bounded structure; established structural contradiction fails.

When the result remains inconclusive
Missing/ambiguous file, incomplete stream, unknown profile, reader bound, nested index or unqualified extension; independent violation retained.

Non-applicability
No NA in this profile.

Assumptions
Supplied URL, date, origin and completeness, unauthenticated. No server observation.

Limitations
Supplied files only, no observed server or site completeness. No full XSD, lastmod/changefreq/priority values, URL host/path/length, canonical or indexing validation.

TS15-A02 · Actual size and population limits.

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

Scope
Declared population of supplied native sitemap files; roots are not automatically discovered.

Evidence
Base64/SHA-256 originals, declared URLs/dates and set plan; native-sitemap-files-v1 bounds.

Method
Count actually decompressed bytes and direct url/sitemap elements, including duplicates and entries without loc.

Acceptance criteria
Each file is at most52,428,800 bytes and50,000 entries; observed excess fails, partial reading without excess is inconclusive.

When the result remains inconclusive
Missing/ambiguous file, incomplete stream, unknown profile, reader bound, nested index or unqualified extension; independent violation retained.

Non-applicability
No NA in this profile.

Assumptions
Supplied URL, date, origin and completeness, unauthenticated. No server observation.

Limitations
Supplied files only, no observed server or site completeness. No full XSD, lastmod/changefreq/priority values, URL host/path/length, canonical or indexing validation.

TS15-A03 · Coverage of declared population and bound children.

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

Scope
Declared population of supplied native sitemap files; roots are not automatically discovered.

Evidence
Base64/SHA-256 originals, declared URLs/dates and set plan; native-sitemap-files-v1 bounds.

Method
Bind each document to an exact declared URL and each index child to a complete leaf; roots and scope remain declared.

Acceptance criteria
All declared documents and branches are qualified; absence/ambiguity/outside-profile is inconclusive, never negative evidence about site sitemap use.

When the result remains inconclusive
Missing/ambiguous file, incomplete stream, unknown profile, reader bound, nested index or unqualified extension; independent violation retained.

Non-applicability
No NA in this profile.

Assumptions
Supplied URL, date, origin and completeness, unauthenticated. No server observation.

Limitations
Supplied files only, no observed server or site completeness. No full XSD, lastmod/changefreq/priority values, URL host/path/length, canonical or indexing validation.

Rule version 0.2.0-rc.1 · Public protocol reference · Versioned source

Put it into practice

← Back to controls