competitor-alternatives

Start with deep competitor research covering product usage, pricing, and review mining from G2 or Capterra. Then follow the defined page structure: TL;DR summary, at-a-glance comparison table, detailed category comparisons, honest who-it's-for sections, and a migration section with switcher testimonials.

There are four formats: singular alternative pages targeting '[Competitor] alternative' keywords, plural alternatives roundups listing 4-7 real options, you-vs-competitor head-to-head pages, and competitor-vs-competitor pages that capture third-party comparison traffic while introducing your product.

Use the comparison_matrix_builder.py script with a JSON input defining features, categories, and status values (full, partial, no, planned) for your product and competitors. It outputs win/loss scoring, advantage and gap detection, and Markdown tables using only the Python standard library.

Yes, acknowledging genuine competitor strengths builds trust with evaluators who will verify claims independently. Pages that only disparage competitors lose credibility, and every claim should be verifiable from public sources or customer quotes to remain legally safe.

Maintain a centralized YAML data file per competitor containing pricing, features, strengths, and weaknesses so updates propagate to all pages. Verify pricing quarterly, update when customers report competitor changes, and do a full annual refresh.

Simple checkmark tables hide important nuance about how features actually work. The Skill recommends paragraph comparisons explaining why differences matter, descriptive cell content instead of checkmarks, and category-grouped tables with ratings and notes.