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