Write to
be cited.
Ranking used to mean satisfying an algorithm. Now it means being the source that Google, Perplexity, and AI Overviews reach for when they summarise an answer. The writing has to earn that role — not just fill a word count.
Talk about my content ↗
“Content that answers questions is everywhere.
Content that earns the right to be cited is rare.”
Start with what
the search means,
not what it says.
The keyword is a signal, not a brief. Before writing a word, the question worth answering is what the person behind that search actually needs — information, a comparison, a decision framework, or a next step.
Get the intent wrong and the content fails regardless of quality. Get it right, and the structure writes itself. Every section earns its place because the reader genuinely needed it.
“The best brief isn’t a keyword and a word count. It’s a clear picture of who’s reading and what they need to leave knowing.”
| Output-first writing | Intent-first writing |
|---|---|
| Word count and keyword density as the measure of success | Whether the reader leaves with what they came for |
| Content that covers everything in case it helps | Content scoped to what this search stage actually needs |
| Generic structure: intro → H2s → conclusion | Structure shaped by how the reader thinks, not how templates work |
| Written to rank, reads like it was written to rank | Written for the reader — ranks as a result |
Thin coverage
is invisible to
AI systems.
Search is no longer just Google. Perplexity, ChatGPT, and AI Overviews are summarising your topic and choosing their sources right now. They choose depth. They choose specificity. They choose the piece that covers the question properly rather than skimming it.
Writing for GEO isn’t a different skill — it’s writing that’s actually good. Covers the entities. Answers the follow-up. Earns the reference.
“I’ve watched Queensferry.net get cited in AI Overviews not because I optimised for them — because the content was thorough enough that it was the obvious source.”
| Surface-level coverage | Depth-first approach |
|---|---|
| Hits the primary keyword, skims the surrounding topic | Covers primary query, related entities, and likely follow-up questions |
| AI systems pass it over for a more complete source | Cited in AI Overviews because it’s the most complete answer available |
| Structured data treated as optional | Schema markup applied where it helps machines read the content |
| Rankings that depend on low competition to hold | Authority that compounds — harder to displace the deeper you go |
Written by someone
who has lived
the question.
The difference between content that sounds authoritative and content that is authoritative comes down to whether the writer has actually been inside the problem. I build and run the sites I write about — two live authority sites earning and ranking under my own name.
That experience changes the content. Not because it adds anecdotes, but because it shapes which details matter, which caveats are real, and which advice would quietly mislead someone who acted on it.
“Long-form pillar content written by an operator who has lived the question — not a freelancer paraphrasing a Google search.”
| Generic SEO content | Operator-written content |
|---|---|
| Covers what the SERPs say — sources from sources | Covers what the work reveals — real experience as the source |
| Advice that’s technically correct but misses the nuance | Advice that reflects what actually happens when you follow through |
| E-E-A-T signals added as an afterthought | E-E-A-T signals that exist because the experience is real |
| Content that ranks and immediately gets superseded | Content that becomes the reference point in its topic |
Content that answers isn’t enough
any more.
If your content isn’t being cited, referenced, or returned in AI-generated answers, the gap isn’t style — it’s substance. Send me what you’re working on and I’ll show you where the depth is missing.