What does SEO Audit check?

It fetches the page, analyzes title, meta description, OG and Twitter Card data, JSON-LD, canonical, sitemap and robots.txt, language, H1 count, favicon, and SERP positions, then returns a 0-100 score.

How is the score calculated?

Points are awarded per element on the defined checks, with a maximum of 100; alignment with best practices yields higher scores.

What if MCP tools are unavailable?

The audit falls back to Claude WebSearch/WebFetch or similar available tools to complete the checks.

Seo Audit

Verified

@fortunto2

npx machina-cli add skill @fortunto2/solo-seo-audit --openclaw

Files (1)

SKILL.md

5.2 KB

/seo-audit

SEO health check for any URL or project landing page. Fetches the page, analyzes meta tags, OG, JSON-LD, sitemap, robots.txt, checks SERP positions for target keywords, and outputs a scored report.

MCP Tools (use if available)

web_search(query, engines, include_raw_content) — SERP position check, competitor analysis
project_info(name) — get project URL if auditing by project name

If MCP tools are not available, use Claude WebSearch/WebFetch as fallback.

Steps

Parse target from $ARGUMENTS.
- If URL (starts with http): use directly.
- If project name: look up URL from project README, CLAUDE.md, or docs/prd.md.
- If empty: ask via AskUserQuestion — "Which URL or project to audit?"
Fetch the page via WebFetch. Extract:
- <title> tag (length check: 50-60 chars ideal)
- <meta name="description"> (length check: 150-160 chars ideal)
- Open Graph tags: og:title, og:description, og:image, og:url, og:type
- Twitter Card tags: twitter:card, twitter:title, twitter:image
- JSON-LD structured data (<script type="application/ld+json">)
- <link rel="canonical"> — canonical URL
- <html lang="..."> — language tag
- <link rel="alternate" hreflang="..."> — i18n tags
- Heading structure: H1 count (should be exactly 1), H2-H3 hierarchy
Check infrastructure files:
- Fetch {origin}/sitemap.xml — exists? Valid XML? Page count?
- Fetch {origin}/robots.txt — exists? Disallow rules? Sitemap reference?
- Fetch {origin}/favicon.ico — exists?
Forced reasoning — assess before scoring: Write out before proceeding:
- What's present: [list of found elements]
- What's missing: [list of absent elements]
- Critical issues: [anything that blocks indexing or sharing]
SERP position check — for 3-5 keywords:
- Extract keywords from page title + meta description + H1.
- For each keyword, search via MCP web_search(query="{keyword}") or WebSearch.
- Record: position of target URL in results (1-10, or "not found").
- Record: top 3 competitors for each keyword.

Score calculation (0-100):

Check	Max Points	Criteria
Title tag	10	Exists, 50-60 chars, contains primary keyword
Meta description	10	Exists, 150-160 chars, compelling
OG tags	10	og:title, og:description, og:image all present
JSON-LD	10	Valid structured data present
Canonical	5	Present and correct
Sitemap	10	Exists, valid, referenced in robots.txt
Robots.txt	5	Exists, no overly broad Disallow
H1 structure	5	Exactly one H1, descriptive
HTTPS	5	Site uses HTTPS
Mobile meta	5	Viewport tag present
Language	5	`lang` attribute on `<html>`
Favicon	5	Exists
SERP presence	15	Found in top 10 for target keywords

Write report to docs/seo-audit.md (in project context) or print to console:

# SEO Audit: {URL}

**Date:** {YYYY-MM-DD}
**Score:** {N}/100

## Summary
{2-3 sentence overview of SEO health}

## Checks

| Check | Status | Score | Details |
|-------|--------|-------|---------|
| Title | pass/fail | X/10 | "{actual title}" (N chars) |
| ... | ... | ... | ... |

## SERP Positions

| Keyword | Position | Top Competitors |
|---------|----------|----------------|
| {kw} | #N or N/A | competitor1, competitor2, competitor3 |

## Critical Issues
- {issue with fix recommendation}

## Recommendations (Top 3)
1. {highest impact fix}
2. {second priority}
3. {third priority}

Output summary — print score and top 3 recommendations.

Notes

Score is relative — 80+ is good for a landing page, 90+ is excellent
SERP checks are approximations (not real-time ranking data)
Run periodically after content changes or before launch

Common Issues

Page fetch fails

Cause: URL is behind authentication, CORS, or returns non-HTML. Fix: Ensure the URL is publicly accessible. For SPAs, check if content is server-rendered.

SERP positions show "not found"

Cause: Site is new or not indexed by search engines. Fix: This is expected for new sites. Submit sitemap to Google Search Console and re-audit in 2-4 weeks.

Low score despite good content

Cause: Missing infrastructure files (sitemap.xml, robots.txt, JSON-LD). Fix: These are the highest-impact fixes. Generate sitemap, add robots.txt with sitemap reference, and add JSON-LD structured data.

Source

git clone https://clawhub.ai/fortunto2/solo-seo-auditView on GitHub

Overview

SEO Audit analyzes a page's on-page signals and delivers a 0-100 score. It checks meta tags, OG/Twitter Card data, JSON-LD, sitemap, robots.txt, canonical URL, language tag, heading structure, and SERP positions to reveal indexing and sharing gaps.

How This Skill Works

It fetches the target URL, extracts title, meta description, OG/Twitter tags, JSON-LD, canonical URL, language, and heading data. It then checks sitemap.xml, robots.txt, favicon, and hreflang references, runs SERP checks for 3-5 keywords, and computes a 0-100 score with a detailed report.

When to Use It

When a user asks to check SEO for a specific URL or page
When you need an SEO health audit for a page or project landing page
When you want an SEO score (0-100) for a page
When you want to verify meta tags, OG/Twitter data, JSON-LD, and canonical tags
When performing SERP position checks for target keywords

Quick Start

Step 1: Provide the URL or project name to audit
Step 2: Run the audit to fetch and analyze page elements
Step 3: Review the 0-100 score report and fix high-priority issues

Best Practices

Confirm the exact URL or project name before starting the audit
Aim for the primary keyword to appear in the title and a compelling meta description
Ensure OG and Twitter Card data are complete and accurate
Validate JSON-LD data and ensure the canonical URL is correct
Check sitemap.xml and robots.txt references, plus language/hreflang signals

Example Use Cases

Audit a product landing page for a SaaS site to improve its SEO score
Review a blog post’s title, meta description, and OG data for social sharing
Verify JSON-LD markup for BreadcrumbList and FAQ on a help article
Check sitemap.xml presence and robots.txt correctness on a marketing site
Benchmark SERP positions for 3-5 keywords against top competitors

Frequently Asked Questions

Add this skill to your agents