A command for producing a 2026 search-visibility plan covering traditional search engines and generative AI systems. It considers technical site health, content, structured data, and distribution.

Planning technical SEO, Core Web Vitals work, structured data, content, author credibility, and distribution across search and generative engines.

It separates Google-focused search work from visibility in AI-generated answers, helping teams assess both areas without treating them as one problem.

gtm-seo — Command for Claude Code by uppifyagency

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/uppifyagency/bettercallclaudegrowth

Made for: Claude Code.

Or install bettercallclaudegrowth, the plugin that ships this one along with the rest of its 9 skills, 11 commands, 3 agents.

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/uppifyagency/bettercallclaudegrowth/gtm-seo/github.svg)](https://agentmods.dev/commands/uppifyagency/bettercallclaudegrowth/gtm-seo)

Your own site

<a href="https://agentmods.dev/commands/uppifyagency/bettercallclaudegrowth/gtm-seo"><img src="https://agentmods.dev/badge/commands/uppifyagency/bettercallclaudegrowth/gtm-seo/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/uppifyagency/bettercallclaudegrowth/gtm-seo"><img src="https://agentmods.dev/badge/commands/uppifyagency/bettercallclaudegrowth/gtm-seo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 728 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.00030	$0.00728
Opus 5	$0.00015	$0.00364
Sonnet 5	$0.00006	$0.00146
Haiku 4.5	$0.00003	$0.00073

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

Security

Grade A, and why

gtm-seo 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.

bettercallclaudegrowth/commands/gtm-seo.md · 32 lines

How it starts

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

/gtm-seo - 2026 SEO + GEO Plan

This command applies the seo-2026-sota skill (folder in skills/). Respect userConfig: write in output_language (IT default), tune everything to userConfig.industry, use userConfig.brand_voice in copy suggestions and userConfig.default_channel to prioritize distribution.

Steps

Load the skill. Invoke the seo-2026-sota skill by name (it activates from its description; do not use file paths): start from its index, use the cheatsheet for verified thresholds and numbers, and dig into the patterns and the chapter from the Topic Index (CWV, schema, AIO, IndexNow, per-model distribution) when needed. DO NOT copy the books' text: extract only what you need to decide.
Frame the input. From $ARGUMENTS, derive the domain/pages, industry/ICP, and goal. Keep the two programs separate: classic SEO (Google) and GEO (generative engines) — the real overlap is low, do not treat them as a single lever.
Technical SEO. Assess on Google technical SEO and Core Web Vitals (LCP/INP/CLS against the cheatsheet's p75 thresholds), plus schema.org (Article+Author+Organization) and E-E-A-T with Experience dominant. Indicate the priority fixes and the official tools/APIs to use for measurement.
Content. Set up content to be selectable by AI Overviews and by LLMs: heading-as-question + atomic answer pattern, and a ToFu→BoFu pivot across the 4 BoFu formats. Tie the topics to the industry and to the ICP's intent.
GEO distribution. Apply GEO (optimization for LLMs: ChatGPT/Claude/Gemini/Perplexity) by mapping ICP → models → channels with the per-model levers and the 80/20 rule. Prioritize consistently with userConfig.default_channel.
Output — 2026 SEO/GEO Plan. Produce a structured plan:
- Summary (1 paragraph: where to act first and why)
- Technical SEO — prioritized CWV/schema/E-E-A-T fixes (impact × effort) with metric and tool
- Content — clusters and BoFu pages, heading-as-question format, ICP intent
- GEO distribution — model → source/channel → action table, with quick wins
- 30/60/90-day roadmap and KPIs (SEO and GEO kept separate)

Read the full file on GitHub · 32 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 · 32 lines · 30 tokens per session scan A 242857359d80

Subscribe to this mod's changes

gtm-seo is a command published in the GitHub repository uppifyagency/bettercallclaudegrowth (5 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 728 once invoked, about $0.0002 per session on Opus 5. 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-31.

Claude Code Marketing and SEO ai-marketing anthropic b2b-saas claude-code-plugin coaching

recall-save

Generate / overwrite .recall/context.md with Recall's local offline summarizer.

raiyanyahya/recall · 15 tokens

notebook-query

Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…

MarcosNahuel/antigravity-plugin-cc · 74 tokens

gtm-seo

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/gtm-seo - 2026 SEO + GEO Plan

Steps

What this file has done since we first saw it

Other commands, from other repositories

recall-save

notebook-query

ccc-orchestrate

standup

audit-project-github

design