Build SEO comparison pages from G2 review themes and AI research

Create a list of 5-10 competitor, alternative, or category comparison pages to build. Use Ahrefs to check search volume, keyword difficulty, current ranking pages, and related terms. Prioritize pages where the searcher likely has buying intent, such as 'alternative,' 'vs,' 'pricing,' 'reviews,' or 'best for' keywords.

Collect public review snippets for each competitor from G2. Separate positive themes, negative themes, switching triggers, feature gaps, support complaints, implementation friction, pricing concerns, and ideal user descriptions. You are not trying to copy reviews. You are extracting patterns in customer language.

Analyze these customer review snippets for {{competitor_name}}.

Review snippets:
{{review_snippets}}

Extract:
- Most common praise themes
- Most common complaint themes
- Implementation or onboarding friction
- Pricing or packaging concerns
- Support or reliability concerns
- Customer language worth reusing as inspiration
- Likely reasons someone would switch

Do not quote reviews directly. Summarize patterns.

Use Perplexity, Ahrefs, and Thruuu to understand what Google currently rewards for each comparison keyword. Note page types, headings, comparison tables, FAQs, competitor claims, and whether the SERP prefers neutral review-style content or vendor-owned pages. Add these observations to your brief before writing.

Use Claude to combine review themes, SERP expectations, and your product proof points into a page brief. Each brief should include the target reader, search intent, page angle, sections, comparison table criteria, FAQs, proof needed, and claims to avoid.

Create an SEO comparison page brief.

Target keyword:
{{target_keyword}}

Competitor:
{{competitor_name}}

SERP findings:
{{serp_findings}}

Review themes:
{{review_themes}}

Our product proof points:
{{our_proof_points}}

Create:
- Search intent summary
- Recommended page angle
- H1 and meta description
- Section outline
- Comparison table criteria
- Proof points required
- FAQs
- Claims to avoid
- Internal links to include

Make it useful and credible, not attack-style.

Generate the page in blocks instead of one long draft. Write the intro, who each product is best for, key differences, comparison table copy, switching section, proof section, and FAQs. Keep the language balanced enough to be credible while still making your positioning clear.

Write comparison page copy from this brief.

Brief:
{{comparison_page_brief}}

Brand voice:
{{brand_voice}}

Rules:
- Be fair and specific
- Do not invent competitor claims
- Use review themes as inspiration, not direct quotes
- Include a balanced 'best fit' section
- Include FAQs based on search intent
- Avoid aggressive takedown language

Output section-by-section copy, not a single article blob.

Use AlsoAsked to find questions related to each comparison keyword. Select the questions that show buying intent or implementation concerns. Add concise answers that help the reader decide, not generic SEO filler.

Before publishing, review each page for unsupported claims, unfair competitor statements, missing proof, and overly aggressive language. Ask Claude to flag claims that need evidence or should be softened. Then have a human review anything involving pricing, legal, security, or compliance comparisons.

Review this comparison page for credibility and risk.

Page copy:
{{comparison_page_copy}}

Known proof points:
{{approved_proof_points}}

Flag:
- Unsupported claims
- Overly aggressive competitor language
- Statements that need evidence
- Legal or compliance risk
- Places where the page sounds biased or untrustworthy

Suggest safer rewrites.