What is technical-seo?

A technical SEO checker for the behind-the-scenes parts of a website that help search engines crawl pages and decide whether to list them.

Use it to audit sitemap links, robots.txt and robots meta directives, canonical tags, URL structure, redirects, crawlability, and indexability.

It finds setup problems such as broken sitemap references, restrictive robots rules, missing or invalid canonical URLs, redirect chains, and pages that cannot be indexed.

technical-seo — Skill for Claude Code and Codex by thisisAhsanIqbal

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 thisisAhsanIqbal/nextjs-seo-audit --skill technical-seo

Clone the repo

git clone --depth 1 https://github.com/thisisAhsanIqbal/nextjs-seo-audit

Made for: Claude Code, Codex.

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/thisisahsaniqbal/nextjs-seo-audit/technical-seo/github.svg)](https://agentmods.dev/skills/thisisahsaniqbal/nextjs-seo-audit/technical-seo)

Your own site

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

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

When invoked 1,226 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.00041	$0.01226
Opus 5.5	$0.00016	$0.00490
Sonnet 5.5	$0.00008	$0.00245
Haiku 4.5	$0.00004	$0.00123

Measured 2mo ago against content hash 1a2ac628f340, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

technical-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 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/technical-seo/SKILL.md · 117 lines

How it starts

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

Technical SEO

Audit fundamental technical SEO factors that affect crawlability and indexability.

1. Canonical URL

Check	Status
`<link rel="canonical">` missing	⚠️ WARN "Add canonical to prevent duplicate content"
Canonical present but empty `href`	❌ FAIL
Canonical points to a different domain	⚠️ WARN "Cross-domain canonical — verify this is intentional"
Canonical is relative (not absolute URL)	⚠️ WARN "Use absolute URLs for canonical tags"
Canonical present and valid	✅ PASS
Multiple canonical tags	❌ FAIL "Only one canonical allowed per page"
Canonical is self-referencing	✅ PASS (best practice)

2. Robots meta

Check	Status
`<meta name="robots" content="noindex">`	⚠️ WARN "Page will not appear in search results"
`<meta name="robots" content="nofollow">`	⚠️ WARN "Links on this page will not be followed"
`<meta name="robots" content="noindex, nofollow">`	⚠️ WARN "Page excluded from search entirely"
`<meta name="robots" content="index, follow">` or absent	✅ PASS "Page is indexable"
`<meta name="googlebot">` present	✅ PASS — report its content

3. Robots.txt references

Check if the page references or is affected by robots.txt:

Look for <meta name="robots"> directives
If analysing a full site, check robots.txt at site root for:
- Disallow rules that block the current page
- Sitemap directive pointing to sitemap location
- Crawl-delay directives (may slow indexing)

4. Sitemap references

Check	Status
`<link rel="sitemap">` present	✅ PASS
No sitemap reference found	⚠️ WARN "Consider adding sitemap reference"

If sitemap URL is available, verify:

Valid XML format
Contains the current page URL
No URLs returning 4xx/5xx status codes

5. URL structure

Analyse the page URL (from <link rel="canonical"> or <meta property="og:url">):

Check	Status
URL contains uppercase letters	⚠️ WARN "Use lowercase-only URLs"
URL contains underscores	⚠️ WARN "Use hyphens instead of underscores"
URL contains special characters or spaces (encoded `%20`)	⚠️ WARN "Simplify URL structure"
URL exceeds 100 characters	⚠️ WARN "Keep URLs concise"
URL has double slashes (`//path`)	❌ FAIL "Fix double slashes"
URL has trailing slash inconsistency	⚠️ WARN "Be consistent with trailing slashes"
Clean, descriptive, lowercase with hyphens	✅ PASS

Read the full file on GitHub · 117 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 · 117 lines · 41 tokens per session scan A 1a2ac628f340

Subscribe to this mod's changes

technical-seo is a skill published in the GitHub repository thisisAhsanIqbal/nextjs-seo-audit (7 stars, last pushed 8mo ago), licensed MIT. It adds 41 tokens to every session and 1,226 once invoked, about $0.0002 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-08-31.

Marketing and SEO agent-skill agent-skills ai-agent claude copilot core-web-vitals

technical-seo next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
technical-seothisisAhsanIqbal/nextjs-seo-audit	Skill	7	8mo ago	MIT	A	41	Claude Code, Codex
podlite-markuppodlite/podlite-skills	Skill	3	13d ago	MIT	A	47	Claude Code
podlite-verifypodlite/podlite-skills	Skill	3	13d ago	MIT	A	64	Claude Code
wgmagent-frontier/wgm	Skill	3	3d ago	MIT	A	155	Claude Code, Codex
ruggedagent-frontier/wgm	Skill	3	3d ago	MIT	A	182	Claude Code, Codex
teach-meagent-frontier/wgm	Skill	3	3d ago	MIT	A	149	Claude Code, Codex
quiz-meagent-frontier/wgm	Skill	3	3d ago	MIT	B	151	Claude Code, Codex