Mobile-first indexing: is your site mobile-friendly?
Google indexes and ranks the mobile version of your site, not the desktop one, and has done so for every new site since 2019. If your site was built years ago without mobile in mind, that version is what Google sees, tap targets and all. Test it free with the Mobile-Friendly Test and PageSpeed Insights, then fix the specific errors they list.
Mobile-first indexing means Googlebot crawls and evaluates your site using a phone, not a desktop browser. The content, links and structured data it stores in its index come from the mobile rendering of your pages. Google finished moving every site it knows about to this model years ago; there is no desktop fallback left to fall back to.
For a Nepali business this matters more than it does for most markets. A large share of Nepal's internet traffic arrives on a phone, often on 3G or 4G, often on a mid-range Android device with a screen under 6 inches. If your site was built in 2016 by whoever was cheapest at the time, there is a real chance nobody has ever checked what it looks like on that device, and Google has been ranking that broken version for years.
What mobile-first indexing actually changed
Before 2019, Google mostly crawled with a desktop user agent and used the desktop page to decide what a page was about and how well it should rank. Mobile-first indexing flipped that: the crawler is Googlebot Smartphone, and the mobile HTML, mobile structured data, mobile internal links, and mobile page speed are what gets used for indexing and ranking, for both mobile and desktop search results.
The practical trap is a mismatch between your mobile and desktop pages. If your desktop site has a full product description, proper heading structure and internal links to related pages, but your mobile version strips half of that out to 'simplify' the layout, Google is indexing the stripped-down version. Anything that exists only on desktop is, for ranking purposes, close to invisible.
This is not a niche concern for old-fashioned sites either. It also catches sites that show different content behind tabs or accordions on mobile that are collapsed by default, sites that hide navigation links behind a hamburger menu built with JavaScript that doesn't render for the crawler, and sites where the mobile template simply has fewer words than the desktop one because someone thought that was tidier.
Test your site with the free tools
You do not need to guess. Two free Google tools tell you exactly where you stand, and both take under a minute per page.
Run both on your homepage first, then on two or three of your most important service or product pages, since mobile usability issues can vary page to page depending on which template or plugin generated them.
- Google's Mobile-Friendly Test (search.google.com/test/mobile-friendly): paste in a URL, it renders the page as Googlebot Smartphone would, shows you a screenshot of what the crawler actually sees, and lists specific usability problems like text too small or clickable elements too close together.
- PageSpeed Insights (pagespeed.web.dev): run it with the Mobile tab selected, not Desktop. It gives you a Core Web Vitals field score and a separate list of opportunities and diagnostics specific to the mobile rendering.
- Google Search Console, if you have it connected: check the Page indexing and Core Web Vitals reports there. Both are already segmented by device and reflect real visits to your actual site, not a one-off test.
- Open the site on an actual cheap Android phone over mobile data if you can. Tools catch structural problems; only your own thumb catches a button that is technically 44px wide but sits under your finger next to three others.
Fix: tap targets too small or too close together
This is the single most common flag on older Nepali business sites, usually inherited from a desktop-first template that used small text links for navigation and never adjusted them for touch.
Google's guidance is a minimum touch target of roughly 48x48 CSS pixels, with at least 8px of spacing between adjacent targets. Anything smaller and a thumb will regularly hit the wrong link, which is both a usability failure and a ranking signal.
- Increase padding on nav links, buttons and footer links, not just the visible text size. A link can look fine and still have a tiny actual clickable area if only the text itself is the target.
- Space out adjacent buttons and links, phone number, WhatsApp, and 'call now' buttons stacked tight together are a repeat offender on Nepali business sites.
- Check footer social icons and pagination controls specifically, they are the most commonly forgotten elements.
- Avoid putting two separate tap targets inline in the same line of text if you can help it, for example a linked phone number immediately next to a linked email address.
Fix: viewport not configured
If a page loads on mobile at desktop width and the user has to pinch and zoom to read it, the site is almost certainly missing a viewport meta tag, or has one set to a fixed width instead of the device width. This is a one-line fix and, if missing, likely means the whole site has never been mobile-tested since launch.
- Add <meta name="viewport" content="width=device-width, initial-scale=1"> inside the <head> of every template, not just the homepage.
- If it is already present, check it is not overridden by a fixed pixel width, content="width=1024" defeats the purpose entirely.
- Confirm the tag actually renders in the page source that Googlebot sees, view-source on the live URL, not just your CMS editor preview.
Fix: text too small to read without zooming
Google flags body text under roughly 12px as too small on mobile, and font sizes copied straight from a desktop stylesheet are a frequent cause, since 14px body text that reads fine on a 24-inch monitor is uncomfortably small on a 5.5-inch phone held at arm's length.
- Set a base body font size of at least 16px for mobile, scaling text with rem units rather than fixed pixel values makes this easier to maintain across templates.
- Check line-height too, cramped line spacing makes even correctly-sized text harder to read on a small screen.
- Watch Devanagari text specifically: Nepali script needs slightly more line-height than Latin text at the same font size to stay legible, and templates built with English-first defaults often shortchange it.
Fix: intrusive interstitials and popups
A full-screen popup that covers the content the moment a mobile visitor lands, before they have read anything, is a direct mobile usability penalty under Google's page experience guidance. This includes newsletter signup modals, app-install banners, and cookie notices that block the whole screen rather than sitting in a dismissible strip.
The rule is not that popups are banned. It is that content the user came for has to be reachable without first navigating around an obstacle covering the viewport, especially on the initial page load.
- Delay signup or promotional popups until scroll depth or a time delay, not on page load.
- Use a banner that occupies a reasonable amount of screen space rather than a full-screen overlay, particularly for legally required notices like cookie consent.
- Exempt app-install prompts and legal age or location interstitials required by law, Google's guidance carves these out explicitly.
- Test the close button itself against the tap-target size guidance above, a popup with an unusably tiny close button just creates a second problem on top of the first.
Key takeaways
- ✓Google indexes and ranks the mobile version of your site for everyone, desktop searchers included, so content missing from mobile is effectively missing from your rankings.
- ✓Test free with Google's Mobile-Friendly Test and PageSpeed Insights on the Mobile tab, then check Search Console's Page indexing report if you have it connected.
- ✓Tap targets need roughly 48x48px with 8px of spacing; cramped nav links and stacked call buttons are the most common failure on older Nepali sites.
- ✓A missing or fixed-width viewport meta tag usually means the site has never been properly mobile-tested since launch.
- ✓Full-screen popups on page load are a direct mobile usability problem; delay them or shrink them to a dismissible banner instead.
Explore the data behind this guide
Mobile-First Indexing Explained, FAQ
What is mobile-first indexing?+
It means Googlebot crawls and evaluates your site using a smartphone user agent, and the mobile version of your pages, not the desktop version, is what gets used to build Google's index and decide rankings for both mobile and desktop search results.
Does mobile-first indexing affect desktop search rankings too?+
Yes. Since the mobile version is what Google indexes, content, links or structured data that exist only on your desktop site are largely invisible to ranking, even for searches performed on a desktop computer.
How do I check if my website is mobile-friendly for free?+
Use Google's Mobile-Friendly Test at search.google.com/test/mobile-friendly for a pass/fail check with a screenshot of what Googlebot sees, and PageSpeed Insights with the Mobile tab selected for a deeper performance and usability breakdown. Both are free and take under a minute per page.
What is the minimum tap target size for mobile usability?+
Google recommends touch targets of roughly 48x48 CSS pixels with at least 8px of spacing between adjacent clickable elements. Nav links, footer icons and stacked call-to-action buttons are the most common places this gets missed.
Are popups bad for mobile SEO?+
Full-screen popups that cover the main content immediately on page load are flagged as intrusive interstitials under Google's page experience guidance. Delaying the popup, using a smaller dismissible banner, or exempting legally required notices like cookie consent avoids the problem.
Related guides
Sources & data note
This guide describes documented Google Search Central guidance on mobile-first indexing and mobile usability, cited above. Specific tap-target and font-size figures are Google's published guidance and are treated as current; verify against the official documentation before relying on them. Observations about Nepal's mobile traffic share, common template defects on older Nepali business sites, and Devanagari line-height needs are our own analysis rather than published findings, and are not separately sourced. Guides are written from primary sources, Nepali government departments, operators, park authorities and standards bodies, and each guide lists the sources used for its own facts. Rules, fees and prices in Nepal change; treat figures as current at the review date shown on each guide and verify anything money- or visa-critical with the issuing authority before you rely on it.