Crawl, index, render
Technical SEO
A nine-category technical audit covering crawlability, indexing, rendering, redirects and site architecture.
Find the technical issues that stop good content from ranking: blocked crawlers, broken canonicals, bad redirect chains, render-blocking JavaScript and sitemap mistakes.
- Audit categories
- 9
- Agent specialists
- 19
- Core commands
- 30
- Report formats
- 3
Live scene
Technical SEO
claude plugin marketplace add AgriciDaniel/claude-seoMITOverview
What Technical SEO actually does
The technical SEO skill walks through the parts of a site that search engines must be able to reach, understand and trust. It checks robots directives, XML sitemaps, canonical tags, redirect behaviour, hreflang, pagination, JavaScript rendering and index bloat.
Findings are scored and sorted by impact instead of being dumped into one long warning list. Each fix explains why it matters, what it depends on and how to verify the result after deployment.
Capabilities
What it helps your agent ship
Detect robots.txt, meta robots, X-Robots-Tag and noindex conflicts.
Validate XML sitemaps, canonical targets and redirect chains.
Audit JavaScript rendering for React, Next.js and Vue sites.
Find duplicate pages, faceted navigation traps and index bloat.
Check hreflang clusters and international URL structure.
Prioritise fixes by crawl impact, effort and expected outcome.
Workflow
The process the skill follows
A repeatable sequence keeps the agent from jumping straight into edits before it understands the job.
- 01
Crawl and inventory
Map reachable URLs, status codes, redirect hops and orphan pages before judging content.
- 02
Check index controls
Compare robots directives, canonicals, sitemap inclusion and actual indexability for each template.
- 03
Test rendering
Open JavaScript-dependent pages in a headless browser so the audit reflects what visitors and crawlers see.
- 04
Score and group findings
Separate critical blockers from warnings and opportunities, then attach a verification step to each fix.
- 05
Re-audit after release
Compare the new crawl against the baseline to confirm the fix worked and nothing regressed.
Inside the pack
References and modules
These are the load-on-demand files or command groups that make the skill useful beyond a single prompt.
Crawlability
robots.txt, meta robots, crawl budget and internal link discovery.
Indexing
Canonicals, duplicates, thin pages, noindex rules and index bloat.
Sitemaps
XML sitemap generation, lastmod accuracy and canonical-only inclusion.
Redirects
301/302 chains, loops, protocol and trailing-slash consistency.
Rendering
Server-rendered content, hydration, blocked resources and content parity.
International
Hreflang clusters, x-default, locale URLs and regional targeting.
Use cases
Where it earns its place
Traffic dropped after a migration
Trace redirects, canonical changes, sitemap gaps and lost internal links in one pass.
JavaScript framework audit
Verify that primary content and links exist in the rendered HTML, not only after hydration.
Index bloat cleanup
Identify thin, duplicate and low-value URLs, then define noindex or pruning rules.
Prompt starters
Try one of these first
Copy a prompt into your agent. Replace the example URL with your own project or page.
Run a technical SEO audit of this site across crawlability, indexing, redirects, rendering and sitemaps.
These pages stopped ranking after a migration. Compare the redirects, canonicals and sitemap to find the cause.
Audit the rendered HTML of this Next.js site and tell me which content is invisible without JavaScript.
Keep exploring
Related skills
Want a site that uses this skill properly?
We build Next.js websites with technical SEO, structured data, 3D scenes and motion that stays inside a performance budget.