Your café website on a phone: what Google's mobile-first indexing page says

Google's page says: "Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." It adds that you do not need a mobile version of your pages for your content to be included in Search results, though "it is very strongly recommended". Google recommends Responsive Web Design, and says that with responsive design "the content and the metadata are the same on the mobile and desktop version of the pages". Google's page says: "The contents of this guide only apply to dynamic serving and separate URL configurations."

What is mobile-first indexing, in Google's words?

Google's page defines it in two sentences: "Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking. This is called mobile-first indexing."

It then says: "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."

For a café, our reading: what Google reads is the phone version of your pages, so that is the version that should carry your menu, hours and address; on a responsive site it is the same page.

Which kind of mobile site does Google recommend?

Google recommends responsive design. Its page says: "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 and the Vary: user-agent HTTP response header 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 page then draws a line: "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."

So the advice in the sections below about matching content and metadata across two versions is written for dynamic serving and separate URLs. On a responsive site, Google says the content and the metadata are the same on the mobile and desktop version of the pages.

What can stop Google seeing a café's content on a separate or dynamically served phone version?

Google's page limits these points to dynamic serving and separate URLs: "The contents of this guide only apply to dynamic serving and separate URL configurations." Under "Make sure that Google can access and render your content" it names three things: a different robots meta tag, content that loads only after an interaction, and blocked resources.

• Robots meta tags. "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."
• Lazy-loading. "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."
• Blocked resources. "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."

For a café, our reading: if a café had a separate phone version and its menu was not loaded until a swipe or a click, Google's page says it won't load that content. So, by Google's own scope line, these points are not advice for a responsive site.

Does the phone version need the same menu and hours as the desktop one?

Yes, on the two set-ups where there are two versions. Google's page says: "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."

It allows a different layout: "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." It gives the reason: "...having the same content on the desktop and mobile version ensures that the two versions can rank for the same keywords." And it asks for the same headings: "Use the same clear and meaningful headings on the mobile site as you do on the desktop site."

The page asks for the same metadata too: "Make sure that the title element and the meta description are equivalent across both versions of your site." Our article on titles and meta descriptions for a café covers those two.

Within the same scope, on visual content the page says: "Provide high quality images." and "Make sure that the mobile site has the same alt text for images as the desktop site." On ads, it says: "Don't let ads harm your mobile page ranking. Follow the Better Ads Standard when displaying ads on mobile devices."

For a café, our reading: with a responsive site there is one set of HTML on one URL, so there is no second version to compare. Google's page says the content and the metadata are the same on both.

How can a café check its own site?

Our free check looks at one part of this. Its list includes the item "Ready to show up in Google search.", described as: "Your home page has a title, a description and the setting that makes it fit a phone screen." Our reading: it looks for the setting that makes the home page fit a phone screen. In our words, it is not a full mobile test.

Sources

• Google Search Central, Mobile site and mobile-first indexing best practices, last updated 2025-12-10 UTC, read 3 November 2026.
• Cupán Studio, Is my café website AI ready? (cupanstudio.com/check), the things it checks, read 3 November 2026.

This is a summary of Google Search Central documentation read on 3 November 2026. The readings marked as ours are not from Google. Cupán Studio builds websites for cafés in Ireland.