AI Search: Optimizing for Two Readers — the Human and Your AI Agent
Summarize this article with AI
A client calls me on a Tuesday morning. 8 000 $ at stake.
A client calls me on a Tuesday morning. He invested 8 000 $ in a redesign. 14 months later, the site plateaus at 4 000 organic sessions a month. His direct competitor captures 37 000. Same market. Same city. His content holds up. His architecture holds him back.
I look at 15 sites a week. They all have the same flaw. They built for Googlebot. They forgot the AI agent that prepares the decision. The rushed human who wants a clear answer too. Only one layer optimized.
Google says it clearly. Its AI search features still rely on classic ranking systems. Microsoft specifies that the Bing index moves from a list of pages to a source of facts. Ahrefs notes both statements in its guide How to Optimize for AI Search. The conclusion is simple. Your page must stay crawlable, indexable, useful. And it must provide facts that AI agents can extract and cite.
Two readers. The human. The autonomous agent. The page that ignores one of the two works at half capacity. Since 2016, I deploy semantic cocoons for this. An architecture that serves both with full consistency.
Optimization no longer targets a single engine. It targets a reading chain: the agent reads, filters, cites; the human validates, compares, decides.
The double specification, in plain terms. Mechanisms I observe with my clients. An immediate application.
The starting point remains the same. Only pages accessible to AI robots enter the conversation. Only pages readable by humans enter the decision. These two flaws are costly. And they are corrected with the same discipline.
What the AI agent comes to get from your page
A leader no longer always types his search. He delegates to an agent. The agent consults 12 pages, cross-references the data, prepares a note. Your page must be among the 12. And it must be usable in one pass.
The agent reads differently from a human. It scans, extracts, compares. It looks at three things: technical access, factual precision, cross-page consistency. A contradictory figure? It discards the source. A robots.txt block? It skips the page entirely.
| Reader | What they expect | What drives them away |
|---|---|---|
| Human | Clear answer, proof, scannable structure | 400-word blocks with no subheadings |
| AI agent | Isolated facts, semantic markup, fresh data | Contradictions, blocked access, outdated dates |
Key takeaway: an agent scans your page rather than reading it. It strips it down. With nothing to extract, it moves on to the competitor.
At an industrial client, the catalog had 945 product pages. The standard page stacked sales arguments. Zero extractable facts: no specification table, no update date, no structured question-and-answer. The agent had nothing to cite. The human had to read 1 200 words to compare two models.
We restructured. Each page opens with a 90-word factual box. Price, lead time, compatibility, last-verified date. Marketing details come after. The agent extracts the box. The human scans it. Two readers served with the same block.
I observe with my clients: this dual reading lowers the bounce rate. It’s mechanical. Less effort, more trust.
Producing more is useless here. Structuring differently, yes. An average page with a clear factual box beats a rich page that is unreadable for the agent. Why? The agent chooses the source that requires the least extraction work. The human chooses the page that requires the least comparison work.
The double specification: clarity for the human, extraction for the agent
The DOSE framework helps me connect mechanics and neurochemistry. I use it to prioritize rather than decorate.
DOSE, concretely: serotonin is status and the signal of seriousness. A clear, complete, dated page reassures. The buyer feels they are dealing with a reliable source. Endorphin comes from reduced effort. When a page is ready to cite, the agent works less. The human too. Cognitive load drops. Decision accelerates.
Guillaume Attias repeats it at BMO Academy. DOSE is a reading grid, not a veneer. A page that forces the buyer to reconstruct the facts fails on both sides.
I set a double specification before each production.
- For the agent: one fact = one isolated sentence, dated, sourced, free of sales adjectives.
- For the human: the same fact in context, with a comparison and a possible action.
- For both: a structure in short blocks. Explicit subheadings. Tables. Factual boxes.
An example observed at a SaaS client. The pricing page displayed 4 offers. The descriptions mixed features and benefits. The agent could not extract a price. The human had to read 700 words to understand the entry offer. We isolated 4 boxes. Each box contains the price, the user limit, the key function, the update date. The agent cites the box. The human compares the 4 blocks in 20 seconds.
Result after 6 weeks: positioned informational queries went from 12 to 47. The page became an extractable source.
The double specification is one production with two outputs. The same fact, presented twice: raw for the agent, contextualized for the human.
Serotonin rises when the page emits a serious signal: recent update dates, cited sources, precise figures. Endorphin rises when the buyer understands effortlessly. Less cognitive load, more clarity. And a page ready to cite.
The costly mistake: optimizing for AI while forgetting the human
I’m going to tell you something agencies hate to hear. Most « optimize for AI search » guides miss the target. They treat the agent as an engine. They forget that behind the agent, there is a human who validates.
You win by making your site readable by both readers. It’s a design choice, not a detail.
At a software publisher, the team had emptied the pages of all narrative. Result: the click-through rate on demos fell by nearly a third. The agent extracted the facts, but the human felt nothing. No serotonin. No status signal. The content was neutral. Clinical. Visitors left.
The fix involved reintroducing two elements. A positioning sentence at the top of the page. A dated social proof box. All while keeping extraction light. The click-through rate recovered. The citation by the agent stayed unchanged. Both readers can share the same page.
The opposite mistake. Ultra-editorialized product pages. No structured data. The agent gives up. The human reads, appreciates, but cannot compare. The cart stays empty.
The common thread? The absence of dual reading. A page must serve both at once: a document for the human, a source for the machine.
The question I ask in every audit: does your page prefer to please or to be cited? The correct answer is both. Otherwise, you lose on both fronts.
Concrètement, un agent ne lit pas votre page en un bloc : il franchit trois verrous dans l’ordre. Voici la chaîne exacte, et ce qui se joue à chaque étape.
Le pipeline que l’agent parcourt avant de vous citer
Accès, extraction, fraîcheur : trois verrous franchis dans l’ordre, puis la citation
The concrete mechanics: access, extraction, consistency
The Ahrefs guide says it plainly. If AI agents cannot access your pages, the rest is useless. It’s the first step. Not the most visible. The most eliminatory.
Three checks matter.
- Access: robots.txt, noindex tags, HTTP status codes. Blockers are more frequent than one might think. A misconfigured firewall or CDN is enough to keep AI crawlers away.
- Extraction: your facts must be isolated, dated, consistent. A figure that contradicts the product page from the FAQ kills the citation.
- Freshness: the agent favors sources that update. A visible last-verified date changes everything.
Ahrefs recommends checking these points in Site Audit, Bot Analytics, and Web Analytics. The « AI discoverability » section flags access issues. The 404, 499, and 5xx codes show pages the agent cannot read. A recurring 404 on a URL requested by AI is often a content opportunity.
Before publishing a page, a personal practice saves time: mentally submit the page to an agent. « What sentence will you cite? » If the answer does not come in 10 seconds, the page is not ready. The same question applies to the human. « What action do you want me to take after 20 seconds? » Both answers must exist.
The most costly mistake remains cross-page consistency. An e-commerce client had three pages for the same product. Same price. Different lead times. The agent chose the competition. Out of caution. A page that contradicts itself cannot be cited.
Cloudflare, for example, controls access for AI crawlers. A bad configuration sometimes blocks without anyone knowing. Check the security settings. A firewall rule intended for advertising bots can exclude search agents.
Measure citations, not just positions
Rankings are no longer enough. A page can rank first on Google and be absent from AI answers. Conversely, a page can be cited by an agent without generating a click. The measurement changes.
Ahrefs suggests tracking mentions in AI answers. The principle: your page counts when it is retrieved, understood, cited. Crawling alone is not enough.
With my clients, I observe three useful indicators.
- Direct citation: your brand or your data appear in the agent’s response.
- AI-origin traffic: sessions that arrive after a generated response. Often more qualified, the agent has already filtered on your behalf.
- Associated queries: the questions that trigger the citation. They reveal the real need.
A concrete case. A comparison guide page attracted 2 400 organic visits per month. The agents never cited it. I added a factual summary table, dated, with 6 criteria. Two weeks later, the page became the primary source for an agent for that comparison. Total traffic barely moved. Demo requests increased. That’s where value plays out.
The trap would be to chase citations at any cost. A cited page that is unreadable for the human does not convert. A pleasant page that is not extractable remains invisible to the agent. Both metrics must progress together.
The method does not sell itself. Pages show themselves. The only measure that ultimately counts is human action. A citation that leads nowhere is worth no more than a ranking without a click.
Six critères décident si votre page passe le filtre des deux lecteurs. Passez-la au crible : sous le seuil, vous perdez la citation.
Auto-audit : votre page est-elle citable ?
Six dimensions vérifiées par l’humain et par l’agent avant de vous retenir
Does your page answer before the question is even asked?
In 2026, a page has two readers: the human and the agent. Your competitors optimize for only one. You serve both with the same URL. That's where the gap widens.
The recipe comes down to five points. Guaranteed access. Isolated facts. Visible dates. Compact tables. Result: the human understands in 20 seconds, the agent extracts in one pass.
Next time you publish a page, two questions. What does the agent read before citing you? What does the human read before clicking? If you cannot answer both in one sentence, the page still needs another pass.
Is your content ready to be cited by an agent, with the human hooked until the end?
Live audit of your human/agent dual reading
For 45 minutes, I look at your pages with you. What the agent can cite. What the human understands. The blockers that cost you decisions.
Book a strategic call — 45 minFrequently Asked Questions
Do you need to optimize differently for AI and for Google?
No. Google says it: AI relies on classic systems. Your page must stay crawlable, indexable, useful. And provide facts the AI can extract.
What blocks an AI agent from accessing my site?
A blocking robots.txt, a noindex tag, 404/499/5xx, a misconfigured firewall or CDN. I check all of that in Ahrefs Site Audit or Bot Analytics.
How do you make a fact easy to cite?
Isolate it in a dated sentence. Boxes, tables, subheadings: the agent extracts effortlessly.
Does AI search replace classic SEO?
No. It layers on top. Rankings remain the base, but getting cited matters too. Both move forward together.
Which indicator should I track first?
I look at direct citations made by agents, traffic coming from AI, and the queries that go with them. The final click, on the other hand, remains human.
