An open protocol for technical SEO
The finding.
The evidence.
The link between them.
An audit becomes more useful when its findings can be explained. TSEP proposes 44 controls to define expectations, retain evidence and make conclusions inspectable.
For SEO consultants, technical teams and their clients.
Content-Type: text/html; charset=utf-8
17 OCT 2026 · 10:41 UTC
SHA-256 05c90b13c4d8…bc095b154
The response is retained.
The scope stays explicit.
An HTTP observation, without a conformity verdict.
01 / The idea
A useful finding
can be inspected.
“It conforms” is not enough. To which expectation? On which pages? Based on which evidence? With what limitations?
TSEP gives these questions a structure. Each control connects scope, expectations and evidence to retain. Missing observations stay visible, and findings can be reviewed in context.
Understand C, NC, NT and NA outcomes →02 / The catalogue
44 controls.
Transparent status.
HTTP, crawling, indexing, links, content, structured data… Explore each control’s expectations and limitations.
Protocol status in this version. Workflow availability in the beta is shown separately in the app.
Browse all 44 controls →03 / The method
From scope to evidence dossier.
Three steps towards a finding that can be understood and discussed.
- 01
Define what you check.
Choose controls, URLs and expectations. A sample does not automatically represent the entire website.
- 02
Keep what you observe.
Retain original evidence, timestamps, hashes and collection bounds. Make missing evidence explicit.
- 03
Explain what you conclude.
Link each finding to its expectation and evidence. Prepare a dossier that can be reviewed, shared and, where supported, replayed.
TSEP CONTROL / Public beta
Move from reading
to a first observation.
The beta captures an HTTP response with its evidence and offers a guided TS02 workflow. Other integrations progress separately, with their own versions.
Open TSEP Control ↗