10/30/2026 · By The Comppound Gecko
Mobile-First Indexing for SaaS Sites
Mobile-first indexing means Google mainly uses the mobile version of a page for indexing and ranking. For a B2B SaaS company, the practical point is this: if something is on your desktop page and missing from what a phone receives, Google may not count it. It doesn't matter that nearly all your buyers visit from a laptop, because Google's crawler still looks at the smartphone version.
Most SaaS sites use responsive design, and that removes most of the risk. The problems that remain come from design choices that strip content out at smaller screen sizes, particularly on complicated pages such as pricing tables and feature comparisons.
Why this applies even if your buyers use desktops
A common objection goes: "our analytics show that most visits come from desktop, so mobile doesn't matter". That's true for conversions, and it's a reason to focus your design work on desktop. It has no bearing on how you get indexed. Google's documentation describes its indexing as using the mobile version of a site's content, crawled with the smartphone agent, whoever your audience is.
So there are two separate questions. What should the mobile experience look like for people? That depends on your audience. What does Google's smartphone crawler receive? That needs to be complete in every case.
Where SaaS pages lose content on mobile
Say you run a 25-person analytics SaaS with a responsive site. Each of these can pass a casual look on a phone while still being a problem.
Comparison tables swapped out for a summary. A desktop table of 40 features across four plans is awkward on a phone, so designers often replace it. If the mobile version's HTML contains only "See full comparison on desktop", the detail has gone. Better options include a horizontally scrollable table, or a simple plan-by-plan list containing the same facts. Our feature comparison table guide has some layouts.
Elements removed by the framework, not just hidden. A CSS class that hides something leaves the content in the HTML, and Google can still read it. A React component that isn't rendered at all on small screens means that the content isn't there. So it's worth asking your developers which method they're using. Conditional rendering based on the screen size, such as a useMediaQuery hook deciding what to return, is the usual cause.
Content behind tabs and accordions. Using them on mobile is fine, as long as the content's already in the page. Google's documentation specifically warns about content that requires user interaction, such as clicking or swiping, to load. An accordion that fetches its text on click is a different matter from one that simply reveals existing text.
Lazy-loaded sections. Google doesn't scroll or click like a person. If content loads only when somebody scrolls, it may not be seen. Native lazy-loading for images is fine, and if you've built something custom, test it. Google has guidance on lazy loading.
Missing metadata and structured data. Titles, descriptions, canonicals and structured data should match between versions. This is rarely an issue on a responsive site, but it can happen when mobile has its own template.
Internal links in menus. A simplified mobile navigation or footer may drop links to your solutions and integrations pages. Those links help Google understand your site's structure, so a stripped-down mobile menu can weaken important pages.
Images missing alt text or replaced by smaller versions. Keep the alt text the same across sizes, and avoid very low-resolution versions for important product screenshots.
Separate mobile sites and dynamic serving
Very few SaaS companies still run an m.example.com site. But if you're serving different HTML to mobile and desktop based on the user agent, or you've got a separate mobile site, all of the above requires much closer attention. Content, metadata and links can all drift apart. Moving to responsive design is worth considering, and Google recommends it as the easiest pattern to implement and maintain.
Some SaaS companies have a variation on this: landing pages built in a separate tool, each with its own mobile version. Check those separately, since they often fall out of step with the desktop design.
How to check your own pages
Four tests will find most problems, and they don't take long.
- Inspect with Search Console. URL Inspection shows the crawled page and which crawler was used. View the HTML and search it for a phrase you know should be there, particularly one from a pricing table or feature list.
- Compare the raw HTML by user agent. Fetch a page twice, then compare the outputs:
curl -s -A "Mozilla/5.0 (Linux; Android 10; Pixel 4) AppleWebKit/537.36 Chrome/120 Mobile Safari/537.36" https://example.com/pricing > mobile.html
curl -s https://example.com/pricing > desktop.html
If your site relies on client-side logic, the raw HTML may be the same, while the rendered page differs. So:
- Compare rendered pages. Crawl the site with a tool set to a smartphone user agent with JavaScript on, then again as desktop. Compare the word counts and internal links per page. Large differences deserve a look.
- Look at it yourself. Use your browser's device emulation, or better, a real phone. Check that text is readable without zooming, buttons are easy to tap, and nothing overflows the screen. It's a usability matter as much as an SEO one.
Search Console no longer has a dedicated mobile usability report, so don't go looking for it in older guides. Lighthouse still flags many of these issues.
How much to invest in the mobile experience
The content has to be complete, and that part isn't optional. But how much you polish the mobile experience should depend on your audience.
Going back to the analytics SaaS, suppose desktop brings in the great majority of your demo requests. It would be sensible to make sure that mobile pages load quickly, read well and have a working form, and to not spend weeks perfecting the mobile version of a complicated comparison table.
There are some exceptions worth checking. Mobile traffic may be higher than you expect for paid social campaigns, and for visitors clicking links in emails or from LinkedIn. People often first see a SaaS product on their phone and return later on a laptop. So a poor mobile page can lose you someone who'd have become a desktop conversion. Look at those channels separately in your analytics, and see landing pages for SaaS paid ads.
Speed matters on mobile as well, particularly as phones have less processing power than a work laptop. Heavy JavaScript that a laptop handles without trouble can feel slow on a mid-range phone. Core Web Vitals for SaaS sites explains how to read those results. Search Console reports them separately for mobile and desktop.
What to do this week
Pick three templates: pricing, a feature page and a blog post. For each, take a phrase from deep in the page and check that it appears in the HTML in URL Inspection. Then look at your comparison tables and the mobile navigation. If everything's there, you can cross this off and move on, as this issue doesn't need ongoing attention beyond a check after each redesign.
Add that check to your technical SEO checklist. And if a redesign's coming up, it's easier to raise this before the components get built.
To have this reviewed as part of a broader technical audit, book a call with Comppound.
Frequently Asked Questions
Google mainly uses the mobile version of a page's content for indexing and ranking, crawled with a smartphone user agent. It applies whatever device your audience uses.
Yes, as the crawler looks at the mobile version even if your buyers use laptops. A responsive site usually handles most of it. The main risk is content removed on small screens.
Content that's in the HTML and hidden by design can be read. Content that only loads after someone clicks or swipes may not be seen, as Google warns in its documentation.
No. Google has one index and uses mobile-first indexing to build it. The ranking of a page on desktop can still differ from its ranking on mobile.
Still have questions? Talk to our team.
The Comppound Gecko
SEO and AI search for B2B SaaS
Comppound plans, produces and publishes search content for B2B SaaS companies. Every article is researched and drafted with AI, then reviewed by a member of the team for accuracy, clarity and usefulness before it is published.
Was this article helpful?
