Mobile-first indexing has been the default for all new websites since 2019 and the default for nearly all websites since 2023. The mobile version of your site is the version Google crawls, indexes, and ranks — period. The desktop version is essentially secondary now from a search perspective.

This article walks through the practical audit checklist we run for small business clients across restaurant marketing, hotel marketing, and trades engagements. The goal isn’t to make you a mobile development expert — it’s to give you the diagnostic framework to catch the specific failures that quietly cost rankings on mobile-first indexed sites.

The audit framework here doesn’t require developer expertise. It does require the discipline to actually look at your site on a phone — not on a phone-shaped browser window, but on a real mobile device, ideally one with imperfect network conditions. That single change in how you evaluate the site surfaces issues that desktop-first audits miss every time.

What mobile-first indexing actually means

According to Google’s mobile-first indexing documentation, Google primarily uses the mobile version of a site’s content for indexing and ranking. This means Googlebot crawls your site as a mobile user agent and treats whatever it sees as the canonical version.

For sites with responsive design that show identical content on mobile and desktop, this is invisible — there’s no difference between what Google sees and what desktop users see. For sites with separate mobile versions, abbreviated mobile menus, or content hidden behind “Read more” toggles on mobile, the difference is significant. Content not present on mobile is, for Google’s purposes, not present at all.

The most common small business failure mode: mobile menus that omit important pages, mobile homepages that strip out service descriptions to look cleaner, and “click to expand” content that’s collapsed by default on mobile. All three patterns hide content from Google that’s visible on desktop. The desktop content effectively doesn’t exist for ranking purposes.

Content not present on mobile is, for Google’s purposes, not present at all. That single fact reshapes how you should think about every design decision.

— From the field

The audit checklist

A complete mobile-first audit covers four areas: content parity, structured data parity, mobile UX, and mobile performance.

Content parity. Open your site in a mobile browser (or use Chrome DevTools mobile emulation). Compare every page to its desktop equivalent. Is the headline the same? The H1? The body content? The internal links? The schema markup? Any content that’s present on desktop but absent on mobile is invisible to Google.

Structured data parity. Schema markup on the desktop version that’s stripped on mobile is effectively missing schema. Run Google’s Rich Results Test against the mobile URL specifically — not just the desktop URL. Many sites have schema injected by desktop-only theme functions that don’t fire on mobile.

Mobile UX. Are buttons and links large enough to tap accurately? Is text readable without pinch-to-zoom? Are forms usable on small screens? These are page experience signals that affect ranking. The bar isn’t “could a developer use this site on a phone” — it’s “could a 65-year-old user with average eyesight and average fine motor control complete the primary action without frustration.”

Mobile performance. Core Web Vitals are measured on mobile separately from desktop. Mobile typically scores worse because of slower network conditions and weaker device CPUs. A site with good desktop Core Web Vitals can still fail on mobile — and mobile is the version Google ranks.

Common mobile failure patterns

The accordion problem. Many sites hide content inside accordion or “click to expand” modules on mobile to save vertical space. Content inside these is technically present in the HTML, but if it’s hidden by default, Google may weight it less. Worse, some implementations remove the content from the DOM entirely on mobile — making it invisible. Test by viewing source on mobile, not just inspecting the rendered page.

The truncated menu problem. Mobile hamburger menus often link to fewer pages than desktop primary navigation. This can artificially reduce internal linking to important pages on the mobile version. Audit your mobile menu against your desktop menu and decide deliberately which links matter enough to keep on mobile.

The disabled-image problem. Some sites disable image loading on mobile for performance reasons, but in doing so they remove the alt text, captions, and surrounding context that helped those images contribute to topical relevance. Better approach: serve smaller, optimized images, not no images.

The interstitial problem. Pop-ups, email signup overlays, and “are you 21” gates that block content on mobile (especially when they’re not easily dismissible) trigger Google’s mobile intrusive interstitial penalty. The penalty is small but consistent. Move these to less intrusive placements on mobile.

Tools for diagnosing mobile issues

Google Search Console’s URL Inspection tool shows you exactly what Googlebot sees when it crawls a page. Critical: use the “View Tested Page” function and select the mobile rendering. This is the single most authoritative view of your mobile content from Google’s perspective.

Chrome DevTools mobile emulation (open DevTools, toggle device toolbar) lets you preview your site at common mobile viewport sizes. Useful for catching layout issues but not a substitute for actual mobile devices, since emulation doesn’t replicate device CPU, network conditions, or touch interaction.

Google’s Mobile-Friendly Test was deprecated in late 2023, but the Rich Results Test now includes mobile rendering. Use it for quick checks on specific URLs.

Actual mobile devices remain the most reliable test. Borrow a partner’s phone if you only own one type of device. iOS Safari and Android Chrome render differently in subtle ways; if your site only works well on one, you’re leaving search traffic on the table.

When mobile fixes need help

Content parity issues are usually fixable without development work — they’re content decisions disguised as technical ones. Decide what content matters, then ensure it’s present on mobile.

Performance issues and structured data issues typically benefit from technical support, especially on older WordPress themes or custom-coded sites where the mobile rendering path is genuinely different from the desktop path. For most small business sites, a half-day of disciplined cleanup eliminates 80% of mobile-first indexing problems.

Where outside help adds value: the diagnostic layer. Knowing whether your mobile-first issues are content, performance, schema, or UX — and which is causing the most ranking impact — is the analytical work that turns a long checklist into a prioritized action plan. This is core to the technical SEO sweeps we run as part of broader local SEO engagements.

Where Piedmont fits in mobile audits

Mobile-first indexing work is one of the routine technical sweeps inside Piedmont engagements — not the headline intervention, but the prerequisite that has to be cleaned up before more strategic work can produce results. The pattern we see across Bay Area service businesses: desktop sites that look strong, mobile renderings that hide content, and rankings that lag what the desktop quality would predict. The remediation is usually content parity work, not full rebuilds.

In practice, mobile audits run alongside Core Web Vitals optimization and page speed work because they reinforce each other — mobile performance is its own Core Web Vitals score, and many of the speed fixes that help one help both. The audit also feeds into site architecture decisions when mobile menu truncation reveals authority distribution problems that desktop navigation was masking.

If you want to know what Google actually sees when it crawls your mobile site — using real Search Console URL Inspection data rather than a desktop emulator — the free 30-minute interview includes a mobile-first audit on your priority pages.