Mobile-First Indexing Checklist for Small Business Websites
Google indexes the mobile version of your site exclusively since 2024. Here's the 12-item checklist for small business sites.
Google completed the migration to mobile-first indexing in 2024. That means Googlebot's primary crawler is a mobile user agent, the mobile version of your pages is what gets indexed, and the content, markup, and signals on your mobile pages are what determine your rankings — regardless of what your desktop version looks like.
For small businesses that built their sites on desktop-first templates or haven't explicitly tested the mobile experience, there are common gaps that hurt rankings. Here's the 12-item checklist.
How to Test Mobile-First Issues
Before working through the checklist, run your URL in PageSpeed Insights and select the Mobile tab. That's what Google sees. Also use Google's URL Inspection tool in Search Console — it shows you Googlebot's rendered HTML and any mobile usability issues it detected.
For visual testing, open Chrome DevTools, press Ctrl+Shift+M (or Cmd+Shift+M on Mac) to toggle Device Mode, and select a common phone size like iPhone 12 or Pixel 5. This isn't identical to Googlebot's rendering, but it catches most layout and content issues.
The 12-Item Checklist
1. Responsive Design (Not a Separate Mobile Site)
Your site should use responsive CSS (@media queries, flexible grid, fluid images) to adapt to mobile viewport widths. Separate mobile sites (m.yoursite.com) create content duplication and canonicalization complexity that hurts indexing.
If you're on a separate mobile site, ensure:
- The canonical URL on the mobile version points to the desktop version (or vice versa — be consistent)
rel="alternate"andrel="canonical"annotations are in place- Both versions have identical content
For responsive sites, confirm the viewport meta tag is present in <head>:
<meta name="viewport" content="width=device-width, initial-scale=1" />
2. Content Parity Between Desktop and Mobile
This is the most common indexing problem on sites built with desktop-first page builders. If your mobile template hides content behind a "Read More" button, collapses sections, or shows a simplified version of the page, that hidden content may not be indexed — or may receive reduced weight.
Test: In Chrome DevTools Device Mode, compare your mobile rendering against desktop. Any content that's on desktop but not visible or accessible on mobile is at risk.
3. No Broken Images on Mobile
Images that load on desktop via JavaScript-dependent rendering may not load in Googlebot's mobile crawl. Test by viewing your mobile rendering in Google's URL Inspection tool and checking whether all images appear in the rendered screenshot.
Also check that <img> tags have alt attributes — the alt text is what Google indexes for image search, and it's the fallback when images don't load.
4. Viewport Meta Tag
Already mentioned in item 1, but worth calling out separately: the <meta name="viewport"> tag is required for Google to render your page correctly as a mobile page. Without it, Googlebot renders at desktop width and applies its own zoom, which produces an incorrect rendering.
The correct tag: <meta name="viewport" content="width=device-width, initial-scale=1">
Do not use maximum-scale=1 or user-scalable=no — these prevent users from zooming and are a mobile usability violation that Google flags.
5. Tap Targets At Least 48px
Google's mobile usability guidelines require interactive elements (buttons, links, form inputs) to be at least 48x48 CSS pixels, with at least 8px spacing between adjacent tap targets. Smaller targets are flagged in PageSpeed Insights under "Tap targets are not sized appropriately."
/* Minimum tap target sizing */
.btn, a, button, input[type="submit"] {
min-height: 48px;
min-width: 48px;
padding: 12px 16px;
}
For navigation menus, ensure hamburger menu items have adequate height. Links in paragraph text (inline) don't need to meet the 48px threshold — the rule applies to interactive controls.
6. No Horizontal Scrolling
A page that scrolls horizontally on mobile has a layout bug. Common causes:
- Fixed-width elements wider than the viewport (e.g.,
width: 1200pxwithoutmax-width: 100%) - Images or embeds without
max-width: 100%; height: auto; - Tables that don't wrap on narrow viewports
Test by reducing the browser window to 375px wide (iPhone viewport) and looking for a horizontal scrollbar or content extending beyond the edge.
/* Global fix for overflow issues */
img, video, iframe, embed {
max-width: 100%;
height: auto;
}
/* Prevent fixed-width tables from causing overflow */
table {
display: block;
overflow-x: auto;
max-width: 100%;
}
7. Structured Data Parity
If you have structured data (schema markup) on your desktop pages — Product schema, LocalBusiness, FAQ, etc. — verify that the same markup is present on the mobile rendering. Schema that exists on desktop but not mobile may not be processed.
For responsive sites this is automatic (same HTML). For separate mobile sites, verify the schema is implemented on both.
8. Lazy-Loaded Images Render Correctly
Google's mobile crawler supports loading="lazy" — but it doesn't scroll the page during crawling, which means images that are far below the fold and triggered by scroll events may not be fetched during indexing.
Test: In Google Search Console's URL Inspection tool, request indexing and check the rendered screenshot. Any images that appear blank in the screenshot are not being crawled.
For critical images (product photos, hero images, important infographics), use loading="eager" to ensure they're always fetched.
9. hreflang Parity for International Sites
If your site targets multiple languages or regions using hreflang annotations, both versions (desktop and mobile, or separate language variations) must have identical hreflang implementations. A mismatch causes Googlebot to receive conflicting signals about which page to serve for which locale.
<!-- Must be identical on all variants -->
<link rel="alternate" hreflang="en-us" href="https://yoursite.com/page/" />
<link rel="alternate" hreflang="en-gb" href="https://yoursite.com/en-gb/page/" />
<link rel="alternate" hreflang="x-default" href="https://yoursite.com/page/" />
10. robots.txt Allows Mobile Crawling
Your robots.txt must not block Googlebot-Mobile. Check your robots.txt at yoursite.com/robots.txt and verify there are no rules blocking Googlebot-Mobile specifically or Googlebot generally on pages you want indexed.
Also verify that any page-level <meta name="robots"> tags are identical on mobile and desktop versions.
11. No Intrusive Interstitials
Google's mobile guidelines prohibit interstitials that cover the main content — full-screen popups, app install banners, or overlays that appear immediately on page load. These are counted against mobile usability and can affect rankings for the affected pages.
Permitted:
- Login prompts (for pages that require authentication)
- Age verification
- Cookie consent (if legally required)
- Banners that use a reasonable amount of screen space (not full-screen)
Not permitted: full-screen popups that appear on mobile before the user can see the page content.
12. Contact Information Readable on Mobile
For local businesses, NAP (Name, Address, Phone) information must be clearly readable on mobile — not cut off, not in a font so small it requires pinching, not hidden in a footer-only pattern that's collapsed on mobile.
This matters for both user experience and local SEO. Google uses NAP consistency to verify business identity for local ranking. If your address is missing or truncated on the mobile version, it's a usability problem and a potential local ranking problem.
Phone numbers should use tel: links for one-tap calling:
<a href="tel:+15551234567">(555) 123-4567</a>
Testing With PageSpeed Insights Mobile
After working through this checklist, run PageSpeed Insights on your homepage and key pages in Mobile mode. Note:
- Core Web Vitals scores — LCP, INP, CLS in mobile view are typically worse than desktop. These are the scores that matter for ranking signals.
- Mobile Usability section — lists specific failures like tap target sizing and text size
- Opportunities — mobile-specific performance issues like render-blocking resources
For LCP specifically on mobile, the most common failure is hero images that aren't preloaded or are served at desktop resolution. For the full LCP score guide, see What Is a Good LCP Score?.
RankCrab's audit runs PageSpeed Insights in mobile mode on your URLs and surfaces CWV scores alongside your other on-page signals, so you're always seeing the mobile score — the one Google uses — not just the desktop score. For the complete Core Web Vitals context, see the Core Web Vitals guide.