Everyone talks about prompt engineering like it's a secret skill. Use the word "expert." Add "think step by step." Use role-play.

That's cargo cult nonsense. Real prompt engineering for SEO is about three things:

1. Understanding what the AI can and can't do 2. Telling it exactly what you want 3. Knowing when to iterate vs. start over

Skill 1: Know the boundaries

Claude (and other LLMs) are good at:

  • Summarizing information
  • Finding patterns
  • Brainstorming variations
  • Explaining complex topics simply
  • Writing prose that sounds human

    • Claude is bad at:

  • Doing math (it hallucinates)
  • Remembering exact numbers (it makes them up)
  • Fetching real-time data (it doesn't have internet)
  • Following extremely precise instructions (it drifts)

    • So here's a bad prompt for SEO work:

    "Analyze these 500 domains and rank them by domain authority."

    Claude can't access domains. It can't fetch their DA scores. It would make up numbers. Bad.

    Here's a good prompt:

    "I have a list of domains and their current DA scores [paste list]. Rank them by growth potential, considering their niche and backlink profile. Explain your reasoning for the top 5."

    You're giving Claude the data. You're asking it to analyze what it can see, not fetch what it can't.

    Skill 2: Be disgustingly specific

    This prompt is bad:

    "Write a blog post about keyword research."

    This prompt is good:

    "Write a 1,500-word blog post in my voice (direct, specific, practical) targeting the keyword 'keyword research tools for SEO professionals.' Include:

  • A specific tool I've used (DataForSEO)
  • Real numbers from my workflow
  • Comparison to SEMrush (mention its weakness: expensive for one-person shops)
  • End with a contrarian take about why most keyword research tools are overbuilt

    • Do NOT include: hedging language, 'it's important to note', em dashes, tricolons."

    The second prompt will produce something useful. The first will produce generic trash.

    The difference: I told Claude exactly what I wanted, including what NOT to do.

    Skill 3: Iterate on direction, not wording

    Bad iteration loop: "Write a blog post about SEO" [Claude produces generic post] "Make it better" [Claude adds more words, doesn't fix the problem] "Make it more specific" [Claude mentions specific tools, but the structure still sucks]

    Good iteration loop: "Write a blog post outline about keyword research" [Claude produces outline] "This outline is too linear. Reorganize around specific client problems instead of general topics" [Claude restructures] "Good. Now expand Section 3 into 800 words of practical steps" [Claude does] "This sounds like AI. Rewrite emphasizing my personal experience and specific numbers" [Claude rewrites with texture]

    The difference: instead of asking for surface-level tweaks, I'm changing the direction based on what's actually wrong.

    Skill 4: Use references, not descriptions

    Bad prompt:

    "Write it in a conversational tone"

    Good prompt:

    "Write it like this previous post of mine [paste excerpt]. Same rhythm, same specificity, same voice."

    Claude is better at matching examples than following abstract descriptions. You want conversational? Show it conversational writing. You want specific? Show it specific examples.

    For SEO, this means:

    Instead of: "Write content that ranks well" Do this: "Write content like [this page that ranks #1 for the target keyword]. Match its structure, depth, and approach."

    Skill 5: Know when to start over

    If you've iterated five times and the core output is still wrong, stop iterating. Start a new conversation.

    Bad workflow:

  • Chat 1: "Write a post on keyword research"
  • Chat 2: "Rewrite it, this is trash"
  • Chat 3: "Actually, write about DataForSEO API specifically"
  • Chat 4: "No, include both high-level and technical content"
  • Chat 5: "This is still bad. Can you fix it?"

    • Better workflow:

  • Chat 1: Do the research conversation. Ask Claude clarifying questions about your angle, your audience, your goal.
  • Chat 2: Start fresh with all the clarity from Chat 1. A single coherent prompt instead of five iterations.

    • New conversations are cheaper (faster API response) and produce better output (no context carryover from failed attempts).

    The meta skill: Know what you actually want

    This is the real skill. Most people don't know what they want from the AI. They just know something is wrong.

    Before you prompt Claude, write down in a sentence:

  • What is the purpose of this content?
  • Who is the reader?
  • What action should they take after reading?
  • What's the one insight I want them to remember?

    • Do that, and your prompts improve 10x.

    Example from my work:

    Bad starting point: "Write a blog post about link building"

    Good starting point: "I want to convince freelancers that manual link building is outdated and they should learn to use automated tools instead. They should finish the post thinking 'I need to try Loganix or similar.' The post should acknowledge that automation requires setup time but the ROI is worth it."

    That clarity changes the whole article. And Claude nails it on the first try.

    The 10-minute prompt session

    This is my actual workflow:

    1. Open a new Claude conversation 2. Dump my raw notes, numbers, and ideas (5 min) 3. Ask Claude: "Given this context, what's the core argument I should make?" (2 min) 4. Claude responds with a thesis 5. I say: "Yes, that. Now write the post" 6. Claude writes it 7. I tweak 2-3 sections manually 8. Done (1 min)

    Total time: 10 minutes. Output quality: good enough to publish with minor editing.

    The key is step 3: let Claude help you clarify what you actually want before you ask it to write.

    The bigger picture

    "Prompt engineering" isn't about magic words. It's about:

  • Understanding the tool
  • Knowing your goal
  • Being specific
  • Iterating on direction, not wording
  • Starting over when necessary

    • That's it. That's the whole skill set.

    Most "prompt engineering courses" teach you to say "act as an expert" and add magic tokens to your prompts. That's nonsense.

    Learn how Claude thinks. Understand its limitations. Know what you want. Be clear. That's all you need.