Mobile SEO Checklist: What Still Matters and What Doesn’t

A mobile SEO checklist is a structured set of technical, content, and UX checks that ensure your site performs well in mobile search. Google indexes the mobile version of your site first, so if your mobile experience is broken, slow, or poorly structured, your rankings will reflect that regardless of how strong your desktop experience is.

The fundamentals are not complicated. Page speed, responsive design, accessible content, and clean crawlability cover the majority of what moves the needle. The rest is refinement.

Why Mobile-First Indexing Changes the Priority Order

When Google moved to mobile-first indexing, it did not just change a technical setting. It changed which version of your site carries the most weight. If your mobile pages are missing content that exists on desktop, stripping out structured data, or loading in ways that frustrate crawlers, your rankings will degrade regardless of what the desktop version looks like.

I spent several years running an agency where we managed significant paid search budgets for retail clients. One thing that became obvious quickly was that organic and paid performance were not independent. A site with poor mobile experience would underperform on both channels simultaneously. Paid traffic would land on slow mobile pages and bounce. Organic rankings would stagnate because the mobile signals were weak. Fixing one without the other was always a partial solution.

The implication for this checklist is straightforward. Mobile SEO is not a separate workstream from your core SEO strategy. It is the foundation of it. If you want to understand how this fits into a broader approach, the Complete SEO Strategy hub covers the full picture, from technical foundations through to content and authority building.

The Technical Checks That Actually Move Rankings

Technical mobile SEO is not glamorous. It is also where most sites leave the most points on the table. These are the checks I would run first on any site, in this order.

Responsive Design vs. Separate Mobile URLs

Responsive design, where a single URL serves different layouts based on screen size, is the configuration Google recommends and the one that creates the fewest ongoing maintenance problems. Separate mobile URLs (the old m.dot approach) introduce redirect chains, canonicalisation issues, and the ongoing overhead of keeping two versions of content in sync.

If you are still running a separate mobile site, migrating to responsive is not just a technical housekeeping task. It is a risk reduction exercise. Every time content gets updated on desktop and the mobile version lags behind, you are creating a gap between what Google indexes and what users see.

Core Web Vitals: The Three Numbers That Matter

Google’s Core Web Vitals are the clearest signal we have of what Google considers a good page experience. There are three primary metrics to track.

Largest Contentful Paint measures how long it takes for the largest visible element, usually a hero image or headline, to load. For mobile, the target is under 2.5 seconds. Most sites fail this because of uncompressed images, render-blocking third-party scripts, or slow server response times.

Cumulative Layout Shift measures visual stability. If elements jump around as a page loads, that is a layout shift. On mobile, this is particularly damaging because screen real estate is limited and users are already handling with less precision. A CLS score below 0.1 is the target.

Interaction to Next Paint replaced First Input Delay as the responsiveness metric. It measures how long the browser takes to respond to user interactions. On mobile, where JavaScript execution is slower due to device constraints, this is frequently the hardest metric to pass.

Google Search Console shows your Core Web Vitals by device type. Run this report first before doing anything else. It will tell you whether you have a widespread problem or isolated pages that need attention. The Semrush mobile SEO guide covers how these metrics interact with broader ranking factors if you want more depth on the relationship.

Page Speed: The Practical Fixes

Page speed on mobile is constrained by two things desktop is not: connection quality and processing power. Even users on modern handsets are often on variable network connections. Pages that load acceptably on a fast Wi-Fi connection can be genuinely painful on a mid-tier mobile network.

The practical fixes, in rough order of impact, are these. Compress and properly size images. Use next-generation formats like WebP or AVIF. Defer JavaScript that is not needed for the initial render. Minimise third-party scripts, particularly tag managers loaded with redundant tags. Enable browser caching. Use a content delivery network if your audience is geographically distributed.

I have run audits on sites where the tag manager alone was adding two seconds to mobile load time because nobody had cleaned it out in three years. Tags accumulate. Analytics scripts, retargeting pixels, chat widgets, A/B testing tools, all of them add weight. On mobile, that weight is paid for in load time and, in the end, in rankings and conversions.

Crawlability and Indexation Checks

Confirm that Googlebot’s mobile crawler is not being blocked by your robots.txt file. This sounds obvious, but it is a more common error than you would expect, particularly after site migrations or CMS updates that reset configuration files.

Check that your mobile pages are not accidentally set to noindex. Again, this happens during development when staging environments get pushed live with directives that were intended to be temporary.

Verify that your XML sitemap includes the canonical versions of your URLs and that those canonical tags are consistent across mobile and desktop. Conflicting canonicals confuse crawlers and dilute ranking signals.

Content Checks for Mobile Search

