SEO Reporter

Audit any URL for core SEO factors and get an actionable report with scores and recommendations.

When to Use

✅ USE this skill when:

• - "Audit the SEO of [URL]"
• "Check [URL] for SEO issues"
• "SEO report for [URL]"
• "Analyze page SEO"
• "What SEO improvements for [URL]?"

When NOT to Use

❌ DON'T use this skill when:

• - Full technical SEO crawl needed → use Screaming Frog, Ahrefs, or Semrush
• Page speed / Core Web Vitals → use PageSpeed Insights
• Backlink analysis → use Ahrefs/Moz
• Keyword research or content optimization → use dedicated SEO tools
• SSL/certificate checks → use sslscan or online checkers

Input

A single URL (must include protocol: https://).

CODEBLOCK0

Output

A markdown SEO audit report covering:

Factor	What It Checks
Title Tag	Presence, length (50-60 chars optimal), uniqueness
Meta Description

Presence, length (150-160 chars optimal), relevance |
| H1 Heading | Exactly one H1 present, content relevance |
| Heading Structure | H1→H2→H3 hierarchy, no missing levels, no multiple H1s |
| Canonical Tag | <link rel="canonical"> present and points to correct URL |
| Robots.txt | File exists, is accessible, and is not blocking important pages |
| Sitemap.xml | File exists, is accessible, and contains the audited URL |
| Open Graph Tags | OG title, description, and image present |
| Mobile Viewport | Viewport meta tag present |
| HTTPS | Page served over secure connection |

Each factor gets a score (Pass / Warning / Fail) and specific recommendations if issues are found.

Usage

Run the audit

CODEBLOCK1

Inline from agent

The agent should run audit.sh with the target URL and present the output as a formatted markdown report.

CODEBLOCK2

Report Format

CODEBLOCK3

Scoring Guide

Score	Meaning
10/10	Perfect — no issues
7-9/10

Good — minor improvements possible | | 4-6/10 | Warning — meaningful issue that should be fixed | | 0-3/10 | Fail — critical issue |

Tips

• - Always validate the URL has a protocol prefix (https://) before running
• The audit is non-destructive (read-only HTTP requests)
• Run from the skill directory so relative paths to helpers work
• For comparing two pages, run the audit on both and diff the scores