What Is Mobile-First Indexing?

What mobile-first indexing means

Mobile-first indexing means that Google predominantly uses the mobile version of a website for indexing and ranking. When Google's algorithms evaluate a website to determine its ranking in search results, they primarily consider the content, structure, and performance of the mobile site.

Google's index contains a record of websites and their content. Before mobile-first indexing, this record was primarily based on the desktop version of web pages. With mobile-first indexing, the mobile version is the primary source for this record. This shift signifies that if a website's mobile version has less content or a different structure than its desktop version, Google will index and rank based on the mobile content.

Why Google switched (2016 → 2023 full rollout)

Google initiated the move towards mobile-first indexing in 2016. This change was a response to the increasing prevalence of mobile browsing. By the mid-2010s, a significant portion of internet traffic originated from mobile devices. Google's goal was to align its indexing process with how most users experienced the web.

The rollout was gradual. Initially, Google only applied mobile-first indexing to new websites or those that were already mobile-friendly. Over several years, Google systematically migrated more sites. The full rollout of mobile-first indexing for all sites was completed in October 2023. This completion means that for virtually all websites, Google's main index and ranking signals are derived from the mobile version of their content. Consequently, any content present only on the desktop version of a site may not be indexed or considered for ranking.

Content hidden on mobile is not indexed

When a website implements accordions, tabs, or expandable sections on its mobile version, content within these hidden elements is still considered by Google for indexing. However, the historical weight given to this content has varied. In earlier iterations of mobile-first indexing, there was a concern that content not immediately visible on page load might be de-prioritized.

Google has clarified that content hidden within accordions or tabs on mobile pages is generally treated the same as visible content, provided it is part of the primary HTML and not loaded asynchronously without proper linking or through user interaction that Googlebot cannot simulate. The critical distinction is that desktop-only content, meaning content that Googlebot can only access when crawling a desktop version of a page, is not indexed at all. If the content is present in the mobile HTML and simply styled to be hidden or revealed by user action (like a click on an accordion), it can be indexed. The key principle is that the mobile version of the page should contain all important content.

Structured data must match across breakpoints

Structured data, such as Schema.org markup, provides search engines with explicit information about a page's content. For mobile-first indexing, it is important that the structured data present on the desktop version of a page is also present and consistent on the mobile version.

If structured data is only included on the desktop version, Google may not discover or utilize it. This can lead to missed opportunities for rich results in the search engine results pages (SERPs). The structured data on both versions should accurately reflect the page's content and intent. There should be parity in the information conveyed through structured data, regardless of whether the user agent is desktop or mobile.

Responsive vs separate m. subdomains

There are primarily two technical approaches to serving content for mobile users: responsive design and separate URLs (often an m. subdomain).

• Responsive Web Design: This approach uses the same URL and the same HTML code for all devices. CSS media queries are used to adjust the layout and content presentation based on the screen size and capabilities of the device. Google recommends responsive design because it simplifies crawling and indexing. There is one version of the content, which Googlebot can easily process regardless of the user agent it is simulating.

  • Example: www.example.com/product-page displays differently on desktop and mobile through CSS adjustments.

• Separate URLs (m. subdomain): This approach serves different HTML pages on different URLs based on the device. For instance, a desktop user might see www.example.com, while a mobile user is redirected to m.example.com. When using separate URLs, it is critical to implement correct annotations:

  • rel="alternate" tags on the desktop page pointing to the mobile page.
  • rel="canonical" tags on the mobile page pointing to the desktop page.
  • HTTP Vary headers to signal to Googlebot that the served content can vary based on the user agent.

  If these annotations are missing or incorrect, Google may struggle to understand the relationship between the two pages, potentially leading to indexing issues or diluted ranking signals. The content on the m. subdomain becomes the primary source for indexing.

  • Example: Desktop version at www.example.com/item1 and mobile version at m.example.com/item1, with appropriate rel="alternate" and rel="canonical" tags.

Regardless of the implementation, the core requirement for mobile-first indexing is that the mobile version of the content is complete and high-quality.

How LemRank audits mobile parity

LemRank's site audit feature helps identify potential issues related to mobile-first indexing by simulating Googlebot's behavior. When you initiate a site audit in LemRank, the crawler:

1. Respects robots.txt directives: The crawler adheres to the rules specified in your robots.txt file, ensuring that it only accesses pages you permit search engines to crawl.
2. Uses a 10 requests/second rate limit: To avoid overwhelming your server, the crawler limits its request rate. This ensures that the audit process does not negatively impact your site's performance.
3. Conducts re-scans weekly: Audits are performed on a weekly cadence to provide ongoing monitoring. This helps detect new issues or verify that previously identified problems have been resolved.

The audit identifies discrepancies between mobile and desktop content that could impact your mobile-first indexing performance. For example, LemRank can detect:

• Missing Content on Mobile: If certain key content blocks, paragraphs, or images are only present in the desktop HTML and completely omitted from the mobile HTML, LemRank flags this. This helps you ensure that all valuable information is accessible to Googlebot on the mobile version.
• Inconsistent Structured Data: The audit compares structured data implementation across desktop and mobile versions of pages. It reports instances where structured data is absent from the mobile version or contains significant discrepancies compared to the desktop version.
• Mobile Usability Issues: While not directly an indexing issue, poor mobile usability can indirectly impact rankings. LemRank identifies issues like small font sizes, unclickable elements, or content that requires excessive zooming, which can lead to negative user experience signals.
• Mobile-Only Errors: Errors that specifically occur when a page is rendered or accessed by a mobile user agent, such as JavaScript errors that prevent content from loading on mobile.

By regularly auditing your site with LemRank, you can identify and rectify issues that might prevent your site from being effectively indexed and ranked under Google's mobile-first indexing paradigm.

Related

• What Is Core Web Vitals
• SERP features explained