Seo Audit
Run a structured technical and on-page SEO audit on your marketing site when organic traffic feels underwhelming and you need a prioritized fix list.
Overview
seo-audit is an agent skill for the Launch phase that runs a prioritized technical and on-page SEO audit and returns a structured report with an action plan.
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill seo-auditWhat is this skill?
- Checks for product-marketing.md context before auditing
- Clarifying questions on priority keywords, Search Console, recent changes, and competitors
- Priority order: Crawlability & Indexation → Technical → On-Page → Content → Authority & Links
- Robots.txt, XML sitemap, and site architecture review
- Audit report: Executive Summary, Technical/On-Page/Content findings, Prioritized Action Plan
- Audit priority order spans 5 layers: Crawlability & Indexation through Authority & Links
- Report structure includes Executive Summary plus Technical, On-Page, and Content finding sections
Adoption & trust: 131k installs on skills.sh; 32.4k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have steady but disappointing organic traffic and no clear, ordered list of what to fix on crawlability, technical SEO, and on-page content.
Who is it for?
Solo founders shipping a SaaS or content site who want agent-led SEO diagnosis before hiring an agency or rewriting every page.
Skip if: Pure paid acquisition, social distribution, or mobile app store optimization where search crawl rules differ.
When should I use this skill?
User asks for an SEO audit of their website, organic traffic feels low, or they need crawlability, technical, and on-page findings with a prioritized plan.
What do I get? / Deliverables
You get an executive summary, sectioned findings, and a prioritized action plan aligned to crawlability-first audit order—not a superficial keyword sprinkle list.
- SEO audit report with executive summary
- Technical, on-page, and content finding sections
- Prioritized action plan
Recommended Skills
Journey fit
Launch → seo is the canonical shelf because the skill delivers crawlability, indexation, on-page, and content findings aimed at getting found in search. Seo subphase matches the eval-driven framework: robots/sitemap, architecture, titles, metas, headings, and prioritized actions—not paid distribution or app-store ASO.
How it compares
Framework-driven site audit skill with report structure, not a one-shot meta-tag generator.
Common Questions / FAQ
Who is seo-audit for?
Solo and indie builders with a live marketing site—especially SaaS—who want systematic SEO findings instead of ad-hoc plugin scores.
When should I use seo-audit?
In Launch when you are optimizing for organic search: after a site is live, when traffic plateaus, before a content sprint, or when you need crawl/index fixes prioritized ahead of copy tweaks.
Is seo-audit safe to install?
Check the Security Audits panel on this Prism page; the skill may fetch your URLs and ask about Search Console—avoid pasting secrets into chat and review what the agent is allowed to access.
SKILL.md
READMESKILL.md - Seo Audit
{ "skill_name": "seo-audit", "evals": [ { "id": 1, "prompt": "Can you do an SEO audit of our SaaS website? We're getting about 2,000 organic visits/month but feel like we should be getting more. URL: https://example.com", "expected_output": "Should check for product-marketing.md first. Should ask clarifying questions about priority keywords, Search Console access, recent changes, and competitors. Should follow the audit framework priority order: Crawlability & Indexation, Technical Foundations, On-Page Optimization, Content Quality, Authority & Links. Should check robots.txt, XML sitemap, site architecture. Should evaluate title tags, meta descriptions, heading structure, and content optimization. Should NOT report on schema markup based solely on web_fetch (must note the detection limitation). Output should follow the Audit Report Structure: Executive Summary, Technical SEO Findings, On-Page SEO Findings, Content Findings, and Prioritized Action Plan.", "assertions": [ "Checks for product-marketing.md", "Asks clarifying questions about keywords, Search Console, recent changes", "Follows audit priority order: crawlability first, then technical, on-page, content, authority", "Checks robots.txt and XML sitemap", "Evaluates title tags, meta descriptions, heading structure", "Does NOT claim 'no schema found' based on web_fetch alone", "Notes schema markup detection limitation", "Output has Executive Summary", "Output has Prioritized Action Plan", "Each finding has Issue, Impact, Evidence, Fix, and Priority" ], "files": [] }, { "id": 2, "prompt": "Why am I not ranking for 'project management software'? We have a page targeting that keyword but it's stuck on page 3.", "expected_output": "Should trigger on the casual 'why am I not ranking' phrasing. Should investigate both on-page and off-page factors. On-page: check title tag, H1, URL alignment with keyword; evaluate content depth vs competitors; check for keyword cannibalization. Technical: check indexation status, canonical tags, crawlability. Content quality: assess E-E-A-T signals, content depth, user engagement. Should provide specific, actionable fixes organized by priority. Should mention competitive analysis against current top-ranking pages.", "assertions": [ "Triggers on casual 'why am I not ranking' phrasing", "Checks title tag, H1, URL alignment with target keyword", "Evaluates content depth vs competitors", "Checks for keyword cannibalization", "Checks indexation status and canonical tags", "Assesses E-E-A-T signals", "Mentions competitive analysis against top-ranking pages", "Provides actionable fixes organized by priority" ], "files": [] }, { "id": 3, "prompt": "We just migrated from WordPress to Next.js and our organic traffic dropped 40% in the last month. Help!", "expected_output": "Should treat this as an urgent migration diagnostic. Should immediately check: redirect mapping (301s from old URLs to new), canonical tags on new pages, robots.txt not blocking crawlers, XML sitemap submitted and updated, meta tags preserved. Should check for common migration issues: redirect chains/loops, soft 404s, lost internal links, changed URL structures without redirects. Should reference Search Console coverage report for indexation issues. Should provide a prioritized recovery plan with critical fixes first. Should mention monitoring timeline expectations (recovery can take weeks).", "assertions": [ "Treats as urgent migration diagnostic", "Checks redirect mapping (301s)", "Checks canonical tags on new pages", "Checks robots.txt not blocking crawlers", "Checks XML sitemap updated and submitted", "Checks for redirect chains or loops", "Checks for soft 404s",