본문으로 건너뛰기
cccskills
무료GitHub에 공개

diagnose-seo

Structured diagnostic for technical SEO problems. Use when the user asks about crawl issues, indexation problems, why pages aren't being indexed, robots.txt questions, canonical errors, sitemap issues, rendering problems, or general technical SEO troubleshooting. For Core Web Vitals and page speed, see audit-speed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md6.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.txt and review the rules
  • Look for overly broad Disallow rules 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 (/page vs /page/)
    • With and without www (example.com vs www.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 hreflang tags linking language variants
  • Verify reciprocal tags (page A points to B, B points back to A)
  • Check for x-default tag

Output Format

Technical SEO Diagnosis: [domain]

Summary

  • Critical issues: [count]
  • Warnings: [count]
  • Passed checks: [count]

Findings by Layer

For each issue found:

LayerIssueSeverityAffected PagesFix
Crawlabilityrobots.txt blocks /blog/CriticalAll blog pagesRemove Disallow: /blog/ from robots.txt
IndexabilityMissing canonical tagsWarning15 pagesAdd 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 full technical report and /seojuice:page-audit [domain] [url] to drill into specific pages.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, chat applications, voice agents, or browser automation. Covers Agent class, state management, callable RPC, Workflows, durable execution, queues, retries, observability, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

galfrevn/apollo2392026년 8월 18일 업데이트

ai-seo

무료

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' or 'agent-readable site.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

galfrevn/apollo2392026년 8월 18일 업데이트

animate

무료

Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits. Writes the implementation. Use when asked to animate something, add motion, make a component feel alive, or build a transition. For critiquing existing motion use review-animations; for auditing a whole codebase use improve-animations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

galfrevn/apollo2392026년 8월 18일 업데이트

Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

galfrevn/apollo2392026년 8월 18일 업데이트

bun

무료

Use when building, running, testing, or bundling JavaScript/TypeScript applications. Reach for Bun when you need to execute scripts, manage dependencies, run tests, or bundle code for production. Bun is a drop-in replacement for Node.js with integrated package manager, test runner, and bundler.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

galfrevn/apollo2392026년 8월 18일 업데이트

Fallback reference for Cloudflare products that have no dedicated skill here — Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Prefer the focused skill when one fits: agents-sdk for the Agents SDK, durable-objects for Durable Objects, workers-best-practices for reviewing or authoring Worker code, wrangler for CLI commands, sandbox-sdk for sandboxed execution. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

galfrevn/apollo2392026년 8월 18일 업데이트

galfrevn의 스킬 모두 보기

이 스킬의 문제 신고