Suede Competitor and Alternative Pages

Use this Suede comparison-page playbook to serve competitive search intent while keeping every product claim current, sourced, and fair.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before creating competitor pages, understand:

1. Your Product

   • Core value proposition
   • Key differentiators
   • Ideal customer profile
   • Pricing model
   • Strengths and honest weaknesses

2. Competitive Landscape

   • Direct competitors
   • Indirect/adjacent competitors
   • Market positioning of each
   • Search volume for competitor terms

3. Goals

   • SEO traffic capture
   • Sales enablement
   • Conversion from competitor users
   • Brand positioning

---

Core Principles

1. Honesty Builds Trust

• Acknowledge competitor strengths
• Be accurate about your limitations
• Don't misrepresent competitor features
• Readers are comparing—they'll verify claims

2. Depth Over Surface

• Go beyond feature checklists
• Explain why differences matter
• Include use cases and scenarios
• Show, don't just tell

3. Help Them Decide

• Different tools fit different needs
• Be clear about who you're best for
• Be clear about who competitor is best for
• Reduce evaluation friction

4. Modular Content Architecture

• Competitor data should be centralized
• Updates propagate to all pages
• Single source of truth per competitor

---

Page Formats

Format 1: [Competitor] Alternative (Singular)

Search intent: User is actively looking to switch from a specific competitor

URL pattern: /alternatives/[competitor] or /[competitor]-alternative

Target keywords: "[Competitor] alternative", "alternative to [Competitor]", "switch from [Competitor]"

Page structure:

1. Why people look for alternatives (validate their pain)
2. Summary: You as the alternative (quick positioning)
3. Detailed comparison (features, service, pricing)
4. Who should switch (and who shouldn't)
5. Migration path
6. Social proof from switchers
7. CTA

---

Format 2: [Competitor] Alternatives (Plural)

Search intent: User is researching options, earlier in journey

URL pattern: /alternatives/[competitor]-alternatives

Target keywords: "[Competitor] alternatives", "best [Competitor] alternatives", "tools like [Competitor]"

Page structure:

1. Why people look for alternatives (common pain points)
2. What to look for in an alternative (criteria framework)
3. List of alternatives (you first, but include real options)
4. Comparison table (summary)
5. Detailed breakdown of each alternative
6. Recommendation by use case
7. CTA

Important: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.

AI-answer expectations by stage: these pages can earn citations in AI answers, but whether AI recommends your brand from them also depends on offsite consensus (reviews, forums, analysts). For emerging brands, a self-ranked list may surface competitors while the brand receives only a citation. Treat that as a hypothesis and route current visibility evidence and claim validation to suede-seo-audit.

---

Format 3: You vs [Competitor]

Search intent: User is directly comparing you to a specific competitor

URL pattern: /vs/[competitor] or /compare/[you]-vs-[competitor]

Target keywords: "[You] vs [Competitor]", "[Competitor] vs [You]"

Page structure:

1. TL;DR summary (key differences in 2-3 sentences)
2. At-a-glance comparison table
3. Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations)
4. Who [You] is best for
5. Who [Competitor] is best for (be honest)
6. What customers say (testimonials from switchers)
7. Migration support
8. CTA

---

Format 4: [Competitor A] vs [Competitor B]

Search intent: User comparing two competitors (not you directly)

URL pattern: /compare/[competitor-a]-vs-[competitor-b]

Page structure:

1. Overview of both products
2. Comparison by category
3. Who each is best for
4. The third option (introduce yourself)
5. Comparison table (all three)
6. CTA

Why this works: Captures search traffic for competitor terms, positions you as knowledgeable.

---

Essential Sections

TL;DR Summary

Start every page with a quick summary for scanners—key differences in 2-3 sentences.

Paragraph Comparisons

Go beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.

Feature Comparison

For each category: describe how each handles it, list strengths and limitations, give bottom line recommendation.

Pricing Comparison

Include tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size.

Who It's For

Be explicit about ideal customer for each option. Honest recommendations build trust.

Migration Section

Cover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched.

For detailed templates: See references/templates.md

---

Content Architecture

Centralized Competitor Data

Create a single source of truth for each competitor with:

• Positioning and target audience
• Pricing (all tiers)
• Feature ratings
• Strengths and weaknesses
• Best for / not ideal for
• Common complaints (from reviews)
• Migration notes

For data structure and examples: See references/content-architecture.md

---

Research Process

Deep Competitor Research

For each competitor, gather:

1. Product research: Sign up, use it, document features/UX/limitations
2. Pricing research: Current pricing, what's included, hidden costs
3. Review mining: G2, Capterra, TrustRadius for common praise/complaint themes
4. Customer feedback: Talk to customers who switched (both directions)
5. Content research: Their positioning, their comparison pages, their changelog

Ongoing Updates

• Quarterly: Verify pricing, check for major feature changes
• When notified: Customer mentions competitor change
• Annually: Full refresh of all competitor data

---

SEO Considerations

Keyword Targeting

Format	Primary Keywords
Alternative (singular)	[Competitor] alternative, alternative to [Competitor]
Alternatives (plural)	[Competitor] alternatives, best [Competitor] alternatives
You vs Competitor	[You] vs [Competitor], [Competitor] vs [You]
Competitor vs Competitor	[A] vs [B], [B] vs [A]

Internal Linking

• Link between related competitor pages
• Link from feature pages to relevant comparisons
• Create hub page linking to all competitor content

Schema Markup

Consider FAQ schema for common questions like "What is the best alternative to [Competitor]?"

---

Output Format

Competitor Data File

Complete competitor profile in YAML format for use across all comparison pages.

Page Content

For each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs.

Page Set Plan

Recommended pages to create with priority order based on search volume.

---

Task-Specific Questions

1. What are common reasons people switch to you?
2. Do you have customer quotes about switching?
3. What's your pricing vs. competitors?
4. Do you offer migration support?

---

Boundaries

• Do not invent, cherry-pick, or present stale competitor claims, prices, features, testimonials, or rankings as current fact.
• Do not publish, deploy, index, or update comparison pages without explicit authorization and a final claim review.
• Do not use competitor trademarks in a way that implies affiliation or reuse protected creative assets without rights.
• Do not decide that an option is universally best; state audience, criteria, tradeoffs, sources, and checked dates.

Routing

• Need current competitor evidence -> use suede-competitor-profiling.
• Need scaled comparison-page architecture -> use suede-programmatic-seo.
• Need final page copy or organic QA -> use suede-copy or suede-seo-audit.
• Need internal battle cards -> use suede-sales-enablement.
• From those skills, route honest public alternative and versus-page composition back to suede-competitors.