agentleFS
gaznilgaznil/seo-skills-by-gaznil/skills/mobile-friendly/SKILL.md

mobile-friendly

Skill0 starsChanged 3 months agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site URL.

    line 24
  2. Distinctive:

    Responsive / viewport: Check viewport meta; breakpoints.

    line 111
  3. Distinctive:

    AMP: Only if legacy or specific use case

    line 113

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site URL.

Identify:

  1. Site type: Responsive, separate AMP, dynamic serving
  2. Content parity: Does mobile show same content as desktop?
  3. Tools: GSC Mobile Usability report; Mobile-Friendly Test

Mobile-First Indexing Requirements

RequirementAction
Content parityMobile version must include same primary content as desktop; avoid hiding key content on mobile
Structured dataSame schema on mobile and desktop; ensure mobile URLs in schema
MetadataSame title, meta description on mobile
MediaImages should be crawlable; avoid lazy-loading above-fold images

Responsive Design & Mobile Adaptation

Responsive design = Single HTML; CSS media queries adapt layout to screen size. Preferred for SEO: one URL, no duplicate content.

PrinciplePractice
Mobile-firstDesign for mobile first; enhance for desktop
Fluid layoutUse %, vw, flex, grid; avoid fixed pixel widths
BreakpointsCommon: 320px, 768px, 1024px, 1280px; match device widths
ImagesResponsive images (srcset, sizes); see image-optimization

Viewport

The viewport meta tag tells browsers how to scale and size the page on mobile. Required for mobile-friendly pages.

<meta name="viewport" content="width=device-width, initial-scale=1">
AttributePurpose
width=device-widthMatch viewport to device screen width
initial-scale=11:1 scale on load; prevents zoom
maximum-scaleAvoid disabling zoom (accessibility)
user-scalable=noAvoid—hurts accessibility

Without viewport: Desktop layout shrunk; horizontal scroll; fails Mobile-Friendly Test. See page-metadata.

Mobile Usability Checklist

ElementGuideline
ViewportSee above; required for mobile-friendly
Font size16px minimum for body text; avoid zooming to read
Touch targetsButtons/links ≥48×48px; adequate spacing between taps
Content widthNo horizontal scrolling; content fits viewport
Intrusive interstitialsAvoid popups that block main content on mobile

Common Issues

IssueFix
Content hidden on mobileShow critical content; avoid accordion/tabs for primary content
Flash / unsupportedReplace with HTML5 alternatives
Text too smallUse base font ≥16px; avoid font-size in px <12
Links too closeIncrease tap target size; add padding

Responsive vs. Separate URLs

ApproachWhenNote
ResponsivePreferredSingle URL; same HTML, CSS media queries
Dynamic servingSame URL, different HTML by user-agentEnsure mobile content parity
Separate URLsm.example.comUse 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.

AspectNote
RankingNo ranking advantage over well-optimized responsive pages
Top StoriesAMP no longer required since 2021; Core Web Vitals suffice
When to considerNews sites, ad-heavy pages, very slow hosting—but responsive + CWV usually better
AlternativeResponsive 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
  • Responsive / viewport: Check viewport meta; breakpoints; fluid layout
  • Content parity: Mobile vs desktop content check
  • AMP: Only if legacy or specific use case
  • Fixes: Prioritized by impact

Related Skills

  • page-metadata: Viewport meta tag; required for mobile
  • core-web-vitals: CWV measured on mobile; replaces AMP for Top Stories; LCP, INP, CLS
  • canonical-tag: Separate mobile URLs; hreflang for mobile
  • image-optimization: Responsive images; mobile LCP
  • rendering-strategies: SSR/SSG for fast mobile load
  • google-search-console: Mobile Usability report

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.