kostja94/marketing-skills

mobile-friendly

When the user wants to optimize for mobile-first indexing or fix mobile usability.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/kostja94/marketing-skills --skill mobile-friendly

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

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

按任务相关推荐

来自同一仓库

更多 Skills

全部 Skills
kostja94
社区

youtube-seo

When the user wants to optimize YouTube videos for search, create video descriptions, or improve channel visibility. Also use when the user mentions "YouTube SEO," "YouTube description," "YouTube tags," "YouTube thumbnail," "YouTube title," "YouTube channel," or "video SEO." For YouTube ads, use youtube-ads.

1小时安装量
3
GitHub Stars
1127
最近更新
11月6日
kostja94
社区

brand-visual-generator

When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics). Also use when the user mentions "brand style guide," "visual identity," "design system," "typography," "color palette," "brand guidelines," "AI brand aesthetics," "brand colors," "font choices," "spacing system," "design tokens," "motion," "distinctive design," "frontend aesthetics," "PowerPoint theme," "Google Slides brand," or "slide master colors." For brand story,

1小时安装量
2
GitHub Stars
1115
最近更新
11月6日
kostja94
社区

medium-posts

When the user wants to write, publish, republish, or optimize posts on Medium.com (canonical tags, distribution, Medium SEO). Also use when the user mentions "Medium," "Medium article," "Medium story," "Medium publishing," "canonical Medium," or "publish on Medium." Not for general parasite SEO when Medium is not the target platform—use parasite-seo. For AI search visibility strategy, use generative-engine-optimization.

1小时安装量
2
GitHub Stars
1115
最近更新
11月6日
kostja94
社区

breadcrumb-generator

Deprecated compatibility entry for Breadcrumb construction. This component is now maintained in Bricks; install and use component-builder to build a new Breadcrumb.

1小时安装量
1
GitHub Stars
1115
最近更新
11月6日