The Content Formats AI Search Engines Prefer: Difference between revisions
No edit summary |
mNo edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
The discipline is in how you report their output. Every one of them samples: their own prompt set, their own infrastructure, their own run frequency. Their number is an estimate from a particular vantage point, not a count of what happened.<br><br>Tracking this is genuinely awkward, and pretending otherwise is how most reporting in this field goes wrong. There is no console. Answers vary between runs. Referral attribution is inconsistent between assistants. Anyone handing you a single confident number has hidden a great deal of variance behind it.<br><br>The Types That Rarely Earn Their Keep Elaborate breadcrumb hierarchies, speakable markup, deeply nested item lists and most of the specialised types outside their intended vertical produce little observable difference in how a brand is understood or recommended.<br><br>Audit for contradiction before adding anything new. Run your key pages through a validator, then read the output against what the page actually says and against your main directory listings. Contradictions are more damaging than gaps, because they actively undermine confidence in the record.<br><br>How You Will Know It Is Working Ask for the raw answers, not a score. A credible report shows you the exact prompts, the exact text an assistant returned, and which pages were cited. You should be able to read it and form your own judgement without trusting anyone's index.<br><br>Then load your key pages with scripts disabled. Whatever remains is roughly what a retrieval system sees. If your product specifications, pricing or service areas vanish, that content needs to exist in the server rendered HTML.<br><br>The defensible position is to spend an hour on it if you like, and to spend the rest of the week on the things every system already reads: accessible pages, accurate Organization markup, consistent identity and content a machine can quote.<br><br>Why That Breaks the Old Playbook The old playbook assumed that if you occupied a high position, you got the visit. That link between position and visibility has weakened. Ahrefs looked at 15,000 long-tail prompts across four assistants in July 2025 and found roughly 80 percent of the cited pages did not rank for the original query at all.<br><br>Record the conditions alongside the results: which assistant, which model version if visible, whether web access was on, the date and the run number. When a result changes sharply, the conditions log is usually what tells you whether the world changed or your setup did.<br><br>Visibility in this channel is not a number you can look up. There is no console that reports how often an assistant named your [https://www.88pianists.com/ ai seo company] last month, and the tools that claim to supply one are sampling rather than counting. That does not make measurement impossible. It makes it manual, and manual is fine as long as you are honest about what you are measuring.<br><br>Write between fifty and two hundred prompts covering five types: the category question, the problem question, the comparison question, the question that names a competitor, and the question that names you directly. The last one matters because it reveals what an assistant believes about you specifically, which is often more alarming than being absent.<br><br>One structural decision saves a lot of trouble later. Keep the raw answers in plain text files named by date, assistant and run number, rather than pasting them into a document that gets reformatted. Six months in you will want to search across every run for the first appearance of a competitor or a source, and a folder of plain files supports that while a slide deck does not.<br><br>Ask to See a Prompt Set The first question is the most revealing. Ask them to show you the prompt set from a current or recent client, with the client's name removed. A team doing real work has this and will show it, because the prompts are craft rather than secret sauce.<br><br>A reasonable rule for planning a content programme is to publish fewer pages and maintain them properly. Twenty pages carrying current figures will out-earn a hundred that were correct on the day they shipped, because freshness is weighted and stale specifics actively cost you. Most teams discover this by building the hundred first, then finding they cannot review them and quietly letting the whole set go out of date.<br><br>Write it once, covering the category question, the problem question, the comparison question, the competitor question and the branded question. Fifty is a workable minimum. Then freeze it, and if you must add prompts later, add them as a separate cohort so the original series stays comparable.<br><br>The terms are used almost interchangeably. Generative engine optimization usually emphasises assistants that write an answer, while answer engine optimization is sometimes used more broadly. Ask any agency what they mean by their term.<br><br>Run the Baseline Properly Run each prompt in a signed out session, or in a fresh session with memory and personalisation disabled. Your own browsing history and past conversations will otherwise skew results toward showing you what you already know. | |||
Latest revision as of 17:08, 18 August 2026
The discipline is in how you report their output. Every one of them samples: their own prompt set, their own infrastructure, their own run frequency. Their number is an estimate from a particular vantage point, not a count of what happened.
Tracking this is genuinely awkward, and pretending otherwise is how most reporting in this field goes wrong. There is no console. Answers vary between runs. Referral attribution is inconsistent between assistants. Anyone handing you a single confident number has hidden a great deal of variance behind it.
The Types That Rarely Earn Their Keep Elaborate breadcrumb hierarchies, speakable markup, deeply nested item lists and most of the specialised types outside their intended vertical produce little observable difference in how a brand is understood or recommended.
Audit for contradiction before adding anything new. Run your key pages through a validator, then read the output against what the page actually says and against your main directory listings. Contradictions are more damaging than gaps, because they actively undermine confidence in the record.
How You Will Know It Is Working Ask for the raw answers, not a score. A credible report shows you the exact prompts, the exact text an assistant returned, and which pages were cited. You should be able to read it and form your own judgement without trusting anyone's index.
Then load your key pages with scripts disabled. Whatever remains is roughly what a retrieval system sees. If your product specifications, pricing or service areas vanish, that content needs to exist in the server rendered HTML.
The defensible position is to spend an hour on it if you like, and to spend the rest of the week on the things every system already reads: accessible pages, accurate Organization markup, consistent identity and content a machine can quote.
Why That Breaks the Old Playbook The old playbook assumed that if you occupied a high position, you got the visit. That link between position and visibility has weakened. Ahrefs looked at 15,000 long-tail prompts across four assistants in July 2025 and found roughly 80 percent of the cited pages did not rank for the original query at all.
Record the conditions alongside the results: which assistant, which model version if visible, whether web access was on, the date and the run number. When a result changes sharply, the conditions log is usually what tells you whether the world changed or your setup did.
Visibility in this channel is not a number you can look up. There is no console that reports how often an assistant named your ai seo company last month, and the tools that claim to supply one are sampling rather than counting. That does not make measurement impossible. It makes it manual, and manual is fine as long as you are honest about what you are measuring.
Write between fifty and two hundred prompts covering five types: the category question, the problem question, the comparison question, the question that names a competitor, and the question that names you directly. The last one matters because it reveals what an assistant believes about you specifically, which is often more alarming than being absent.
One structural decision saves a lot of trouble later. Keep the raw answers in plain text files named by date, assistant and run number, rather than pasting them into a document that gets reformatted. Six months in you will want to search across every run for the first appearance of a competitor or a source, and a folder of plain files supports that while a slide deck does not.
Ask to See a Prompt Set The first question is the most revealing. Ask them to show you the prompt set from a current or recent client, with the client's name removed. A team doing real work has this and will show it, because the prompts are craft rather than secret sauce.
A reasonable rule for planning a content programme is to publish fewer pages and maintain them properly. Twenty pages carrying current figures will out-earn a hundred that were correct on the day they shipped, because freshness is weighted and stale specifics actively cost you. Most teams discover this by building the hundred first, then finding they cannot review them and quietly letting the whole set go out of date.
Write it once, covering the category question, the problem question, the comparison question, the competitor question and the branded question. Fifty is a workable minimum. Then freeze it, and if you must add prompts later, add them as a separate cohort so the original series stays comparable.
The terms are used almost interchangeably. Generative engine optimization usually emphasises assistants that write an answer, while answer engine optimization is sometimes used more broadly. Ask any agency what they mean by their term.
Run the Baseline Properly Run each prompt in a signed out session, or in a fresh session with memory and personalisation disabled. Your own browsing history and past conversations will otherwise skew results toward showing you what you already know.