Overview
Technical SEO Checker is the skill of auditing the site conditions that determine whether good pages can actually be crawled, indexed, and trusted. For a one-person company, technical SEO should stay simple and ruthless: remove blockers, stabilize canonical paths, keep performance acceptable, and avoid avoidable crawl waste.
When to Use This Skill
Use this before and after major releases, when rankings drop unexpectedly, when answer-engine visibility falls despite strong content, or when you suspect crawl or canonical problems are distorting performance.
What This Skill Does
This skill helps you check the few technical layers that actually matter for a lean content site: robots, sitemap, canonicals, redirects, indexability, basic performance, and structured data sanity.
How to Use
Step 1: Check crawl access. Confirm robots.txt, sitemap discovery, and that important paths are not blocked.
Step 2: Check canonical integrity. Every important page should point to its intended canonical URL, and redirects should support that choice.
Step 3: Check indexability. Look for accidental noindex, orphan pages, thin duplicates, and pages that exist in the site but not the sitemap.
Step 4: Check route hygiene. Legacy paths should resolve cleanly. Do not let old traffic fall back to the homepage or soft 404 behavior.
Step 5: Check performance basics. You do not need perfection, but you do need stable load behavior, readable markup, and mobile-safe layout.
Step 6: Check structured data and metadata. Article, FAQ, Organization, and canonical signals should reinforce the page instead of conflicting with it.
Output
The output should include:
- A list of blockers by severity
- Affected URLs or patterns
- The fix recommendation
- Whether the issue affects crawl, index, traffic, or citations
Evidence and Sources According to Google technical documentation, crawlability, canonical consistency, and valid structured data are the baseline signals that must be stable before content quality improvements can fully compound.
Common Mistakes
Do not run a huge checklist without prioritizing impact. Do not spend weeks on micro-optimizations while canonical and redirect issues stay broken. Do not create multiple public URLs for the same page. Do not treat sitemap presence as proof that a page is healthy.
SKILL.md file
Preview raw SKILL.md. Open the full source below. Scroll, inspect, then download the exact SKILL.md file if you want the original.
# technical-seo-checker
Technical SEO Checker
Overview
Technical SEO Checker is the skill of auditing the site conditions that determine whether good pages can actually be crawled, indexed, and trusted. For a one-person company, technical SEO should stay simple and ruthless: remove blockers, stabilize canonical paths, keep performance acceptable, and avoid avoidable crawl waste.
When to Use This Skill
Use this before and after major releases, when rankings drop unexpectedly, when answer-engine visibility falls despite strong content, or when you suspect crawl or canonical problems are distorting performance.
What This Skill Does
This skill helps you check the few technical layers that actually matter for a lean content site: robots, sitemap, canonicals, redirects, indexability, basic performance, and structured data sanity.
How to Use
Step 1: Check crawl access. Confirm `robots.txt`, sitemap discovery, and that important paths are not blocked.
Step 2: Check canonical integrity. Every important page should point to its intended canonical URL, and redirects should support that choice.
Step 3: Check indexability. Look for accidental `noindex`, orphan pages, thin duplicates, and pages that exist in the site but not the sitemap.
Step 4: Check route hygiene. Legacy paths should resolve cleanly. Do not let old traffic fall back to the homepage or soft 404 behavior.
Step 5: Check performance basics. You do not need perfection, but you do need stable load behavior, readable markup, and mobile-safe layout.
Step 6: Check structured data and metadata. Article, FAQ, Organization, and canonical signals should reinforce the page instead of conflicting with it.
Output
The output should include:
A list of blockers by severity
Affected URLs or patterns
The fix recommendation
Whether the issue affects crawl, index, traffic, or citations
Evidence and Sources
According to Google technical documentation, crawlability, canonical consistency, and valid structured data are the baseline signals that must be stable before content quality improvements can fully compound.
- Source: [Google Search Central - robots.txt specifications](https://developers.google.com/search/docs/crawling-indexing/robots/robots_txt)
- Source: [Google Search Central - Consolidate duplicate URLs](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls)
- Source: [Google Search Central - Introduction to structured data](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data)
Common Mistakes
Do not run a huge checklist without prioritizing impact.
Do not spend weeks on micro-optimizations while canonical and redirect issues stay broken.
Do not create multiple public URLs for the same page.
Do not treat sitemap presence as proof that a page is healthy.
Preview raw SKILL.md. Open the full source below. Scroll, inspect, then download the exact SKILL.md file if you want the original.
# technical-seo-checker
Technical SEO Checker
Overview
Technical SEO Checker is the skill of auditing the site conditions that determine whether good pages can actually be crawled, indexed, and trusted. For a one-person company, technical SEO should stay simple and ruthless: remove blockers, stabilize canonical paths, keep performance acceptable, and avoid avoidable crawl waste.
When to Use This Skill
Use this before and after major releases, when rankings drop unexpectedly, when answer-engine visibility falls despite strong content, or when you suspect crawl or canonical problems are distorting performance.
What This Skill Does
This skill helps you check the few technical layers that actually matter for a lean content site: robots, sitemap, canonicals, redirects, indexability, basic performance, and structured data sanity.
How to Use
Step 1: Check crawl access. Confirm `robots.txt`, sitemap discovery, and that important paths are not blocked.
Step 2: Check canonical integrity. Every important page should point to its intended canonical URL, and redirects should support that choice.
Step 3: Check indexability. Look for accidental `noindex`, orphan pages, thin duplicates, and pages that exist in the site but not the sitemap.
Step 4: Check route hygiene. Legacy paths should resolve cleanly. Do not let old traffic fall back to the homepage or soft 404 behavior.
Step 5: Check performance basics. You do not need perfection, but you do need stable load behavior, readable markup, and mobile-safe layout.
Step 6: Check structured data and metadata. Article, FAQ, Organization, and canonical signals should reinforce the page instead of conflicting with it.
Output
The output should include:
A list of blockers by severity
Affected URLs or patterns
The fix recommendation
Whether the issue affects crawl, index, traffic, or citations
Evidence and Sources
According to Google technical documentation, crawlability, canonical consistency, and valid structured data are the baseline signals that must be stable before content quality improvements can fully compound.
- Source: [Google Search Central - robots.txt specifications](https://developers.google.com/search/docs/crawling-indexing/robots/robots_txt)
- Source: [Google Search Central - Consolidate duplicate URLs](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls)
- Source: [Google Search Central - Introduction to structured data](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data)
Common Mistakes
Do not run a huge checklist without prioritizing impact.
Do not spend weeks on micro-optimizations while canonical and redirect issues stay broken.
Do not create multiple public URLs for the same page.
Do not treat sitemap presence as proof that a page is healthy.
Comments & Discussion
Add a comment