Technical SEO Auditor
Purpose
Find technical SEO issues that prevent search engines from crawling, indexing, understanding, and ranking important pages.
When to Use
Use this skill when the task is to review crawlability, indexation, robots.txt, sitemap, canonical tags, redirects, status codes, duplicate pages, pagination, performance, or structured data foundations.
Inputs
Useful inputs: website URL, crawl data, Search Console data, robots.txt, sitemap, CMS/platform, page templates, error reports, and priority pages.
Workflow
- Define priority pages and technical risk.
- Review robots, sitemap, status codes, redirects, canonicals, noindex, and duplicates.
- Check template-level technical patterns.
- Review mobile, speed, structured data, and international tags when relevant.
- Prioritize fixes by indexation and ranking impact.
Output
Always provide technical diagnosis, crawl/index blockers, template issues, priority fixes, validation steps, and next actions.
Common Mistakes
- Fixing minor warnings before index blockers.
- Ignoring template-level problems.
- Confusing canonical hints with guaranteed indexation.
- Not validating after fixes.
Related Skills
- indexation-crawlability-auditor
- schema-markup-specialist
- site-speed-auditor
- multilingual-seo-localizer
1---2name: technical-seo-auditor3description: Technical SEO Auditor4---5# Technical SEO Auditor67## Purpose89Find technical SEO issues that prevent search engines from crawling, indexing, understanding, and ranking important pages.1011## When to Use1213Use this skill when the task is to review crawlability, indexation, robots.txt, sitemap, canonical tags, redirects, status codes, duplicate pages, pagination, performance, or structured data foundations.1415## Inputs1617Useful inputs: website URL, crawl data, Search Console data, robots.txt, sitemap, CMS/platform, page templates, error reports, and priority pages.1819## Workflow20211. Define priority pages and technical risk.222. Review robots, sitemap, status codes, redirects, canonicals, noindex, and duplicates.233. Check template-level technical patterns.244. Review mobile, speed, structured data, and international tags when relevant.255. Prioritize fixes by indexation and ranking impact.2627## Output2829Always provide technical diagnosis, crawl/index blockers, template issues, priority fixes, validation steps, and next actions.3031## Common Mistakes3233- Fixing minor warnings before index blockers.34- Ignoring template-level problems.35- Confusing canonical hints with guaranteed indexation.36- Not validating after fixes.3738## Related Skills3940- indexation-crawlability-auditor41- schema-markup-specialist42- site-speed-auditor43- multilingual-seo-localizer
dasexperten