Mobile search behaviour is different from desktop search behaviour, though not in the ways that are often claimed. Users are not searching for fundamentally different things on mobile. They are reading in different conditions, with different levels of patience, and on screens where poor formatting is immediately obvious.

Content Parity Between Mobile and Desktop

With mobile-first indexing, any content hidden on mobile is, from Google’s perspective, potentially less significant. This includes content collapsed behind tabs, accordions, or “read more” toggles.

Google has indicated that content hidden in these ways on mobile is still indexed, but the practical question is whether it carries the same weight as visible content. The safest approach is to ensure your most important content, particularly the copy that contains your primary keyword targets, is visible without interaction on mobile.

Structured Data on Mobile Pages

Structured data is one of those areas where the gap between what sites say they have and what they actually have tends to be significant. If you have implemented schema markup, verify that it is present on the mobile version of your pages, not just the desktop version.

Use Google’s Rich Results Test with a mobile user agent to confirm that your schema is rendering correctly and that it is eligible for rich results. FAQ schema, product schema, and review schema all have mobile-specific rendering in search results that can materially improve click-through rates.

Readability and Formatting

Font sizes below 16px are consistently flagged by Google’s mobile usability tools as problematic. Line length matters too. Text that spans the full width of a desktop screen and then wraps awkwardly on mobile is a common formatting problem that gets ignored because it is only visible when you actually test on a device.

Paragraphs that work on desktop can feel oppressive on mobile. Shorter paragraphs, clear subheadings, and adequate white space are not just stylistic preferences. They are functional decisions that affect how long users stay on the page. There is a commercial argument for readable content that goes beyond SEO. Writing that holds attention converts better. Copyblogger’s work on content engagement makes this case clearly if you want a reference point.

UX Checks That Affect Both Rankings and Conversions

Google’s mobile usability signals and conversion performance are more closely related than most teams treat them. A site that frustrates users also frustrates Google’s quality assessments. The overlap is not coincidental.

Tap Targets and Touch Usability

Tap targets, buttons, links, form fields, need to be large enough to hit accurately with a finger. Google recommends a minimum of 48×48 pixels with adequate spacing between targets. This is one of the most commonly failed checks on older sites, particularly those with navigation menus that were designed for mouse interaction.

Run the mobile usability report in Search Console. It flags tap target issues at scale and tells you which pages are affected. Fix the highest-traffic pages first.

Intrusive Interstitials

Google penalises pages that show intrusive interstitials on mobile, specifically pop-ups that cover the main content immediately after a user arrives from search. This is distinct from cookie consent banners, login dialogs, and age verification gates, which are exempt.

The practical implication is that email capture pop-ups, promotional overlays, and app download banners that trigger on page load can harm your mobile rankings. Time-delayed pop-ups that appear after a user has engaged with the page are a lower risk, though still worth testing carefully.

I have seen this cause real ranking drops on e-commerce sites. A client running aggressive email capture on mobile landing pages saw measurable organic traffic decline after Google updated its interstitials policy. The pop-up had been running for years on desktop without issue. On mobile, it was a different story.

Mobile Navigation

Navigation on mobile needs to work as a standalone system, not as a compressed version of desktop navigation. Hamburger menus are standard and widely understood. The problems arise when navigation hierarchies are too deep, when dropdowns require hover interactions that do not translate to touch, or when breadcrumbs are missing and users cannot orient themselves within the site structure.

Internal linking on mobile pages also deserves attention. Links that are clearly visible and well-spaced on desktop can become difficult to tap when viewed on a 375px screen. Check your most important conversion paths on an actual device, not just in a browser’s responsive design mode.

Local and Voice Search Considerations

Mobile search has a stronger local intent signal than desktop search. Users searching on mobile are more likely to be looking for something nearby, something time-sensitive, or something they intend to act on immediately. This has direct implications for how you structure content and metadata.

Local SEO Signals for Mobile

If your business has physical locations, your Google Business Profile is as important as anything on your website for mobile search visibility. Ensure NAP (name, address, phone number) data is consistent across your site and your profile. Ensure your profile is complete, with accurate hours, categories, and recent photos.

LocalBusiness schema on your site reinforces these signals. It is a relatively low-effort implementation with a meaningful impact on local mobile search visibility, particularly for multi-location businesses where consistency across locations is difficult to maintain manually.

Voice Search and Conversational Queries

Voice search on mobile tends to produce longer, more conversational queries than typed search. The SEO implication is that content structured around natural language questions, with clear, concise answers, is better positioned to capture these queries.

FAQ sections, clearly structured heading hierarchies, and content that answers specific questions directly are all useful here. This is not a separate content strategy. It is a refinement of good content structure that benefits both voice and text search.

How to Measure Mobile SEO Performance Without Drawing the Wrong Conclusions

