When the user wants to optimize for mobile-first indexing or fix mobile usability. Also use when the user mentions "mobile-friendly," "mobile-first indexing," "mobile SEO," "responsive design," "mobile adaptation," "mobile viewport," "viewport meta," "touch targets," "font size mobile," "AMP," or "Accelerated Mobile Pages." For viewport meta, use page-metadata.
Start a fresh conversation. Replace the highlighted placeholders.
Use mobile-friendly to assess and prioritize mobile-first indexing and usability fixes for [site or page], covering responsive layout, mobile/desktop content parity, viewport, text, touch targets, and intrusive interstitials.
Required inputs
[site or page]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: mobile-friendlydescription: When the user wants to optimize for mobile-first indexing or fix mobile usability. Also use when the user mentions "mobile-friendly," "mobile-first indexing," "mobile SEO," "responsive design," "mobile adaptation," "mobile viewport," "viewport meta," "touch targets," "font size mobile," "AMP," or "Accelerated Mobile Pages." For viewport meta, use page-metadata.metadata: version: 1.1.2
SEO Technical: Mobile-Friendly
Guides mobile-first indexing optimization and mobile usability. Google uses the mobile version of pages for indexing and ranking; mobile-friendliness is a ranking factor.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Scope (Technical SEO)
Mobile-first indexing: Google primarily crawls and indexes mobile version
Mobile adaptation: Responsive design, viewport, breakpoints
Content parity: Mobile and desktop content should match (or mobile preferred)
Mobile usability: Viewport, font size, touch targets, no intrusive interstitials
AMP: Accelerated Mobile Pages—status and when to consider
Initial Assessment
Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
Identify:
Site type: Responsive, separate AMP, dynamic serving
Content parity: Does mobile show same content as desktop?
Without viewport: Desktop layout shrunk; horizontal scroll; fails Mobile-Friendly Test. See page-metadata.
Mobile Usability Checklist
Element
Guideline
Viewport
See above; required for mobile-friendly
Font size
16px minimum for body text; avoid zooming to read
Touch targets
Buttons/links ≥48×48px; adequate spacing between taps
Content width
No horizontal scrolling; content fits viewport
Intrusive interstitials
Avoid popups that block main content on mobile
Common Issues
Issue
Fix
Content hidden on mobile
Show critical content; avoid accordion/tabs for primary content
Flash / unsupported
Replace with HTML5 alternatives
Text too small
Use base font ≥16px; avoid font-size in px <12
Links too close
Increase tap target size; add padding
Responsive vs. Separate URLs
Approach
When
Note
Responsive
Preferred
Single URL; same HTML, CSS media queries
Dynamic serving
Same URL, different HTML by user-agent
Ensure mobile content parity
Separate URLs
m.example.com
Use canonical + hreflang; see canonical-tag, page-metadata
Accelerated Mobile Pages (AMP)
AMP is a web component framework for fast-loading pages. Status (2024–2025): Still supported; no longer required for Top Stories or ranking.
Aspect
Note
Ranking
No ranking advantage over well-optimized responsive pages
Top Stories
AMP no longer required since 2021; Core Web Vitals suffice
When to consider
News sites, ad-heavy pages, very slow hosting—but responsive + CWV usually better
Alternative
Responsive design + core-web-vitals optimization; SSR/SSG; see rendering-strategies
Recommendation: For most sites, prioritize responsive design and Core Web Vitals over AMP. AMP adds maintenance (separate AMP HTML); modern optimization offers similar performance with more flexibility.
Output Format
Mobile Usability status: Pass/fail from GSC or Mobile-Friendly Test