senternet-site-compare-pages

Creates SEO-optimized competitor alternative and versus comparison pages for React and Next.js sites.

Updated May 8, 2026
One-click install
npx skills add https://github.com/MattSenter/senternet-site-skills --skill senternet-site-compare-pages-mattsenter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: senternet-site-compare-pages
Source: https://github.com/MattSenter/senternet-site-skills/tree/main/.claude/skills/senternet-site-compare-pages
Command: npx skills add https://github.com/MattSenter/senternet-site-skills --skill senternet-site-compare-pages-mattsenter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Capturing high-intent search traffic from users evaluating competitors requires dedicated "X alternative" and "X vs Y" pages, but building them with correct URLs, metadata, schema markup, and internal linking is repetitive and error-prone. ## Core Features & Use Cases - Four Page Formats: Supports singular alternative, plural alternatives listicle, direct versus, and competitor-vs-competitor page structures with URL and title conventions. - Reusable ComparePage Component: Provides a React component with feature comparison tables, verdict sections, CTAs, and Schema.org Article JSON-LD. - SEO Integration: Covers routing, prerender entries, sitemap inclusion, share image generation, and internal linking, with a Next.js static-generation track using generateStaticParams and generateMetadata. - Use Case: A SaaS founder wants to rank for "[Competitor] alternative" searches; this Skill generates the comparison page, wires it into routes and sitemap, and adds footer links so Google can discover and rank it. ## Quick Start Ask the AI to create a competitor alternative comparison page for a specific competitor using this skill.

Frequently Asked Questions about senternet-site-compare-pages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a competitor alternative page for SEO?▼

Build a dedicated page at a URL like /compare/competitor-alternative with the keyword in the title, H1, and URL. Include a feature comparison table, an honest verdict, a signup CTA, and Schema.org Article markup, then link to it from your footer and home page.

What URL structure works best for versus comparison pages?▼

Use the exact search keyword in the URL, such as /compare/yourapp-vs-competitor or /compare/competitor-alternative. Include the year in the title tag since comparison queries are time-sensitive, and match the H1 to the primary keyword.

Does this comparison page approach work with Next.js?▼

Yes, the Next.js track uses app/vs/[competitor]/page.tsx and app/alternatives/[competitor]/page.tsx with generateStaticParams for static builds. generateMetadata supplies per-competitor titles, descriptions, canonicals, and OG images derived from a competitor data file.

How many words should a competitor comparison page have?▼

Aim for 600 or more words, since Google rewards depth on commercial comparison queries. Include features where the competitor wins to build authenticity, and link to two or three other comparison pages for internal discovery.

Why are my comparison pages not ranking in Google?▼

Common causes are missing internal links, templated duplicate metadata across pages, and URLs that omit the exact keyword. Add a Comparisons footer section, derive unique metadata per competitor, and refresh the year in titles annually.