Entity, Corroboration, Hooks, Output
The ECHO framework
ECHO is a four-pillar framework for making AI answer engines recommend a brand. The pillars are Entity, Corroboration, Hooks and Output, and they are the four prerequisites every answer engine imposes before it will name a brand in an answer.
What is the ECHO framework?
ECHO is a four-pillar framework for making AI answer engines recommend a brand. The pillars are Entity, Corroboration, Hooks and Output, and they are the four prerequisites every answer engine imposes before it will name a brand in an answer.
The machine needs to know who you are (Entity). It needs to trust what it knows (Corroboration). It needs to find your content when answering a relevant question (Hooks). And you need to know whether any of this is working (Output). Miss any one of these and you have a gap that no amount of content, advertising, or traditional SEO can close.
- Name
- ECHO
- Stands for
- Entity, Corroboration, Hooks, Output
- Originated by
- Peter Victor Jones
- Defined in
- ECHO: How to Make AI Recommend Your Brand
- Pillars
- 4, applied in a fixed order
What are the four pillars?
The four pillars are Entity, Corroboration, Hooks, Output. Each one names a question the answer engine has to be able to settle before it will recommend a brand, and each one names the failure mode you get when it cannot.
Does the machine know who you are?
Pillar 1 of 4 CorroborationDoes it trust what it knows?
Pillar 2 of 4 HooksDoes it find your content when the question is asked?
Pillar 3 of 4 OutputCan you tell whether any of it is working?
Pillar 4 of 4| Pillar | The question | The failure mode | Chapters |
|---|---|---|---|
| 1. Entity | Does the machine know who you are? | If the machine does not know you exist, the problem is Entity. | 3, 4 |
| 2. Corroboration | Does it trust what it knows? | If it knows you exist but will not repeat what it knows, the problem is Corroboration. | 5, 6 |
| 3. Hooks | Does it find your content when the question is asked? | If it trusts you but never surfaces your content for the question being asked, the problem is Hooks. | 7, 8 |
| 4. Output | Can you tell whether any of it is working? | If you cannot tell which of these is happening, the problem is Output, and that is where to start. | 9, 10 |
Why is the order fixed?
The pillar sequence is not a matter of preference. Corroboration has nothing to confirm until an entity exists to be confirmed. Hooks are content a machine will not retrieve if it does not yet trust the source. Measurement tells you very little when the thing being measured has not been built.
After the first read, the structure becomes a fault-finding tool. Each pillar corresponds to a specific failure mode. That is what makes the order more than a table of contents: work started at the wrong pillar does not fail loudly, it just fails to move anything.
How is ECHO rolled out?
The book sets out a 30/60/90 day rollout that follows the pillar order: Entity foundation in the first month, the Corroboration layer in the second, Hooks and measurement in the third.
| Window | Key actions | Deliverables | Done when |
|---|---|---|---|
| Days 1 to 30 Entity foundation |
|
|
Brand and category search returns a knowledge panel, a Google Business Profile, or a clear single-source definition. Schema validates. No conflicting facts on top sources. |
| Days 31 to 60 Corroboration layer |
|
|
The top five citations are consistent. At least one independent source corroborates core facts. The review profile is growing with specific, detailed reviews. |
| Days 61 to 90 Hooks and measurement |
|
|
A Share of Answer baseline is established. At least one target query cluster shows a brand mention in AI answers. The reporting cadence is set. |
Source: ECHO print proof, Chapter 11, the 30/60/90-day implementation roadmap table, pages 66 to 67.
What goes wrong most often?
The book names five pitfalls, and the first is the one that costs the most: starting with content before the entity fundamentals are fixed.
- Starting with content before fixing entity fundamentals
- If the machine does not know who you are, no amount of content will make it say your name.
- Chasing volume over consistency
- Fifty directory listings with five different versions of your address do more harm than five listings with perfect consistency.
- Treating AI visibility as a one-time project
- The information ecosystem changes constantly. Share of Answer requires ongoing measurement and maintenance.
- Ignoring what the AI actually says
- Share of Answer tells you whether you are mentioned. The qualitative check tells you whether the mention is accurate and helpful. An inaccurate AI mention can be worse than no mention at all.
- Expecting immediate results
- Entity resolution, corroboration building, and content investment operate on timescales of weeks to months, not days.
Where is ECHO defined?
ECHO is defined in ECHO: How to Make AI Recommend Your Brand by Peter Victor Jones, and this site is its canonical home. Every fact about the framework that should be treated as settled originates here.
ECHO: How to Make AI Recommend Your Brand is a 76 page book in 6 parts. Parts 2 to 5 build one pillar each.
Start with the Entity pillar
Chapter 3 opens the Entity pillar and is published here in full. It is the chapter that defines what an entity means to a machine.