Install
$ agentstack add skill-hainrixz-claude-seo-ai-seo-mobile ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
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):
- Viewport meta: a `
exists withwidth=device-widthandinitial-scale=1. Flag missing, fixed-width (width=1024), or zoom-blocking (user-scalable=no,maximum-scale=1`) values — the last also harms accessibility. - 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).
- Tap-target size: interactive elements (links, buttons, form controls) should be large enough and spaced so adjacent targets are not easily mis-tapped.
- Legible base font: body text rendered at a readable base size, not a desktop-only small size that forces pinch-zoom on mobile.
- 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 `intowhen absent. Deterministic, additive, verifiable — emitted as a diff forfix`. - 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(or--file) — inspecthead_hygiene.viewport. Tap-target/overflow geometry is amanual_reviewpass over the rendered snapshot. - Tap-target and overflow checks need the rendered snapshot (computed layout). When only
raw_htmlis available and layout cannot be resolved, status isneeds_api, never a falsepass.
Findings
Emit findings per schema/finding.schema.json. Examples:
M7b.viewport.missing— no viewport meta (statusfail, severity 3,fixable: auto, axissearch, confidenceestablished).M7b.viewport.user_scalable_no— viewport disables zoom (statuswarn, severity 3,fixable: advisory, axissearch, confidenceestablished).M7b.layout.horizontal_scroll— content overflows the small viewport (statusfail, severity 3,fixable: advisory, axissearch, confidencedirectional).M7b.taptarget.too_small— interactive targets too small/close (statuswarn, severity 3,fixable: advisory, axissearch, confidencedirectional).
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Hainrixz
- Source: Hainrixz/claude-seo-ai
- License: MIT
- Homepage: https://tododeia.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.