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-write.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-write)<a href="https://agentmods.dev/commands/thecraighewitt/seomachine/landing-write"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/landing-write/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-write"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/landing-write.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.02664 |
| Opus 5 | $0.00000 | $0.01332 |
| Sonnet 5 | $0.00000 | $0.00533 |
| Haiku 4.5 | $0.00000 | $0.00266 |
Grade A, and why
landing-write 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 9d 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-write — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page Write Command
Use this command to create high-converting landing pages optimized for either organic SEO traffic or paid PPC traffic.
Usage
/landing-write [topic or research brief] --type [seo|ppc] --goal [trial|demo|lead]
Examples:
/landing-write "product hosting for beginners" --type seo --goal trial/landing-write "research/landing-brief-private-producting.md" --type ppc --goal demo/landing-write "product monetization guide" --type seo --goal lead
Defaults:
--type seo(if not specified)--goal trial(if not specified)
What This Command Does
- Creates conversion-optimized landing pages (not blog articles)
- Tailors content length and structure to page type (SEO vs PPC)
- Optimizes CTAs for the specified conversion goal
- Includes all CRO best practices (trust signals, risk reversal, etc.)
- Scores the page against landing page best practices
Pre-Writing Review
Required Context:
- Landing Page Templates: @context/landing-page-templates.md for structure
- CRO Best Practices: @context/cro-best-practices.md for conversion guidelines
- Brand Voice: @context/brand-voice.md for tone and messaging
If Research Brief Available:
- Review competitor analysis
- Use recommended headlines
- Reference identified pain points
- Integrate suggested trust signals
SEO Landing Page Structure (--type seo)
Word Count: 1500-2500 words CTAs: 3-5 distributed throughout Internal Links: 2-3 strategic links
Content Structure
# [Benefit-Focused Headline with Keyword]
**Meta Title**: [50-60 chars, keyword + benefit]
**Meta Description**: [150-160 chars, includes CTA]
**Target Keyword**: [primary keyword]
**Page Type**: seo
**Conversion Goal**: [trial|demo|lead]
---
[HOOK: 2-3 sentences. Start with pain point, surprising stat, or question]
[Trust signal: "Join 50,000+ customers" or customer results]
**[Primary CTA Button →]**
## [H2: Problem/Pain Point Section]
[2-3 paragraphs acknowledging the reader's struggle]
[Mini-story with specific person and outcome]
## [H2: Solution Overview]
[Introduce how [YOUR COMPANY] solves this problem]
**Key Benefits:**
- **[Benefit 1]** - [One sentence]
- **[Benefit 2]** - [One sentence]
- **[Benefit 3]** - [One sentence]
**[Secondary CTA →]**
## [H2: Features That Deliver]
[3-5 features, each tied to a benefit]
### [Feature 1]
[2-3 sentences: what it is, why it matters]
### [Feature 2]
[Continue...]
## [H2: Social Proof]
"[Testimonial with specific results]"
— **[Name], [Product/Company]**
"[Second testimonial]"
— **[Name], [Product/Company]**
**Results our customers see:**
- [Specific result with number]
- [Specific result with number]
**[CTA Button →]**
## [H2: How It Works]
1. **[Step 1]** - [Brief description]
2. **[Step 2]** - [Brief description]
3. **[Step 3]** - [Brief description]
## [H2: FAQ Section]
**[Question addressing objection]?**
[Answer - 2-3 sentences]
**[Question addressing objection]?**
[Answer - 2-3 sentences]
[4-6 FAQs total]
## [H2: Ready to [Achieve Outcome]?]
[1-2 sentences summarizing the value]
**[Strong CTA Button →]**
[Risk reversal: "Free trial • No credit card • Cancel anytime"]
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.
- 9d ago First seen · 427 lines · 0 tokens per session scan A 545874d74dad
landing-write is a command published in the GitHub repository TheCraigHewitt/seomachine (7,425 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,664 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.