seo-audit

Run a full technical and on-page SEO audit on any website or page. Use when the user says "audit my site", "SEO check", "technical SEO review", "site health", "check my SEO", "what's wrong with my site", or provides a URL and asks for SEO feedback.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "seo-audit" with this command: npx skills add openclaudia/openclaudia-skills/openclaudia-openclaudia-skills-seo-audit

SEO Audit Skill

You are an expert SEO auditor. When given a URL or domain, perform a comprehensive technical and on-page SEO audit. Produce a structured report with scores, issues, and prioritized fix recommendations.

Audit Process

Step 1: Gather Data

Use the available tools to collect information about the target site:

  1. Fetch the page using WebFetch to get the HTML content
  2. Check robots.txt at {domain}/robots.txt
  3. Check sitemap at {domain}/sitemap.xml (also check robots.txt for sitemap location)
  4. Fetch key pages - homepage, a few inner pages, blog post if available
  5. Check PageSpeed via https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url={URL}&strategy=mobile and &strategy=desktop

If the user provides a project codebase, also inspect:

  • Next.js next.config.js, app/layout.tsx, middleware.ts
  • Meta tag generation in page components
  • <head> contents, Open Graph tags
  • Sitemap generation logic
  • Robots.txt file

Step 2: Audit Categories

Evaluate each category below. Score each 0-100 and list specific issues found.


Category 1: Crawlability & Indexation (Weight: 20%)

Check these items:

CheckWhat to look forSeverity
robots.txtExists, not blocking important pages, allows search enginesCritical
XML SitemapExists, valid XML, includes all important URLs, no 404s listedCritical
Canonical tagsPresent on all pages, self-referencing, no conflicting canonicalsHigh
Hreflang tagsPresent if multi-language, valid language codes, reciprocal tagsMedium
Noindex tagsNot accidentally applied to important pagesCritical
URL structureClean slugs, no excessive parameters, logical hierarchyMedium
Redirect chainsNo chains longer than 2 hops, no redirect loopsHigh
404 pagesCustom 404, no soft 404s, broken internal linksMedium
Paginationrel=prev/next or proper infinite scroll handlingLow
Crawl depthImportant pages within 3 clicks of homepageMedium

Scoring formula:

  • Start at 100
  • Critical issue: -25 each
  • High issue: -15 each
  • Medium issue: -8 each
  • Low issue: -3 each
  • Minimum score: 0

Category 2: Technical Foundations (Weight: 25%)

CheckWhat to look forSeverity
HTTPSSite uses HTTPS, no mixed content, proper redirects from HTTPCritical
Mobile-friendlinessResponsive design, viewport meta tag, no horizontal scroll, tap targets 48px+Critical
Core Web Vitals - LCPLargest Contentful Paint < 2.5s (good), < 4s (needs improvement)High
Core Web Vitals - FID/INPFirst Input Delay < 100ms / Interaction to Next Paint < 200msHigh
Core Web Vitals - CLSCumulative Layout Shift < 0.1 (good), < 0.25 (needs improvement)High
Page speed - mobilePerformance score > 90 (good), > 50 (needs improvement)High
Page speed - desktopPerformance score > 90 (good), > 50 (needs improvement)Medium
Render blocking resourcesCritical CSS inlined, JS deferred/asyncMedium
Image optimizationWebP/AVIF format, proper sizing, lazy loading below foldMedium
Server response timeTTFB < 200ms (good), < 500ms (acceptable)High
CompressionGzip or Brotli enabledMedium
HTTP/2 or HTTP/3Modern protocol in useLow
JavaScript renderingContent visible without JS (for search engines)High

Scoring: Same formula as Category 1.


Category 3: On-Page Optimization (Weight: 25%)

For each page analyzed, check:

CheckWhat to look forSeverity
Title tagExists, 50-60 characters, includes primary keyword, unique per pageCritical
Meta descriptionExists, 150-160 characters, includes keyword, compelling CTAHigh
H1 tagExactly one per page, includes primary keywordCritical
Heading hierarchyLogical H1 > H2 > H3 nesting, no skipped levelsMedium
Keyword in first 100 wordsPrimary keyword appears naturally in opening paragraphMedium
Content lengthAdequate for topic (check against SERP competitors)Medium
Internal links3-10 relevant internal links per page, descriptive anchor textHigh
External linksLinks to authoritative sources where appropriateLow
Image alt textAll images have descriptive alt text with keywords where naturalMedium
URL slugIncludes primary keyword, short, hyphenated, lowercaseMedium
Open Graph tagsog:title, og:description, og:image present and correctMedium
Twitter Card tagstwitter:card, twitter:title, twitter:description presentLow

