Technical
AI Engine Optimization and Featured Snippets Side by Side
SEO splintered this year. Google Search, AI Overviews, ChatGPT's citations, Perplexity's sources. Each surface pulls from slightly different signals. The good news: one set of writing habits serves all of them reasonably well. Eight months of writing for both humans and machines has given me a concrete playbook.
The Single Pattern That Serves Both
Direct-answer lede followed by supporting depth. The first paragraph states the answer in plain terms. The next sections give the reasoning, examples, and caveats. Featured snippets pull from the lede. AI engines cite the depth. The reader gets both.
Most blog posts bury the answer five paragraphs deep behind a personal story. Both machines and skimming humans leave. Put the answer first. Earn the reader's time with the depth that follows.
The Formats Machines Prefer
Clear headings with question-shaped wording. 'How does X work' beats 'A journey into X'. Machines use headings as retrieval anchors.
Lists with parallel structure. Three to seven items, each starting with the same grammatical shape. This formats cleanly in both featured snippets and AI-generated summaries.
One-paragraph answers after headings. Forty to sixty words. This is the sweet spot for Google's featured snippet extractor and matches what AI tools cite cleanly.
## How does X work
X works by [clear 40-word answer that stands alone].
[Supporting detail for readers who want to go deeper.]What Machines Penalize
Stuffed keyword phrases. Current ranking systems detect them and demote. Write for the reader; the keywords will be there naturally if the topic is real.
Thin content scaled. Ten short articles on tangential subtopics rank worse than one deep article on the main topic. Depth compounds; breadth without depth dilutes.
AI-generated filler. Detection is imperfect but improving. Filler that was fine a year ago is a liability now. Write to say something specific and concrete from your own experience.
The AEO-Specific Moves
Answer Engine Optimization rewards a few extra habits: explicit entity linking (link to company names, technical terms, and people), structured data for article types, and dated content that signals freshness. The Schema.org Article type is a strong baseline; add JSON-LD with published date, author, and main entity to every article page.
Measuring Both
Google Search Console for classic search visibility. Manual probes in ChatGPT and Perplexity for the AI side: do they cite my article on the topics I wrote about. No tool yet gives the full picture. I sample monthly.
One writing discipline, two surfaces served. That is the leverage.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read