seo-audit-report
Skill12 starsChanged 29 days agoMITView on GitHub
Full-site SEO / GEO / AEO / AIO audit for any website. Crawls up to N pages using Chrome TLS impersonation (bypasses Akamai/Cloudflare), runs a Screaming Frog-class check catalog across Technical, Content, Security, Social, GEO, and AIO pillars, and produces an executive-level PDF report plus CSV/JSON/Markdown data files. Suitable for client deliverables and CTO reviews.
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- younesbenallal/seo-skillstheir own version, first seen Aug 14, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- younesbenallal/seo-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- agent/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- router/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/verification.mdcCursor rule
- agentic-agileSkill
- agentic-portfolioSkill
- client-onboardingSkill
- cooldown-resumeSkill
- drillSkill
- ecc-harness-patternsSkill
- fabric-patternsSkill
- graphiti-temporalSkill
- managed-agents-dreamsSkill
- model-catalogue-updateSkill
- platform-setupSkill
- repowise-intelligenceSkill
- risky-module-reviewSkill
- user-researchSkill
- video-contextSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 49
Run a full SEO / GEO / AEO / AIO audit against any public website and produce an executive-level PDF report suitable for CTO or client …
- Very specific: line 65
All other parameters have sensible defaults.
- Distinctive: line 92
Before trusting results, spot-check the JSON:
- Distinctive: line 129
Verify bypass success: check the JSON as shown above.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: seo-audit-report
Purpose
Run a full SEO / GEO / AEO / AIO audit against any public website and produce an executive-level PDF report suitable for CTO or client delivery.
The crawl uses curl_cffi with Chrome 120 TLS impersonation to bypass bot-protection layers (Akamai, Cloudflare) that block plain httpx crawlers. Playwright browser mode is supported when system dependencies are available; curl_cffi is the reliable fallback.
Quick Start
python scripts/run_seo_audit.py \
--website-url https://www.example.com \
--output-dir ./seo-outputAll other parameters have sensible defaults. See --help for full options.
Parameters
| Parameter | Default | Description |
--website-url | required | Site to audit |
--max-pages | 100 | Crawl budget (pages) |
--max-depth | 3 | Link-follow depth |
--output-dir | ./seo-audit-output | Where to write files |
--monthly-organic-revenue | 0 | Revenue baseline for at-risk modelling |
--check-image-sizes | true | HEAD-request image sizes (slower) |
--no-check-image-sizes | — | Skip image size checks for speed |
Output Files
| File | Contents |
{domain}_seo_audit.pdf | Executive PDF report (cover, executive summary, pillar deep-dives, full findings, delegation plan, methodology) |
{domain}_report.json | Full machine-readable report (all pages, all issues, pillar scores) |
{domain}_report.md | Markdown version of the report |
{domain}_findings.csv | Summary CSV: one row per finding type with priority, URLs affected, how-to-fix |
{domain}_pages.csv | Per-page CSV: URL, status, title, H1, word count, issues found |
{domain}_issues.csv | Per-issue-instance CSV: URL × check_code × details |
Verify Bypass Quality
Before trusting results, spot-check the JSON:
import json
with open("seo-output/example.com_report.json") as f:
r = json.load(f)
pages = r["pages"]
# All should show status_code=200 and via="curl_cffi"
print({p["url"]: (p["status_code"], p.get("fetch_via","?")) for p in pages[:5]})Repeated 403s with small HTML bodies indicate the site is still blocking; report that plainly rather than fabricating findings.
How This Skill Works (Agent Instructions)
- Install dependencies (first run only):
cd autonomous-ai-agency python -m venv .venv && source .venv/bin/activate pip install -r requirements.txt # playwright install chromium # optional — curl_cffi is used as fallback - Run the audit:
Expect 3–20 minutes depending on site size and network. For large sites (500 pages) expect up to 90 minutes with browser mode.source .venv/bin/activate python scripts/run_seo_audit.py \ --website-url "{{ website_url }}" \ --max-pages {{ max_pages | default(100) }} \ --max-depth {{ max_depth | default(3) }} \ --output-dir "{{ output_dir | default('./seo-audit-output') }}" \ --monthly-organic-revenue {{ monthly_organic_revenue | default(0) }} - Verify bypass success: check the JSON as shown above.
- Present the PDF to the user and provide a 3–5 sentence summary:
- Overall health score and worst pillar
- Top 3 issues by strategic pressure
- Pages crawled vs pages genuinely bypassed vs still blocked
Revenue-at-Risk Disclaimer (load-bearing — always include in reports)
Revenue-at-risk figures use a saturating exponential model
share = 0.35 × (1 − e^(−pressure/50))applied to aggregate issue severity. They are model estimates of proportional organic revenue exposure, not measured losses. Leavemonthly_organic_revenue=0when the baseline is unknown; all figures will display as £0/month.
Troubleshooting
| Symptom | Cause | Fix |
| All pages return 403 | Bot wall not bypassed | curl_cffi should handle most; try increasing timeout_seconds |
libXdamage.so.1 error | Missing Playwright system libs | curl_cffi fallback activates automatically |
| Audit times out | Site too large / slow | Reduce --max-pages or --max-depth |
| Report has 0 pages | Crawl seeding failed | Check URL is correct and publicly reachable |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

