# Create Competitor Alternative Pages

Competitive search pages often become shallow feature tables that buyers do not trust. This skill helps create fair, research-backed alternative and comparison pages for SEO and sales enablement.

## Install

```bash
npx skillstore add coreyhaines31/competitor-alternatives
```

## Metadata

- Status: approved
- Slug: coreyhaines31-competitor-alternatives
- Skillstore revision: r1
- Version status: missing
- Tree hash: 05ef84b47282aa9fadc59400858dd29a6effb549ea3bc733f4a0ffaa6cad6748
- Author: coreyhaines31
- GitHub username: coreyhaines31
- License: MIT
- Repository: https://github.com/coreyhaines31/marketingskills/tree/main/skills/competitor-alternatives
- Ref: d11af420e07cd866fe39cfa937efef3223896c06
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/coreyhaines31-competitor-alternatives
- Manifest: https://skillstore.pages.dev/api/skills/coreyhaines31-competitor-alternatives/manifest

## Capabilities

- Defines four competitor page formats: singular alternative, plural alternatives, direct comparison, and competitor-versus-competitor pages.
- Provides recommended page structures, URL patterns, keyword targets, and tone guidance for each format.
- Shows how to centralize competitor data so pricing, strengths, weaknesses, and migration notes stay consistent.
- Includes reusable section templates for summaries, feature comparisons, pricing, support, audience fit, migration, and social proof.
- Adds guidance for index pages, internal linking, FAQ schema, research sources, and refresh cadence.

## Use Cases

- Build a competitor alternative page: Create a page for buyers searching for an alternative to a named competitor, with honest positioning and migration guidance.
- Plan a comparison content hub: Map index pages, internal links, URL patterns, and priority competitor topics for a scalable comparison content program.
- Support competitive sales conversations: Turn competitor research into fair comparison copy that sales teams can use during buyer evaluation.

## Prompt Templates

### Draft a simple alternative page

```
Create an outline for a [Competitor] alternative page for [Product]. Our main differentiator is [Differentiator], and our ideal customer is [Audience].
```

### Write a fair comparison page

```
Create a [Product] vs [Competitor] page plan. Include a TL;DR, comparison sections, who each product fits, migration notes, and CTA ideas.
```

### Create a comparison hub plan

```
Build a competitor comparison content plan for [Product]. Use these competitors: [List]. Include page types, URL patterns, hub pages, internal links, and priority order.
```

### Refresh existing competitor content

```
Audit this competitor page draft for accuracy, fairness, buyer usefulness, SEO coverage, and missing proof. Suggest specific updates and sections to add.
```

## Limitations

- It does not verify live competitor pricing, features, or search volume automatically.
- It needs accurate product positioning, competitor names, customer quotes, and migration details from the user.
- It does not create CMS templates, publish pages, or manage deployment workflows.
- Competitive claims may need legal, brand, or compliance review before publication.

## Best Practices

- Use current competitor research, customer proof, and clear source dates for claims that buyers can verify.
- Acknowledge competitor strengths and your own tradeoffs so the comparison feels credible.
- Centralize competitor data and refresh pricing, features, and positioning on a regular schedule.

## Anti Patterns

- Do not publish generic feature checklists without explaining why differences matter.
- Do not exaggerate competitor weaknesses or hide cases where the competitor is a better fit.
- Do not reuse stale pricing, reviews, or product details across pages without verification.

## Security Audit

- Audited at: 2026-07-06T07:16:47.666\+00:00
- Summary: The static external command alerts are false positives caused by Markdown URL examples, fenced Markdown, YAML, and JSON samples. The system reconnaissance alert is also a false positive because the line advises avoiding duplicated competitor research. No malicious intent, prompt injection, command execution, network access, or data exfiltration was found.

## Stats

- Views: 142
- Downloads: 12
- Favorites: 0
- Popularity score: 0