Fictional company and URL: atelier-exemple.test. No remote website was scanned and no observation was added to the Observatory. This is not a previous state of Edikka. Scoring method: 2026-09-09.v5.
Identical conditions: HTTP 200 response, robots.txt allowing all paths, sitemap present and no optional AI context file. One HTML page is assessed; links are not followed.
HTML before the fixes
<!doctype html>
<html lang="en"><head>
<title>Example Studio — Consulting for SMEs</title>
<meta name="description" content="Operations consulting for SMEs: diagnosis, action plan and progress tracking.">
<meta name="robots" content="noindex">
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Organization","name":"Example Studio",}</script>
</head><body><main>
<h1>Operations consulting for SMEs</h1>
<p>Example Studio is a fictional company used to explain a technical diagnosis. Its offer includes a scoping workshop, a process analysis and a prioritised action plan. This demonstration page is intended to be accessible to search engines.</p>
<h2>How does an engagement work?</h2>
<p>The project lead describes their objectives and shares the relevant documents. A consultant identifies friction points, presents the findings and proposes verifiable steps. Deliverables include an executive summary and a decision list.</p>
<h2>Frequently asked questions</h2>
<p>What results can be expected? A documented plan with sources for each finding. This example guarantees no commercial outcome. All company information is entirely fictional.</p>
<a href="/en/expertise">Offer details</a><a href="/en/contact">Contact the studio</a>
</main></body></html>
HTML after the fixes
<!doctype html>
<html lang="en"><head>
<title>Example Studio — Consulting for SMEs</title>
<meta name="description" content="Operations consulting for SMEs: diagnosis, action plan and progress tracking.">
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Organization","name":"Example Studio"}</script>
<link rel="canonical" href="https://atelier-exemple.test/">
</head><body><main>
<h1>Operations consulting for SMEs</h1>
<p>Example Studio is a fictional company used to explain a technical diagnosis. Its offer includes a scoping workshop, a process analysis and a prioritised action plan. This demonstration page is intended to be accessible to search engines.</p>
<h2>How does an engagement work?</h2>
<p>The project lead describes their objectives and shares the relevant documents. A consultant identifies friction points, presents the findings and proposes verifiable steps. Deliverables include an executive summary and a decision list.</p>
<h2>Frequently asked questions</h2>
<p>What results can be expected? A documented plan with sources for each finding. This example guarantees no commercial outcome. All company information is entirely fictional.</p>
<a href="/en/expertise">Offer details</a><a href="/en/contact">Contact the studio</a>
</main></body></html>
Points by check — same page, same method| Check | Before | After |
|---|
| Page accessible over HTTP | 4/4 | 4/4 |
|---|
| Verifiable robots policy | 3/3 | 3/3 |
|---|
| XML sitemap detected | 3/3 | 3/3 |
|---|
| No noindex directive | 0/2 | 2/2 |
|---|
| Canonical URL declared | 0/2 | 2/2 |
|---|
| Title and H1 present | 2/2 | 2/2 |
|---|
| Access rules available | 1/1 | 1/1 |
|---|
| Generic access to the tested URL | 5/5 | 5/5 |
|---|
| Explicit AI context · bonus | 0/1 | 0/1 |
|---|
| JSON-LD block present | 4/4 | 4/4 |
|---|
| Structured types identified | 0/4 | 4/4 |
|---|
| Readable JSON-LD syntax | 0/2 | 2/2 |
|---|
| Organisation or website entity | 0/2 | 2/2 |
|---|
| Title and description extracted | 2/2 | 2/2 |
|---|
| Content organised into sections | 2/2 | 2/2 |
|---|
| Links to useful pages | 2/2 | 2/2 |
|---|
| Question-or-answer signals | 2/2 | 2/2 |
|---|
| Evidence mentions detected | 2/2 | 2/2 |
|---|