What is landing-audit?

A command that reviews an existing landing page—a focused web page designed to get visitors to take one action—for conversion improvements.

Use it to audit a page from a URL or file, review its headline, calls to action, trust signals, structure, and search visibility, and save prioritized recommendations.

It finds problems that may stop visitors from signing up, requesting a demo, or becoming leads, using page content and available performance data.

How TheCraigHewitt/seomachine configures Claude Code

About the project

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.

TheCraigHewitt/seomachine · 7,427 stars · on GitHub · seomachine.io

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/TheCraigHewitt/seomachine/main/.claude/commands/landing-audit.md

Clone the repo

git clone --depth 1 https://github.com/TheCraigHewitt/seomachine

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/thecraighewitt/seomachine/landing-audit/github.svg)](https://agentmods.dev/commands/thecraighewitt/seomachine/landing-audit)

Your own site

<a href="https://agentmods.dev/commands/thecraighewitt/seomachine/landing-audit"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/landing-audit/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/thecraighewitt/seomachine/landing-audit"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/landing-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,931 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01931
Opus 5	$0.00000	$0.00966
Sonnet 5	$0.00000	$0.00386
Haiku 4.5	$0.00000	$0.00193

Measured 12d ago against content hash 90b0ade20730, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

landing-audit 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 12d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

landing-audit — 100% identical, 0 lines differ

.claude/commands/landing-audit.md · 306 lines

How it starts

The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Landing Page Audit Command

Use this command to audit existing landing pages for conversion optimization opportunities.

Usage

/landing-audit [URL or file path] --goal [trial|demo|lead]

Examples:

/landing-audit https://yoursite.com/private-producting-solutions/
/landing-audit landing-pages/product-hosting-beginners-2025-12-11.md --goal trial
/landing-audit https://yoursite.com/pricing/ --goal trial

Defaults:

--goal trial (if not specified)

What This Command Does

Fetches or reads the landing page content
Runs comprehensive CRO analysis using multiple analyzers
Pulls GA4 performance data (if available for [YOUR COMPANY] pages)
Generates prioritized recommendations
Saves audit report for reference

Analysis Modules Used

1. Landing Page Scorer

Module: data_sources/modules/landing_page_scorer.py

Overall score (0-100) against CRO best practices
Category scores: Above-fold, CTAs, Trust signals, Structure, SEO
Critical issues and warnings
Publishing readiness assessment

2. Above-the-Fold Analyzer

Module: data_sources/modules/above_fold_analyzer.py

Headline quality assessment
Value proposition clarity
CTA visibility check
Trust signal presence
5-second test evaluation

3. CTA Analyzer

Module: data_sources/modules/cta_analyzer.py

CTA count and distribution
Individual CTA quality scoring
Goal alignment check
Placement recommendations

4. Trust Signal Analyzer

Module: data_sources/modules/trust_signal_analyzer.py

Testimonial analysis (count, quality, specificity)
Social proof detection
Risk reversal presence
Authority signals

5. CRO Checker

Module: data_sources/modules/cro_checker.py

Checklist-based audit (30+ checks)
Pass/fail for each CRO best practice
Critical failures identification
Category-by-category breakdown

Process

Step 1: Content Retrieval

For URLs:

Fetch page content using WebFetch tool
Extract main content from HTML
Convert to markdown for analysis

Read the full file on GitHub · 306 lines

Changes

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.

12d ago First seen · 306 lines · 0 tokens per session scan A 90b0ade20730

Subscribe to this mod's changes

landing-audit 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,931 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.

Marketing and SEO

seomachine: Command for Claude Code