To make mobile content crawlable and indexable by Google, the key is to ensure that Google can access and render all primary content, without being blocked by robots settings or requiring clicks or swipes to load it. The mobile version should retain the desktop version’s primary content. If the two versions use separate URLs, also check page mappings and URL formats. Before making changes, confirm how the site’s mobile version is actually implemented, rather than simply checking whether it looks right on a phone.
First, check whether URLs and content match across both versions
Google’s crawler documentation states that Google Search primarily indexes the mobile content of most websites, so most Googlebot requests come from the mobile crawler. Start by checking whether the mobile and desktop versions use the same URL, then compare the content each version actually provides.
- The mobile version should retain the same primary text and important images, rather than offering only an abridged summary of the desktop version.
- The layout can differ—for example, content can appear in collapsible sections or tabs—but displaying content in a collapsed section must not mean downloading the primary content only after a click.
- Titles, meta descriptions, and alt text for important images should also be checked against the desktop version.
Remove access restrictions and indexing blocks
Google must be able to access and render the mobile content and its required resources. If mobile images use a different set of URLs, make sure those URLs are not blocked by disallow rules in robots.txt; checking only desktop resources is not enough.
Both versions should use the same robots meta tags. For pages intended to appear in the search index, take particular care to rule out an accidental noindex setting on the mobile version: once mobile-first indexing is enabled, Google will not index pages carrying that tag. Google’s documentation also warns that nofollow on the mobile version may affect image crawling and indexing; do not treat it as the same restriction as noindex.
Lazy loading must not depend on user interaction
Google Search does not interact with web pages. If the second half of an article is retrieved only after clicking “Show more,” or images download only after a scroll event is triggered, check whether Google can see that content.
When implementing lazy loading, you can use native browser functionality for images and iframes, IntersectionObserver, or a library that supports viewport-based loading. The relevant content should load when it enters the viewport, without requiring user interaction. Content immediately visible when the page opens should not be lazy-loaded. Finally, use the URL Inspection tool to confirm that the rendered page actually displays the primary content.
Map separate mobile URLs page by page
If the two versions use different URLs, each desktop page with distinct content should have a corresponding mobile page, rather than all pages redirecting to the mobile homepage. Pages that work on desktop but display errors on mobile also affect indexing.
Also, do not use a # fragment at the end of a URL to identify a separate mobile page. Google’s documentation states that URL fragments generally cannot be indexed. For sites using separate URLs, check this alongside page-by-page mapping.
Mobile crawling and indexing: perspectives from across the web
How can you make infinite-scroll content indexable by search engines?
If a long article or list of items loads in sections through infinite scrolling, also support pagination so that each section has its own permanent URL and consistently displays the same content whenever that URL is loaded. For example, use an absolute page number as a query parameter rather than a relative date that changes over time. This helps search engines find and correctly index each section, and makes the content easier for users to share.
Is it enough for images to display correctly on mobile?
No. You also need to confirm that Google can recognize the images’ formats and markup. Google’s documentation gives an example: although Google supports SVG, it cannot index a JPG placed in an image tag within inline SVG. Important images on mobile should not be too small or have too low a resolution. You can compress high-quality images to reduce loading time, but also check that they remain crawlable.
What should sites with separate mobile URLs check for multilingual configurations and structured data?
If the two versions use different URLs, update the URLs in structured data to the correct ones. If hreflang links multilingual pages, mobile URLs should link to mobile URLs in the corresponding language, while desktop URLs should link to desktop URLs. These checks apply to sites with the relevant structured data or multilingual configurations; they do not mean every site must add these configurations.
Can robots.txt control mobile and desktop Googlebot separately?
You cannot specifically distinguish between Googlebot Smartphone and Googlebot Desktop in robots.txt. Although their HTTP user-agent headers distinguish them, both follow the same product token in robots.txt. When reviewing rules, consider their impact on both crawlers. Google’s documentation states that most websites are indexed primarily using their mobile content, so most Googlebot requests come from the mobile crawler.
References
- 行動版內容優先索引系統的最佳做法 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Is it enough for images to display correctly on mobile?; What should sites with separate mobile URLs check for multilingual configurations and structured data?
- Googlebot 簡介 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Can robots.txt control mobile and desktop Googlebot separately?
- 修正延遲載入的網站內容 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: How can you make infinite-scroll content indexable by search engines?
- Mobile-First Indexing: What It Means & Best Practiceswww.semrush.com · 2020-10-07T11:00:00Z — Discusses: Is it enough for images to display correctly on mobile?



