
Technical Seo Checker
Solo builders use this tool to audit technical SEO health, identify crawlability and indexing issues, and optimize Core Web Vitals without manual testing.
Install
npx skills add https://github.com/aaron-he-zhu/seo-geo-claude-skills --skill technical-seo-checkerWhat is this skill?
- Audits crawlability, indexing, and Core Web Vitals in one run
- Checks robots.txt, sitemaps, canonical tags, and HTTPS security
- Identifies mobile-friendliness and site speed bottlenecks
Adoption & trust: 4.5k installs on skills.sh; 2.1k GitHub stars; 2/3 security scanners passed (skills.sh audits).
Recommended Skills
Journey fit
Technical SEO checking is an ongoing operational task for monitoring site health and search engine visibility after launch. Site auditing and performance monitoring ensures continuous compliance with search engine requirements and identifies crawlability/indexing issues.
Common Questions / FAQ
Is Technical Seo Checker safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Technical Seo Checker
# Technical SEO Checker This skill performs comprehensive technical SEO audits to identify issues that may prevent search engines from properly crawling, indexing, and ranking your site. ## What This Skill Does Audits crawlability, indexability, Core Web Vitals, mobile-friendliness, HTTPS/security, structured data, URL structure, and international SEO with scored results and a prioritized fix roadmap. ## Quick Start Start with one of these prompts, then finish with the standard handoff summary from [Skill Contract](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/skill-contract.md). ### Full Technical Audit ``` Perform a technical SEO audit for [URL/domain] ``` ### Specific Issue Check ``` Check Core Web Vitals for [URL] ``` ``` Audit crawlability and indexability for [domain] ``` ### Pre-Migration Audit ``` Technical SEO checklist for migrating [old domain] to [new domain] ``` ``` Pre-migration audit: WordPress to Next.js headless ``` The migration flow has 6 stages (baseline snapshot, risk map, redirect map, staging QA, cutover checklist, T+1/T+7/T+30 diff). See [references/pre-migration-playbook.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/optimize/technical-seo-checker/references/pre-migration-playbook.md) for the full workflow and red-flag patterns. ### LLM Crawler Handling (GPTBot / ClaudeBot / PerplexityBot) ``` Audit how my site handles AI crawlers — I want to allow retrieval but block training ``` As of 2026, robots.txt must make explicit decisions about AI engines. See [references/llm-crawler-handling.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/optimize/technical-seo-checker/references/llm-crawler-handling.md) for the bot inventory, three stance patterns (default-open, default-closed, split), robots.txt templates, and the Cloudflare edge-override gotcha. ### Site-Wide / Bulk Audit (5+ URLs) For e-commerce and large sites (e.g., "40 of 50 products not indexed"), switch to bulk mode — sample per URL pattern, report pattern-level findings, deliver portfolio priority instead of per-URL output: ``` Bulk audit: 50 product pages on example.com, 40 not indexed ``` ``` Audit all URLs in https://example.com/sitemap.xml ``` See [references/bulk-audit-playbook.md](https://github.com/aaron-he-zhu/s