diagnose-seo_skill

Overview

This skill performs a structured diagnostic for technical SEO problems, focusing on crawlability, indexability, renderability, and on-page signals. It helps identify why pages aren’t being crawled or indexed and produces a prioritized fix list with concrete remediation steps. Use it when you suspect robots, canonical, sitemap, or rendering issues are harming search presence.

How this skill works

The diagnostic runs through four ordered layers: Crawlability (robots.txt, server responses, sitemaps, architecture), Indexability (meta robots, X-Robots-Tag, canonicalization, duplicates), Renderability (HTML vs. JS content, lazy-load, visibility), and Signals (titles, meta descriptions, headings, structured data). For each failing check it records severity, affected pages, and a concise fix. The output includes a summary of critical issues, warnings, and passed checks plus a prioritized remediation list.

When to use it

• Pages are not appearing in search results or dropping suddenly.
• Search Console shows crawl errors, blocked URLs, or indexing drops.
• You need to diagnose robots.txt or sitemap misconfigurations.
• Canonical tags or redirects may be causing duplicate-content or deindexing.
• Pages rely on JavaScript and may not render correctly for crawlers.

Best practices

• Diagnose in order: crawlability → indexability → renderability → signals.
• Start with robots.txt and sitemap validation before troubleshooting canonicals.
• Prefer server-side rendered or server-side hydrated content for critical SEO pages.
• Use self-referencing canonical tags and single canonical per page.
• Keep title and meta description unique and descriptive; validate structured data.

Example use cases

• A blog section suddenly returns ‘not indexed’ in Search Console after a deploy.
• An e-commerce site has duplicated product pages due to parameterized URLs.
• A single-page app shows content to users but isn’t indexed by Google.
• Sitemaps contain redirects and 404s, confusing crawlers and wasting budget.
• Robots.txt from staging was accidentally deployed and blocked the site.