Technical SEO Audit
Categories
1. Crawlability
- robots.txt: exists, valid, not blocking important resources
- XML sitemap: run
claude-seo run sitemap_discovery.py <url> --json; require a
valid entry in found, and report stale or unsafe robots.txt declarations
separately from working fallback locations
- Noindex tags: intentional vs accidental
- Crawl depth: important pages within 3 clicks of homepage
- JavaScript rendering: check if critical content requires JS execution
- Crawl budget: for large sites (>10k pages), efficiency matters
- Googlebot fetch limits: Googlebot fetches the first 2MB of HTML and first 64MB of a PDF (uncompressed; 15MB is the broader crawler-infra default). Long-standing, not a 2026 change, but inline base64 images, oversized inline CSS/JS, or bloated nav can push critical content/JSON-LD past the cap and out of the index. Keep key content + structured data within the first 2MB.
- Crawl rate auto-adjusts (backs off on 5xx/slow responses); there is no manual crawl-rate control (the legacy Search Console setting was removed Jan 2024). Influence crawling via sitemaps, server responsiveness, and robots controls.
- Google's canonical crawling/robots reference moved to developers.google.com/crawling (migrated 2025-11-20); IP-range files relocated to
/crawling/ipranges/ and googlebot.json was renamed common-crawlers.json.
- AMP has no separate ranking advantage. Since 2026-07-01, Google Search sends
users directly to publisher-hosted AMP URLs, so do not recommend AMP Cache,
AMP Viewer, or signed exchange maintenance. Audit AMP against the same content,
action-parity, and quality requirements as other pages.
AI Crawler Management
As of 2025-2026, AI companies actively crawl the web to train models and power AI search. Managing these crawlers via robots.txt is a critical technical SEO consideration.
Known AI crawlers:
| Crawler |
Company |
robots.txt token |
Purpose |
| GPTBot |
OpenAI |
GPTBot |
Model training |
| ChatGPT-User |
OpenAI |
ChatGPT-User |
Real-time browsing |
| ClaudeBot |
Anthropic |
ClaudeBot |
Model training |
| PerplexityBot |
Perplexity |
PerplexityBot |
Search index + training |
| Bytespider |
ByteDance |
Bytespider |
Model training |
| Google-Extended |
Google |
Google-Extended |
Gemini training (NOT search) |
| CCBot |
Common Crawl |
CCBot |
Open dataset |
Key distinctions:
- Blocking
Google-Extended prevents Gemini training use but does NOT affect Google Search indexing or AI Overviews (those use Googlebot)
- Blocking
GPTBot prevents OpenAI training but does NOT prevent ChatGPT from citing your content via browsing (ChatGPT-User)
- ~3-5% of websites now use AI-specific robots.txt rules
Example, selective AI crawler blocking:
# Allow search indexing, block AI training crawlers
User-agent: GPTBot
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: Bytespider
Disallow: /
# Allow all other crawlers (including Googlebot for search)
User-agent: *
Allow: /
Recommendation: Consider your AI visibility strategy before blocking. Being cited by AI systems drives brand awareness and referral traffic. Cross-reference the seo-geo skill for the full AI crawler/fetcher taxonomy.
User-triggered fetchers ignore robots.txt by design. Google now documents Google-Agent (Project Mariner, agentic browsing) plus Google-NotebookLM and Google Messages as user-triggered fetchers that cannot be blocked via robots.txt. Use server-side access controls instead. By contrast, Google-Extended and Google-CloudVertexBot obey robots.txt. Emerging: Web Bot Auth (RFC 9421) lets bots authenticate cryptographically via a Signature-Agent header + key directory at agent.bot.goog (used by Google-Agent); reverse-DNS verification remains the fallback.
2. Indexability
- Canonical tags: self-referencing, no conflicts with noindex
- Duplicate content: near-duplicates, parameter URLs, www vs non-www
- Canonicalization fixes can take time: Google may retain corrected pages in a
duplicate cluster for up to two weeks while re-evaluating them. Do not
interpret an unchanged canonical immediately after a fix as proof that the
fix failed.
- Thin content: pages below minimum word counts per type
- Pagination: rel=next/prev or load-more pattern
- Hreflang: correct for multi-language/multi-region sites
- Index bloat: unnecessary pages consuming crawl budget
3. Security
- HTTPS: enforced, valid SSL certificate, no mixed content
- Security headers:
- Content-Security-Policy (CSP)
- Strict-Transport-Security (HSTS)
- X-Frame-Options
- X-Content-Type-Options
- Referrer-Policy
- HSTS preload: check preload list inclusion for high-security sites
- Back-button hijacking (spam-policy violation, malicious practices): flag pages that defeat the Back button via
history.pushState/replaceState (including scripts injected by third-party ad/library platforms). Added to Google's spam policies 2026-04-13; enforcement live since 2026-06-15 (manual actions + automated demotions): treat as Critical.
4. URL Structure
- Clean URLs: descriptive, hyphenated, no query parameters for content
- Hierarchy: logical folder structure reflecting site architecture
- Redirects: no chains (max 1 hop), 301 for permanent moves
- URL length: flag >100 characters
- Trailing slashes: consistent usage
5. Mobile Optimization & Page Experience
- Responsive design: viewport meta tag, responsive CSS
- Touch targets: minimum 48x48px with 8px spacing
- Font size: minimum 16px base
- No horizontal scroll
- Mobile-first indexing: Googlebot Smartphone is the primary crawler (rollout completed 2024). A mobile version is not strictly required (Google says "very strongly recommended"), sites that don't work on mobile can still be indexed, but the real risk is content/parity loss, not hard exclusion.
- Mobile/desktop content parity (highest-value mobile check): equivalent primary content, matching robots meta tags, matching titles/descriptions, equivalent structured data, crawlable resources; avoid lazy-loading primary content that requires user interaction.
- Intrusive interstitials / ad density: flag full-page interstitials, standalone consent-redirect pages, persistent blocking dialogs, and excessive/distracting ad density (a named page-experience aspect). Acceptable: small banners, standard CMS/legal dialogs.
- "Read more" deep links: keep key content immediately visible on load (not behind tabs/accordions), don't hijack scroll on load, and preserve URL hash fragments, content hidden behind expandable sections is less likely to qualify.
Page experience is guidance, not a single ranking system. Only Core Web Vitals feeds ranking directly; HTTPS is a confirmed but lightweight signal (affects <~1% of queries). Relevance can still win even when page experience is sub-par, so don't over-weight security headers. Note: the standalone Page Experience report was removed from Search Console (monitor via the Core Web Vitals + HTTPS reports).
6. Core Web Vitals
- LCP (Largest Contentful Paint): target <=2.5s
- INP (Interaction to Next Paint): target <=200ms
- INP replaced FID on March 12, 2024. FID was removed from Chrome's field-data tools (CrUX API, PageSpeed Insights) on September 9, 2024 (Lighthouse is a lab tool that never reported FID). Do NOT reference FID anywhere.
- CLS (Cumulative Layout Shift): target <=0.1
- Evaluation uses 75th percentile of real user data
- Use PageSpeed Insights API or CrUX data if MCP available
7. Structured Data
- Detection: JSON-LD (preferred), Microdata, RDFa
- Validation against Google's supported types
- See seo-schema skill for full analysis
8. JavaScript Rendering
- Check if content visible in initial HTML vs requires JS
- Identify client-side rendered (CSR) vs server-side rendered (SSR)
- Flag SPA frameworks (React, Vue, Angular) that may cause indexing issues
- Verify dynamic rendering setup if applicable
JavaScript SEO: Canonical & Indexing Guidance (December 2025)
Google updated its JavaScript SEO documentation in December 2025 with critical clarifications:
- Canonical conflicts: If a canonical tag in raw HTML differs from one injected by JavaScript, Google may use EITHER one. Ensure canonical tags are identical between server-rendered HTML and JS-rendered output.
- noindex with JavaScript: If raw HTML contains
<meta name="robots" content="noindex"> but JavaScript removes it, Google MAY still honor the noindex from raw HTML. Serve correct robots directives in the initial HTML response.
- Non-200 status codes: Google does NOT render JavaScript on pages returning non-200 HTTP status codes. Any content or meta tags injected via JS on error pages will be invisible to Googlebot.
- Structured data in JavaScript: Product, Article, and other structured data injected via JS may face delayed processing. For time-sensitive structured data (especially e-commerce Product markup), include it in the initial server-rendered HTML.
Best practice: Serve critical SEO elements (canonical, meta robots, structured data, title, meta description) in the initial server-rendered HTML rather than relying on JavaScript injection.
9. IndexNow Protocol
- Check if site supports IndexNow for Bing, Yandex, Naver
- Supported by search engines other than Google
- Recommend implementation for faster indexing on non-Google engines
Agent-Friendly Pages & Agentic Browsing
AI agents (not just AI summarizers) increasingly read sites through three
channels: vision models on screenshots, raw HTML/DOM, and the accessibility
tree (the cleanest signal). Audit criteria: semantic HTML (real <button>
and <a>, not <div onclick>), label associations, interactive target sizing,
layout stability across templates, cursor: pointer correctness, live in
references/agent-friendly-pages.md.
Google now ships a Lighthouse Agentic Browsing category (default-on since
Lighthouse 13.3.0, Chrome 150+; buckets: agent-centric accessibility, CLS +
llms.txt, three WebMCP audits). It reports a fractional pass-ratio (X of N),
not a 0-100 score, keep that distinct from this skill's own Agent-UX 0-100
heuristic below. Lighthouse 13.4.1 re-enabled the category through the PSI API.
It is also available through Lighthouse CLI with
--only-categories=agentic-browsing, DevTools, and the PSI web UI. See
references/agent-friendly-pages.md.
Audit command
# Render with Playwright + capture accessibility tree, then score
claude-seo run agent_ux_check.py https://example.com --json
The scanner outputs an Agent-UX score (0-100) plus itemized issues:
- HTML findings: real buttons / anchors,
<div onclick> widgets, semantic
landmarks, inputs without <label for>, inputs without ARIA labels
- Accessibility tree findings: total nodes, interactive nodes, unnamed
interactive elements,
role="generic" ratio
The accessibility-tree snapshot uses Chromium's
Accessibility.getFullAXTree CDP command through Playwright. To capture the
tree without scoring, use
claude-seo run render_page.py <url> --a11y-tree --json.
Surface findings as opportunities, not failures; don't gate audits on a
sub-100 Agent-UX score. WebMCP origin-trial/sign-up status needs verification,
and absence of WebMCP support is still an opportunity, not a defect.
Output
Technical Score: XX/100
Category Breakdown
| Category |
Status |
Score |
| Crawlability |
pass/warn/fail |
XX/100 |
| Indexability |
pass/warn/fail |
XX/100 |
| Security |
pass/warn/fail |
XX/100 |
| URL Structure |
pass/warn/fail |
XX/100 |
| Mobile |
pass/warn/fail |
XX/100 |
| Core Web Vitals |
pass/warn/fail |
XX/100 |
| Structured Data |
pass/warn/fail |
XX/100 |
| JS Rendering |
pass/warn/fail |
XX/100 |
| IndexNow |
pass/warn/fail |
XX/100 |
Critical Issues (fix immediately)
High Priority (fix within 1 week)
Medium Priority (fix within 1 month)
Low Priority (backlog)
DataForSEO Integration (Optional)
If DataForSEO MCP tools are available, use on_page_instant_pages for real page analysis (status codes, page timing, broken links, on-page checks), on_page_lighthouse for Lighthouse audits (performance, accessibility, SEO scores), and domain_analytics_technologies_domain_technologies for technology stack detection.
Google API Integration (Optional)
If Google API credentials are configured, use claude-seo run pagespeed_check.py <url> --json for real PSI + CrUX field data (replaces lab-only CWV estimates), claude-seo run crux_history.py <url> --json for 25-week CWV trends, and claude-seo run gsc_inspect.py <url> --json for real indexation status per URL.
Error Handling
| Scenario |
Action |
| URL unreachable |
Report connection error with status code. Suggest verifying URL, checking DNS resolution, and confirming the site is publicly accessible. |
| robots.txt not found |
Note that no robots.txt was detected at the root domain. Recommend creating one with appropriate directives. Continue audit on remaining categories. |
| HTTPS not configured |
Flag as a critical issue. Report whether HTTP is served without redirect, mixed content exists, or SSL certificate is missing/expired. |
| Core Web Vitals data unavailable |
Note that CrUX data is not available (common for low-traffic sites). Suggest using Lighthouse lab data as a proxy and recommend increasing traffic before re-testing. |
1---
2name: seo-technical
3description: >
4 Technical SEO audit across 9 categories: crawlability, indexability, security,
5 URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering,
6 and IndexNow protocol. Use when user says "technical SEO", "crawl issues",
7 "robots.txt", "Core Web Vitals", "site speed", or "security headers".
8user-invocable: true
9argument-hint: "[url]"
10license: MIT
11metadata:
12 source: https://skillmd.com/skills/gabrielmoreira/seo-technical
13 author: AgriciDaniel
14 version: "2.2.5"
15 category: seo
16---
17
18# Technical SEO Audit
19
20## Categories
21
22### 1. Crawlability
23- robots.txt: exists, valid, not blocking important resources
24- XML sitemap: run `claude-seo run sitemap_discovery.py <url> --json`; require a
25 valid entry in `found`, and report stale or unsafe robots.txt declarations
26 separately from working fallback locations
27- Noindex tags: intentional vs accidental
28- Crawl depth: important pages within 3 clicks of homepage
29- JavaScript rendering: check if critical content requires JS execution
30- Crawl budget: for large sites (>10k pages), efficiency matters
31- Googlebot **fetch limits**: Googlebot fetches the first **2MB of HTML** and first **64MB of a PDF** (uncompressed; 15MB is the broader crawler-infra default). Long-standing, not a 2026 change, but inline base64 images, oversized inline CSS/JS, or bloated nav can push critical content/JSON-LD past the cap and out of the index. Keep key content + structured data within the first 2MB.
32- Crawl rate **auto-adjusts** (backs off on 5xx/slow responses); there is **no manual crawl-rate control** (the legacy Search Console setting was removed Jan 2024). Influence crawling via sitemaps, server responsiveness, and robots controls.
33- Google's canonical crawling/robots reference moved to **developers.google.com/crawling** (migrated 2025-11-20); IP-range files relocated to `/crawling/ipranges/` and `googlebot.json` was renamed `common-crawlers.json`.
34- AMP has no separate ranking advantage. Since 2026-07-01, Google Search sends
35 users directly to publisher-hosted AMP URLs, so do not recommend AMP Cache,
36 AMP Viewer, or signed exchange maintenance. Audit AMP against the same content,
37 action-parity, and quality requirements as other pages.
38
39#### AI Crawler Management
40
41As of 2025-2026, AI companies actively crawl the web to train models and power AI search. Managing these crawlers via robots.txt is a critical technical SEO consideration.
42
43**Known AI crawlers:**
44
45| Crawler | Company | robots.txt token | Purpose |
46|---------|---------|-----------------|---------|
47| GPTBot | OpenAI | `GPTBot` | Model training |
48| ChatGPT-User | OpenAI | `ChatGPT-User` | Real-time browsing |
49| ClaudeBot | Anthropic | `ClaudeBot` | Model training |
50| PerplexityBot | Perplexity | `PerplexityBot` | Search index + training |
51| Bytespider | ByteDance | `Bytespider` | Model training |
52| Google-Extended | Google | `Google-Extended` | Gemini training (NOT search) |
53| CCBot | Common Crawl | `CCBot` | Open dataset |
54
55**Key distinctions:**
56- Blocking `Google-Extended` prevents Gemini training use but does NOT affect Google Search indexing or AI Overviews (those use `Googlebot`)
57- Blocking `GPTBot` prevents OpenAI training but does NOT prevent ChatGPT from citing your content via browsing (`ChatGPT-User`)
58- ~3-5% of websites now use AI-specific robots.txt rules
59
60**Example, selective AI crawler blocking:**
61```
62# Allow search indexing, block AI training crawlers
63User-agent: GPTBot
64Disallow: /
65
66User-agent: Google-Extended
67Disallow: /
68
69User-agent: Bytespider
70Disallow: /
71
72# Allow all other crawlers (including Googlebot for search)
73User-agent: *
74Allow: /
75```
76
77**Recommendation:** Consider your AI visibility strategy before blocking. Being cited by AI systems drives brand awareness and referral traffic. Cross-reference the `seo-geo` skill for the full AI crawler/fetcher taxonomy.
78
79> **User-triggered fetchers ignore robots.txt by design.** Google now documents **Google-Agent** (Project Mariner, agentic browsing) plus **Google-NotebookLM** and **Google Messages** as *user-triggered* fetchers that **cannot be blocked via robots.txt**. Use server-side access controls instead. By contrast, `Google-Extended` and `Google-CloudVertexBot` obey robots.txt. Emerging: **Web Bot Auth** (RFC 9421) lets bots authenticate cryptographically via a `Signature-Agent` header + key directory at `agent.bot.goog` (used by Google-Agent); reverse-DNS verification remains the fallback.
80
81### 2. Indexability
82- Canonical tags: self-referencing, no conflicts with noindex
83- Duplicate content: near-duplicates, parameter URLs, www vs non-www
84- Canonicalization fixes can take time: Google may retain corrected pages in a
85 duplicate cluster for **up to two weeks** while re-evaluating them. Do not
86 interpret an unchanged canonical immediately after a fix as proof that the
87 fix failed.
88- Thin content: pages below minimum word counts per type
89- Pagination: rel=next/prev or load-more pattern
90- Hreflang: correct for multi-language/multi-region sites
91- Index bloat: unnecessary pages consuming crawl budget
92
93### 3. Security
94- HTTPS: enforced, valid SSL certificate, no mixed content
95- Security headers:
96 - Content-Security-Policy (CSP)
97 - Strict-Transport-Security (HSTS)
98 - X-Frame-Options
99 - X-Content-Type-Options
100 - Referrer-Policy
101- HSTS preload: check preload list inclusion for high-security sites
102- **Back-button hijacking** (spam-policy violation, malicious practices): flag pages that defeat the Back button via `history.pushState`/`replaceState` (including scripts injected by third-party ad/library platforms). Added to Google's spam policies 2026-04-13; **enforcement live since 2026-06-15** (manual actions + automated demotions): treat as Critical.
103
104### 4. URL Structure
105- Clean URLs: descriptive, hyphenated, no query parameters for content
106- Hierarchy: logical folder structure reflecting site architecture
107- Redirects: no chains (max 1 hop), 301 for permanent moves
108- URL length: flag >100 characters
109- Trailing slashes: consistent usage
110
111### 5. Mobile Optimization & Page Experience
112- Responsive design: viewport meta tag, responsive CSS
113- Touch targets: minimum 48x48px with 8px spacing
114- Font size: minimum 16px base
115- No horizontal scroll
116- Mobile-first indexing: Googlebot Smartphone is the primary crawler (rollout completed 2024). A mobile version is **not strictly required** (Google says "very strongly recommended"), sites that don't work on mobile can still be indexed, but the real risk is **content/parity loss**, not hard exclusion.
117- **Mobile/desktop content parity** (highest-value mobile check): equivalent primary content, matching robots meta tags, matching titles/descriptions, equivalent structured data, crawlable resources; avoid lazy-loading primary content that requires user interaction.
118- **Intrusive interstitials / ad density**: flag full-page interstitials, standalone consent-redirect pages, persistent blocking dialogs, and excessive/distracting ad density (a named page-experience aspect). Acceptable: small banners, standard CMS/legal dialogs.
119- **"Read more" deep links**: keep key content **immediately visible on load** (not behind tabs/accordions), don't hijack scroll on load, and preserve URL hash fragments, content hidden behind expandable sections is less likely to qualify.
120
121> **Page experience is guidance, not a single ranking system.** Only **Core Web Vitals** feeds ranking directly; **HTTPS** is a confirmed but lightweight signal (affects <~1% of queries). Relevance can still win even when page experience is sub-par, so don't over-weight security headers. Note: the standalone **Page Experience report was removed** from Search Console (monitor via the Core Web Vitals + HTTPS reports).
122
123### 6. Core Web Vitals
124- **LCP** (Largest Contentful Paint): target <=2.5s
125- **INP** (Interaction to Next Paint): target <=200ms
126 - INP replaced FID on March 12, 2024. FID was removed from Chrome's field-data tools (CrUX API, PageSpeed Insights) on September 9, 2024 (Lighthouse is a lab tool that never reported FID). Do NOT reference FID anywhere.
127- **CLS** (Cumulative Layout Shift): target <=0.1
128- Evaluation uses 75th percentile of real user data
129- Use PageSpeed Insights API or CrUX data if MCP available
130
131### 7. Structured Data
132- Detection: JSON-LD (preferred), Microdata, RDFa
133- Validation against Google's supported types
134- See seo-schema skill for full analysis
135
136### 8. JavaScript Rendering
137- Check if content visible in initial HTML vs requires JS
138- Identify client-side rendered (CSR) vs server-side rendered (SSR)
139- Flag SPA frameworks (React, Vue, Angular) that may cause indexing issues
140- Verify dynamic rendering setup if applicable
141
142#### JavaScript SEO: Canonical & Indexing Guidance (December 2025)
143
144Google updated its JavaScript SEO documentation in December 2025 with critical clarifications:
145
1461. **Canonical conflicts:** If a canonical tag in raw HTML differs from one injected by JavaScript, Google may use EITHER one. Ensure canonical tags are identical between server-rendered HTML and JS-rendered output.
1472. **noindex with JavaScript:** If raw HTML contains `<meta name="robots" content="noindex">` but JavaScript removes it, Google MAY still honor the noindex from raw HTML. Serve correct robots directives in the initial HTML response.
1483. **Non-200 status codes:** Google does NOT render JavaScript on pages returning non-200 HTTP status codes. Any content or meta tags injected via JS on error pages will be invisible to Googlebot.
1494. **Structured data in JavaScript:** Product, Article, and other structured data injected via JS may face delayed processing. For time-sensitive structured data (especially e-commerce Product markup), include it in the initial server-rendered HTML.
150
151**Best practice:** Serve critical SEO elements (canonical, meta robots, structured data, title, meta description) in the initial server-rendered HTML rather than relying on JavaScript injection.
152
153### 9. IndexNow Protocol
154- Check if site supports IndexNow for Bing, Yandex, Naver
155- Supported by search engines other than Google
156- Recommend implementation for faster indexing on non-Google engines
157
158## Agent-Friendly Pages & Agentic Browsing
159
160AI agents (not just AI summarizers) increasingly read sites through three
161channels: vision models on screenshots, raw HTML/DOM, and the **accessibility
162tree** (the cleanest signal). Audit criteria: semantic HTML (real `<button>`
163and `<a>`, not `<div onclick>`), label associations, interactive target sizing,
164layout stability across templates, `cursor: pointer` correctness, live in
165`references/agent-friendly-pages.md`.
166
167Google now ships a Lighthouse **Agentic Browsing** category (default-on since
168Lighthouse 13.3.0, Chrome 150+; buckets: agent-centric accessibility, CLS +
169llms.txt, three WebMCP audits). It reports a **fractional pass-ratio (X of N),
170not a 0-100 score**, keep that distinct from this skill's own Agent-UX 0-100
171heuristic below. Lighthouse 13.4.1 re-enabled the category through the PSI API.
172It is also available through Lighthouse CLI with
173`--only-categories=agentic-browsing`, DevTools, and the PSI web UI. See
174`references/agent-friendly-pages.md`.
175
176### Audit command
177
178```bash
179# Render with Playwright + capture accessibility tree, then score
180claude-seo run agent_ux_check.py https://example.com --json
181```
182
183The scanner outputs an Agent-UX score (0-100) plus itemized issues:
184- HTML findings: real buttons / anchors, `<div onclick>` widgets, semantic
185 landmarks, inputs without `<label for>`, inputs without ARIA labels
186- Accessibility tree findings: total nodes, interactive nodes, unnamed
187 interactive elements, `role="generic"` ratio
188
189The accessibility-tree snapshot uses Chromium's
190`Accessibility.getFullAXTree` CDP command through Playwright. To capture the
191tree without scoring, use
192`claude-seo run render_page.py <url> --a11y-tree --json`.
193
194Surface findings as **opportunities**, not failures; don't gate audits on a
195sub-100 Agent-UX score. WebMCP origin-trial/sign-up status needs verification,
196and absence of WebMCP support is still an opportunity, not a defect.
197
198## Output
199
200### Technical Score: XX/100
201
202### Category Breakdown
203| Category | Status | Score |
204|----------|--------|-------|
205| Crawlability | pass/warn/fail | XX/100 |
206| Indexability | pass/warn/fail | XX/100 |
207| Security | pass/warn/fail | XX/100 |
208| URL Structure | pass/warn/fail | XX/100 |
209| Mobile | pass/warn/fail | XX/100 |
210| Core Web Vitals | pass/warn/fail | XX/100 |
211| Structured Data | pass/warn/fail | XX/100 |
212| JS Rendering | pass/warn/fail | XX/100 |
213| IndexNow | pass/warn/fail | XX/100 |
214
215### Critical Issues (fix immediately)
216### High Priority (fix within 1 week)
217### Medium Priority (fix within 1 month)
218### Low Priority (backlog)
219
220## DataForSEO Integration (Optional)
221
222If DataForSEO MCP tools are available, use `on_page_instant_pages` for real page analysis (status codes, page timing, broken links, on-page checks), `on_page_lighthouse` for Lighthouse audits (performance, accessibility, SEO scores), and `domain_analytics_technologies_domain_technologies` for technology stack detection.
223
224## Google API Integration (Optional)
225
226If Google API credentials are configured, use `claude-seo run pagespeed_check.py <url> --json` for real PSI + CrUX field data (replaces lab-only CWV estimates), `claude-seo run crux_history.py <url> --json` for 25-week CWV trends, and `claude-seo run gsc_inspect.py <url> --json` for real indexation status per URL.
227
228## Error Handling
229
230| Scenario | Action |
231|----------|--------|
232| URL unreachable | Report connection error with status code. Suggest verifying URL, checking DNS resolution, and confirming the site is publicly accessible. |
233| robots.txt not found | Note that no robots.txt was detected at the root domain. Recommend creating one with appropriate directives. Continue audit on remaining categories. |
234| HTTPS not configured | Flag as a critical issue. Report whether HTTP is served without redirect, mixed content exists, or SSL certificate is missing/expired. |
235| Core Web Vitals data unavailable | Note that CrUX data is not available (common for low-traffic sites). Suggest using Lighthouse lab data as a proxy and recommend increasing traffic before re-testing. |