# GEO Content Patterns by Type

Templates and structural patterns for creating GEO-optimized content across different content types.

## Blog Posts and Articles

### Structure

1. **Opening paragraph** — State the core answer/thesis in the first 2 sentences. Include a key statistic if available.
2. **Table of contents** — For posts over 1000 words, include a linked TOC. AI engines use these to understand topic scope.

3. **Core sections** (H2s) — Each H2 should be a question or a clear topic phrase. Lead each section with its answer.
4. **Supporting detail** — After the direct answer, provide context, examples, data, and nuance.

5. **FAQ section** — End with 3-5 frequently asked questions in Q&A format. These are highly extractable by AI engines.
6. **Summary/Key takeaways** — Bullet list of the main points. AI engines frequently pull from summary sections.

### Example Opening

```text

## How Long Does It Take to Learn Python?

Most beginners can learn Python basics in 2-4 weeks with consistent daily practice of 1-2 hours.

Reaching intermediate proficiency typically takes 3-6 months, while advanced mastery requires

1-2 years of hands-on project experience. According to a 2024 Stack Overflow survey, Python

remains the most-wanted programming language, with 67% of developers who don't use it expressing

interest in learning it.

```

## Product and Service Pages

### Structure (2)

1. **Product definition** — "X is a [category] that [primary function] for [target audience]."
2. **Key features/benefits** — Bulleted list with one-line descriptions.

3. **How it works** — Numbered steps or brief process explanation.
4. **Pricing** (if applicable) — Clear pricing table or range. AI engines frequently cite pricing info.

5. **Comparison to alternatives** — Brief positioning against known competitors or categories.
6. **Use cases** — 2-3 specific scenarios with concrete details.

7. **FAQ** — Common purchase/usage questions answered directly.

### Key Principle

Product pages often get skipped by AI engines because they read as marketing copy. Counter this by including factual, verifiable claims, specific numbers (dimensions, speeds, capacities), and honest comparisons. AI engines trust product pages that read like informed reviews more than ones that read like ads.

## FAQ and Knowledge Base Pages

### Structure (3)

- Each question as an H2 or H3
- Answer in the first sentence, explanation following

- Use the exact phrasing people use when asking (natural language, not jargon)
- Group related questions under topic headings

- Include "Related questions" links between entries

### Example

```text

## Can I return an opened product?

Yes, opened products can be returned within 30 days of purchase for a full refund, provided

they are in resalable condition with original packaging. Exceptions include perishable goods,

personalized items, and digital downloads. To initiate a return, contact support@example.com

or use the Returns portal in your account dashboard.

```

### Key Principle (2)

FAQ pages are the highest-value GEO content type because they directly match question-answer patterns. Each Q&A pair is a self-contained unit that AI engines can extract whole. Write each answer as if it will be read without any surrounding context.

## Technical Documentation

### Structure (4)

1. **Overview** — What the tool/API/feature does in 1-2 sentences.
2. **Quick start** — Minimal steps to get running.

3. **Detailed usage** — Organized by feature or use case.
4. **Code examples** — Annotated, runnable code snippets.

5. **Configuration reference** — Tables of parameters, options, defaults.
6. **Troubleshooting** — Common errors and their solutions.

7. **Changelog/Version notes** — What changed and when.

### Key Principle (3)

Technical docs get cited heavily by AI coding assistants. Make code examples copy-pasteable and self-contained. Include expected output. Use consistent parameter tables with columns: Name, Type, Default, Description. Date version references clearly.

## Landing Pages

### Structure (5)

1. **Hero statement** — Clear value proposition in one sentence.
2. **Problem/solution framing** — What problem you solve, stated concretely.

3. **Social proof** — Named testimonials, client logos, specific metrics ("used by 10,000+ teams").
4. **Feature highlights** — 3-5 key features with specific benefits.

5. **How it works** — Simple 3-step explanation.
6. **Pricing/CTA** — Clear next step.

### Key Principle (4)

Landing pages are harder to optimize for GEO because they are inherently promotional. Include enough factual, verifiable information (founding year, team size, concrete metrics, named clients) that AI engines can treat the page as a source of facts rather than just marketing.

## Comparison and Review Pages

### Structure (6)

1. **Verdict up front** — State the recommendation in the opening.
2. **Comparison table** — Side-by-side feature/price/spec comparison.

3. **Category-by-category analysis** — Each criterion as its own section with a clear winner stated.
4. **Use-case recommendations** — "Best for X: [Option A]. Best for Y: [Option B]."

5. **Methodology** — Brief note on how you evaluated.
6. **FAQ** — Common decision-making questions.

### Key Principle (5)

Comparison queries ("X vs Y", "best Z for W") are among the most common AI engine queries. AI engines love structured comparison content because it directly answers decision-making questions. Use tables generously. State clear opinions backed by specific criteria — AI engines cite decisive analysis, not fence-sitting.

### Example Comparison Table

```markdown

| Feature | Tool A | Tool B | Tool C |

|---------|--------|--------|--------|

| Starting Price | $12/mo | $29/mo | Free |

| Max Users | 10 | Unlimited | 5 |

| API Access | Yes | Yes | No |

| Mobile App | iOS only | iOS + Android | iOS + Android |

| Best For | Small teams | Enterprise | Solo users |

```