/seo-mobile
Audit mobile-friendliness of a page from the PageSnapshot — verify the viewport meta, no horizontal-scroll/fixed-width layouts, adequate tap targets, legible base font, and mobile/desktop content parity — and generate the viewport meta when missing. Module M7b. Feeds the Search
$ npx -y skills add Hainrixz/claude-seo-ai --skill seo-mobile --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/seo-mobile
Context preview
The summary Claude sees to decide when to auto-load this skill.
Audit mobile-friendliness of a page from the PageSnapshot — verify the viewport meta, no horizontal-scroll/fixed-width layouts, adequate tap targets, legible base font, and mobile/desktop content parity — and generate the viewport meta when missing. Module M7b. Feeds the Search
SKILL.md
seo-mobile.SKILL.mdname: seo-mobile
description: Audit mobile-friendliness of a page from the PageSnapshot — verify the viewport meta, no horizontal-scroll/fixed-width layouts, adequate tap targets, legible base font, and mobile/desktop content parity — and generate the viewport meta when missing. Module M7b. Feeds the Search SEO score.
allowed-tools: Read, Grep, Glob, WebFetch, Bash
seo-mobile (M7b)
Google indexes mobile-first: the mobile rendering of a page is the canonical one for ranking. This module checks that a page is usable on a small viewport. Layout problems that hurt mobile usability often surface as CLS — cross-check `references/cwv-thresholds.md`.
Audits
Working from the PageSnapshot (`rendered_dom` if present, else `raw_html`): 1. **Viewport meta**: a `<meta name="viewport">` exists with `width=device-width` and `initial-scale=1`. Flag missing, fixed-width (`width=1024`), or zoom-blocking (`user-scalable=no`, `maximum-scale=1`) values — the last also harms accessibility. 2. **No horizontal scroll**: detect fixed-width containers / large absolute widths that force the viewport wider than the device (content overflowing a ~360 px small viewport). 3. **Tap-target size**: interactive elements (links, buttons, form controls) should be large enough and spaced so adjacent targets are not easily mis-tapped. 4. **Legible base font**: body text rendered at a readable base size, not a desktop-only small size that forces pinch-zoom on mobile. 5. **Content parity**: the mobile DOM must contain the same primary content, headings, structured data, and links as desktop — mobile-first indexing ranks what is in the mobile render, so hidden/stripped mobile content is a ranking risk.
Fixes
- **AUTO** (`fixable: auto`): inject `<meta name="viewport" content="width=device-width, initial-scale=1">` into `<head>` when absent. Deterministic, additive, verifiable — emitted as a diff for `fix`.
- **ADVISORY** (`fixable: advisory`): fixed-width/overflow layouts, tap-target sizing, base-font, and parity gaps depend on CSS, design system, and JS — high breakage risk. The tool diagnoses and prioritizes but does **not** auto-edit layout code. **Never invent** breakpoint values or pixel sizes — report observed values or leave a clearly-marked TODO for the user.
Verification
- Method `dom_assert`: assert against the snapshot (viewport meta presence/content, computed widths, target geometry).
- Reproduce the deterministic part (viewport meta presence/content) offline: `node ${CLAUDE_SKILL_DIR}/../../scripts/parse-html.mjs --url <u>` (or `--file <path>`) — inspect `head_hygiene.viewport`. Tap-target/overflow geometry is a `manual_review` pass over the rendered snapshot.
- Tap-target and overflow checks need the **rendered** snapshot (computed layout). When only `raw_html` is available and layout cannot be resolved, status is `needs_api`, never a false `pass`.
Findings
Emit findings per `schema/finding.schema.json`. Examples:
- `M7b.viewport.missing` — no viewport meta (status `fail`, severity 3, `fixable: auto`, axis `search`, confidence `established`).
- `M7b.viewport.user_scalable_no` — viewport disables zoom (status `warn`, severity 3, `fixable: advisory`, axis `search`, confidence `established`).
- `M7b.layout.horizontal_scroll` — content overflows the small viewport (status `fail`, severity 3, `fixable: advisory`, axis `search`, confidence `directional`).
- `M7b.taptarget.too_small` — interactive targets too small/close (status `warn`, severity 3, `fixable: advisory`, axis `search`, confidence `directional`).
Each finding: `evidence.observed` quotes the page (the meta tag string, the overflowing selector/width, the target geometry); `verification.reproduce` is the runnable command above; `expected_impact` is banded + confidence-tagged (no naked %).
Honesty
- Mobile-friendliness is a usability baseline, not a strong positive ranking lever — a fast, well-built desktop-only site does not get a ranking *boost* for adding a viewport tag; it removes a usability liability. Frame fixes as removing risk, not gaining rank.
- Google retired the standalone "Mobile-Friendly Test" tool and the page-experience badge; there is no single mobile-friendly ranking flag to "win." Don't ship that myth.
- A present viewport meta does not prove the layout is actually responsive — confirm with the rendered snapshot, don't infer responsiveness from the tag alone.
Read more
name: seo-mobile description: Audit mobile-friendliness of a page from the PageSnapshot — verify the viewport meta, no horizontal-scroll/fixed-width layouts, adequate tap targets, legible base font, and mobile/desktop content parity — and generate the viewport meta when missing. Module M7b. Feeds the Search SEO score. allowed-tools: Read, Grep, Glob, WebFetch, Bash
seo-mobile (M7b)
Google indexes mobile-first: the mobile rendering of a page is the canonical one for ranking. This module checks that a page is usable on a small viewport. Layout problems that hurt mobile usability often surface as CLS — cross-check `references/cwv-thresholds.md`.
Audits
Working from the PageSnapshot (`rendered_dom` if present, else `raw_html`): 1. **Viewport meta**: a `<meta name="viewport">` exists with `width=device-width` and `initial-scale=1`. Flag missing, fixed-width (`width=1024`), or zoom-blocking (`user-scalable=no`, `maximum-scale=1`) values — the last also harms accessibility. 2. **No horizontal scroll**: detect fixed-width containers / large absolute widths that force the viewport wider than the device (content overflowing a ~360 px small viewport). 3. **Tap-target size**: interactive elements (links, buttons, form controls) should be large enough and spaced so adjacent targets are not easily mis-tapped. 4. **Legible base font**: body text rendered at a readable base size, not a desktop-only small size that forces pinch-zoom on mobile. 5. **Content parity**: the mobile DOM must contain the same primary content, headings, structured data, and links as desktop — mobile-first indexing ranks what is in the mobile render, so hidden/stripped mobile content is a ranking risk.
Fixes
- **AUTO** (`fixable: auto`): inject `<meta name="viewport" content="width=device-width, initial-scale=1">` into `<head>` when absent. Deterministic, additive, verifiable — emitted as a diff for `fix`.
- **ADVISORY** (`fixable: advisory`): fixed-width/overflow layouts, tap-target sizing, base-font, and parity gaps depend on CSS, design system, and JS — high breakage risk. The tool diagnoses and prioritizes but does **not** auto-edit layout code. **Never invent** breakpoint values or pixel sizes — report observed values or leave a clearly-marked TODO for the user.
Verification
- Method `dom_assert`: assert against the snapshot (viewport meta presence/content, computed widths, target geometry).
- Reproduce the deterministic part (viewport meta presence/content) offline: `node ${CLAUDE_SKILL_DIR}/../../scripts/parse-html.mjs --url <u>` (or `--file <path>`) — inspect `head_hygiene.viewport`. Tap-target/overflow geometry is a `manual_review` pass over the rendered snapshot.
- Tap-target and overflow checks need the **rendered** snapshot (computed layout). When only `raw_html` is available and layout cannot be resolved, status is `needs_api`, never a false `pass`.
Findings
Emit findings per `schema/finding.schema.json`. Examples:
- `M7b.viewport.missing` — no viewport meta (status `fail`, severity 3, `fixable: auto`, axis `search`, confidence `established`).
- `M7b.viewport.user_scalable_no` — viewport disables zoom (status `warn`, severity 3, `fixable: advisory`, axis `search`, confidence `established`).
- `M7b.layout.horizontal_scroll` — content overflows the small viewport (status `fail`, severity 3, `fixable: advisory`, axis `search`, confidence `directional`).
- `M7b.taptarget.too_small` — interactive targets too small/close (status `warn`, severity 3, `fixable: advisory`, axis `search`, confidence `directional`).
Each finding: `evidence.observed` quotes the page (the meta tag string, the overflowing selector/width, the target geometry); `verification.reproduce` is the runnable command above; `expected_impact` is banded + confidence-tagged (no naked %).
Honesty
- Mobile-friendliness is a usability baseline, not a strong positive ranking lever — a fast, well-built desktop-only site does not get a ranking *boost* for adding a viewport tag; it removes a usability liability. Frame fixes as removing risk, not gaining rank.
- Google retired the standalone "Mobile-Friendly Test" tool and the page-experience badge; there is no single mobile-friendly ranking flag to "win." Don't ship that myth.
- A present viewport meta does not prove the layout is actually responsive — confirm with the rendered snapshot, don't infer responsiveness from the tag alone.
The SEO + AI-search (GEO/AEO) optimization toolkit for Claude Code — two-score audit + opt-in fixer. Built for 2026-2027.
Repo: Hainrixz/claude-seo-ai
Other skills on claude-seo-ai.
- /audit
Audit a website or web codebase for SEO and AI-search (GEO/AEO) — produces two independent 0-100 scores (Search SEO + AI Visibility) plus a prioritized, evidence-backed report. Read-only; never writes files. Use when the user asks to audit, analyze, check, or score a site's SEO,
Open skill - /fix
Opt-in fixer (the /claude-seo-ai:fix command). Applies the safe, deterministic SEO/AI-search fixes from an audit to the user's code — meta viewport/charset/lang, JSON-LD, robots.txt AI directives, hreflang, sitemaps, OG/Twitter cards, image dimensions, canonical, llms.txt.
Open skill - /geo
Analyze and score only a page's AI-search visibility (GEO/AEO) — answer extractability, fact density, AI-crawler access, entity linking, and llms.txt — and report an AI Visibility score with a citability breakdown. Read-only. Use for "will AI engines cite this?", GEO/AEO, or
Open skill - /score
Recompute and display the two scores (Search SEO + AI Visibility) from the most recent audit's findings, without re-crawling. Use to re-show or refresh the scores after an audit, or to score a saved findings JSON file.
Open skill - /seo-ai-crawlers
Audit AI crawler access and citability for a page — confirm retrieval/citation bots (OAI-SearchBot, Claude-SearchBot, PerplexityBot) are allowed and the Googlebot vs Google-Extended split is correct, classify training vs search/retrieval vs user-fetch user-agents, check the page
Open skill - /seo-core-web-vitals
Audit Core Web Vitals & page performance — measure LCP, INP, and CLS against p75 field thresholds, diagnose render-blocking resources, unoptimized images, and layout-shift sources, and produce prioritized, advisory-only remediation guidance. Module M15. Feeds the Search SEO
Open skill