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/analyze-existing.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/analyze-existing)<a href="https://agentmods.dev/commands/thecraighewitt/seomachine/analyze-existing"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/analyze-existing/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/analyze-existing"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/analyze-existing.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.01309 |
| Opus 5 | $0.00000 | $0.00655 |
| Sonnet 5 | $0.00000 | $0.00262 |
| Haiku 4.5 | $0.00000 | $0.00131 |
Grade A, and why
analyze-existing 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 11d 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:
- analyze-existing — 98% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Existing Command
Use this command to review and analyze existing your company blog posts for SEO opportunities, content gaps, and improvement areas.
Usage
/analyze-existing [URL or file path]
What This Command Does
- Fetches and analyzes existing blog post content
- Evaluates current SEO performance and optimization
- Identifies outdated information or statistics
- Suggests content expansion opportunities
- Provides actionable improvement recommendations
Process
Content Analysis
- URL/File Input: Accept either a live URL or local file path
- Content Extraction: Pull the full article text, headings, and structure
- Publication Date Check: Note when content was originally published
- Current Relevance: Identify outdated information, statistics, or references
- Completeness: Assess if topic coverage is comprehensive or has gaps
SEO Audit (Enhanced with New Analysis Tools)
- Search Intent Analysis (NEW!): Determine if content matches user search intent (informational/commercial/transactional/navigational)
- Target Keyword: Identify primary keyword and variations
- Keyword Density & Clustering (NEW!): Deep analysis of keyword density, distribution heatmap, topic clustering, and keyword stuffing risk detection
- Keyword Placement: Check H1, H2, first 100 words, meta title/description
- Heading Structure: Evaluate H1-H6 hierarchy and keyword integration
- Content Length Comparison (NEW!): Compare word count against top 10-20 SERP competitors to determine optimal length
- Meta Elements: Review meta title (50-60 chars) and description (150-160 chars)
- Internal Links: Count and evaluate quality of internal links (aim for 3-5+)
- External Links: Check for authoritative external sources
- Readability Score (NEW!): Calculate Flesch Reading Ease, Flesch-Kincaid Grade Level, passive voice ratio, sentence complexity
- SEO Quality Rating (NEW!): Overall score (0-100) with category breakdowns for content, keywords, meta, structure, links, and readability
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.
- 11d ago First seen · 119 lines · 0 tokens per session scan A ffcee4953de5
analyze-existing is a command published in the GitHub repository TheCraigHewitt/seomachine (7,427 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,309 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.