Skip to main content

$ ~/ym8 --define detection-diagnosis-resolution

Detection, Diagnosis, Resolution (DDR)

toolUpdated 2026-03-01
answer
Detection, Diagnosis, Resolution (DDR) is the three-phase operational framework used in AEO to systematically identify AI visibility issues, analyse their root causes, and implement targeted fixes. It transforms AEO from reactive guesswork into a structured improvement process.

definition

The DDR framework — Detection, Diagnosis, Resolution — provides a systematic approach to improving AI visibility. Rather than making broad, unfocused changes and hoping for improvement, DDR follows a structured process that identifies specific issues, determines their causes, and applies targeted solutions.

Detection is the monitoring phase: running query banks across AI engines, tracking Share of Model and Citation Rate, monitoring brand mention accuracy, and flagging anomalies. Detection answers "what is happening?"—your brand is missing from ChatGPT responses for category queries, your Citation Rate on Perplexity has dropped, or a competitor has displaced you in a key topic area.

Diagnosis is the analytical phase: investigating why a detected issue exists. If your brand is missing from ChatGPT responses, is it because your content isn't structured for AI extraction? Because a competitor published more authoritative content? Because your llms.txt is missing or inaccurate? Diagnosis requires both technical analysis and competitive intelligence.

Resolution is the action phase: implementing specific fixes based on the diagnosis. This might involve Technical AEO changes (adding structured data, fixing crawler access), content improvements (restructuring pages for answer-first formatting), or strategic actions (publishing comparison content, building citation sources). Each resolution is targeted at the specific root cause identified during diagnosis.

The DDR cycle is continuous—after resolution, you return to detection to measure whether the fix was effective, creating a feedback loop of continuous improvement.

why_it_matters

DDR provides the operational methodology that makes AEO actionable and measurable. Without a structured framework, AEO efforts tend to be scattered and unmeasurable. DDR ensures that every action is informed by data (detection), guided by analysis (diagnosis), and targeted at a specific outcome (resolution).

examples

examples
  • Detection: discovering that your brand is mentioned in only 5% of category queries on Claude. Diagnosis: your llms.txt is missing and Claude relies heavily on this file. Resolution: implementing llms.txt with comprehensive brand information.
  • Detection: Citation Rate dropped 20% on Perplexity after a site migration. Diagnosis: new URL structure broke existing citations. Resolution: implementing redirects and updating content for the new URLs.

faq

Q1

How often should the DDR cycle run?

Detection should be continuous (or at least weekly). Diagnosis is triggered by detected issues. Resolution timelines vary by issue complexity—Technical AEO fixes may take days, content improvements may take weeks. The full DDR cycle should complete monthly at minimum.

Q2

What tools support the DDR framework?

The AEO Platform is designed around the DDR framework, providing automated detection (Share of Model monitoring, Citation Rate tracking), diagnostic analysis (competitive comparison, content gap identification), and resolution guidance (prioritised recommendations, impact scoring).

Related Terms

Related Engines

next_step

Monitor Your AI Visibility

See how your brand appears with the default core pair. Start with ChatGPT and Claude by default. Expand monitoring only when the workflow needs it.