Subchapter 2.3
README.mdMarkdown17 KBView on GitHub
Generate machine-readable content that earns citations from ChatGPT, Claude, Gemini, and Google AI Overviews.
Not a tool or app - this is a guided workflow with templates for use with Claude Code.
This repo contains instructions and templates for Claude Code to generate AEO-optimized content for any website. When you start a Claude Code session here, Claude will:
No coding required. Just natural language requests to Claude.
cd /Users/bencium/AISEO
# Start Claude Code session"Generate AEO content for my product at example.com/product"Copy the generated HTML into your website or CMS.
| File | Purpose | Audience |
|---|---|---|
prd.md | Complete AEO content generation guide with templates | Claude Code |
CLAUDE.md | Project context and development guidelines | Claude Code |
README.md | Usage instructions and workflow | You (human) |
Key file: prd.md contains all the templates, best practices, and guidelines Claude uses to generate content.
50-word definition with:
- What the product is
- Why it matters
- "Last updated" date
- Product schema markupEach FAQ includes:
- 7-12 word natural question
- 30-50 word answer (AI sweet spot)
- Persistent anchor link
- FAQPage JSON-LD schema
- "Last updated" dateFor key claims:
- Claim statement
- Methodology
- Data source + date
- Limitations
- Contact infoComplete working schemas for:
- FAQPage (FAQ sections)
- HowTo (step-by-step guides)
- Product (product pages)
- Organization (about page)When relevant:
- Numbered steps
- Prerequisites/constraints
- Expected outcomes
- HowTo schema markupGather this information about your website/product:
Target URL or page description
Product/service details
Top customer questions (aim for 15)
Evidence/data (if available)
Competitor information (optional)
Simple approach:
"Generate AEO content for [website URL or product description]"Detailed approach:
"I need AEO-optimized content for [product name].
Product: [brief description]
Target page: [URL]
Top questions: [list 5-10 customer questions]
Data available: [any benchmarks, research, or stats]
Generate:
- Product overview (50 words)
- 15 FAQs with schema
- Evidence blocks for key claims
- All necessary JSON-LD markup"Claude will:
prd.md to generate contentReview the content
Implement on your website
<head> sectionValidate
Test with AI engines
Track results
"Generate AEO content for my SaaS analytics product.
Product: Real-time analytics dashboard for e-commerce stores
URL: analytics.example.com
Top questions:
- What is real-time analytics?
- How is this different from Google Analytics?
- What metrics can I track?
- How long does setup take?
- What integrations are supported?
We have benchmark data: 127ms median query latency from Q3 2025 study"1. Product Overview:
<article id="product-overview">
<h1>What is [Product Name]?</h1>
<div class="overview-answer">
<p>[Product Name] is a real-time analytics dashboard for
e-commerce stores that tracks customer behavior and sales metrics.
As of October 2025, it processes over 10M events daily with
sub-second latency. This matters because real-time insights enable
immediate optimization of marketing campaigns and inventory.</p>
<p class="meta">Last updated: 2025-10-31</p>
</div>
<!-- Product schema -->
<script type="application/ld+json">
{ ... complete schema ... }
</script>
</article>2. 15 FAQs with Schema:
<section id="faq">
<h2>Frequently Asked Questions</h2>
<div class="faq-item" id="faq-what-is-realtime-analytics">
<h3>What is real-time analytics?</h3>
<p>Real-time analytics processes and displays customer behavior
data within seconds of events occurring, enabling immediate
business decisions. Unlike batch processing (hourly/daily),
real-time systems update dashboards continuously as customers
interact with your store.</p>
<p class="meta">Last updated: 2025-10-31</p>
</div>
<!-- 14 more FAQs -->
<!-- FAQPage Schema -->
<script type="application/ld+json">
{ ... complete FAQPage schema with all 15 FAQs ... }
</script>
</section>3. Evidence Block:
<aside class="evidence-panel" id="evidence-query-latency">
<h4>Evidence: Query Performance Benchmark</h4>
<dl>
<dt>Claim:</dt>
<dd>127ms median query latency for dashboard analytics</dd>
<dt>Methodology:</dt>
<dd>Measured 10,000 dashboard queries across 50 e-commerce stores
over 30-day period</dd>
<dt>Data Source:</dt>
<dd><a href="https://example.com/benchmarks/2025-q3">Q3 2025
Performance Report</a></dd>
<dt>Date:</dt>
<dd>September 15, 2025</dd>
<dt>Limitations:</dt>
<dd>Performance measured on standard tier; enterprise tier may
vary ±15ms based on custom configurations</dd>
</dl>
</aside>Plus complete schema markup, validation guidance, and implementation checklist.
<script type="application/ld+json"> in <head>After implementing generated content, verify:
<head> sectiondatePublished and dateModified fieldslastUpdated timestamp in ISO 8601 formatRun these prompts across ChatGPT, Claude, and Gemini:
| Intent | Engine | Mentioned? | Linked? | Accurate? | Evidence Quoted? | Notes |
|---|---|---|---|---|---|---|
| What is X | ChatGPT | ✅ Yes | ✅ Yes | ✅ Yes | ❌ No | Generic description |
| Compare X vs Y | Claude | ❌ No | ❌ No | N/A | N/A | Doesn’t know us yet |
| Best [category] | Gemini | ✅ Yes | ❌ No | ✅ Yes | ✅ Yes | Cited our benchmark |
4-8 weeks after implementation:
12 weeks:
Critical insight: 95% of AI citations come from content updated in the last 10 months.
| Content Type | Check | Update |
|---|---|---|
| Homepage & FAQ | Monthly review | Quarterly update |
| Product pages | When features change | Immediately |
| Evidence blocks | Every 6 months | When data refreshes |
| Blog posts | Quarterly | Add “Last reviewed” even if unchanged |
| How-to guides | When process changes | Immediately |
| Mistake | Fix |
|---|---|
| ❌ FAQ answers too long | ✅ Keep to 30-50 words |
| ❌ Missing dates | ✅ Add “Last updated” everywhere |
| ❌ Vague claims | ✅ Include specific data, methods, dates |
| ❌ No schema markup | ✅ FAQPage schema is essential |
| ❌ Marketing speak | ✅ Use factual, specific language |
| ❌ Buried answers | ✅ Front-load the answer, details second |
| ❌ Pronoun ambiguity | ✅ Say “the product” not “it” |
| ❌ Missing evidence | ✅ Add methodology for all claims |
| ❌ Stale content | ✅ Update within 10 months or lose visibility |
No dependencies required:
<script> tags)Compatible with:
Each new Claude Code session in this directory can:
"Generate AEO content for [new page/product]""Update the FAQ section with new questions and refresh dates""Add 5 more FAQs about [topic]"
"Generate evidence blocks for [specific claims]""Check if this schema is correct: [paste schema]""Analyze how [competitor URL] structures their content for AEO"1. PREPARE
├─ Gather product info
├─ List top 15 customer questions
├─ Collect evidence/data
└─ Note competitors
2. GENERATE (Claude Code session)
├─ "Generate AEO content for [URL/product]"
├─ Claude analyzes requirements
├─ Claude uses prd.md templates
└─ Receive complete HTML + schema
3. IMPLEMENT
├─ Copy HTML to your website
├─ Add schema to <head>
└─ Verify anchor links work
4. VALIDATE
├─ Google Rich Results Test
├─ Check FAQ word counts
├─ Verify all dates present
└─ Test anchor links
5. TEST
├─ Manual prompts (ChatGPT, Claude, Gemini)
├─ Track in scorecard
└─ Monitor over 4-8 weeks
6. MAINTAIN
├─ Monthly review
├─ Quarterly updates
└─ Refresh data every 6 monthsNo. Claude generates ready-to-use HTML. Just copy/paste into your CMS.
Yes. Each Claude session can generate content for different sites/products.
Claude can help generate relevant questions based on your product description.
No. Start with product overview + 15 FAQs. Add evidence blocks as you gather data.
Track with manual AI engine tests (prompt scorecard). Results typically visible in 4-8 weeks.
Yes! Treat Claude’s output as a strong starting point. Edit to match your voice, but keep:
Generate optimized product overviews, feature FAQs, and comparison content that helps AI engines understand and cite your product.
Create category overviews with structured product information that AI can extract and recommend to shoppers.
Build expertise-demonstrating content with evidence blocks showing methodology, case studies, and credentials.
Structure technical docs with HowTo schema and clear step-by-step guides that AI can parse and cite.
Transform blog content with FAQ sections, evidence blocks, and proper schema to increase AI discoverability.
Remember: This is about immediate action over perfect strategy. Generate content, test with AI engines, iterate based on results.
This repository contains guides and templates for content generation. Generated content is yours to use freely.
This file