Mobile Friendly

作者 kostja948dd89c57395e无许可证1K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库2天前更新

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.

仅含说明Marketing & Sales
AI 生成的概览

指导移动优先索引与移动端可用性优化的技术 SEO 技能。

功能
提供移动优先索引要求、响应式设计、视口 meta 标签和移动端可用性检查方面的指导。内容涵盖内容一致性、触摸目标、字体大小、侵入式插页以及 AMP 现状。输出包含按优先级排序的移动 SEO 修复建议的评估结果。
适用场景
适用于为移动优先索引优化网站或修复移动端可用性问题的场景。当用户提到移动友好、移动 SEO、响应式设计、视口 meta、触摸目标或 AMP 时也可使用。
运行要求
无需脚本或特殊工具,仅为说明性内容。可选参考项目上下文以及 Google Search Console、Mobile-Friendly Test 等外部 SEO 工具。

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:

  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.

html
<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

来源与署名

来源:kostja94/marketing-skills位于skills/seo/technical/mobile-friendly提交8dd89c5

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架