Comparison Article
Write an honest X vs Y or best alternatives article: real differentiators, a decision table, and a clear pick for each type of reader.
Write a comparison article for the query: [e.g. "Notion vs Obsidian" / "best Mailchimp alternatives"]. Options to compare: [LIST 2-8 OPTIONS] Who is searching this: [READER + WHAT THEY ARE TRYING TO DECIDE] My relationship to these products: [e.g. "I make one of them" / "I use two of them daily" / "none, I am researching"] Facts I can supply: [PRICING, LIMITS, FEATURES YOU KNOW FIRST-HAND, or "none yet"] Structure: 1. **The one-paragraph answer.** Name the best pick for the most common reader in the first 60 words. Readers who have to scroll before they find an answer go back to the results page. 2. **Who each option is for.** One short paragraph per option: the type of user it fits and the type it does not. Say what each one is genuinely worse at. 3. **Comparison table.** Rows are the 5-8 dimensions that actually change the decision, not every feature. Pick dimensions where the options differ; a row where all options score the same is filler. 4. **The real differentiators.** 3-5 paragraphs on the differences that survive a trial: workflow fit, pricing at scale, lock-in, ecosystem, support. Avoid feature-checklist parity claims. 5. **Recommendations by scenario.** "Choose A if you [situation]. Choose B if you [situation]." Cover 3-5 scenarios. 6. **What could change this.** Roadmap items, pricing shifts, or dealbreakers that would flip the recommendation. Rules: - Mark every claim about pricing, limits, or features that you are not certain of as [VERIFY: claim]. Do not state a price or a feature limit from memory as fact; these change constantly. - Do not manufacture balance. If one option clearly wins for the target reader, say so. - If I make one of these products, still name its real weaknesses. Readers detect a rigged comparison instantly and it costs more trust than the honest version costs sales. - No conclusion that restates the article. End on the recommendation.
How to use
Comparison pages are the highest-intent content you can publish and the easiest to get wrong, because models happily invent pricing tiers and feature limits. Treat every [VERIFY] flag as required work: open the pricing pages and confirm before publishing, then add the date you checked. The 'what could change this' section is what keeps the page useful a year later and gives you a natural update cadence.
More writing prompts
Rewrite the text below in plain language for [AUDIENCE, e.g. "patients with no medical background" / "customers reading a policy update" / "new hires on day one"]. Target reading level: [e.g. "8th grade" / "as simple as the content allows"]. How to rewrite: - Lead with what the reader must DO or what happens to them. Background comes af
Plain Language Rewrite
Rewrite dense policy, legal, medical, or technical text at a target reading level without losing a single obligation or number.
Build an FAQ page for [PRODUCT/SERVICE/TOPIC]. Real questions people ask me: """ [PASTE SUPPORT TICKETS, SALES CALL NOTES, SEARCH QUERIES, OR COMMENTS. RAW IS FINE.] """ Facts I can state as true: [PRICING, POLICIES, LIMITS, TIMELINES] Do this: 1. **Cluster** the raw questions into distinct questions people actually ask. Merge duplicat
FAQ Page From Real Questions
Turn support tickets and sales objections into an FAQ page that answers in the first sentence and is structured for AI search engines.
Create the metadata package for this YouTube video. Video transcript or outline: """ [PASTE TRANSCRIPT WITH TIMESTAMPS IF YOU HAVE THEM, OR THE OUTLINE] """ Channel and audience: [WHO WATCHES, WHAT THEY EXPECT FROM YOU] What someone would search to find this: [1-3 PHRASES, OR "you tell me"] Produce: 1. **Titles**: 8 options under 60 c
YouTube Metadata Pack
Generate ranked title options, a search-optimized description, and accurate timestamp chapters from a transcript or outline.