bofu-seo-aeo-strategy

Files (3)

• SKILL.md
• aeo-for-bofu.md · references/
• format-patterns.md · references/

SKILL.md (first lines)

## Why this matters

BOFU queries — "X vs Y", "alternatives to X", "best X", "best X for Y" — are where late-stage evaluation happens. Buyers typing these have done their problem-awareness and solution-awareness work; they are choosing. These pages are also the most structurally standardized format in SEO, which means both Google's quality systems and AI answer engines have clear expectations of what a trustworthy, useful comparison or listicle looks like. Get the format right and credibility is compounding; get it wrong and the format itself flags the page as low-effort.

Two realities shape every BOFU decision:

1. **Buyers filter BOFU content skeptically.** A third-party review platform or a peer Reddit thread carries more weight than a vendor's own comparison page. Your page must earn credibility inside a frame where it's presumed biased.
2. **AI answer engines have reshuffled the citation pool.** Listicles, software-review aggregator pages, Reddit threads, YouTube review transcripts, and large publishers are disproportionately cited for commercial queries. Vendor-owned BOFU content alone does not earn AI citation share — third-party presence is a prerequisite, not a substitute.

This skill teaches the craft for producing BOFU content that (a) picks the right format for the intent, (b) earns credibility despite the conflict-of-interest frame, (c) is structured for both human scanning and LLM extraction, and (d) integrates with the third-party surfaces where buyers actually evaluate.

## Process

1. **Classify the query intent.** Pin the page to one of the four BOFU formats — comparison, alternative, listicle, or segment page. Format drives structure. Getting this wrong creates mid-funnel content wearing BOFU clothes.
2. **Audit the SERP and citation pool.** Who ranks for the target query today? What do AI engines cite? Identify the content archetype (aggregator, publisher, vendor) dominating each surface.
3. **Decide your angle and stance.** Will the page include your own product? If so, at what position and with what framing? Can you honestly win on the compared dimensions? What segments will you call out?
4. **Gather first-hand material.** Use every tool you plan to compare. Capture screenshots, run representative workflows, note specific observations. BOFU credibility depends on demonstrable hands-on experience.
5. **Structure the page to the canonical pattern.** Apply the format-specific H2 sequence (Section 3.2 below, and `references/format-patterns.md` for depth).
6. **Apply credibility moves.** Concession sections, worked pricing, dated screenshots, segmented verdicts, third-party ratings, explicit methodology. These are not optional; they are the difference between a trusted comparison and affiliate wallpaper.
7. **Optimize for AI extraction.** Direct-answer first paragraph, question-form H2s, clean tables, fan-out sub-query coverage (FAQ section), entity density, summary box.
8. **Invest in third-party presence in parallel.** software-review profiles with active reviews, legitimate Reddit participation, YouTube review presence, and brand-mention building. These are prerequisites, not afterthoughts.
9. **Implement technically.** URL canonicalization, schema, internal linking from informational TOFU to the BOFU money page.
10. **Set the maintenance cadence.** BOFU content decays faster than almost any other content type. Quarterly review is the floor.

## Frameworks

### 1. The four BOFU formats — distinguish and select

Most BOFU mistakes happen before the first word is written, when the author treats all four formats as interchangeable. They are not.

| Format | Typical query | Intent signal | Canonical structure | Default length |
|---|---|---|---|---|
| **Comparison page** | "[Tool A] vs [Tool B]", "[Incumbent] vs [Challenger]" | Active evaluation between 2–3 named tools | Feature Deep Dive (Pattern A) | 2,500–4,500 words |
| **Alternative page** | "Alternatives to [incumbent]", "[category] alternatives" | Dissatisfaction with incumbent; open shortlist | Listicle with positioning (Pattern C) | 2,000–3,500 words |
| **"Best X" listicle** | "Best project management software", "Best CRM" | Fresh evaluation across full category | Ranked listicle with methodology | 2,500–5,500 words |
| **"Best X for Y" segment page** | "Best CRM for small business", "Best PM tool for agencies" | Segmented evaluation within a category | Segmented listicle with narrower scope | 2,000–3,500 words |

**Rule:** one page = one format. Do not mix a comparison into a listicle or a listicle into a segment page. The H2 sequence and the reader's expectation are different for each.

**Selecting between them:**

