TSEPCONTROL FREE BETA
Menu

Where would you like to go?

Navigation only · no analysis is started

THE DEMO · YOURS TO EXPLORE

Three SEO errors.
Found, fixed, proven.

Understand → Check → Act → Recheck.
Follow three examples, from the problem to evidence after the fix.

Understand a result No account. No waiting.

ATELIER.EXAMPLE · COMPLETED ANALYSIS

Three fixes.
Evidence of the recheck.

Scope · Fictional dossier: synthetic responses and reviews. Engine verdicts on supplied evidence. Details

DOSSIER VERDICTS · 4 SELECTED CONTROLSAfter correction · remaining evidence is listed

3 C · Verified

0 NC · To correct

1 NT · Not established

0 NA · Not applicable

TS04 · Control C · Verified

robots.txt now allows /assets/app.js.

01 Understand

The rule now allows this public script. /admin/ remains disallowed.

Objective Allow crawling of the script the page needs while keeping /admin/ disallowed.

02 Check

robots.txt · line 3 · Googlebot group
User-agent: GooglebotDisallow: /admin/Allow: /assets/
Open the original response

03 Act

Correct the rule disallowing /assets/. In this example, that directory contains only public resources: Allow: /assets/. The /admin/ rule is retained.

04 Recheck

BEFORE 09:00 UTC

To correctDisallow: /assets/

AFTER 09:10 UTC

VerifiedAllow: /assets/

TS04-A01 · The robots policy allows the declared resource.

Control C · Verified: robots policy and resource access review supplied. No remaining evidence within this scope.

View the access review ↗Fictional evidence in the corrected dossier

Before report ↗After report ↗
Return to the initial findings

Run the same test on your site.

Prefilled workflow. Confirm your expectations before running the test.

Read the 4 controls and the three stories ↓

THE DOSSIER EVIDENCE

Open the evidence.
Keep the dossier.

Download the evidence
The 4 selected controls, in detailFindings, engine results and evidence to complete

THE COMPLETE VIEW

The example, one control at a time

Open a control to read its result and this fictional dossier’s evidence.

4selected controls
TS01Does the page respond as intended?HTTP and availability C · Verified

Engine result on the example evidence

/formations returns 200 with the expected content.

View the report and evidence ↗

Expected response, destination and content for this URL at test time. No JavaScript rendering or indexing status established.

Act

Confirm the expected destination and text, then run verification.

Try my own URL →
Understand this TSEP control

Method: Send a GET request, follow redirects and record the final status code.

Criterion: Each GET reaches a final 200 response for the expected resource; retain timestamp and redirect chain.

Limits: A test from one IP does not prove the response received by Googlebot.

TS01 · TSEP 0.3.0-draft.8 · Required evidence: Intent, complete GET trace and retained body; reasoned findings for A01–A02.

TS02Do redirects lead to the right page?HTTP and availabilityControl C · Verified

01 Understand

The destination is reached in one permanent redirect. The two intermediate steps are gone.

Objective One permanent redirect to /offre, followed by a 200 response.

02 Check

Retained HTTP chain
301  /ancienne-offre  →  /offre200  /offre
Open the original response

03 Act

Change the /ancienne-offre rule to point directly to /offre. Update internal links too, then recheck the route.

04 Recheck

BEFORE 09:00 UTC

To correct3 redirects · 301 → 301 → 301 → 200

AFTER 09:10 UTC

Verified1 redirect · 301 → 200

TS02-A02 · The HTTP route matches the declared destination and hop count.

Control C · Verified: approved plan and route matching the expectations. No remaining evidence within this scope.

View the plan approval ↗Fictional evidence in the corrected dossier

Before report ↗After report ↗
Return to the initial findings

Run the same test on your site.

Prefilled workflow. Confirm your expectations before running the test.

TS04Do robots.txt rules match your intentions?Robots and accessControl C · Verified

01 Understand

The rule now allows this public script. /admin/ remains disallowed.

Objective Allow crawling of the script the page needs while keeping /admin/ disallowed.

02 Check

robots.txt · line 3 · Googlebot group
User-agent: GooglebotDisallow: /admin/Allow: /assets/
Open the original response

03 Act

Correct the rule disallowing /assets/. In this example, that directory contains only public resources: Allow: /assets/. The /admin/ rule is retained.

04 Recheck

BEFORE 09:00 UTC

To correctDisallow: /assets/

AFTER 09:10 UTC

VerifiedAllow: /assets/

TS04-A01 · The robots policy allows the declared resource.

Control C · Verified: robots policy and resource access review supplied. No remaining evidence within this scope.

View the access review ↗Fictional evidence in the corrected dossier

Before report ↗After report ↗
Return to the initial findings

Run the same test on your site.

Prefilled workflow. Confirm your expectations before running the test.

TS07Are indexing directives consistent?IndexingControl NT · 2 pieces of evidence to add

01 Understand

The source directive now matches your objective. The recheck retains the evidence.

Objective This strategic page should be eligible for indexing.

02 Check

Received HTML · line 5
<!doctype html><html lang="fr"><head>  <meta charset="utf-8">  <meta name="robots" content="index, follow">  <title>Formations photo — Atelier</title></head><body>  <main><h1>Formations photo</h1></main></body></html>
Open the original response

03 Act

Noindex is removed. index, follow has no effect, just like an absent tag.

04 Recheck

BEFORE 09:00 UTC

To correctnoindex, follow

AFTER 09:10 UTC

Verifiedindex, follow

TS07-A01 · The source directive matches the objective.

Correction verified ✓ · 2 pieces of evidence to add before concluding: unobstructed access, browser rendering

Before report ↗After report ↗
Return to the initial findings

Run the same test on your site.

Prefilled workflow. Confirm your expectations before running the test.

I already have TSEP evidence to import — advanced

Assessment applies the engine to supplied captures and reviews. Automated observations and your declarations are not sufficient to constitute this evidence. Your selected controls are carried into this step.

Import evidence for these controls →

TSEP 0.3.0-draft.8 · Edikka — Technical SEO Evidence Protocol · CC-BY-4.0 · Reference catalogue

How this example is verifiedSame engine, same expectations before and after

Responses, pages and dates are fictional. The seven reports were calculated by the TSEP engine, then replayed offline from their evidence. Expectations stay identical before and after each correction.

The plan owner’s decision and the access review are fictional evidence marked as synthetic exercises. They go through the same adapters as the real TS02 and TS04 workflows. TS07 still needs two pieces of evidence: unobstructed access and browser rendering. The other 40 controls are outside this example. No Googlebot visit, indexing or JavaScript execution is claimed.

TSEP 0.3.0-draft.8 · Results and engine identity · TS01 baseline report