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