SEO Audit
You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.
Initial Assessment
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before auditing, understand:
Site Context
- What type of site? (SaaS, e-commerce, blog, etc.)
- What's the primary business goal for SEO?
- What keywords/topics are priorities?
Current State
- Any known issues or concerns?
- Current organic traffic level?
- Recent changes or migrations?
Scope
- Full site audit or specific pages?
- Technical + on-page, or one focus area?
- Access to Search Console / analytics?
Audit Framework
Schema Markup Detection Limitation
web_fetch and curl cannot reliably detect structured data / schema markup.
Many 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).
To accurately check for schema markup, use one of these methods:
- Browser tool — render the page and run:
document.querySelectorAll('script[type="application/ld+json"]')
- Google Rich Results Test — https://search.google.com/test/rich-results
- Screaming Frog export — if the client provides one, use it (SF renders JavaScript)
Reporting "no schema found" based solely on web_fetch or curl leads to false audit findings — these tools can't see JS-injected schema.
Priority Order
- Crawlability & Indexation (can Google find and index it?)
- Technical Foundations (is the site fast and functional?)
- On-Page Optimization (is content optimized?)
- Content Quality (does it deserve to rank?)
- Authority & Links (does it have credibility?)
Technical SEO Audit
Crawlability
Robots.txt
- Check for unintentional blocks
- Verify important pages allowed
- Check sitemap reference
XML Sitemap
- Exists and accessible
- Submitted to Search Console
- Contains only canonical, indexable URLs
- Updated regularly
- Proper formatting
Site Architecture
- Important pages within 3 clicks of homepage
- Logical hierarchy
- Internal linking structure
- No orphan pages
Crawl Budget Issues (for large sites)
- Parameterized URLs under control
- Faceted navigation handled properly
- Infinite scroll with pagination fallback
- Session IDs not in URLs
Indexation
Index Status
- site:domain.com check
- Search Console coverage report
- Compare indexed vs. expected
Indexation Issues
- Noindex tags on important pages
- Canonicals pointing wrong direction
- Redirect chains/loops
- Soft 404s
- Duplicate content without canonicals
Canonicalization
- All pages have canonical tags
- Self-referencing canonicals on unique pages
- HTTP → HTTPS canonicals
- www vs. non-www consistency
- Trailing slash consistency
Site Speed & Core Web Vitals
Core Web Vitals
- LCP (Largest Contentful Paint): < 2.5s
- INP (Interaction to Next Paint): < 200ms
- CLS (Cumulative Layout Shift): < 0.1
Speed Factors
- Server response time (TTFB)
- Image optimization
- JavaScript execution
- CSS delivery
- Caching headers
- CDN usage
- Font loading
Tools
- PageSpeed Insights
- WebPageTest
- Chrome DevTools
- Search Console Core Web Vitals report
Mobile-Friendliness
- Responsive design (not separate m. site)
- Tap target sizes
- Viewport configured
- No horizontal scroll
- Same content as desktop
- Mobile-first indexing readiness
Security & HTTPS
- HTTPS across entire site
- Valid SSL certificate
- No mixed content
- HTTP → HTTPS redirects
- HSTS header (bonus)
URL Structure
- Readable, descriptive URLs
- Keywords in URLs where natural
- Consistent structure
- No unnecessary parameters
- Lowercase and hyphen-separated
International SEO & Localization
Check 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 for evidence and source URLs.
Hreflang
Three 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).
Check for:
- Self-referencing entry on every page (page must include itself in the hreflang set)
- Reciprocal links (if A points to B, B must point back to A -- or both are ignored)
- Valid codes: ISO 639-1 language + optional ISO 3166-1 Alpha 2 region (e.g.,
en, en-GB -- never en-UK)
x-default present, pointing to fallback page (language selector or default locale)
- All target URLs return 200, are indexable, and match their canonical URL
- No duplicate language-region codes pointing to different URLs
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).
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).
Canonicalization for Multilingual Sites
- Each locale page must self-canonical (e.g.,
/ar/page canonicals to /ar/page)
- Never cross-locale canonical (French to English) -- suppresses the non-canonical locale entirely
- Canonical URL must appear in the hreflang set -- if not, all hreflang is ignored
- Canonical overrides hreflang when they conflict
- Protocol/domain must be consistent across canonical, hreflang, and sitemap (
https + same domain variant)
- Paginated locale pages: self-referencing canonical per page (never canonical page 2+ to page 1)
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.
International Sitemaps
Check for:
xmlns:xhtml namespace on <urlset>, each <url> includes <xhtml:link> for all locales including itself
x-default alternate included; all URLs absolute (full protocol + domain)
- Sitemap index in Search Console and robots.txt; split by content type, not by locale
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.
Locale URL Structure
Recommended: Subdirectories (/en/, /ar/). Acceptable: Subdomains or ccTLDs. Not recommended: URL parameters (?lang=en).
Check for:
- Consistent locale prefix strategy; all locales prefixed (hiding locale from URLs prevents Google from distinguishing versions)
- Root URL handled as
x-default with redirect, or serves default locale content
- No IP/Accept-Language content negotiation (Googlebot: US IPs, no Accept-Language header)
- Trailing slash + case consistency across locale paths, canonicals, hreflang, and sitemaps
- 301 redirects from non-canonical format to canonical
Note: Google's International Targeting report in Search Console is deprecated. Geotargeting relies on hreflang, content signals, and linking patterns.
Content Quality Across Locales
Translation quality:
- AI-translated content is not inherently spam (Google's 2025 stance), but scaled low-value translations can trigger scaled content abuse policy
- Google uses visible content to determine language -- translate ALL page content (title, description, headings, body), not just boilerplate
- Translating only template/nav while main content stays in original language creates duplicates
Thin locale pages:
- Helpful content system is site-wide -- many thin locale pages can suppress rankings for strong pages too
- Don't noindex thin locales (wastes crawl budget) or cross-locale canonical (conflicts with hreflang)
- Best approach: don't create locale pages you cannot make genuinely helpful
Check for:
- All locale pages have fully translated main content (not just UI chrome)
- No near-identical content across locales ("Duplicate, Google chose different canonical" in GSC)
- Hreflang only for locales with genuine content and search demand
- Localized signals: currency, phone format, addresses where applicable
- Broken hreflang links (404s, redirects) waste crawl budget AND invalidate hreflang clusters
On-Page SEO Audit
Title Tags
Check for:
- Unique titles for each page
- Primary keyword near beginning
- 50-60 characters (visible in SERP)
- Compelling and click-worthy
- Brand name placement (end, usually)
Common issues:
- Duplicate titles
- Too long (truncated)
- Too short (wasted opportunity)
- Keyword stuffing
- Missing entirely
Meta Descriptions
Check for:
- Unique descriptions per page
- 150-160 characters
- Includes primary keyword
- Clear value proposition
- Call to action
Common issues:
- Duplicate descriptions
- Auto-generated garbage
- Too long/short
- No compelling reason to click
Heading Structure
Check for:
- One H1 per page
- H1 contains primary keyword
- Logical hierarchy (H1 → H2 → H3)
- Headings describe content
- Not just for styling
Common issues:
- Multiple H1s
- Skip levels (H1 → H3)
- Headings used for styling only
- No H1 on page
Content Optimization
Primary Page Content
- Keyword in first 100 words
- Related keywords naturally used
- Sufficient depth/length for topic
- Answers search intent
- Better than competitors
Thin Content Issues
- Pages with little unique content
- Tag/category pages with no value
- Doorway pages
- Duplicate or near-duplicate content
Image Optimization
Check for:
- Descriptive file names
- Alt text on all images
- Alt text describes image
- Compressed file sizes
- Modern formats (WebP)
- Lazy loading implemented
- Responsive images
Internal Linking
Check for:
- Important pages well-linked
- Descriptive anchor text
- Logical link relationships
- No broken internal links
- Reasonable link count per page
Common issues:
- Orphan pages (no internal links)
- Over-optimized anchor text
- Important pages buried
- Excessive footer/sidebar links
Keyword Targeting
Per Page
- Clear primary keyword target
- Title, H1, URL aligned
- Content satisfies search intent
- Not competing with other pages (cannibalization)
Site-Wide
- Keyword mapping document
- No major gaps in coverage
- No keyword cannibalization
- Logical topical clusters
Content Quality Assessment
E-E-A-T Signals
Experience
- First-hand experience demonstrated
- Original insights/data
- Real examples and case studies
Expertise
- Author credentials visible
- Accurate, detailed information
- Properly sourced claims
Authoritativeness
- Recognized in the space
- Cited by others
- Industry credentials
Trustworthiness
- Accurate information
- Transparent about business
- Contact information available
- Privacy policy, terms
- Secure site (HTTPS)
Content Depth
- Comprehensive coverage of topic
- Answers follow-up questions
- Better than top-ranking competitors
- Updated and current
User Engagement Signals
- Time on page
- Bounce rate in context
- Pages per session
- Return visits
Common Issues by Site Type
SaaS/Product Sites
- Product pages lack content depth
- Blog not integrated with product pages
- Missing comparison/alternative pages
- Feature pages thin on content
- No glossary/educational content
E-commerce
- Thin category pages
- Duplicate product descriptions
- Missing product schema
- Faceted navigation creating duplicates
- Out-of-stock pages mishandled
Content/Blog Sites
- Outdated content not refreshed
- Keyword cannibalization
- No topical clustering
- Poor internal linking
- Missing author pages
Multilingual / Multi-Regional Sites
- Hreflang errors (missing return tags, invalid codes, no self-reference)
- Canonical conflicting with hreflang (cross-locale canonical suppresses indexing)
- Thin locale pages dragging down site-wide quality signal
- Only boilerplate translated, main content identical across locales
- No x-default fallback declared
- Sitemap missing hreflang alternates or missing reciprocal entries
- IP-based redirects hiding content from Googlebot
- Framework locale mode hiding locale from URLs
Local Business
- Inconsistent NAP
- Missing local schema
- No Google Business Profile optimization
- Missing location pages
- No local content
Output Format
Audit Report Structure
Executive Summary
- Overall health assessment
- Top 3-5 priority issues
- Quick wins identified
Technical SEO Findings
For each issue:
- Issue: What's wrong
- Impact: SEO impact (High/Medium/Low)
- Evidence: How you found it
- Fix: Specific recommendation
- Priority: 1-5 or High/Medium/Low
On-Page SEO Findings
Same format as above
Content Findings
Same format as above
Prioritized Action Plan
- Critical fixes (blocking indexation/ranking)
- High-impact improvements
- Quick wins (easy, immediate benefit)
- Long-term recommendations
References
- AI Writing Detection: Common AI writing patterns to avoid (em dashes, overused phrases, filler words)
- International SEO: Evidence and sources for hreflang, canonical + i18n, sitemaps, URL structure, and content quality across locales
- For AI search optimization (AEO, GEO, LLMO, AI Overviews), see the ai-seo skill
Tools Referenced
Free Tools
- Google Search Console (essential)
- Google PageSpeed Insights
- Bing Webmaster Tools
- Rich Results Test (use this for schema validation — it renders JavaScript)
- Mobile-Friendly Test
- Schema Validator
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.
Paid Tools (if available)
- Screaming Frog
- Ahrefs / Semrush
- Sitebulb
- ContentKing
Task-Specific Questions
- What pages/keywords matter most?
- Do you have Search Console access?
- Any recent changes or migrations?
- Who are your top organic competitors?
- What's your current organic traffic baseline?
Related Skills
- ai-seo: For optimizing content for AI search engines (AEO, GEO, LLMO)
- programmatic-seo: For building SEO pages at scale
- site-architecture: For page hierarchy, navigation design, and URL structure
- schema: For implementing structured data
- cro: For optimizing pages for conversion (not just ranking)
- analytics: For measuring SEO performance
Source: coreyhaines31/marketingskills → skills/seo-audit/SKILL.md
1---
2name: seo-audit-4
3description: "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. For AI search optimization, see ai-seo."
4category: marketing-and-growth
5source_repo: coreyhaines31/marketingskills
6source_path: "skills/seo-audit/SKILL.md"
7source_url: https://github.com/coreyhaines31/marketingskills/blob/HEAD/skills/seo-audit/SKILL.md
8metadata:
9 source: https://skillmd.com/skills/coreyhaines31/seo-audit-4
10---
11
12
13# SEO Audit
14
15You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.
16
17## Initial Assessment
18
19**Check for product marketing context first:**
20If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
21
22Before auditing, understand:
23
241. **Site Context**
25 - What type of site? (SaaS, e-commerce, blog, etc.)
26 - What's the primary business goal for SEO?
27 - What keywords/topics are priorities?
28
292. **Current State**
30 - Any known issues or concerns?
31 - Current organic traffic level?
32 - Recent changes or migrations?
33
343. **Scope**
35 - Full site audit or specific pages?
36 - Technical + on-page, or one focus area?
37 - Access to Search Console / analytics?
38
39---
40
41## Audit Framework
42
43### Schema Markup Detection Limitation
44
45**`web_fetch` and `curl` cannot reliably detect structured data / schema markup.**
46
47Many 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).
48
49**To accurately check for schema markup, use one of these methods:**
501. **Browser tool** — render the page and run: `document.querySelectorAll('script[type="application/ld+json"]')`
512. **Google Rich Results Test** — https://search.google.com/test/rich-results
523. **Screaming Frog export** — if the client provides one, use it (SF renders JavaScript)
53
54Reporting "no schema found" based solely on `web_fetch` or `curl` leads to false audit findings — these tools can't see JS-injected schema.
55
56### Priority Order
571. **Crawlability & Indexation** (can Google find and index it?)
582. **Technical Foundations** (is the site fast and functional?)
593. **On-Page Optimization** (is content optimized?)
604. **Content Quality** (does it deserve to rank?)
615. **Authority & Links** (does it have credibility?)
62
63---
64
65## Technical SEO Audit
66
67### Crawlability
68
69**Robots.txt**
70- Check for unintentional blocks
71- Verify important pages allowed
72- Check sitemap reference
73
74**XML Sitemap**
75- Exists and accessible
76- Submitted to Search Console
77- Contains only canonical, indexable URLs
78- Updated regularly
79- Proper formatting
80
81**Site Architecture**
82- Important pages within 3 clicks of homepage
83- Logical hierarchy
84- Internal linking structure
85- No orphan pages
86
87**Crawl Budget Issues** (for large sites)
88- Parameterized URLs under control
89- Faceted navigation handled properly
90- Infinite scroll with pagination fallback
91- Session IDs not in URLs
92
93### Indexation
94
95**Index Status**
96- site:domain.com check
97- Search Console coverage report
98- Compare indexed vs. expected
99
100**Indexation Issues**
101- Noindex tags on important pages
102- Canonicals pointing wrong direction
103- Redirect chains/loops
104- Soft 404s
105- Duplicate content without canonicals
106
107**Canonicalization**
108- All pages have canonical tags
109- Self-referencing canonicals on unique pages
110- HTTP → HTTPS canonicals
111- www vs. non-www consistency
112- Trailing slash consistency
113
114### Site Speed & Core Web Vitals
115
116**Core Web Vitals**
117- LCP (Largest Contentful Paint): < 2.5s
118- INP (Interaction to Next Paint): < 200ms
119- CLS (Cumulative Layout Shift): < 0.1
120
121**Speed Factors**
122- Server response time (TTFB)
123- Image optimization
124- JavaScript execution
125- CSS delivery
126- Caching headers
127- CDN usage
128- Font loading
129
130**Tools**
131- PageSpeed Insights
132- WebPageTest
133- Chrome DevTools
134- Search Console Core Web Vitals report
135
136### Mobile-Friendliness
137
138- Responsive design (not separate m. site)
139- Tap target sizes
140- Viewport configured
141- No horizontal scroll
142- Same content as desktop
143- Mobile-first indexing readiness
144
145### Security & HTTPS
146
147- HTTPS across entire site
148- Valid SSL certificate
149- No mixed content
150- HTTP → HTTPS redirects
151- HSTS header (bonus)
152
153### URL Structure
154
155- Readable, descriptive URLs
156- Keywords in URLs where natural
157- Consistent structure
158- No unnecessary parameters
159- Lowercase and hyphen-separated
160
161---
162
163## International SEO & Localization
164
165Check 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.
166
167### Hreflang
168
169Three 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).
170
171**Check for:**
172- Self-referencing entry on every page (page must include itself in the hreflang set)
173- Reciprocal links (if A points to B, B must point back to A -- or both are ignored)
174- Valid codes: ISO 639-1 language + optional ISO 3166-1 Alpha 2 region (e.g., `en`, `en-GB` -- never `en-UK`)
175- `x-default` present, pointing to fallback page (language selector or default locale)
176- All target URLs return 200, are indexable, and match their canonical URL
177- No duplicate language-region codes pointing to different URLs
178
179**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).
180
181**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).
182
183### Canonicalization for Multilingual Sites
184
185- Each locale page must self-canonical (e.g., `/ar/page` canonicals to `/ar/page`)
186- Never cross-locale canonical (French to English) -- suppresses the non-canonical locale entirely
187- Canonical URL must appear in the hreflang set -- if not, all hreflang is ignored
188- Canonical overrides hreflang when they conflict
189- Protocol/domain must be consistent across canonical, hreflang, and sitemap (`https` + same domain variant)
190- Paginated locale pages: self-referencing canonical per page (never canonical page 2+ to page 1)
191
192**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.
193
194### International Sitemaps
195
196**Check for:**
197- `xmlns:xhtml` namespace on `<urlset>`, each `<url>` includes `<xhtml:link>` for all locales including itself
198- `x-default` alternate included; all URLs absolute (full protocol + domain)
199- Sitemap index in Search Console and robots.txt; split by content type, not by locale
200
201**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.
202
203### Locale URL Structure
204
205**Recommended:** Subdirectories (`/en/`, `/ar/`). **Acceptable:** Subdomains or ccTLDs. **Not recommended:** URL parameters (`?lang=en`).
206
207**Check for:**
208- Consistent locale prefix strategy; all locales prefixed (hiding locale from URLs prevents Google from distinguishing versions)
209- Root URL handled as `x-default` with redirect, or serves default locale content
210- No IP/Accept-Language content negotiation (Googlebot: US IPs, no Accept-Language header)
211- Trailing slash + case consistency across locale paths, canonicals, hreflang, and sitemaps
212- 301 redirects from non-canonical format to canonical
213
214**Note:** Google's International Targeting report in Search Console is deprecated. Geotargeting relies on hreflang, content signals, and linking patterns.
215
216### Content Quality Across Locales
217
218**Translation quality:**
219- AI-translated content is not inherently spam (Google's 2025 stance), but scaled low-value translations can trigger scaled content abuse policy
220- Google uses visible content to determine language -- translate ALL page content (title, description, headings, body), not just boilerplate
221- Translating only template/nav while main content stays in original language creates duplicates
222
223**Thin locale pages:**
224- Helpful content system is site-wide -- many thin locale pages can suppress rankings for strong pages too
225- Don't noindex thin locales (wastes crawl budget) or cross-locale canonical (conflicts with hreflang)
226- Best approach: don't create locale pages you cannot make genuinely helpful
227
228**Check for:**
229- All locale pages have fully translated main content (not just UI chrome)
230- No near-identical content across locales ("Duplicate, Google chose different canonical" in GSC)
231- Hreflang only for locales with genuine content and search demand
232- Localized signals: currency, phone format, addresses where applicable
233- Broken hreflang links (404s, redirects) waste crawl budget AND invalidate hreflang clusters
234
235---
236
237## On-Page SEO Audit
238
239### Title Tags
240
241**Check for:**
242- Unique titles for each page
243- Primary keyword near beginning
244- 50-60 characters (visible in SERP)
245- Compelling and click-worthy
246- Brand name placement (end, usually)
247
248**Common issues:**
249- Duplicate titles
250- Too long (truncated)
251- Too short (wasted opportunity)
252- Keyword stuffing
253- Missing entirely
254
255### Meta Descriptions
256
257**Check for:**
258- Unique descriptions per page
259- 150-160 characters
260- Includes primary keyword
261- Clear value proposition
262- Call to action
263
264**Common issues:**
265- Duplicate descriptions
266- Auto-generated garbage
267- Too long/short
268- No compelling reason to click
269
270### Heading Structure
271
272**Check for:**
273- One H1 per page
274- H1 contains primary keyword
275- Logical hierarchy (H1 → H2 → H3)
276- Headings describe content
277- Not just for styling
278
279**Common issues:**
280- Multiple H1s
281- Skip levels (H1 → H3)
282- Headings used for styling only
283- No H1 on page
284
285### Content Optimization
286
287**Primary Page Content**
288- Keyword in first 100 words
289- Related keywords naturally used
290- Sufficient depth/length for topic
291- Answers search intent
292- Better than competitors
293
294**Thin Content Issues**
295- Pages with little unique content
296- Tag/category pages with no value
297- Doorway pages
298- Duplicate or near-duplicate content
299
300### Image Optimization
301
302**Check for:**
303- Descriptive file names
304- Alt text on all images
305- Alt text describes image
306- Compressed file sizes
307- Modern formats (WebP)
308- Lazy loading implemented
309- Responsive images
310
311### Internal Linking
312
313**Check for:**
314- Important pages well-linked
315- Descriptive anchor text
316- Logical link relationships
317- No broken internal links
318- Reasonable link count per page
319
320**Common issues:**
321- Orphan pages (no internal links)
322- Over-optimized anchor text
323- Important pages buried
324- Excessive footer/sidebar links
325
326### Keyword Targeting
327
328**Per Page**
329- Clear primary keyword target
330- Title, H1, URL aligned
331- Content satisfies search intent
332- Not competing with other pages (cannibalization)
333
334**Site-Wide**
335- Keyword mapping document
336- No major gaps in coverage
337- No keyword cannibalization
338- Logical topical clusters
339
340---
341
342## Content Quality Assessment
343
344### E-E-A-T Signals
345
346**Experience**
347- First-hand experience demonstrated
348- Original insights/data
349- Real examples and case studies
350
351**Expertise**
352- Author credentials visible
353- Accurate, detailed information
354- Properly sourced claims
355
356**Authoritativeness**
357- Recognized in the space
358- Cited by others
359- Industry credentials
360
361**Trustworthiness**
362- Accurate information
363- Transparent about business
364- Contact information available
365- Privacy policy, terms
366- Secure site (HTTPS)
367
368### Content Depth
369
370- Comprehensive coverage of topic
371- Answers follow-up questions
372- Better than top-ranking competitors
373- Updated and current
374
375### User Engagement Signals
376
377- Time on page
378- Bounce rate in context
379- Pages per session
380- Return visits
381
382---
383
384## Common Issues by Site Type
385
386### SaaS/Product Sites
387- Product pages lack content depth
388- Blog not integrated with product pages
389- Missing comparison/alternative pages
390- Feature pages thin on content
391- No glossary/educational content
392
393### E-commerce
394- Thin category pages
395- Duplicate product descriptions
396- Missing product schema
397- Faceted navigation creating duplicates
398- Out-of-stock pages mishandled
399
400### Content/Blog Sites
401- Outdated content not refreshed
402- Keyword cannibalization
403- No topical clustering
404- Poor internal linking
405- Missing author pages
406
407### Multilingual / Multi-Regional Sites
408- Hreflang errors (missing return tags, invalid codes, no self-reference)
409- Canonical conflicting with hreflang (cross-locale canonical suppresses indexing)
410- Thin locale pages dragging down site-wide quality signal
411- Only boilerplate translated, main content identical across locales
412- No x-default fallback declared
413- Sitemap missing hreflang alternates or missing reciprocal entries
414- IP-based redirects hiding content from Googlebot
415- Framework locale mode hiding locale from URLs
416
417### Local Business
418- Inconsistent NAP
419- Missing local schema
420- No Google Business Profile optimization
421- Missing location pages
422- No local content
423
424---
425
426## Output Format
427
428### Audit Report Structure
429
430**Executive Summary**
431- Overall health assessment
432- Top 3-5 priority issues
433- Quick wins identified
434
435**Technical SEO Findings**
436For each issue:
437- **Issue**: What's wrong
438- **Impact**: SEO impact (High/Medium/Low)
439- **Evidence**: How you found it
440- **Fix**: Specific recommendation
441- **Priority**: 1-5 or High/Medium/Low
442
443**On-Page SEO Findings**
444Same format as above
445
446**Content Findings**
447Same format as above
448
449**Prioritized Action Plan**
4501. Critical fixes (blocking indexation/ranking)
4512. High-impact improvements
4523. Quick wins (easy, immediate benefit)
4534. Long-term recommendations
454
455---
456
457## References
458
459- [AI Writing Detection](references/ai-writing-detection.md): Common AI writing patterns to avoid (em dashes, overused phrases, filler words)
460- [International SEO](references/international-seo.md): Evidence and sources for hreflang, canonical + i18n, sitemaps, URL structure, and content quality across locales
461- For AI search optimization (AEO, GEO, LLMO, AI Overviews), see the **ai-seo** skill
462
463---
464
465## Tools Referenced
466
467**Free Tools**
468- Google Search Console (essential)
469- Google PageSpeed Insights
470- Bing Webmaster Tools
471- Rich Results Test (**use this for schema validation — it renders JavaScript**)
472- Mobile-Friendly Test
473- Schema Validator
474
475> **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.
476
477**Paid Tools** (if available)
478- Screaming Frog
479- Ahrefs / Semrush
480- Sitebulb
481- ContentKing
482
483---
484
485## Task-Specific Questions
486
4871. What pages/keywords matter most?
4882. Do you have Search Console access?
4893. Any recent changes or migrations?
4904. Who are your top organic competitors?
4915. What's your current organic traffic baseline?
492
493---
494
495## Related Skills
496
497- **ai-seo**: For optimizing content for AI search engines (AEO, GEO, LLMO)
498- **programmatic-seo**: For building SEO pages at scale
499- **site-architecture**: For page hierarchy, navigation design, and URL structure
500- **schema**: For implementing structured data
501- **cro**: For optimizing pages for conversion (not just ranking)
502- **analytics**: For measuring SEO performance
503
504---
505
506**Source:** [`coreyhaines31/marketingskills`](https://github.com/coreyhaines31/marketingskills) → `skills/seo-audit/SKILL.md`