What this Skill helps with

Technical SEO Auditor turns supplied crawl and page evidence into a prioritized checklist covering crawl access, indexation, canonicals, sitemaps, hreflang, Core Web Vitals, status codes, and related technical signals. It keeps observed issues separate from checks that still need data.

Who this Skill is for

Use it for technical SEO practitioners, developers, agencies, and site owners preparing a health review, migration, indexation investigation, or release check. The page is more useful with exports and configuration files than with a URL alone.

What you provide

  • The site or affected URL set
  • Crawl exports and status codes
  • Search Console indexation information
  • robots.txt, sitemap, canonical, and hreflang data
  • Core Web Vitals or PageSpeed reports
  • Platform, rendering, migration, and release context

What it produces

  • A checklist grouped by technical area
  • Evidence, severity, confidence, and affected URLs
  • Crawlability and indexation issues
  • Canonical, hreflang, robots, and sitemap checks
  • Recommended owner and verification step
  • An ordered remediation plan

How the Skill works

The workflow checks access and indexation before secondary signals, because an inaccessible page cannot benefit from later changes. It compares declared canonicals, status codes, sitemap inclusion, and language targeting when those datasets are available. Each issue records what was observed and what still needs confirmation.

Installation and first use

  1. Download and add the Skill to Claude.
  2. Attach the crawl and Search Console evidence.
  3. Explain recent migrations, releases, or indexation changes.
  4. Ask for an evidence table before recommendations.
  5. Assign technical changes to an owner and test them safely.

Example workflow and expected output

Provide a crawl showing redirected sitemap URLs, conflicting canonicals, and pages blocked by robots.txt. The expected output orders crawl and indexation issues first, lists affected URLs, and gives a verification method for each proposed fix. It should not claim that a live configuration was checked when only an export was supplied.

Limits and review guidance

The Skill cannot replace a current crawl, server logs, rendered-page inspection, or Search Console evidence. Technical changes can remove pages from search or create redirect loops, so test them in staging and keep rollback instructions. Confirm final URLs and live responses after deployment.

Frequently asked questions

Can it audit a site from only the homepage URL?

It can create a preliminary checklist, but a meaningful audit needs crawl, indexation, and configuration evidence.

Does it make technical changes automatically?

No. It produces an ordered review. Developers or site administrators must approve and implement changes.

How are issues prioritized?

Priority should reflect user and search impact, affected URL count, confidence, effort, and the risk of making the change.