SEO troubleshooting can feel like digital detective work. You see a traffic drop, a rankings slip, or a crawl error, and the root cause is a mystery. Manually checking every possibility eats hours you don’t have.
What if you had an AI consultant that could instantly diagnose the most likely culprits and give you a clear action plan? This prompt does exactly that. It transforms vague anxiety into structured, actionable solutions.
📋 The Prompt
First, analyze this problem. List the 3-5 most probable technical, on-page, or external causes based on common SEO failure patterns.
For each probable cause, provide:
1. A specific, actionable step to investigate and confirm it.
2. A direct fix or mitigation strategy if this cause is confirmed.
Structure the final answer as a clear diagnostic report with immediate next steps. Prioritize the most likely or impactful causes first.
How It Works
This prompt works because it forces structured thinking. Instead of a vague ‘help with SEO,’ it mimics a consultant’s workflow: diagnosis before prescription.
The magic is in the two-part command. First, it asks for probable causes. This leverages the AI’s training on vast SEO case studies and common pitfalls. It’s not guessing; it’s pattern-matching against known issues.
Second, for each cause, it demands an investigation step and a fix. This is crucial. Anyone can list problems. A true expert tells you how to verify the problem and then solve it. This creates a ready-to-execute checklist, moving you from analysis to action instantly.
For broader strategy, this prompt is a perfect tactical companion to our Master AI for SEO guide. Use that for the big picture, and this prompt for firefighting specific issues.
Pro Tips & Variations
Be Specific in Your Problem Description: ‘Traffic down’ is weak. ‘Traffic from informational blog posts down 30% since the last core update, while commercial page traffic is stable’ gives the AI a powerful signal. Include timeframes, page types, and any recent site changes.
Common Mistake: Jumping to Conclusions. The prompt’s first output is a list of probabilities, not certainties. Use Step 1 (investigation) for each cause to validate. Don’t implement a fix for ‘Cause C’ until you’ve ruled out ‘Cause A’.
Tweak for Proactive Audits: Change the opening to ‘Act as a proactive SEO auditor. I want to prevent common problems for my site about [topic].’ The AI will then output a checklist of pre-emptive checks and hardening strategies, which aligns with the optimization hacks philosophy.
Combine with Research: If the AI suggests an issue with content relevance, feed its output into The SEO Research Prompt to deeply analyze the topic and competition for your fix.
Frequently Asked Questions
Is this prompt only for technical SEO problems?
Not at all. It’s designed for the full spectrum: technical (crawl errors, speed), on-page (content, meta data), and external (algorithm updates, lost backlinks). Just describe your symptom clearly.
How accurate are the AI's 'probable causes'?
They are educated hypotheses based on common patterns. Treat them as a highly informed starting point for your investigation, not a final verdict. Always verify with your own data.
Can I use this for a site-wide drop vs. a page-specific issue?
Yes. The specificity of your input dictates the output. For site-wide, describe that. The AI will prioritize broad causes (e.g., site penalty, hosting issue, global meta tag error). For one page, it focuses on individual elements.
What if the AI doesn't list the cause I'm suspecting?
That’s valuable data! It means your suspected cause is statistically less likely given the symptoms you provided. It should prompt you to either refine your problem description or seriously consider the AI’s alternative hypotheses.
How is this different from just searching a forum for my problem?
Forums give you fragmented, anecdotal advice. This prompt synthesizes knowledge into a personalized, structured report. It considers *your* described context and provides a logical sequence of actions, saving you from sifting through dozens of conflicting forum posts.