Measurement is where mobile SEO work either gets validated or gets ignored. The teams that treat this as a one-time project, run the checklist, fix the issues, and move on, consistently underperform the teams that build a measurement cadence around it.

Early in my agency career, I worked with a client who had invested significantly in a site redesign with mobile optimisation as a stated goal. Six months after launch, nobody could tell you whether mobile organic traffic had improved, whether Core Web Vitals scores had changed, or whether the conversion rate on mobile had moved. The work had been done. The measurement had not. That is not an unusual situation. It is the default situation on most accounts I have reviewed.

Segment your analytics by device type as a baseline. Mobile organic traffic, mobile conversion rate, and mobile bounce rate should be tracked separately from desktop. Aggregate numbers hide the story.

Run the Search Console mobile usability report monthly. Track Core Web Vitals by device type. Set up alerts for significant drops in mobile impressions or clicks. These are not complex measurement requirements. They are the minimum viable dashboard for anyone who wants to manage mobile SEO as a continuous practice rather than a periodic project.

The Semrush off-page SEO checklist is worth reading alongside this one, because authority signals affect mobile rankings in exactly the same way they affect desktop rankings. Mobile SEO is not a closed system.

For a broader framework that connects mobile performance to your overall search strategy, the Complete SEO Strategy hub provides the context that makes individual checklists more useful. A checklist without a strategy is just a list of tasks.

The Mobile SEO Checklist: Consolidated

Below is the consolidated checklist, organised by category. This is not exhaustive. It covers the checks that consistently produce the most impact across the sites I have worked on.

Technical Foundation

• Responsive design implemented (single URL, CSS-based layout adaptation)
• Googlebot smartphone not blocked in robots.txt
• Mobile pages not set to noindex
• Canonical tags consistent between mobile and desktop
• XML sitemap includes canonical URLs
• HTTPS implemented and mobile pages served securely
• No redirect chains on mobile URLs

Page Speed and Core Web Vitals

• LCP under 2.5 seconds (mobile, measured in Search Console field data)
• CLS below 0.1
• INP under 200 milliseconds
• Images compressed and in next-generation formats
• Images sized appropriately for mobile viewports
• Render-blocking JavaScript deferred or eliminated
• Third-party scripts audited and unnecessary ones removed
• Browser caching enabled
• CDN in place if audience is geographically distributed

Content and Structured Data

• Primary content visible on mobile without requiring interaction
• Structured data present on mobile version of pages
• Rich Results Test passing with mobile user agent
• Font sizes 16px or above for body text
• Paragraphs formatted for mobile reading (shorter, more frequent breaks)
• Meta titles and descriptions appropriate for mobile SERP display

UX and Usability

• Tap targets minimum 48×48 pixels with adequate spacing
• No intrusive interstitials on page load from organic search
• Mobile navigation functional without hover interactions
• Forms usable on mobile (appropriate input types, no horizontal scrolling)
• Internal links spaced and sized for touch interaction
• Content tested on actual devices, not just browser emulation

Local and Additional Signals

• Google Business Profile complete and accurate (if applicable)
• NAP data consistent across site and third-party listings
• LocalBusiness schema implemented (if applicable)
• FAQ or structured Q&A content for conversational query capture

Measurement

• Analytics segmented by device type
• Mobile organic traffic tracked separately
• Core Web Vitals monitored monthly in Search Console
• Mobile usability report reviewed monthly
• Mobile conversion rate tracked as a standalone metric

The Optimizely SEO checklist covers some complementary ground on the broader technical and on-page side if you want to cross-reference your work against another framework. And Moz’s work on SEO testing beyond title tags is worth reading if you want to build a more rigorous approach to validating which changes are actually driving results rather than assuming causality.

What This Checklist Will Not Do For You

A checklist is a tool for reducing errors, not a substitute for judgement. I have seen teams run through mobile SEO checklists thoroughly and still produce poor outcomes because they were fixing symptoms rather than causes. A site with fundamentally weak content, thin authority, and no clear search intent alignment will not rank well on mobile even with a perfect technical setup.

Mobile SEO is also not a one-time intervention. Sites change. Plugins get updated and introduce new scripts. Images get uploaded without compression. New pages get built by teams who were not briefed on mobile standards. The checklist needs to be part of a recurring audit process, not a project that gets closed and archived.

When I was building out the SEO practice at iProspect, one of the things that separated the accounts that grew consistently from the ones that plateaued was the discipline of ongoing measurement and iteration. The teams that treated technical SEO as a project to be completed always found themselves starting over. The teams that treated it as a continuous operational standard maintained their gains and compounded them.

That is the right frame for this checklist. Not a task to tick off, but a standard to maintain.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions