Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from repo
Run a comprehensive SEO audit covering technical issues, on-page optimization, and content quality
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
SKILL.md
1---2name: seo-audit3description: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.4metadata:5version: 1.2.06---78# SEO Audit910You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.1112## Initial Assessment1314**Check for product marketing context first:**15If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.1617Before auditing, understand:18191. **Site Context**20- What type of site? (SaaS, e-commerce, blog, etc.)21- What's the primary business goal for SEO?22- What keywords/topics are priorities?23242. **Current State**25- Any known issues or concerns?26- Current organic traffic level?27- Recent changes or migrations?28293. **Scope**30- Full site audit or specific pages?31- Technical + on-page, or one focus area?32- Access to Search Console / analytics?3334---3536## Audit Framework3738### Schema Markup Detection Limitation3940**`web_fetch` and `curl` cannot reliably detect structured data / schema markup.**4142Many CMS plugins (AIOSEO, Yoast, RankMath) inject JSON-LD via client-side JavaScript — it won't appear in static HTML or `web_fetch` output (which strips `<script>` tags during conversion).4344**To accurately check for schema markup, use one of these methods:**451. **Browser tool** — render the page and run: `document.querySelectorAll('script[type="application/ld+json"]')`462. **Google Rich Results Test** — https://search.google.com/test/rich-results473. **Screaming Frog export** — if the client provides one, use it (SF renders JavaScript)4849Reporting "no schema found" based solely on `web_fetch` or `curl` leads to false audit findings — these tools can't see JS-injected schema.5051### Priority Order521. **Crawlability & Indexation** (can Google find and index it?)532. **Technical Foundations** (is the site fast and functional?)543. **On-Page Optimization** (is content optimized?)554. **Content Quality** (does it deserve to rank?)565. **Authority & Links** (does it have credibility?)5758---5960## Technical SEO Audit6162### Crawlability6364**Robots.txt**65- Check for unintentional blocks66- Verify important pages allowed67- Check sitemap reference6869**XML Sitemap**70- Exists and accessible71- Submitted to Search Console72- Contains only canonical, indexable URLs73- Updated regularly74- Proper formatting7576**Site Architecture**77- Important pages within 3 clicks of homepage78- Logical hierarchy79- Internal linking structure80- No orphan pages8182**Crawl Budget Issues** (for large sites)83- Parameterized URLs under control84- Faceted navigation handled properly85- Infinite scroll with pagination fallback86- Session IDs not in URLs8788### Indexation8990**Index Status**91- site:domain.com check92- Search Console coverage report93- Compare indexed vs. expected9495**Indexation Issues**96- Noindex tags on important pages97- Canonicals pointing wrong direction98- Redirect chains/loops99- Soft 404s100- Duplicate content without canonicals101102**Canonicalization**103- All pages have canonical tags104- Self-referencing canonicals on unique pages105- HTTP → HTTPS canonicals106- www vs. non-www consistency107- Trailing slash consistency108109### Site Speed & Core Web Vitals110111**Core Web Vitals**112- LCP (Largest Contentful Paint): < 2.5s113- INP (Interaction to Next Paint): < 200ms114- CLS (Cumulative Layout Shift): < 0.1115116**Speed Factors**117- Server response time (TTFB)118- Image optimization119- JavaScript execution120- CSS delivery121- Caching headers122- CDN usage123- Font loading124125**Tools**126- PageSpeed Insights127- WebPageTest128- Chrome DevTools129- Search Console Core Web Vitals report130131### Mobile-Friendliness132133- Responsive design (not separate m. site)134- Tap target sizes135- Viewport configured136- No horizontal scroll137- Same content as desktop138- Mobile-first indexing readiness139140### Security & HTTPS141142- HTTPS across entire site143- Valid SSL certificate144- No mixed content145- HTTP → HTTPS redirects146- HSTS header (bonus)147148### URL Structure149150- Readable, descriptive URLs151- Keywords in URLs where natural152- Consistent structure153- No unnecessary parameters154- Lowercase and hyphen-separated155156---157158## International SEO & Localization159160Check when the site serves multiple languages or regions. Misconfigurations can suppress indexing of entire locale variants or drag down site-wide quality signals. See [International SEO reference](references/international-seo.md) for evidence and source URLs.161162### Hreflang163164Three equivalent placement methods: HTML `<link>` in `<head>`, HTTP `Link` headers, XML sitemap `<xhtml:link>`. If using multiple, they must agree -- conflicting signals cause Google to drop that pair. For 10+ locales, prefer sitemap-based (no page weight, no per-request cost).165166**Check for:**167- Self-referencing entry on every page (page must include itself in the hreflang set)168- Reciprocal links (if A points to B, B must point back to A -- or both are ignored)169- Valid codes: ISO 639-1 language + optional ISO 3166-1 Alpha 2 region (e.g., `en`, `en-GB` -- never `en-UK`)170- `x-default` present, pointing to fallback page (language selector or default locale)171- All target URLs return 200, are indexable, and match their canonical URL172- No duplicate language-region codes pointing to different URLs173174**Common errors:** Missing self-referencing entry (all hreflang ignored). No return tag / one-directional (pair dropped). Invalid codes like `en-UK` (use `en-GB`). Hreflang target is non-canonical, 404, or blocked (cluster discarded). HTML and sitemap annotations disagree (conflicting pair dropped).175176**At scale:** `<xhtml:link>` children don't count toward 50K URL sitemap limit, but the 50MB file size limit becomes the bottleneck (plan 2K-5K URLs per file with full hreflang). Focus hreflang on pages receiving wrong-language traffic -- not required on every page. For Bing: supplement with `<html lang>` and `<meta http-equiv="content-language">` (Bing treats hreflang as a weak signal).177178### Canonicalization for Multilingual Sites179180- Each locale page must self-canonical (e.g., `/ar/page` canonicals to `/ar/page`)181- Never cross-locale canonical (French to English) -- suppresses the non-canonical locale entirely182- Canonical URL must appear in the hreflang set -- if not, all hreflang is ignored183- Canonical overrides hreflang when they conflict184- Protocol/domain must be consistent across canonical, hreflang, and sitemap (`https` + same domain variant)185- Paginated locale pages: self-referencing canonical per page (never canonical page 2+ to page 1)186187**Common mistakes:** all locales canonical to English (kills indexing), canonical URL not in hreflang set (silently ignored), protocol mismatch between canonical and hreflang, CMS setting deep page canonical to homepage.188189### International Sitemaps190191**Check for:**192- `xmlns:xhtml` namespace on `<urlset>`, each `<url>` includes `<xhtml:link>` for all locales including itself193- `x-default` alternate included; all URLs absolute (full protocol + domain)194- Sitemap index in Search Console and robots.txt; split by content type, not by locale195196**Next.js caveat:** `alternates.languages` does NOT auto-include a self-referencing `<xhtml:link>` for the `<loc>` URL -- you must add the current locale explicitly.197198### Locale URL Structure199200**Recommended:** Subdirectories (`/en/`, `/ar/`). **Acceptable:** Subdomains or ccTLDs. **Not recommended:** URL parameters (`?lang=en`).201202**Check for:**203- Consistent locale prefix strategy; all locales prefixed (hiding locale from URLs prevents Google from distinguishing versions)204- Root URL handled as `x-default` with redirect, or serves default locale content205- No IP/Accept-Language content negotiation (Googlebot: US IPs, no Accept-Language header)206- Trailing slash + case consistency across locale paths, canonicals, hreflang, and sitemaps207- 301 redirects from non-canonical format to canonical208209**Note:** Google's International Targeting report in Search Console is deprecated. Geotargeting relies on hreflang, content signals, and linking patterns.210211### Content Quality Across Locales212213**Translation quality:**214- AI-translated content is not inherently spam (Google's 2025 stance), but scaled low-value translations can trigger scaled content abuse policy215- Google uses visible content to determine language -- translate ALL page content (title, description, headings, body), not just boilerplate216- Translating only template/nav while main content stays in original language creates duplicates217218**Thin locale pages:**219- Helpful content system is site-wide -- many thin locale pages can suppress rankings for strong pages too220- Don't noindex thin locales (wastes crawl budget) or cross-locale canonical (conflicts with hreflang)221- Best approach: don't create locale pages you cannot make genuinely helpful222223**Check for:**224- All locale pages have fully translated main content (not just UI chrome)225- No near-identical content across locales ("Duplicate, Google chose different canonical" in GSC)226- Hreflang only for locales with genuine content and search demand227- Localized signals: currency, phone format, addresses where applicable228- Broken hreflang links (404s, redirects) waste crawl budget AND invalidate hreflang clusters229230---231232## On-Page SEO Audit233234### Title Tags235236**Check for:**237- Unique titles for each page238- Primary keyword near beginning239- 50-60 characters (visible in SERP)240- Compelling and click-worthy241- Brand name placement (end, usually)242243**Common issues:**244- Duplicate titles245- Too long (truncated)246- Too short (wasted opportunity)247- Keyword stuffing248- Missing entirely249250### Meta Descriptions251252**Check for:**253- Unique descriptions per page254- 150-160 characters255- Includes primary keyword256- Clear value proposition257- Call to action258259**Common issues:**260- Duplicate descriptions261- Auto-generated garbage262- Too long/short263- No compelling reason to click264265### Heading Structure266267**Check for:**268- One H1 per page269- H1 contains primary keyword270- Logical hierarchy (H1 → H2 → H3)271- Headings describe content272- Not just for styling273274**Common issues:**275- Multiple H1s276- Skip levels (H1 → H3)277- Headings used for styling only278- No H1 on page279280### Content Optimization281282**Primary Page Content**283- Keyword in first 100 words284- Related keywords naturally used285- Sufficient depth/length for topic286- Answers search intent287- Better than competitors288289**Thin Content Issues**290- Pages with little unique content291- Tag/category pages with no value292- Doorway pages293- Duplicate or near-duplicate content294295### Image Optimization296297**Check for:**298- Descriptive file names299- Alt text on all images300- Alt text describes image301- Compressed file sizes302- Modern formats (WebP)303- Lazy loading implemented304- Responsive images305306### Internal Linking307308**Check for:**309- Important pages well-linked310- Descriptive anchor text311- Logical link relationships312- No broken internal links313- Reasonable link count per page314315**Common issues:**316- Orphan pages (no internal links)317- Over-optimized anchor text318- Important pages buried319- Excessive footer/sidebar links320321### Keyword Targeting322323**Per Page**324- Clear primary keyword target325- Title, H1, URL aligned326- Content satisfies search intent327- Not competing with other pages (cannibalization)328329**Site-Wide**330- Keyword mapping document331- No major gaps in coverage332- No keyword cannibalization333- Logical topical clusters334335---336337## Content Quality Assessment338339### E-E-A-T Signals340341**Experience**342- First-hand experience demonstrated343- Original insights/data344- Real examples and case studies345346**Expertise**347- Author credentials visible348- Accurate, detailed information349- Properly sourced claims350351**Authoritativeness**352- Recognized in the space353- Cited by others354- Industry credentials355356**Trustworthiness**357- Accurate information358- Transparent about business359- Contact information available360- Privacy policy, terms361- Secure site (HTTPS)362363### Content Depth364365- Comprehensive coverage of topic366- Answers follow-up questions367- Better than top-ranking competitors368- Updated and current369370### User Engagement Signals371372- Time on page373- Bounce rate in context374- Pages per session375- Return visits376377---378379## Common Issues by Site Type380381### SaaS/Product Sites382- Product pages lack content depth383- Blog not integrated with product pages384- Missing comparison/alternative pages385- Feature pages thin on content386- No glossary/educational content387388### E-commerce389- Thin category pages390- Duplicate product descriptions391- Missing product schema392- Faceted navigation creating duplicates393- Out-of-stock pages mishandled394395### Content/Blog Sites396- Outdated content not refreshed397- Keyword cannibalization398- No topical clustering399- Poor internal linking400- Missing author pages401402### Multilingual / Multi-Regional Sites403- Hreflang errors (missing return tags, invalid codes, no self-reference)404- Canonical conflicting with hreflang (cross-locale canonical suppresses indexing)405- Thin locale pages dragging down site-wide quality signal406- Only boilerplate translated, main content identical across locales407- No x-default fallback declared408- Sitemap missing hreflang alternates or missing reciprocal entries409- IP-based redirects hiding content from Googlebot410- Framework locale mode hiding locale from URLs411412### Local Business413- Inconsistent NAP414- Missing local schema415- No Google Business Profile optimization416- Missing location pages417- No local content418419---420421## Output Format422423### Audit Report Structure424425**Executive Summary**426- Overall health assessment427- Top 3-5 priority issues428- Quick wins identified429430**Technical SEO Findings**431For each issue:432- **Issue**: What's wrong433- **Impact**: SEO impact (High/Medium/Low)434- **Evidence**: How you found it435- **Fix**: Specific recommendation436- **Priority**: 1-5 or High/Medium/Low437438**On-Page SEO Findings**439Same format as above440441**Content Findings**442Same format as above443444**Prioritized Action Plan**4451. Critical fixes (blocking indexation/ranking)4462. High-impact improvements4473. Quick wins (easy, immediate benefit)4484. Long-term recommendations449450---451452## References453454- [AI Writing Detection](references/ai-writing-detection.md): Common AI writing patterns to avoid (em dashes, overused phrases, filler words)455- [International SEO](references/international-seo.md): Evidence and sources for hreflang, canonical + i18n, sitemaps, URL structure, and content quality across locales456- For AI search optimization (AEO, GEO, LLMO, AI Overviews), see the **ai-seo** skill457458---459460## Tools Referenced461462**Free Tools**463- Google Search Console (essential)464- Google PageSpeed Insights465- Bing Webmaster Tools466- Rich Results Test (**use this for schema validation — it renders JavaScript**)467- Mobile-Friendly Test468- Schema Validator469470> **Note on schema detection:** `web_fetch` strips `<script>` tags (including JSON-LD) and cannot detect JS-injected schema. Use the browser tool, Rich Results Test, or Screaming Frog instead — they render JavaScript and capture dynamically-injected markup. See the Schema Markup Detection Limitation section above.471472**Paid Tools** (if available)473- Screaming Frog474- Ahrefs / Semrush475- Sitebulb476- ContentKing477478---479480## Task-Specific Questions4814821. What pages/keywords matter most?4832. Do you have Search Console access?4843. Any recent changes or migrations?4854. Who are your top organic competitors?4865. What's your current organic traffic baseline?487488---489490## Related Skills491492- **ai-seo**: For optimizing content for AI search engines (AEO, GEO, LLMO)493- **programmatic-seo**: For building SEO pages at scale494- **site-architecture**: For page hierarchy, navigation design, and URL structure495- **schema-markup**: For implementing structured data496- **page-cro**: For optimizing pages for conversion (not just ranking)497- **analytics-tracking**: For measuring SEO performance498