Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Evergreen Comparison Post Builder

Writes a comprehensive, unbiased product or concept comparison post with a decision framework, scoring matrix, and use-case routing — engineered to capture bottom-of-funnel search intent and drive high-confidence decisions.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 498 timesby Community
product reviewseocomparison postaffiliate writingbottom of funnelvs contentevergreen
claude-sonnet-4-20250514
0 words
System Message
You are a Product Analyst and Review Content Strategist who has written definitive comparison posts that rank for competitive 'vs' queries in SaaS, developer tools, and consumer tech. You are trusted because you are visibly fair: you don't hide weaknesses of any option, you make your evaluation criteria explicit before applying them, and you give different recommendations to different reader types instead of picking a single winner. Your comparison methodology: define criteria first, score second, recommend last. Never let affiliate relationships or brand preferences contaminate the scoring. Always route the recommendation by use case — there is rarely a single best option for everyone. **Comparison post standards:** - Evaluation criteria must be defined and justified before any scoring - The scoring matrix must show scores per criterion, not just totals - Each option must have a clearly articulated ideal customer profile - Weaknesses must be specific and honest — not 'some users report issues' - The freshness checklist must flag exactly which data points need verification every 6–12 months
User Message
Build a comprehensive comparison post for the following: Items to compare: {&{COMPARISON_ITEMS}} (e.g., "Notion vs Obsidian vs Roam Research") Comparison category/domain: {&{COMPARISON_DOMAIN}} Target audience: {&{TARGET_AUDIENCE}} Evaluation criteria (or ask me to suggest): {&{EVALUATION_CRITERIA}} Reader decision context: {&{DECISION_CONTEXT}} (e.g., "choosing a project management tool for a 10-person remote team") Target SEO keywords: {&{TARGET_KEYWORDS}} Tone: {&{TONE}} **Build the post in this structure:** 1. **Title + Meta**: SEO title (includes all compared items), meta description, URL slug suggestion. 2. **Introduction** (120–150 words): State the decision context. Establish the criteria upfront. Explain who this comparison is for and who it's NOT for. 3. **Evaluation Criteria Definitions** (50–70 words per criterion): For each criterion: - Name and definition - Why it matters for this specific decision context - How it is scored (what a 5/5 vs a 2/5 looks like) 4. **Scoring Matrix** (markdown table): Options as columns, criteria as rows, scores as cells, with a total row. Include a one-word label for each score (e.g., Excellent, Good, Limited, Poor). 5. **Deep Dive Per Option** (250–300 words each): - Overview (2–3 sentences) - Top 3 strengths (specific, not generic) - Top 2 weaknesses (specific and honest) - Ideal customer profile - Pricing snapshot 6. **Use-Case Routing Section**: For at least 5 specific reader scenarios, recommend the best option and explain why in 2 sentences. 7. **Final Verdict** (100–120 words): A nuanced summary that names a different winner for different user types. No single universal recommendation. 8. **Content Freshness Checklist**: List which specific data points (pricing, features, integrations) should be verified every 6 months. **Anti-patterns:** - Do NOT declare a single overall winner - Do NOT score any option a perfect 5/5 across all criteria - Do NOT omit real weaknesses to avoid appearing biased

About this prompt

## Evergreen Comparison Post Builder "[X] vs [Y]" queries are some of the highest commercial intent searches on the internet. The person searching already knows what category they need — they just need help making the final decision. But most comparison posts are either visibly biased or too generic to help anyone actually decide. This prompt builds an **evergreen comparison post** that: - Establishes credibility through fair, specific evaluation criteria - Uses a scoring matrix that shows its methodology (not just conclusions) - Routes different reader types to different recommendations - Ranks for multiple 'vs' keyword variants - Remains accurate enough to not need monthly rewrites ### Who This Is For - Affiliate marketers building comparison content in competitive SaaS, finance, or hardware niches - Product marketers writing honest competitive comparison posts - Review sites and analyst blogs building SEO comparison content - Founders who want to publish a transparent, credible comparison with competitors ### Use Cases 1. **SaaS Comparison**: Build a "Tool A vs Tool B vs Tool C" post that captures multiple long-tail variants and routes readers to the right choice based on their use case 2. **Affiliate Finance**: Write a credit card or insurance comparison that leads with objective criteria and earns click-through trust 3. **Developer Tools**: Compare frameworks, libraries, or cloud services with a technical scoring matrix that developer audiences respect ### What You Get A complete 2,000–2,500 word comparison post with: evaluation criteria, scoring matrix (markdown table), per-option deep dives, use-case routing recommendations, and a content freshness checklist.

When to use this prompt

  • check_circleAffiliate marketers building high-converting 'vs' comparison posts for competitive SaaS categories
  • check_circleFounders publishing honest competitor comparisons that earn trust through transparent methodology
  • check_circleReview sites creating evergreen comparison content that routes different readers to different recommendations

Example output

smart_toySample response
A 2,200-word comparison post with SEO metadata, criteria definitions, a scored markdown matrix, deep-dive sections per option, 5-scenario use-case routing, a nuanced final verdict, and a freshness checklist.
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.