Home / Real cases end to end

Making your site readable by AIs, citation and agentic navigation

Being cited by a conversational assistant and being usable by a navigating agent are two distinct requirements, one plays out off the site on reliable mentions, the other plays out on the page itself.

A site can appear in a conversational assistant's answer while no agent manages to click its purchase button, and the reverse happens just as often. These are two distinct capabilities, checked by two distinct controls, and confusing one with the other puts the effort in the wrong place.

Citation plays out off the site

Being named in an answer generated by an assistant depends first on what other pages say about the site, not on what its own code displays. An independent study tracked 1885 pages already cited by AIs at the time they added JSON-LD schema markup between August 2025 and March 2026, compared with 4000 control pages that had not added any, each page measured thirty days before and thirty days after the addition, and it measured no significant rise in citations on the conversational engines observed. The markup helps an engine resolve ambiguity about an entity and makes a fact easier to extract, which remains useful, but it does not create the mention itself. The lever that matters is still built elsewhere: reliable third-party pages that cite the content with attribution, work carried out off the site and close to the search and citation optimisation covered in the content pipeline.

Agentic navigation plays out on the page

An agent browsing a page to complete a task asks a different question: can it identify what it is looking at? A button with no text and no accessible label stays invisible to an agent reading the page's structure, even when it is perfectly visible to the eye. This audit is run locally, without depending on a remote assistant.

set -o noclobber
cat > fragment-exemple.html << 'EOF'
<button class="icon-close"></button>
<button aria-label="Fermer la fenêtre">X</button>
<a href="/panier">Voir le panier</a>
EOF
grep -c "aria-label" fragment-exemple.html

On this fabricated fragment, the command returns 1: only one of the two buttons carries a usable label, the first stays mute despite its visual presence. The text link names itself and needs no extra attribute.

Two scopes, two proofs

Adding schema markup in the hope of a rise in citations measures an effect that did not occur in the study cited above. Auditing only button structure, without ever checking who cites the site elsewhere, leaves the citation question entirely open. Checking that a deep page, not just the homepage, remains directly linkable, then checking that its interactive elements carry a usable name, acts on both fronts at once without confusing what each control proves.