Adapting to mobile-first indexing takes more than shrinking the layout. First, check that the mobile version has the same primary content as the desktop version, Google can access and render the content, and each page has the correct counterpart on the other version. Google’s official guidance explains that indexing and ranking are based on the mobile content crawled by its smartphone agent. Not having a mobile version does not mean a site cannot appear in search results, but Google still strongly recommends creating a mobile-friendly version.
Identify your site architecture first to determine what to check
The settings you need to check depend on your site architecture. Google recommends responsive web design because it is easier to implement and maintain, not because other architectures are unacceptable.
- Responsive design: The same URL serves the same HTML, with the display adapting to the screen size.
- Dynamic serving: The same URL serves different HTML depending on the device. Check device detection and response header settings.
- Separate URLs: Desktop and mobile versions each have their own URLs. In addition to content differences, check redirects and make sure each page has the correct counterpart.
The additional checks for differences between versions in Google’s guidance mainly apply to dynamic serving and separate-URL setups. Not every check calls for a change to a responsive website.
Content can be rearranged, but should not be reduced to a brief summary
Consistency does not mean the two versions must look identical. It means the mobile version must retain the same primary information. For example, if a desktop product page includes specifications, instructions, and important images, the mobile version should not contain only the product name and a purchase button.
- Compare the primary text, headings, and important images to identify anything missing from the mobile version.
- Check that image alt text, descriptive titles, captions, and filenames are consistent.
- Long content can be moved into collapsible sections or tabs, but primary information must not be removed in the process.
These adjustments help ensure the mobile version has complete content available for indexing, but they do not guarantee higher rankings.
Make sure crawlers can see the content, not just users
Being able to open a page on a phone does not mean Google can retrieve all its content. Compare the robots meta tags on both versions to ensure mobile pages intended for indexing have not mistakenly been set to noindex. Also confirm that robots.txt does not block resource URLs that need to be crawled.
Primary content should load without requiring a user to swipe, click, or type. For example, specifications can appear in a collapsible section, but if they load only after a click, the loading method needs to change. As Google’s guidance recommends, use the URL Inspection tool to confirm that the relevant content is visible in the rendered page.
Match separate URLs page by page instead of redirecting them all to the homepage
If the two versions use different URLs, each desktop page with distinct content should have an equivalent mobile page. For example, different product pages should not all redirect to the mobile homepage. The official guidance states that, once mobile-first indexing is enabled, redirecting multiple pages to a single URL in this way will prevent the affected pages from being indexed.
Check for page errors as well: if a desktop page works normally but its mobile counterpart displays an error, this also affects whether the page can be indexed. Checks and fixes therefore need to go beyond the homepage: confirm that each content page has a working mobile counterpart.
Mobile-first indexing: perspectives from across the web
Do you still need to maintain a desktop version under mobile-first indexing?
You should still cater to desktop users; there is no need to abandon the desktop version because of mobile-first indexing. Neil Patel notes that some features or elements are unavailable or less useful on phones, so the desktop experience still matters. The two versions can adapt their layouts to different screens and usage contexts, but the mobile version must retain the same primary content.
How can you keep checking for differences between the two versions when a site has many pages?
Change detection tools can compare crawl results for the mobile and desktop versions to help identify differences at scale and monitor unexpected changes. Screaming Frog notes that this type of comparison can also be used for JavaScript and non-JavaScript versions. After finding differences, you still need to check each one to determine whether it involves primary content that should be retained.
What should you check in the mobile version's structured data?
Check that the URLs in the mobile version's structured data are correct, and look for data extraction errors. If you use Data Highlighter to provide structured data, Google recommends regularly checking its dashboard for extraction errors. You can also use the URL Inspection tool to confirm that the relevant content is visible in the rendered page.
What are the key checks for videos on the mobile version?
Google recommends using supported video formats and tags, avoiding video URLs that change with every page load, and using the same video structured data on the mobile and desktop versions. Videos should also be placed where mobile users can easily find them. If users have to scroll a long way down to see a video, its ranking may be affected.
References
- 行動版內容優先索引系統的最佳做法 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Do you still need to maintain a desktop version under mobile-first indexing?; How can you keep checking for differences between the two versions when a site has many pages?
- A Complete Guide to Mobile SEOneilpatel.com · 2026-04-06T19:00:00+00:00 — Discusses: Do you still need to maintain a desktop version under mobile-first indexing?
- Screaming Frog SEO Spider Update – Version 15.0www.screamingfrog.co.uk · 2021-04-12T08:13:12+00:00 — Discusses: How can you keep checking for differences between the two versions when a site has many pages?



