What is seo-technical?

A guide to the technical parts of SEO, including how site structure, search crawling, page speed, and structured data affect how search engines understand a website.

Auditing technical SEO, improving site architecture and Core Web Vitals, fixing crawl or indexing issues, and checking structured data.

It helps diagnose indexing, crawling, performance, migration, and ranking problems that are not caused by the page content itself.

seo-technical — Skill for Claude Code by brainbytes-dev

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.

Any agent

npx skills add brainbytes-dev/everything-claude-marketing --skill seo-technical

Clone the repo

git clone --depth 1 https://github.com/brainbytes-dev/everything-claude-marketing

Made for: Claude Code.

Or install everything-claude-marketing, the plugin that ships this one along with the rest of its 72 skills, 22 commands, 18 agents, 2 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/skills/brainbytes-dev/everything-claude-marketing/seo-technical/github.svg)](https://agentmods.dev/skills/brainbytes-dev/everything-claude-marketing/seo-technical)

Your own site

<a href="https://agentmods.dev/skills/brainbytes-dev/everything-claude-marketing/seo-technical"><img src="https://agentmods.dev/badge/skills/brainbytes-dev/everything-claude-marketing/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/skills/brainbytes-dev/everything-claude-marketing/seo-technical"><img src="https://agentmods.dev/badge/skills/brainbytes-dev/everything-claude-marketing/seo-technical.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,900 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.00032	$0.02900
Opus 5.5	$0.00013	$0.01160
Sonnet 5.5	$0.00006	$0.00580
Haiku 4.5	$0.00003	$0.00290

Measured 2mo ago against content hash 22e171349526, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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/seo-technical/SKILL.md · 345 lines

How it starts

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

Technical SEO

When to Activate

Use this skill when auditing a website's technical SEO health, diagnosing crawl or indexing issues, optimizing Core Web Vitals, implementing structured data, or planning site architecture. Also use when migrating a site, launching a new domain, or troubleshooting ranking drops that aren't content-related.

First Questions

What CMS/framework is the site built on? (WordPress, Next.js, Shopify, custom — each has different technical SEO considerations)
What's the current state? (new site, established site with issues, migration in progress)
What triggered this audit? (ranking drop, new site launch, performance issues, indexing problems)
Do you have access to Google Search Console and server logs?
What's the site size? (100 pages vs. 100,000 pages — crawl budget matters at scale)

Crawlability and Indexing

Robots.txt

The robots.txt file controls which crawlers can access which parts of your site.

Best practices:

Place at domain root: https://example.com/robots.txt
Never block CSS or JavaScript files (Googlebot needs them to render pages)
Block admin pages, staging environments, internal search results, and duplicate parameter URLs
Reference your XML sitemap: Sitemap: https://example.com/sitemap.xml

Template:

User-agent: *
Allow: /
Disallow: /admin/
Disallow: /staging/
Disallow: /search?
Disallow: /*?sort=
Disallow: /*?filter=

Sitemap: https://example.com/sitemap.xml

Common mistakes:

Accidentally blocking the entire site (Disallow: /) after a staging-to-production migration
Blocking JavaScript/CSS files that Googlebot needs for rendering
Not updating robots.txt after URL structure changes

XML Sitemaps

Sitemaps tell search engines which pages exist and which are most important.

Best practices:

Include only indexable, canonical pages (200 status, no noindex)
Maximum 50,000 URLs per sitemap file; use sitemap index for larger sites
Include <lastmod> with accurate dates (not today's date on every page)
Submit sitemap in Google Search Console
Auto-generate sitemaps (don't maintain manually)
Separate sitemaps by content type for large sites: sitemap-blog.xml, sitemap-products.xml

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

2mo ago First seen · 345 lines · 32 tokens per session scan A 22e171349526

Subscribe to this mod's changes

seo-technical is a skill published in the GitHub repository brainbytes-dev/everything-claude-marketing (10 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 2,900 once invoked, about $0.0001 per session on Opus 5.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.

Marketing and SEO

seo-technical next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
seo-technicalbrainbytes-dev/everything-claude-marketing	Skill	10	7mo ago	MIT	A	32	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code