
Diagnose Seo
- 2.1k installs
- 17 repo stars
- Updated February 27, 2026
- calm-north/seojuice-skills
diagnose-seo is a structured technical SEO troubleshooting skill across crawl, index, render, and signal layers.
About
The diagnose-seo skill applies a four-layer technical SEO diagnostic ordered by dependency: crawlability, indexability, renderability, and on-page signals. Crawlability checks robots.txt rules, XML sitemap health, site architecture depth, redirect chains, HTTPS enforcement, and server responses including soft 404s. Indexability reviews meta robots, X-Robots-Tag headers, canonical self-reference and conflicts, and duplicate URL sets across slashes, www, HTTP, and parameters. Renderability examines whether core content appears in raw HTML versus JavaScript-loaded views and flags lazy or login-gated content invisible to crawlers. Signals layer covers unique titles, meta descriptions, heading hierarchy, structured data validation, and hreflang reciprocity for multilingual sites. Output format summarizes critical issues, warnings, and passed checks with a findings table and prioritized fix list by impact. The skill defers Core Web Vitals speed work to audit-speed while focusing on crawl and index troubleshooting.
- Diagnoses in four ordered layers from crawlability through signals.
- Checks robots.txt, sitemaps, architecture, redirects, and HTTPS.
- Audits canonicals, noindex conflicts, and duplicate URL patterns.
- Validates JS rendering visibility and structured data readiness.
- Outputs a prioritized findings table with severity and fixes.
Diagnose Seo by the numbers
- 2,120 all-time installs (skills.sh)
- +5 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #277 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
diagnose-seo capabilities & compatibility
- Capabilities
- four layer crawl, index, render, and signals dia · robots.txt and xml sitemap inspection checklists · canonical and duplicate content conflict detecti · javascript rendering and content visibility chec · prioritized findings table and fix list output f
- Use cases
- seo · debugging · research
What diagnose-seo says it does
Technical SEO problems fall into four categories. Diagnose in this order
Check for conflicting signals: canonical says page A, but noindex is set
For Core Web Vitals and page speed, see audit-speed
npx skills add https://github.com/calm-north/seojuice-skills --skill diagnose-seoAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.1k |
|---|---|
| repo stars | ★ 17 |
| Security audit | 2 / 3 scanners passed |
| Last updated | February 27, 2026 |
| Repository | calm-north/seojuice-skills ↗ |
Why are my pages not being crawled or indexed correctly?
Diagnose crawl, indexation, canonical, sitemap, and rendering issues using a four-layer technical SEO framework.
Who is it for?
Sites with indexation drops, canonical errors, robots blocks, or JS rendering concerns.
Skip if: Skip for Core Web Vitals and page speed audits; use audit-speed instead.
When should I use this skill?
User mentions crawl issues, indexation problems, robots.txt, canonical errors, or sitemap failures.
What you get
A layered diagnosis with severity-ranked fixes for crawl, indexation, rendering, and on-page signal issues.
- Technical SEO diagnosis report
- Layer-specific remediation steps
By the numbers
- Skill version 1.0.0
- Diagnoses technical SEO across 4 ordered layers: crawl, indexation, canonicalization, and rendering
Files
Diagnose SEO
Structured diagnostic framework for crawl issues, canonicalization errors, indexation problems, and rendering failures.
Diagnostic Approach
Technical SEO problems fall into four categories. Diagnose in this order — each layer depends on the previous one working correctly:
1. Crawlability — Can search engines find and access the pages? 2. Indexability — Are the pages allowed to be indexed? 3. Renderability — Can search engines see the full content? 4. Signals — Are the right signals (titles, structured data, links) in place?
Layer 1: Crawlability
Check these in order:
robots.txt
- Fetch
[domain]/robots.txtand review the rules - Look for overly broad
Disallowrules blocking important paths - Verify
Sitemap:directive points to the correct sitemap URL - Check for different rules per user-agent (Googlebot vs others)
Common mistakes:
Disallow: /blocking the entire site (often left from staging)- Blocking CSS/JS files that Googlebot needs for rendering
- Blocking API or AJAX endpoints that load dynamic content
- Staging robots.txt accidentally deployed to production
XML Sitemap
- Fetch the sitemap URL(s) and check:
- Does it return 200? Is it valid XML?
- Does it list all important pages?
- Does it exclude pages that shouldn't be indexed (404s, redirects, noindex pages)?
- Are
<lastmod>dates accurate and recent? - For large sites: is there a sitemap index?
Site Architecture
- Pages should be reachable within 3 clicks from the homepage
- Check for orphan pages (no internal links pointing to them)
- Check for redirect chains (page A → B → C — should be A → C)
- Check for redirect loops
Server Response
- Do all important pages return HTTP 200?
- Check for unexpected 301/302 redirects
- Check for soft 404s (page returns 200 but shows "not found" content)
- Verify HTTPS is enforced (HTTP should 301 to HTTPS)
Layer 2: Indexability
Meta Robots / X-Robots-Tag
- Check for
<meta name="robots" content="noindex">on pages that should be indexed - Check HTTP headers for
X-Robots-Tag: noindex - Common cause: CMS accidentally applying noindex to pagination, tag pages, or new pages
Canonical Tags
- Every page should have a
<link rel="canonical">pointing to itself (self-referencing canonical) - Check for canonical tags pointing to wrong pages (common in paginated content, filtered URLs)
- Check for conflicting signals: canonical says page A, but noindex is set, or the page redirects
Canonical diagnosis checklist:
- [ ] Does the canonical URL match the actual URL?
- [ ] Is the canonical URL accessible (returns 200)?
- [ ] Does the canonical URL have the same content?
- [ ] Is there only one canonical tag on the page?
Duplicate Content
- Check for the same content accessible at multiple URLs:
- With and without trailing slash (
/pagevs/page/) - With and without
www(example.comvswww.example.com) - HTTP vs HTTPS
- URL parameters creating duplicate pages (
?sort=price,?page=1) - Each duplicate set needs one canonical URL; all others should redirect or use canonical tags
Layer 3: Renderability
JavaScript Rendering
- Does the page content appear in the raw HTML source? Or is it loaded via JavaScript?
- If JS-rendered: does Googlebot see the full content? (Use URL Inspection tool in Search Console)
- Check for content hidden behind click events, tabs, or accordions
- Check for lazy-loaded content that only appears on scroll
Core Content Visibility
- Is the main content in the initial HTML? Or loaded async after page load?
- Are important elements (titles, headings, product details) in the DOM on first render?
- Check for content that requires login or cookies to view
Layer 4: Signals
Title Tags
- Every page has a unique
<title> - Title includes the primary keyword
- Under 60 characters (to avoid truncation in SERPs)
- Descriptive and click-worthy
Meta Descriptions
- Every important page has a meta description
- 150-160 characters
- Includes target keyword and a value proposition
- Unique per page
Heading Structure
- One H1 per page containing the primary keyword
- Logical heading hierarchy (H1 → H2 → H3, no skips)
- Headings describe section content (not decorative)
Structured Data
- Check for JSON-LD structured data appropriate to the page type
- Validate with Google's Rich Results Test
- Common types: Article, Product, FAQ, HowTo, BreadcrumbList, Organization
Hreflang (multilingual sites)
- Check for correct
hreflangtags linking language variants - Verify reciprocal tags (page A points to B, B points back to A)
- Check for
x-defaulttag
Output Format
Technical SEO Diagnosis: [domain]
Summary
- Critical issues: [count]
- Warnings: [count]
- Passed checks: [count]
Findings by Layer
For each issue found:
| Layer | Issue | Severity | Affected Pages | Fix |
|---|---|---|---|---|
| Crawlability | robots.txt blocks /blog/ | Critical | All blog pages | Remove Disallow: /blog/ from robots.txt |
| Indexability | Missing canonical tags | Warning | 15 pages | Add self-referencing canonicals |
| ... | ... | ... | ... | ... |
Priority Fix List
Ordered by impact: 1. [Critical fix] — affects [n] pages, blocks [crawling/indexing/ranking] 2. [Warning fix] — affects [n] pages, reduces [signal quality] 3. ...
---
Pro Tip: Run the free SEO Audit for a quick
technical check, the Broken Link Checker
to find dead links, and the Robots.txt Generator
to fix crawl directives. SEOJuice MCP users can run /seojuice:site-health for a fulltechnical report and /seojuice:page-audit [domain] [url] to drill into specific pages.Related skills
How it compares
Pick diagnose-seo over audit-speed when pages are missing from the index, not when the problem is Core Web Vitals or load performance.
FAQ
What order should I diagnose technical SEO issues?
Start with crawlability, then indexability, renderability, and finally on-page signals.
How do I spot canonical problems?
Confirm self-referencing canonicals, accessible targets, matching content, and no conflicting noindex or redirects.
Does this skill cover page speed?
No. It focuses on crawl and index diagnostics; use audit-speed for Core Web Vitals.
Is Diagnose Seo safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.