SEO Audit

What this skill does

SEO Audit skill performs comprehensive URL and site-section analysis covering crawlability, indexation signals, on-page elements, content quality and intent fit, internal linking, page experience, structured data, and competitive context for prioritized pages. It produces severity-ranked findings with fix guidance practitioners can hand to developers and content owners.

Unlike automated scan dumps, the audit interprets which issues actually block rankings or AI citability for your target queries given site type and business model.

Who it's for

SEO managers doing pre-launch or quarterly reviews, developers receiving ticket backlogs from consultants, and marketing leads evaluating agency audit deliverables. Run on new site migrations, replatforms, or after major template changes.

Works at single-URL granularity or representative samples for large sites.

Key workflows

Define scope: single URL, template type, or path prefix. Collect target keywords and competitor URLs. Audit technical access (robots, canonicals, hreflang if applicable), on-page alignment, content depth, UX blockers, schema presence, and link context.

Output prioritized issue list with effort estimates, owner tags (dev, content, SEO), and verification steps post-fix. Optional executive summary highlighting revenue-risk issues first.

Common questions

Teams ask audit versus Technical SEO skill overlap—SEO Audit is holistic page/site diagnosis; Technical SEO and AI Crawler Audit goes deeper on crawl infrastructure and bot access. Another question is JavaScript SEO; workflows note rendering-dependent findings.

Large ecommerce sites often audit category templates rather than every SKU page initially.

How to use in Metaflow

Provide URL(s), targets, and any GSC or crawl export context. Run audit pass, implement fixes, re-audit critical items. Compose client reports via Artifact Composer. Pair with On-Page Optimization for rewrite execution on priority URLs.

Sample-based audits for large sites prioritize template types by traffic and revenue contribution—category templates before blog tags. Issue tickets include acceptance criteria developers can test in staging, such as canonical self-reference validation or structured data rich result preview. Competitive SERP context explains when a page is technically sound but loses on content depth or link authority, redirecting effort appropriately. Post-migration audits compare redirect maps, index coverage trends, and ranking recovery timelines against realistic benchmarks.

Accessibility overlaps with SEO are noted where heading order, link text, and alt attributes affect both usability and crawl understanding. Log of historical audit regressions helps teams identify recurring dev-side mistakes—such as accidental noindex on new templates—so prevention checklists improve over time.

Rendered HTML versus raw source comparisons catch client-side SEO mistakes where tags exist only after JavaScript execution, affecting indexation and AI fetch reliability.

For broader context, see our roundup of marketing skills claude, and read Claude skills for SEO for related setup guidance.