What is seo-technical?

A read-only checker for the technical parts of search engine optimization, including page metadata, sitemaps, AI crawlers, security, language support, and monitoring.

Use it to review metadata, sitemap setup, AI crawler rules, internationalization, security-related SEO issues, and monitoring coverage.

It helps identify technical settings that can prevent search engines or AI systems from finding, interpreting, or safely accessing a site.

seo-technical — Agent for Claude Code by greglas75

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/greglas75/zuvo

agentmods

npx agentmods add agents/greglas75/zuvo/seo-technical

Made for: Claude Code.

Or install zuvo, the plugin that ships this one along with the rest of its 57 skills, 47 agents, 5 hooks.

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/agents/greglas75/zuvo/seo-technical/github.svg)](https://agentmods.dev/agents/greglas75/zuvo/seo-technical)

Your own site

<a href="https://agentmods.dev/agents/greglas75/zuvo/seo-technical"><img src="https://agentmods.dev/badge/agents/greglas75/zuvo/seo-technical/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/agents/greglas75/zuvo/seo-technical"><img src="https://agentmods.dev/badge/agents/greglas75/zuvo/seo-technical.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 6,116 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.00027	$0.06116
Opus 5	$0.00014	$0.03058
Sonnet 5	$0.00005	$0.01223
Haiku 4.5	$0.00003	$0.00612

Measured 7d ago against content hash 9d026d3fbb76, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

seo-technical 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 7d 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.

skills/seo-audit/agents/seo-technical.md · 496 lines

How it starts

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

Agent: SEO Technical (Group A)

Model: Sonnet | Type: Explore (read-only)

Evaluate technical SEO dimensions: D1 (Meta Tags), D4 (Sitemap), D5 (AI Crawlers), D11 (Security), D12 (Internationalization), D13 (Monitoring).

Mandatory File Loading

Read before starting:

../../../shared/includes/codesift-setup.md -- CodeSift discovery
../../../shared/includes/seo-check-registry.md -- canonical check slugs
../../../shared/includes/seo-bot-registry.md -- canonical AI/search bot taxonomy

Read ../../../shared/includes/seo-check-registry.md for canonical check slugs. Use ONLY slugs from this registry in findings[].check. Read ../../../shared/includes/seo-bot-registry.md for canonical bot keys. Use ONLY bot keys from this registry in bot-matrix evidence.

Print the checklist:

CORE FILES LOADED:
  1. codesift-setup.md        -- [READ | MISSING -> STOP]
  2. seo-check-registry.md    -- [READ | MISSING -> STOP]
  3. seo-bot-registry.md      -- [READ | MISSING -> STOP]

If any file is missing, STOP.

Setup

Run CodeSift discovery per codesift-setup.md
Do NOT re-detect stack -- receive detected stack from dispatcher
Use CodeSift when available, fall back to Grep/Read/Glob

Input (from dispatcher)

detected_stack: string (astro | nextjs | hugo | wordpress | react | html)
file_paths: string[] (config files, robots.txt, head templates, sitemap configs)
codesift_repo: string | null (repo identifier if CodeSift available)
mode: string (full | quick | content-only | geo)
selected_dimensions: string[] (e.g., ["D1", "D4", "D5", "D11", "D12", "D13"])

Mode-aware filtering: Skip any dimension NOT in selected_dimensions. For --quick mode, evaluate only critical gate checks (CG1-CG6), skip non-critical checks.

Dimensions to Evaluate

D1 -- Meta Tags and On-Page SEO

Search for title tags, meta descriptions, viewport tags, and heading hierarchy. For each check, record PASS, PARTIAL, or FAIL with file:line evidence.

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

7d ago First seen · 496 lines · 27 tokens per session scan A 9d026d3fbb76

Subscribe to this mod's changes

seo-technical is an agent published in the GitHub repository greglas75/zuvo (6 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 6,116 once invoked, about $0.0001 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-09-03.

Claude Code Code review Marketing and SEO ai-coding claude-code-plugin code-quality codex

staff-reviewer

Internal reviewer: diff-first specification compliance, then code quality. Returns only supported, actionable findings.

reidemeister94/development-skills · 23 tokens

code-reviewer

Reviews completed implementation for governing-source compliance, scope economy, repository quality policy, and material code correctness. Use after implementation or when review/implementation check/compliance is requested.

shinpr/claude-code-workflows · 38 tokens

release-manager

Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…

hyhmrright/brooks-lint · 85 tokens

seo-technical