| name | seobeast-audit |
| description | Full-site SEO audit for any URL. Spawns 6 parallel subagents covering technical SEO, content quality, performance, security, structured data, and AEO (AI engine readiness). Returns a composite 0–100 score with prioritized issues. No API keys required. Triggers on: "seo audit", "seobeast-audit", "audit my site", "check seo", "technical seo check".
|
| user-invokable | true |
| argument-hint | <url> |
seobeast-audit
Full-site SEO audit via 6 parallel specialist subagents. Runs on any public URL with no setup.
Usage
/seobeast-audit https://example.com
Orchestration
When invoked with a URL, execute this sequence:
Step 1 — Prefetch shared data (do this once, before spawning subagents)
Use WebFetch to retrieve:
- The page HTML at
<url>
<origin>/robots.txt<origin>/llms.txt
Pass this prefetched data to all subagents to avoid duplicate fetches.
Step 2 — Spawn 6 subagents in parallel using the Task tool
Each subagent receives:
- The URL to audit
- The prefetched HTML, robots.txt content, and llms.txt content
- A specific domain to focus on (defined in agents/*.md)
Subagents:
seo-technical — Crawlability, indexability, URL structure, canonical, redirects, robots.txtseo-content — Word count, H1/H2 usage, E-E-A-T signals, thin content, readabilityseo-performance — Render-blocking resources, lazy loading, image dimensions, CWV hintsseo-security — HTTPS, HSTS, CSP, X-Frame-Options, security headersseo-schema — JSON-LD detection, Organization schema, Article/Product schema, breadcrumbsseo-aeo — AI crawler access (GPTBot, ClaudeBot, PerplexityBot), llms.txt, passage citability
Step 3 — Aggregate results and output the unified report
Output Format
After all subagents complete, output exactly this format:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
seobeast-audit · <url>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Score: <N>/100 [████████░░░░░░░░░░░░] Grade: <A/B/C/D/F>
Technical SEO [████████░░] <score>/100 <N> issues
Content [███████░░░] <score>/100 <N> issues
Performance [█████░░░░░] <score>/100 <N> issues
Security [████████░░] <score>/100 <N> issues
Structured Data [███░░░░░░░] <score>/100 <N> issues
AEO [██░░░░░░░░] <score>/100 <N> issues
── Critical ─────────────────────────────────────────
✗ <issue title> (<category>)
...
── High Priority ────────────────────────────────────
⚠ <issue title> (<category>)
...
── Medium Priority ──────────────────────────────────
⚠ <issue title> (<category>)
...
── Passing ──────────────────────────────────────────
✓ <brief summary of what's working>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
seobeast-audit · seobeast.co
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Score Bar Rendering
Use Unicode block characters for the score bars:
█ for filled segments░ for empty segments- 10 segments total per bar
- Filled = round(score / 10)
Overall score bar is 20 segments wide.
Priority Definitions
-
Critical: Blocks indexing, causes penalties, or directly harms rankings. Fix immediately.
- meta noindex on a non-staging page
- robots.txt blocking all crawlers
- GPTBot blocked in robots.txt
- No HTTPS (HTTP page)
- No H1 tag
- No title tag
-
High: Significant ranking or visibility impact. Fix within 1 week.
- Missing meta description
- Missing og:image
- No JSON-LD structured data
- Render-blocking scripts (>3)
- Images missing alt text (>30%)
-
Medium: Optimization opportunities. Fix within 1 month.
- Missing llms.txt
- Missing HSTS header
- Title too long or too short
- No sitemap referenced
- Missing author attribution
Scoring Methodology
Calculate a composite 0–100 score using these category weights:
| Category | Weight |
|---|
| Core SEO | 14% |
| Performance | 12% |
| Content | 10% |
| Technical SEO | 7% |
| Crawlability | 7% |
| Links | 6% |
| Security | 6% |
| Structured Data | 6% |
| AEO Readiness | 5% |
| Images | 5% |
| E-E-A-T | 5% |
| Social | 3% |
| Mobile | 3% |
| Accessibility | 3% |
| URL Structure | 2% |
| Redirects | 2% |
| JavaScript | 1% |
| Internationalization | 1% |
| HTML Validation | 1% |
| Legal | 1% |
Error Handling
| Scenario | Action |
|---|
| URL unreachable | Report error, do not guess content |
| robots.txt returns 404 | Note it, continue audit without robots data |
| Subagent fails | Report partial results, flag the failed domain |
| Non-HTML response | Report content type, skip HTML-dependent checks |
AEO Section Notes
The AEO (AI Engine Optimization) section is a first-class audit pillar:
- Check
robots.txt for GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, OAI-SearchBot
- Check for
/llms.txt presence and basic structure (H1 title + ## sections)
- Evaluate whether content paragraphs are 80–200 words (optimal for AI citation)
- Check if sections begin with direct answers (not "In this article, we will...")
- Flag SSR vs CSR: pages requiring JS execution may be invisible to AI crawlers
CWV Reference (2026)
Current thresholds per Google:
- LCP: Good <2.5s, Needs Improvement 2.5–4s, Poor >4s
- INP: Good <200ms, Needs Improvement 200–500ms, Poor >500ms (replaced FID March 2024)
- CLS: Good <0.1, Needs Improvement 0.1–0.25, Poor >0.25
Do not reference FID. INP is the sole interactivity metric. FID was removed from all Google tools in September 2024.
Schema Notes
- FAQPage schema: Google removed rich results for commercial sites in August 2023. Retain existing FAQPage for LLM citation benefit only. Do not recommend adding new FAQPage for commercial sites.
- HowTo schema: Deprecated by Google in September 2023. Never recommend.
- FAQ and HowTo rich results still exist for government and healthcare sites only.
