seomachine: Command for Claude Code

.claude/commands/landing-publish.md

landing-publish is a command for Claude Code from TheCraigHewitt/seomachine. It costs 0 tokens per session (1,527 once invoked), scanned A, original, MIT.

A command that publishes a prepared landing page to WordPress as a page rather than a blog post.

In plain words
What is it for?
Use it to validate a Markdown landing-page file, create the WordPress page through the REST API, set Yoast SEO fields, apply a template, or mark the page as noindex.
Why use it?
It reduces manual copying and checks that the page meets the required quality, metadata, and content conditions before publishing.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is TheCraigHewitt/seomachine's own configuration. It tells Claude Code how to work on seomachine itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything seomachine configures →

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,434 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-publish.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.

agentmods badge for landing-publish

README.md
[![agentmods](https://agentmods.dev/badge/commands/thecraighewitt/seomachine/landing-publish/github.svg)](https://agentmods.dev/commands/thecraighewitt/seomachine/landing-publish)
Your own site
<a href="https://agentmods.dev/commands/thecraighewitt/seomachine/landing-publish"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/landing-publish/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.

agentmods 80×15 button for landing-publish

Your own site · 80×15
<a href="https://agentmods.dev/commands/thecraighewitt/seomachine/landing-publish"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/landing-publish.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,527 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01527
Opus 5 $0.00000 $0.00763
Sonnet 5 $0.00000 $0.00305
Haiku 4.5 $0.00000 $0.00153

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

Security

Grade A, and why

landing-publish 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.

.claude/commands/landing-publish.md · 252 lines

How it starts

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

Landing Page Publish Command

Use this command to publish landing pages to WordPress as pages (not blog posts).

Usage

/landing-publish [file path] [options]

Options:

  • --noindex: Set noindex meta (for PPC pages)
  • --template [slug]: Use specific WordPress page template

Examples:

  • /landing-publish landing-pages/product-hosting-beginners-2025-12-11.md
  • /landing-publish landing-pages/free-trial-ppc-2025-12-11.md --noindex
  • /landing-publish landing-pages/pricing-comparison-2025-12-11.md --template landing-page

What This Command Does

  1. Validates the landing page file
  2. Checks landing page score (must be ≥75)
  3. Parses markdown and metadata
  4. Creates WordPress page via REST API
  5. Sets Yoast SEO fields
  6. Returns edit URL for review

Prerequisites

Before publishing, ensure:

  1. Landing page score is ≥75 (run /landing-audit first)
  2. No critical issues remain
  3. All required metadata is present
  4. Content has been scrubbed for AI watermarks

File Format Requirements

Landing page files must include this metadata:

# [H1 Headline]

**Meta Title**: [50-60 characters]
**Meta Description**: [150-160 characters]
**Target Keyword**: [primary keyword]
**Page Type**: seo | ppc
**Conversion Goal**: trial | demo | lead
**URL Slug**: /[page-slug]/

---

[Content...]

Publishing Process

Step 1: Validation

Check file exists and contains required fields:

  • Meta Title (required)
  • Meta Description (required)
  • Target Keyword (required for SEO pages)
  • Page Type
  • Conversion Goal
  • URL Slug

Step 2: Score Check

Run landing page scorer:

from data_sources.modules.landing_page_scorer import score_landing_page

score = score_landing_page(content, page_type, goal, meta_title, meta_description, keyword)

if score['overall_score'] < 75:
    print("Score too low. Fix issues before publishing.")
    print(f"Current score: {score['overall_score']}")
    print(f"Critical issues: {score['critical_issues']}")
    # Abort publishing

Read the full file on GitHub · 252 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.

  1. 12d ago First seen · 252 lines · 0 tokens per session scan A b8e582b59aef

Subscribe to this mod's changes

landing-publish 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 1,527 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.