# 移动端 SEO 完整指南

> 来源：Google Search Central

---

* Ranking and search appearance
  ** Visual Elements gallery  **
  ** Title links  **
  ** Snippets  **
  ** Images  **
  ** Videos  **
  ** Structured data  **
  ** Favicons  **

  * Site-specific guides
  ** Ecommerce  **
  ** International and multilingual sites  **

  * Data analysis
  ** Get started with Search Console  **
  ** Debug traffic drops  **
  ** Using Search Console and Google Analytics data for SEO  **
  ** Get started with Google Trends  **

[ Support ](https://developers.google.com/search/help) [ Blog ](https://developers.google.com/search/blog) [ What's new ](https://developers.google.com/search/news)

  ** All updates  **
  ** Documentation updates  **
  ** Ranking updates  **
  ** New YouTube videos  **
  ** Recent podcast episodes  **

[ Events ](https://developers.google.com/search/events) [ Case studies ](https://developers.google.com/search/case-studies)

`/`

  * English
  * Deutsch
  * Español
  * Español – América Latina
  * Français
  * Indonesia
  * Italiano
  * Polski
  * Português – Brasil
  * Tiếng Việt
  * Türkçe
  * Русский
  * العربيّة
  * हिंदी
  * ภาษาไทย
  * 中文 – 简体
  * 中文 – 繁體
  * 日本語
  * 한국어

Sign in

  ** Documentation **

[Search Console](https://goo.gle/searchconsole)

[ ](https://developers.google.com/search)

  ** Google Search Central **

  ** Documentation  **
    * More 
  ** Support  **
  ** Blog  **
  ** What's new  **
    * More 
  ** Events  **
  ** Case studies  **

  **Introduction**
  * Search Essentials

    **Overview**
    **Technical requirements**
    **Spam policies**

  * SEO fundamentals

    **SEO Starter Guide**
    **How Google Search works**
    **Creating helpful, reliable, people-first content**
    **Do you need an SEO?**
    **Maintaining your site's SEO**
    **Developer's guide to Search**
    **Get your website on Google**
    **Guidance on using generative AI**

  * Crawling and indexing

    **Overview**
    **File types Google can index**
    **URL structure**
    **Links**
    * Sitemaps

      **Learn about sitemaps**
      **Build and submit a sitemap**
      **Manage sitemaps with sitemap index file**
      * Sitemap extensions

        **Image sitemaps**
        **News sitemaps**
        **Video sitemaps and alternatives**
        **Combining sitemap extensions**

    * Crawler management

      **Ask Google to recrawl your URLs**
      **Troubleshoot crawl errors**
      * Google crawlers

        **List of Google crawlers**
        **Googlebot**
        **Reduce the Google crawl rate**
        **Verifying Googlebot and other Google crawlers**

    * robots.txt

      **Introduction to robots.txt**
      **How Google interprets the robots.txt specification**

    * Canonicalization

      **What is URL canonicalization**
      **How to specify a canonical URL with rel="canonical" and other methods**
      **Fix canonicalization issues**

    **Mobile site and mobile-first indexing**
    * AMP

      **AMP on Google Search guidelines**
      **Understand how AMP works in search results**
      **Enhance AMP content**
      **Validate AMP content**
      **Remove AMP content**

    * JavaScript

      **Understand the JavaScript SEO basics**
      **Fix search-related JavaScript problems**
      **Fix lazy-loaded content**
      **Dynamic rendering as a workaround**

    * Page and content metadata

      **Page metadata**
      * Meta tags

        **Meta tags and HTML attributes that Google supports**
        **Robots meta tag, data-nosnippet, and X-Robots-Tag**
        **noindex**

      **rel attributes**

    * Removals

      **Control what you share with Google**
      **Page removals**
      **Image removals**
      **Redacted information**

    * Site moves and changes

      **Redirects and Google Search**
      * Site moves

        **Changing your hosting**
        **Move a site with URL changes**

      **A/B testing**
      **Temporarily pause or disable a website**

  * Ranking and search appearance

    **Overview**
    **AI features**
    **Byline dates**
    **Favicons**
    **Featured snippets**
    **Flexible Sampling**
    **Google Discover**
    **Images**
    * Local features

      **Business details**
      **Top Places List**
      **Opting out of local search results**

    * Page experience

      **Understanding page experience**
      **Core Web Vitals**
      **Interstitials and dialogs**
      **Get started with signed exchanges on Google Search**

    **Preferred sources**
    * Ranking systems

      **A guide to Google Search ranking systems**
      **Reviews system**

    * Ranking updates

      **List of ranking updates**
      **Core updates**
      **Spam updates**

    **Site names**
    **Sitelinks**
    **Snippets**
    * Structured data

      **Understand how structured data works**
      **Structured data general guidelines**
      **Enriched search results**
      **Generate structured data with JavaScript**
      * Feature guides

        **All structured data features**
        **Article**
        **Book actions**
        **Breadcrumb**
        **Carousel**
        **Course list**
        **Dataset**
        **Discussion forum**
        **Education Q&A**
        **Employer aggregate rating**
        **Fact check**
        **Event**
        **FAQ**
        **Image metadata**
        **Job posting**
        **Local business**
        **Math solver**
        **Movie carousel**
        **Organization**
        * Shopping

          **Overview**
          **Product snippet**
          **Merchant listing**
          **Variants**
          **Loyalty program**
          **Merchant return policy**
          **Merchant shipping policy**

        **Profile page**
        **Q&A**
        **Recipe**
        **Review snippet**
        **Software app**
        **Speakable**
        **Subscription and paywalled content**
        **Vacation rental**
        **Video**

    **Title links**
    * Translated features

      **Translated results**
      **Ad networks and translation-related Google Search features**

    **Videos**
    **Visual Elements gallery**
    * Web Stories

      **Enable Web Stories on Google**
      **Best practices for creating Web Stories**
      **Web Story content policy**

    * Early Adopters Program

      **Package tracking**
      **Structured data carousels (beta)**

  * Monitoring and debugging

    **Debug drops in Search traffic**
    * Monitor with Search Console

      **Get started with Search Console**
      **Improve SEO with a bubble chart**
      **Using Search Console and Google Analytics data for SEO**

    * Debug with search operators

      **Overview**
      **site: search operator**
      **Google Images search operators**

    * Preventing and monitoring abuse

      **Overview**
      **Prevent user-generated spam**
      **Malware and unwanted software**
      **Prevent a malware infection**
      **Social engineering (phishing and deceptive sites)**
      **Google Safe Browsing Repeat Offenders Policy**

    **Get started with Google Trends**

  * Site-specific guides

    * Ecommerce

      **Overview**
      **Where content can appear**
      **Share product data**
      **Include structured data**
      **Launch a new website**
      **Write high quality reviews**
      **Design a URL structure**
      **Ecommerce site structure**
      **Pagination, incremental page loading, and Search**

    * International and multilingual

      **Overview**
      **Managing multi-regional and multilingual sites**
      **Tell Google about localized versions of your page**
      **How Google crawls locale-adaptive pages**

    * Explicit content

      **Guidelines for sites with explicit content**
      **What to do if your site is incorrectly flagged as explicit**

  * SEO fundamentals 
  ** Introduction  **
  ** Search Essentials  **
  ** SEO Starter Guide  **
  ** How Google Search Works  **
  ** Do you need an SEO?  **
  * Crawling and indexing 
  ** Sitemaps  **
  ** robots.txt  **
  ** Meta tags  **
  ** Crawler management  **
  ** Removals  **
  ** Canonicalization  **
  ** Redirects  **
  ** JavaScript SEO  **
  * Ranking and search appearance 
  ** Visual Elements gallery  **
  ** Title links  **
  ** Snippets  **
  ** Images  **
  ** Videos  **
  ** Structured data  **
  ** Favicons  **
  * Site-specific guides 
  ** Ecommerce  **
  ** International and multilingual sites  **
  * Data analysis 
  ** Get started with Search Console  **
  ** Debug traffic drops  **
  ** Using Search Console and Google Analytics data for SEO  **
  ** Get started with Google Trends  **

  ** All updates  **
  ** Documentation updates  **
  ** Ranking updates  **
  ** New YouTube videos  **
  ** Recent podcast episodes  **

  ** Home **
  ** Search Central **
  ** Documentation **

Send feedback 

# Mobile site and mobile-first indexing best practices

Google uses the mobile version of a site's content, crawled with the [smartphone agent](/search/docs/crawling-indexing/overview-google-crawlers), for indexing and ranking. This is called mobile-first indexing. 

While it's not required to have a mobile version of your pages to have your content included in Google's Search results, it is very strongly recommended. These best practices apply to mobile sites in general, and by definition to mobile-first indexing. 

To make sure that your users have the best experience, follow the best practices detailed in this guide. 

## Create a mobile-friendly site

If you haven't already, create a mobile-friendly website so your users visiting your site through a mobile phone can have a stellar experience. There are three configurations you can choose from to create a mobile-friendly site: 

  **Responsive design:** Serves the same HTML code on the same URL regardless of the users' device (for example, desktop, tablet, mobile, non-visual browser), but can display the content differently based on the screen size. Google recommends Responsive Web Design because it's the easiest design pattern to implement and maintain.
  * Dynamic serving: Uses the same URL regardless of device. This configuration relies on [`user-agent` sniffing](https://en.wikipedia.org/wiki/Browser_sniffing) and the [`Vary: user-agent` HTTP response header](https://developer.mozilla.org/docs/Web/HTTP/Headers/Vary) to serve a different version of the HTML to different devices. 
  * Separate URLs: Serves different HTML to each device, and on separate URLs. Like dynamic serving, this configuration relies on the `user-agent` and `Vary` HTTP headers to redirect users to the device-appropriate version of the site. 

The contents of this guide only apply to dynamic serving and separate URL configurations. In case of responsive design, the content and the metadata are the same on the mobile and desktop version of the pages. 

If you use a CMS, such as Wix or Blogger, you might need to find a new mobile-friendly theme for your site if you can't modify your existing theme. Try searching for the name of your CMS and "mobile friendly", for example, "wix mobile friendly". 

## Make sure that Google can access and render your content

Make sure that Google can access and render your mobile page content and resources.

  * Use the same robots `meta` tags on the mobile and desktop site. If you use a different robots `meta` tag on the mobile site (especially the `noindex` or `nofollow` tags), Google may fail to crawl and index your page when your site is enabled for mobile-first indexing. 
  * Don't lazy-load primary content upon user interaction. Google won't load content that requires user interactions (for example, swiping, clicking, or typing) to load. [Make sure that Google can see lazy-loaded content](/search/docs/crawling-indexing/javascript/lazy-loading). 
  * Let Google crawl your resources. Some resources have different URLs on the mobile site from those on the desktop site. If you want Google to crawl your URLs, make sure that you're not blocking the URL with the [`disallow` rule](/search/docs/crawling-indexing/robots/robots_txt#disallow). 

## Make sure that content is the same on desktop and mobile

Even with the equivalent content, differences in DOM or layout between desktop and mobile page can result in Google understanding the content differently. However having the same content on the desktop and mobile version ensures that the two versions can rank for the same keywords. 

  * Make sure that your mobile site contains the same content as your desktop site.  If your mobile site has less content than your desktop site, consider updating your mobile site so that its primary content is equivalent to your desktop site. You can have a different design on mobile to maximize user experience (for example, moving content into accordions or tabs); just make sure that the content is equivalent to the desktop site, since indexing on your site comes from the mobile site.  If it's your intention that the mobile page should have less content than the desktop page, you can expect some traffic loss when your site is enabled mobile-first indexing, since Google can't get as much information from your page as before. Instead of removing content, consider moving content into accordions or tabs to save space. 
  * Use the same clear and meaningful headings on the mobile site as you do on the desktop site. 

## Check your structured data

If you have structured data on your site, make sure that it's present on both versions of your site. Here are some specific things to check: 

  * Make sure that your mobile and desktop sites have the same structured data. If you have to prioritize which types you add to your mobile site, start with [`Breadcrumb`](/search/docs/appearance/structured-data/breadcrumb), [`Product`](/search/docs/appearance/structured-data/product), and [`VideoObject`](/search/docs/appearance/structured-data/video) structured data. 
  * Use correct URLs in structured data. Make sure that URLs in the structured data on the mobile versions are updated to the mobile URLs. 
  * If you use Data Highlighter, train it on your mobile site. If you use [Data Highlighter](https://support.google.com/webmasters/answer/2692911) to provide structured data, regularly check the [Data Highlighter dashboard](https://www.google.com/webmasters/tools/data-highlighter) for extraction errors. 

## Put the same metadata on both versions of your site

Make sure that the [`title` element](/search/docs/appearance/title-link#page-titles) and the [meta description](/search/docs/appearance/snippet#meta-descriptions) are equivalent across both versions of your site. 

## Check the placement of your ads

Don't let ads harm your mobile page ranking. Follow the [Better Ads Standard](https://www.betterads.org/standards/) when displaying ads on mobile devices. For example, ads at the top of the page can take up too much room on a mobile device, which is a bad user experience 

## Check visual content

### Check your images

Make sure that the images on your mobile site follow the [image best practices](/search/docs/appearance/google-images). In particular, we recommend that you: 

  * Provide [high quality images](/search/docs/appearance/google-images#good-quality-photos).  Don't use images that are too small or have a low resolution on the mobile site. 
  * Use a [supported format for images](/search/docs/appearance/google-images#supported-image-formats).  Don't use unsupported formats or tags. For example, Google supports SVG format images, but our systems can't index a .jpg image in the `<image>` tag inside an inline SVG. 
  * Don't use URLs that change every time the page loads for images. Google won't be able to process and index your resources properly if you use constantly-changing URLs for them. 
  * Make sure that the mobile site has the same alt text for images as the desktop site.  Use [descriptive alt text](/search/docs/appearance/google-images#descriptive-alt-text) for images on your mobile site as you do on your desktop site. 
  * Make sure that the mobile page content quality is as good as the desktop page.  Use the same [titles, captions, filenames, and text](/search/docs/appearance/google-images#descriptive-titles-captions-filenames) relevant to the images on the mobile site as you do for the desktop site. 

If your site is using different image URLs for the desktop and mobile site, you may see a temporary image traffic loss while your site transitions to mobile-first indexing.  This is because the image URLs on the mobile site are new to Google indexing, and it will take some time for the new image URLs to gain enough historical search results to get a better ranking. To avoid a temporary image traffic loss, use the same image URLs across both versions of your site. If you don't mind a temporary image traffic loss, you don't need to take any action. 

### Check your videos

Make sure that the videos on your mobile site follow the [video best practices](/search/docs/appearance/video). In particular, we recommend that you: 

  * Don't use URLs that change every time the page loads for your videos. Google won't be able to process and index your resources properly if you use constantly changing URLs for them. 
  * Use a [supported format](/search/docs/appearance/video#file-types) for your videos and put videos in supported tags. Videos are identified in the page by the presence of an HTML tag, for example: `<video>`, `<embed>`, or `<object>`. 
  * Use the same video structured data on both your mobile site and desktop site. For more information, check your structured data. 
  * Place the video in an easy to find position on the page when viewed on a mobile device.  For example, it might harm the video's ranking if users need to scroll down too much to find the video on mobile page. 

## Additional best practices for separate URLs

If your site has separate URLs for the desktop and mobile versions of a page (also known as m-dot), we recommend the following additional best practices: 

  * Make sure that the error page status is the same on both the desktop and mobile sites.  If a page on your desktop site serves normal contents and your mobile site's version of that page serves an error page, this page will be missing from the index. 
  * Make sure that your mobile version doesn't have URL fragments. The fragment part of the URL is the end of the URL that starts with `#`. Most of the time, URL fragments are not indexable, these pages will be missing from the index after your domain is enabled for mobile-first indexing. 
  * Ensure that the desktop versions that serve different contents have equivalent mobile versions.  If different URLs redirect to the same URL (for example, to the home page on mobile devices) after your domain is enabled for mobile-first indexing, all these pages will be missing from the index. 
  * Verify both versions of your site in [Search Console](https://search.google.com/search-console) to make sure that you have access to data and messages for both versions. Your site may experience a data shift when Google switches to mobile-first indexing for your site. 
  * Check `hreflang` links on separate URLs. When you use `rel=hreflang` [`link` elements](/search/docs/specialty/international/localized-versions) for [internationalization](/search/docs/specialty/international/managing-multi-regional-sites), link between mobile and desktop URLs separately. Your mobile URLs' `hreflang` must point to mobile URLs, and similarly desktop URL `hreflang` must point to desktop URLs. 

Here's an example of `hreflang` for the home page of a site with separate URLs for mobile and desktop. 

### Mobile

In this example, the mobile site URL is `https://m.example.com/`.
    
        <link rel="canonical" href="https://example.com/">
    <link rel="alternate" hreflang="es" href="https://m.example.com/es/">
    <link rel="alternate" hreflang="fr" href="https://m.example.com/fr/">
    <link rel="alternate" hreflang="de" href="https://m.example.com/de/">
    <link rel="alternate" hreflang="th" href="https://m.example.com/th/">

### Desktop

In this example, the desktop site URL is `https://example.com/`.
    
        <link rel="canonical" href="https://example.com/">
    <link rel="alternate" media="only screen and (max-width: 640px)" href="https://m.example.com/">
    <link rel="alternate" hreflang="es" href="https://example.com/es/">
    <link rel="alternate" hreflang="fr" href="https://example.com/fr/">
    <link rel="alternate" hreflang="de" href="https://example.com/de/">
    <link rel="alternate" hreflang="th" href="https://example.com/th/">

  * Ensure that your mobile site has enough capacity to handle a potential increase in [crawl rate](https://support.google.com/webmasters/answer/35253) on the mobile version of your site. 
  * Verify that your [robots.txt rules](/search/docs/crawling-indexing/robots/intro) work as you intend for both versions of your site. The robots.txt file lets you specify which parts of a website may be crawled or not. In most cases, use the same robots.txt rules for both mobile and desktop versions of your site. 
  * Use the correct `rel=canonical` and `rel=alternate` `link` elements  between your mobile and desktop versions. The desktop URL is always the canonical, and the mobile version is the alternate of that URL. 

Here's an example of `rel=canonical` and `rel=alternate` for a separate URLs site setup. 

### Mobile

In this example, the mobile site URL is `https://m.example.com/` and includes a `link` element that points to the desktop URL as the canonical URL.
    
        <link rel="canonical" href="https://example.com/">

### Desktop

In this example, the desktop site URL is `https://example.com/` and includes a `link` element that points to itself as the canonical URL, followed by another `link` element that points to the mobile version as the alternate version of this URL.
    
        <link rel="canonical" href="https://example.com/">
    <link rel="alternate" media="only screen and (max-width: 640px)" href="https://m.example.com/">

## Troubleshooting

Here's a list of the most common errors that can stop sites from being enabled for mobile-first indexing or could cause a drop in ranking after a site is enabled for mobile-first indexing. If your site isn't enabled for mobile-first indexing yet, you've seen a drop in ranking after your site is enabled for mobile-first indexing, or you've received a message in Search Console, check the following list of common errors and resolve possible errors you may have: 

Errors  
---  
  
### Missing structured data

|  error What caused the issue: The mobile page doesn't have all the structured data markup that the desktop page has.  done Fix the issue

  1. Verify that the structured data is present on both versions of your site (desktop and mobile). 
  2. Make sure that your mobile and desktop sites have the same structured data.
  3. Use correct URLs in structured data. Make sure that URLs in the structured data on the mobile versions are updated to the correct URLs. 
  4. Check extraction errors for your structured data. If you use [Data Highlighter](https://support.google.com/webmasters/answer/2692911) to provide structured data, regularly check the [Data Highlighter dashboard](https://www.google.com/webmasters/tools/data-highlighter) for extraction errors. 
  5. Use the [URL Inspection tool](https://support.google.com/webmasters/answer/9012289) to check that the content is visible on the rendered page (the rendered page is how Google sees your page). 

  
  
### `noindex` tag on pages

|  error What caused the issue: A mobile page is blocked from indexing by a `noindex` tag.  done Fix the issue: Use the same robots `meta` tags on the mobile site and the desktop site. Don't use the `noindex` tag on the mobile page (otherwise, Google won't index your page when your site is enabled for mobile-first indexing).   
  
### Missing image

|  error What caused the issue: The mobile page doesn't have all the important images that the desktop page has.  done Fix the issue

  1. Make sure that your mobile site contains the same content as your desktop site. If your mobile site has less content than your desktop site, consider updating your mobile site so that its primary content is equivalent with your desktop site. Only the content shown on the mobile site is used for indexing. 
  2. Use the same robots `meta` tags on the mobile site and the desktop site. Don't use the `nofollow` tag on the mobile page (otherwise, Google won't crawl and index the images on your page when your site is enabled for mobile-first indexing). 
  3. Use a [supported format and tag for images](/search/docs/appearance/google-images#supported-image-formats). For example, Google supports SVG format images, but our systems can't index a .jpg image in the `<image>` tag inside an inline SVG. 
  4. Don't lazy-load primary content upon user interaction. Google won't load content that requires user interactions (for example, swiping, clicking, or typing) to load. [Make sure that Google can see lazy-loaded content](/search/docs/crawling-indexing/javascript/lazy-loading). 

  
  
### Blocked image

|  error What caused the issue: An important image on the mobile page is blocked by robots.txt.  done Fix the issue: Let Google crawl your resources. Some images have different URLs on the mobile site from those on the desktop site. If you want Google to crawl your URLs, don't block the URL with the [`disallow` rule](/search/doc/crawling-indexing/robots/robots_txt#disallow).   
  
### Low quality image

|  error What caused the issue: An important image on the mobile page is too small or low resolution.  done Fix the issue: Provide [high quality images](/search/docs/appearance/google-images#good-quality-photos). Don't use images that are too small or have a low resolution on the mobile site.   
  
### Missing alt text

|  error What caused the issue: An important image on the mobile page is missing alt text.  done Fix the issue: Use the same [alt text](/search/docs/appearance/google-images#descriptive-alt-text) for images on your mobile site as you do on your desktop site.   
  
### Missing page title

|  error What caused the issue: A mobile page is missing a title.  done Fix the issue: Make sure that the [titles](/search/docs/appearance/title-link#page-titles) and [meta descriptions](/search/docs/appearance/snippet#meta-descriptions) are equivalent across both versions of your site.   
  
### Missing meta description

|  error What caused the issue: A mobile page is missing the meta description.  done Fix the issue: Make sure that the [titles](/search/docs/appearance/title-link#page-titles) and [meta descriptions](/search/docs/appearance/snippet#meta-descriptions) are equivalent across both versions of your site.   
  
### Mobile URL is an error page

|  error What caused the issue: The mobile page is an error page.  done Fix the issue: Make sure error page status is the same across desktop and mobile site. If a page on your desktop site serves normal contents and your mobile site's version of that page serves an error page, this page will be missing from the index.   
  
### Mobile URL has anchor fragment

|  error What caused the issue: The mobile URL includes an anchor fragment; Google can't index URLs that include fragments.  done Fix the issue: Make sure your mobile version doesn't have URL fragments. Most of the time, fragment URLs are not indexable, and these pages will be missing from the index after your domain is enabled for mobile-first indexing.   
  
### Mobile page blocked by robots.txt

|  error What caused the issue: The mobile page is blocked by a robots.txt rule.  done Fix the issue: Verify that your robots.txt rules and robots `meta` tags work as you intended for both versions of your site. Use the same robots.txt rules for both mobile and desktop versions of your site.   
  
### Duplicate mobile page target

|  error What caused the issue: Multiple desktop pages redirect to the same mobile page.  done Fix the issue: Ensure desktop versions which serve different contents have equivalent mobile versions. If different URLs redirects to the same URL, on mobile devices, after your domain is enabled for mobile-first indexing, all these pages will be missing from the index.   
  
### Desktop site redirects to the mobile home page

|  error What caused the issue: Most or all pages on your desktop site redirect to the mobile site's home page.  done Fix the issue: Ensure the desktop version has an equivalent mobile version. If different URLs redirect to the home page on mobile devices, all these pages will be missing from the index after your domain is migrated for mobile-first indexing.   
  
### Page quality issues

|  error What caused the issue: The mobile page has issues with ads, missing content, titles, or descriptive elements for images on the page.  done Fix the issue:

  1. Don't let ads harm your mobile page ranking. Follow the [Better Ads Standard](https://www.betterads.org/standards/) when displaying ads on mobile devices. 
  2. Make sure your mobile site contains the same content as your desktop site. If your mobile site has less content than your desktop site, consider updating your mobile site so that its primary content is equivalent with your desktop site. Only the content shown on the mobile site is used for indexing. 
  3. Make sure you use the same clear and meaningful headings on the mobile site as you do on the desktop site. 
  4. Use the same [titles, captions, filenames, and text](/search/docs/appearance/google-images#descriptive-titles-captions-filenames) relevant to the images on the mobile site you do for the desktop site. 

  
  
### Video issues

|  error What caused the issue: The mobile page has a video that is not in a supported format, is placed in a difficult to find location, is missing meta descriptions, or is very slow to load.  done Fix the issue:

  1. Use a [supported format](/search/docs/appearance/video#file-types) for your videos and put them in supported tags. Videos are identified in the page by the presence of an HTML tag, for example: `<video>`, `<embed>`, or `<object>`. 
  2. Don't lazy-load primary content upon user interaction. Google won't load content that requires user interactions (for example, swiping, clicking or typing) to load. [Make sure Google can see lazy-loaded content](/search/docs/crawling-indexing/javascript/lazy-loading). 
  3. Place the video in an easy to find location on your mobile site. For example, it might harm the video's ranking if users need to scroll down too much to find the video on mobile page. 

  
  
### Hostload issues

|  error What caused the issue: Some of the hosts don't have enough hostload.  done Fix the issue: Ensure that your mobile site has enough capacity to handle a potential increase in [crawl rate](https://support.google.com/webmasters/answer/35253) on the mobile version of your site.   
  
Send feedback 

Except as otherwise noted, the content of this page is licensed under the [Creative Commons Attribution 4.0 License](https://creativecommons.org/licenses/by/4.0/), and code samples are licensed under the [Apache 2.0 License](https://www.apache.org/licenses/LICENSE-2.0). For details, see the [Google Developers Site Policies](https://developers.google.com/site-policies). Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-12-10 UTC.

Need to tell us more?  [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-12-10 UTC."],[],["Google prioritizes mobile content for indexing and ranking. Key actions include ensuring content parity between mobile and desktop versions, with identical `meta` tags, structured data, headings, and metadata. Avoid `noindex` tags, and don't block resources with `robots.txt`. Use high-quality images with consistent alt text and avoid dynamic URL changes for images and videos. For separate URLs, set desktop versions as canonical with an alternate link to the mobile version. Common errors to fix include missing content, blocked resources, and incorrect metadata.\n"]] 

  ** LinkedIn  **

Join us on LinkedIn

  ** YouTube  **

Watch our videos

  ** Blog  **

Subscribe to our RSS feed

  ** Podcast  **

Listen to Search Off the Record

  ** X (Twitter)  **

Join us on X (Twitter)

  * ### Get support

    ** Go to the help forum **
    ** Submit a question for office hours **
    ** Report spam, phishing, or malware **
    ** More support resources **
  * ### Resources

    ** Do you need an SEO? **
    ** SEO Starter Guide **
    ** Status of Search systems **
    ** Search Console documentation **
    ** Case Studies **
  * ### Tools

    ** Search Console **
    ** Rich Results Test **
    ** PageSpeed Insights **
    ** AMP Test **

[ ](https://developers.google.com/)

  ** Android **
  ** Chrome **
  ** Firebase **
  ** Google Cloud Platform **
  ** Google AI **
  ** All products **

  ** Terms **
  ** Privacy **
  * Manage cookies 

  * English
  * Deutsch
  * Español
  * Español – América Latina
  * Français
  * Indonesia
  * Italiano
  * Polski
  * Português – Brasil
  * Tiếng Việt
  * Türkçe
  * Русский
  * العربيّة
  * हिंदी
  * ภาษาไทย
  * 中文 – 简体
  * 中文 – 繁體
  * 日本語
  * 한국어