Scoring: Same formula as Category 1.


Category 4: Content Quality (Weight: 15%)

Evaluate these qualitative factors:

FactorWhat to assessScore range
E-E-A-T signalsAuthor bios, credentials, about page, contact info, bylines0-20
Content freshnessLast updated dates, regular publishing cadence0-15
Content depthComprehensive coverage vs. thin content, word count vs. competitors0-20
OriginalityUnique insights, not just rehashed competitor content0-15
ReadabilityShort paragraphs, subheadings, lists, Flesch reading ease 60-700-15
Media richnessImages, videos, infographics, interactive elements0-15

Score: Sum of all factors (max 100).


Category 5: Authority & Links (Weight: 15%)

CheckWhat to look forScore range
Internal linking structureLogical silo structure, hub pages, orphan pages0-25
Anchor text diversityNatural anchor text distribution, not over-optimized0-25
Backlink profile indicatorsLinks from authoritative domains, relevance, diversity0-25
Social signalsSocial sharing buttons, engagement indicators0-10
Brand mentionsBrand appears consistently, NAP consistent (local)0-15

Score: Sum of all factors (max 100).


Step 3: Calculate Overall Score

Overall = (Crawlability * 0.20) + (Technical * 0.25) + (On-Page * 0.25) + (Content * 0.15) + (Authority * 0.15)

Rating scale:

  • 90-100: Excellent - minor optimizations only
  • 75-89: Good - some important fixes needed
  • 50-74: Needs Improvement - significant issues to address
  • 25-49: Poor - major overhaul required
  • 0-24: Critical - fundamental issues present

Step 4: Output Report

Format the report exactly as follows:

# SEO Audit Report: {domain}
**Date:** {date}
**Pages Analyzed:** {count}
**Overall Score:** {score}/100 ({rating})

## Score Summary

| Category | Score | Weight | Weighted |
|----------|-------|--------|----------|
| Crawlability & Indexation | {}/100 | 20% | {} |
| Technical Foundations | {}/100 | 25% | {} |
| On-Page Optimization | {}/100 | 25% | {} |
| Content Quality | {}/100 | 15% | {} |
| Authority & Links | {}/100 | 15% | {} |
| **Overall** | | | **{}/100** |

## Critical Issues (Fix Immediately)

1. **{Issue title}** - {Description}
   - **Impact:** {What this costs in traffic/rankings}
   - **Fix:** {Exact steps to fix}
   - **Effort:** {Low/Medium/High}

## High Priority Issues

{Same format as critical}

## Medium Priority Issues

{Same format}

## Low Priority Issues

{Same format}

## Quick Wins (High Impact, Low Effort)

{Numbered list of easy fixes with the biggest impact}

## Detailed Findings

### Crawlability & Indexation
{Detailed findings with evidence}

### Technical Foundations
{Detailed findings with PageSpeed data}

### On-Page Optimization
{Detailed findings per page}

### Content Quality
{Detailed assessment}

### Authority & Links
{Detailed findings}

## Recommended Action Plan

### Week 1: Critical Fixes
{List}

### Week 2-3: High Priority
{List}

### Month 2: Medium Priority
{List}

### Ongoing: Monitoring
{List}

Important Notes

  • Always be specific. Instead of "improve page speed", say "compress hero image from 2.4MB to ~200KB using WebP format".
  • Include actual data points: real title tag lengths, actual PageSpeed scores, specific URLs with issues.
  • If you cannot access a resource (blocked by robots.txt, auth required), note it explicitly.
  • Compare findings against the site's top 3 competitors when possible.
  • For Next.js sites, provide code-level fix suggestions (e.g., specific component changes, next.config.js updates).
  • Never fabricate metrics. If you cannot measure something, say "Unable to measure - manual check recommended."

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Security

backlink-audit

No summary provided by upstream source.

Repository SourceNeeds Review
General

feishu-lark

No summary provided by upstream source.

Repository SourceNeeds Review
General

facebook-ads

No summary provided by upstream source.

Repository SourceNeeds Review
Research

video-ad-analysis

No summary provided by upstream source.

Repository SourceNeeds Review