Audit and repair how a site is discovered, crawled, rendered, indexed, and navigated: technical and on-page SEO diagnosis, international setup, content quality signals, information architecture, page hierarchy, navigation, URL conventions, internal linking, visual sitemaps, and migrations. Use when rankings or organic traffic decline, pages are not indexed, or a site needs restructuring; use structured-data for JSON-LD and template-pages for scaled page systems.
Installs into .claude/skills of the current project.
Are you the author of Search Health?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/mtent-search-health)
---
name: search-health
description: Audit and repair how a site is discovered, crawled, rendered, indexed, and navigated: technical and on-page SEO diagnosis, international setup, content quality signals, information architecture, page hierarchy, navigation, URL conventions, internal linking, visual sitemaps, and migrations. Use when rankings or organic traffic decline, pages are not indexed, or a site needs restructuring; use structured-data for JSON-LD and template-pages for scaled page systems.
license: MIT
metadata:
version: "2.0.0"
author: MTEnt
---
# Search Health
Separate discovery, crawlability, rendering, canonical selection, indexing, ranking, traffic, and conversion; evidence of one state does not prove the next. Design architecture around audience tasks and content ownership, not page counts.
If `.agents/marketing-context.md` exists, read it first; it is the truth file every skill in this hub shares, and its evidence states are constraints. Read [audit-system.md](references/audit-system.md) for technical access, international, on-page, content quality, site-type checks, and the prioritization record. Read [architecture-system.md](references/architecture-system.md) for site models, hierarchy, navigation, URLs, sitemaps, internal links, and migrations.
## Operating contract
1. Define site, environments, markets, languages, page types, audiences and primary tasks, business outcome, known changes, access, and reporting period.
2. Verify current search-engine guidance from official sources and inspect the actual site and representative rendered pages.
3. Attach each finding to observed evidence, affected scope, likely impact, confidence, owning layer, fix, and verification; prioritize access and canonical defects before metadata polish.
4. For architecture work establish hierarchy and navigation from user decisions before naming URLs, and give every page type a purpose, creation rule, owner, internal-link role, and retirement condition.
5. Return implementation-ready fixes, the migration map where applicable, validation steps, and monitoring.
Do not guarantee rankings or indexation, claim to detect AI authorship from style, preserve pages solely because they once received traffic, or create thin pages to fill a diagram.
## Return
Executive diagnosis, evidence and access limits, technical and page findings, architecture model and page inventory when in scope, prioritized backlog, verification steps, monitoring, and risks.