- If the query names exactly two or three tools → **comparison**
- If the query names one incumbent and asks for substitutes → **alternative**
- If the query asks for the whole category → **listicle**
- If the query narrows by audience, size, use case, or industry → **segment page**
- If you are a vendor and the query is "best [your category]" → expect a head-term SERP dominated by review sites and large publishers; prefer **segment pages** where you can win on specificity

### 2. Canonical structural patterns

These are the H2 sequences that recur across strong pages. Use them as scaffolding, not a straitjacket. See `references/format-patterns.md` for deep patterns including per-tool sub-structures, table specifications, and worked H2 examples for each format.

**Pattern A — Comparison page (X vs Y)**

```
H1: [Product A] vs [Product B]: [year] Comparison
H2: [A] vs [B] at a glance  ← comparison table + TL;DR here
H2: What is [A]?
H2: What is [B]?
H2: Feature comparison
  H3: [Feature 1]
  H3: [Feature 2]
  H3: [Feature 3]
H2: Pricing comparison  ← worked examples at specific volumes
H2: User reviews and third-party ratings
H2: Where [A] is the better choice
H2: Where [B] is the better choice  ← the concession section
H2: Which should you choose?  ← segmented recommendation
H2: FAQ
```

**Pattern C — Alternative page and "Best X" listicle**

```
H1: [N] Best [Competitor] Alternatives / Best [Category] in [year]
H2: Why look for a [Competitor] alternative? / Why this matters
H2: What to look for  ← evaluation criteria
H2: How we evaluated  ← methodology
H2: Quick comparison  ← at-a-glance table
H2: 1. [Tool] — Best for [use case]
  H3: Key features
  H3: Pricing
  H3: Pros / Cons
  H3: Best for
H2: 2. [Tool] — …
  (7–12 tools total)
H2: How to choose the right [tool]
H2: FAQ
```

**Pattern D — Segment page ("Best X for Y")**

Uses Pattern C scaffolding with two adjustments: (a) evaluation criteria are segment-specific, not generic, and (b) the tool list is filtered to those that genuinely fit the segment. A "best CRM for solo consultants" page should not include enterprise-only tools, even if the parent "best CRM" page does.

### 3. Credibility moves — the core craft

A vendor or affiliated author writing BOFU content is read inside a presumed-bias frame. Credibility is earned through specific moves. These are non-negotiable on any page meant to rank or be cited by AI.

**Objectivity moves:**
- **Concession section.** At least one H2 acknowledging where a competitor is the better choice, with specifics (use cases, features, pricing tiers). Strong vendor-authored comparisons do this visibly—mirror that pattern.
- **Segmented verdicts, not blanket winners.** "A is better for enterprise; B is better for SMB" instead of "A is the winner." Recommendations split by use case.
- **Third-party ratings cited** (software review aggregators and analyst summaries) rather than self-assessment.
- **Explicit methodology** — how many tools were tested, over what period, against what criteria, by whom, with what disclosed connections.

**Evidence moves:**
- **Screenshots of the actual product in use** — dated, captioned, showing the specific workflow discussed. Not stock marketing images. Not the competitor's marketing site.
- **Specific observations only possible from usage.** "The CSV export truncates fields above 255 characters" beats "easy to export." The specificity is the proof.
- **Worked pricing examples at specific volumes.** "For a 25-person team on the Business plan, monthly cost: A = $X, B = $Y" beats "A is more expensive." Link to the competitor's official pricing page; timestamp your pricing data.
- **Dated content.** Year in title, last-updated timestamp visible on-page.

**Format moves:**
- **Tables with descriptive cells, not binary checkmarks.** "Unlimited users" beats "Yes". "Starts at $15/user/month, annual only" beats "$$".
- **Named author with demonstrable expertise.** A LinkedIn-verifiable role, related writing history, or domain-credible background. Not "Editorial Team".
- **Per-tool structure consistent across entries.** If Tool 1 gets Pricing / Pros / Cons / Best for, every other tool gets the same, in the same order.

**The self-inclusion question.** If your product is in the category, three stances exist:
- **Include honestly, ranked on merit.** Acceptable if genuine first-hand testing of competitors, visible methodology, and no #1 position for yourself unless earned on the evaluation criteria.
- **Exclude and link.** Keep the main listicle competitor-only; maintain a separate "How we compare" page for readers who want your view.
- **Split.** Main content excludes; a clearly-disclosed vendor perspective box sits at the end.

From narayan-metaflow/metaflow-marketing-skills, MIT.

More from narayan-metaflow/metaflow-marketing-skills