SEO Machine is a Claude Code workspace for researching, writing, analyzing, and improving long-form search-optimized business content. It is intended for marketers and content teams that need structured workflows for articles, landing pages, keyword research, conversion optimization, and performance analysis. Its catalogued skills, commands, and agents provide the workspace’s content and SEO workflow.
Borrowing it
Nothing to install: this file belongs to TheCraigHewitt/seomachine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TheCraigHewitt/seomachine/main/.claude/commands/landing-competitor.mdgit clone --depth 1 https://github.com/TheCraigHewitt/seomachineWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/thecraighewitt/seomachine/landing-competitor)<a href="https://agentmods.dev/commands/thecraighewitt/seomachine/landing-competitor"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/landing-competitor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/thecraighewitt/seomachine/landing-competitor"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/landing-competitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.02030 |
| Opus 5 | $0.00000 | $0.01015 |
| Sonnet 5 | $0.00000 | $0.00406 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
landing-competitor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- landing-competitor — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page Competitor Analysis Command
Use this command to analyze a specific competitor's landing page in depth.
Usage
/landing-competitor [URL]
Examples:
/landing-competitor https://competitor1.com/pricing//landing-competitor https://competitor2.com/features//landing-competitor https://competitor3.com/product/
What This Command Does
- Fetches and analyzes the competitor's landing page
- Extracts key CRO elements and patterns
- Identifies their strengths and weaknesses
- Provides actionable insights for [YOUR COMPANY] pages
- Saves analysis for reference
Analysis Framework
1. Page Overview
- URL and page type (homepage, pricing, feature, etc.)
- Estimated word count
- Page structure (sections, headers)
- Primary conversion goal
2. Above-the-Fold Analysis
- Headline (exact text and approach)
- Subheadline/value proposition
- CTA (text, visibility, design description)
- Trust signals visible
- Overall first impression
3. Content Strategy
- Key messages and themes
- Benefit vs feature balance
- Pain points addressed
- Unique value propositions
- Content organization
4. CTA Strategy
- All CTAs found (text and placement)
- CTA frequency and distribution
- CTA text patterns
- Goal alignment
5. Trust Signals
- Testimonials (count, quality, specificity)
- Social proof (customer counts, logos)
- Risk reversals (trials, guarantees)
- Authority signals (awards, media)
6. Objection Handling
- FAQ presence and quality
- Objections addressed in copy
- Comparison content
- Pricing transparency
7. Technical/UX Elements
- Page load speed (estimated)
- Mobile considerations visible
- Form complexity (if present)
- Navigation strategy
Output Format
Competitor Analysis Report
# Competitor Landing Page Analysis
**Competitor**: [Company Name]
**URL**: [URL]
**Analysis Date**: [date]
**Page Type**: [pricing/feature/homepage/etc.]
---
## Quick Summary
| Aspect | Rating | Notes |
|--------|--------|-------|
| Headline | [Strong/Moderate/Weak] | [brief note] |
| Value Prop | [Clear/Moderate/Unclear] | [brief note] |
| CTAs | [Strong/Moderate/Weak] | [brief note] |
| Trust Signals | [Strong/Moderate/Weak] | [brief note] |
| Overall CRO | [Strong/Moderate/Weak] | [brief note] |
---
## Above-the-Fold Breakdown
### Headline
**Text**: "[exact headline]"
**Approach**: [number/question/benefit/etc.]
**Strengths**: [what works]
**Weaknesses**: [what could be better]
### Subheadline/Value Prop
**Text**: "[exact text]"
**Clarity**: [clear/unclear]
**Specificity**: [specific/vague]
### Primary CTA
**Text**: "[exact CTA text]"
**Visibility**: [prominent/visible/hidden]
**Action Verb**: [yes/no - which verb]
**Benefit Word**: [yes/no - which word]
### Trust Signal Above Fold
**Present**: [yes/no]
**Type**: [customer count/rating/testimonial/logo/etc.]
**Text**: "[exact text if applicable]"
---
## Full CTA Analysis
| CTA Text | Position | Type | Strength |
|----------|----------|------|----------|
| "[text]" | [above fold/mid/bottom] | [primary/secondary] | [score] |
| "[text]" | [position] | [type] | [score] |
**Patterns Observed:**
- [Pattern 1]
- [Pattern 2]
---
## Trust Signals Inventory
### Testimonials
| Quote | Attribution | Specificity |
|-------|-------------|-------------|
| "[quote excerpt]" | [name, title] | [specific/vague] |
### Social Proof
- **Customer Count**: [if present]
- **Results/Numbers**: [if present]
- **Customer Logos**: [if present]
### Risk Reversals
- [ ] Free trial - Duration: [X days]
- [ ] No credit card
- [ ] Money-back guarantee
- [ ] Cancel anytime
### Authority Signals
- [Authority signal if present]
---
## Content Structure
**Estimated Word Count**: [X] words
**Number of Sections**: [X]
### Section Breakdown
1. **[Section title]** - [purpose/content summary]
2. **[Section title]** - [purpose/content summary]
3. **[Section title]** - [purpose/content summary]
### Content Focus
- **Benefits emphasized**: [list]
- **Features mentioned**: [list]
- **Pain points addressed**: [list]
---
## Strengths to Learn From
1. **[Strength 1]**
- What they do: [description]
- Why it works: [explanation]
- How [YOUR COMPANY] can use: [application]
2. **[Strength 2]**
- What they do: [description]
- Why it works: [explanation]
- How [YOUR COMPANY] can use: [application]
3. **[Strength 3]**
- What they do: [description]
- Why it works: [explanation]
- How [YOUR COMPANY] can use: [application]
---
## Weaknesses to Exploit
1. **[Weakness 1]**
- What's missing/weak: [description]
- Impact: [why it matters]
- [YOUR COMPANY] advantage: [how to capitalize]
2. **[Weakness 2]**
- What's missing/weak: [description]
- Impact: [why it matters]
- [YOUR COMPANY] advantage: [how to capitalize]
3. **[Weakness 3]**
- What's missing/weak: [description]
- Impact: [why it matters]
- [YOUR COMPANY] advantage: [how to capitalize]
---
## Key Takeaways for [YOUR COMPANY]
### Must Do (Critical Lessons)
1. [Takeaway 1]
2. [Takeaway 2]
### Should Do (Important Lessons)
1. [Takeaway 1]
2. [Takeaway 2]
### Could Do (Nice Ideas)
1. [Takeaway 1]
2. [Takeaway 2]
### Avoid (What Not to Copy)
1. [Anti-pattern 1]
2. [Anti-pattern 2]
---
## Recommended Differentiation
Based on this analysis, [YOUR COMPANY] should differentiate by:
1. **[Differentiation angle 1]**
- They say: [competitor approach]
- We should say: [[YOUR COMPANY] approach]
2. **[Differentiation angle 2]**
- They say: [competitor approach]
- We should say: [[YOUR COMPANY] approach]
---
## Headlines to Beat Theirs
Their headline: "[competitor headline]"
Better alternatives for [YOUR COMPANY]:
1. "[[YOUR COMPANY] headline option 1]"
2. "[[YOUR COMPANY] headline option 2]"
3. "[[YOUR COMPANY] headline option 3]"
---
## CTAs to Beat Theirs
Their primary CTA: "[competitor CTA]"
Stronger alternatives for [YOUR COMPANY]:
1. "[[YOUR COMPANY] CTA option 1]"
2. "[[YOUR COMPANY] CTA option 2]"
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 327 lines · 0 tokens per session scan A 6a00097df458
landing-competitor is a command published in the GitHub repository TheCraigHewitt/seomachine (7,434 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,030 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.