Mobile SEO Checklist: What Moves Rankings

A mobile SEO checklist covers the technical, on-page, and UX factors that determine how well your site performs in mobile search. That means page speed, crawlability, structured data, Core Web Vitals, and how Google’s mobile-first index reads your content, not just whether your site looks acceptable on a phone.

Most sites have already cleared the obvious hurdles. Responsive design is table stakes. Where rankings diverge now is in the details: render-blocking resources, font scaling, tap target sizing, and whether your mobile experience actually serves the intent behind the query or just technically passes a test.

Why Mobile-First Indexing Changed the Rules

Google completed its rollout of mobile-first indexing in 2023. What that means in practice is that Googlebot primarily crawls and evaluates the mobile version of your pages when determining how to rank them. If your desktop site has content, structured data, or internal links that your mobile version does not, Google is ranking you on the lesser version of your own work.

I have seen this catch out brands that should know better. A retail client we worked with had a desktop product description running to 400 words with detailed specifications, FAQs, and schema markup. The mobile version collapsed that content behind a “show more” toggle that was loaded via JavaScript, which Googlebot was not reliably rendering. The content existed, technically, but was not being indexed. Rankings for long-tail product queries were weak for no obvious reason until we looked at what mobile Googlebot was actually seeing.

The fix was straightforward once diagnosed. The lesson was less comfortable: assumptions about what Google can see are not a substitute for checking what Google actually sees.

This sits within a broader SEO framework worth understanding. If you want context on how mobile performance connects to the rest of your search strategy, the Complete SEO Strategy hub covers the full picture.

Mobile SEO Checklist: Technical Foundation

Before anything else, your technical setup needs to be clean. These are the items that affect whether Google can crawl, render, and index your mobile pages correctly.

1. Viewport Configuration

Every page needs a correctly configured viewport meta tag. The standard implementation is <meta name="viewport" content="width=device-width, initial-scale=1">. Without it, mobile browsers render your page at desktop width and scale it down, which produces a poor experience and signals to Google that mobile optimisation is not a priority. Check this across your templates, not just your homepage.

2. Mobile Crawl Verification

Use Google Search Console’s URL Inspection tool to check how Googlebot Mobile renders your key pages. Pay attention to what content is visible in the rendered HTML versus what requires JavaScript execution. If critical content or structured data only appears after JS runs, test whether Googlebot is actually rendering it. The “Test Live URL” function in Search Console is the most direct way to verify this.

3. Robots.txt and Crawl Access

Confirm that your robots.txt does not block Googlebot Smartphone from crawling CSS, JavaScript, or image files. This is a legacy issue that still surfaces in site audits, particularly on older CMS implementations where someone added disallow rules to reduce server load and forgot about them. Blocked resources prevent Google from rendering your pages correctly, which affects how they are indexed and ranked.

4. Canonical Tags

If you run separate mobile URLs (m.domain.com) rather than a responsive design, canonical tags become critical. Each mobile URL should point to its desktop equivalent, and each desktop URL should include a rel="alternate" tag pointing to the mobile version. Responsive design avoids this complexity entirely, which is one reason it is the recommended approach. Separate mobile URLs are a maintenance liability that most teams underestimate.

5. Structured Data Parity

Any schema markup present on your desktop pages must also appear on your mobile pages. This includes product schema, review schema, FAQ schema, and breadcrumb markup. If your CMS renders different templates for mobile and desktop, audit both. Missing structured data on mobile means Google may not surface rich results for those pages, regardless of how well the desktop version is marked up.

Mobile SEO Checklist: Page Speed and Core Web Vitals

Speed matters more on mobile than desktop because mobile connections are less reliable, processors are less powerful, and users are less patient. Google’s Core Web Vitals are the clearest signal of where speed problems are costing you. Semrush’s mobile SEO guide covers the technical dimensions of this in useful depth if you want to go further on the measurement side.

6. Largest Contentful Paint (LCP)

LCP measures how long it takes for the largest visible element on the page to load. Google’s threshold for “good” is under 2.5 seconds. The most common culprits for poor LCP on mobile are unoptimised hero images, render-blocking resources, and slow server response times. Compress images, use next-gen formats (WebP or AVIF), and consider lazy loading below-the-fold content while prioritising above-the-fold assets.

7. Interaction to Next Paint (INP)

INP replaced First Input Delay as a Core Web Vital in 2024. It measures the responsiveness of a page to user interactions across the entire session, not just the first click. A good INP score is under 200 milliseconds. On mobile, this is primarily a JavaScript problem. Excessive main thread work, long tasks, and third-party scripts all degrade INP. Audit your JS execution with Chrome DevTools and identify which scripts are blocking interaction responsiveness.

8. Cumulative Layout Shift (CLS)

CLS measures visual stability. A score above 0.1 means elements are shifting around as the page loads, which is both a ranking signal and a genuine usability problem. On mobile, the most frequent causes are images without defined dimensions, dynamically injected content (ads, banners, cookie notices), and web fonts causing text reflow. Set explicit width and height attributes on all images and reserve space for dynamic content before it loads.

9. Image Optimisation

Images are the single largest contributor to page weight on most sites. Compress all images, serve them in modern formats, and implement responsive images using the srcset attribute so mobile devices receive appropriately sized files rather than desktop-resolution images scaled down by CSS. A 2MB hero image that looks fine on desktop is a significant speed penalty on a mobile connection.

One thing I have learned from running audits across dozens of client sites: the image problem is almost never a knowledge problem. Everyone knows images should be compressed. It is an implementation and governance problem. No one owns it, the CMS makes it easy to upload originals, and it accumulates quietly until the site is carrying hundreds of megabytes of unnecessary weight.

10. Minify and Defer Non-Critical Resources

Minify CSS, JavaScript, and HTML files to reduce their size. Defer or async-load JavaScript that is not required for initial render. Eliminate render-blocking resources that sit in the <head> and prevent the browser from displaying content until they have fully loaded. Tools like Google PageSpeed Insights and Lighthouse will flag these specifically, with recommendations attached.

A word of caution on speed scores: I have seen teams spend significant time optimising a PageSpeed score from 72 to 79 and calling it a win. That is not necessarily a win. Scores are a directional indicator. What matters is whether real users, on real devices, on real connections, experience meaningful improvement. Use field data from Search Console’s Core Web Vitals report alongside lab data from Lighthouse. They tell different stories, and both perspectives matter. Analytics tools give you a view of reality, not reality itself.

Mobile SEO Checklist: On-Page and UX Factors

Technical health gets you into the game. On-page quality and user experience determine whether you stay there. Google’s algorithms have become increasingly capable of distinguishing between pages that technically function on mobile and pages that are genuinely useful on mobile.

11. Font Size and Readability

Body text should be a minimum of 16px on mobile. Smaller text forces users to pinch-zoom, which signals a poor mobile experience. Headings should have clear visual hierarchy. Line height matters too: 1.5 to 1.6 for body text is generally comfortable on mobile screens. These are not aesthetic preferences, they affect bounce rate and time on page, which are behavioural signals Google uses to assess page quality.

12. Tap Target Sizing

Interactive elements, including buttons, links, and form inputs, should have a minimum tap target size of 48×48 pixels with adequate spacing between them. Small, closely spaced tap targets cause accidental clicks and user frustration. Google’s mobile usability report in Search Console flags pages with tap targets that are too small or too close together. Fix these systematically rather than one at a time.

13. Content Parity Between Mobile and Desktop

As noted earlier, Google indexes the mobile version of your pages. Any content that is hidden, collapsed, or truncated on mobile should still be in the DOM and accessible to Googlebot. Tabbed content, accordions, and “read more” toggles are not inherently problematic, but verify that Googlebot can access the content within them. Use the URL Inspection tool to check rendered HTML against what you expect to be indexed.

14. Intrusive Interstitials

Google has a specific penalty for intrusive interstitials on mobile. Pop-ups that cover the main content immediately after a user arrives from search, or before they have had a chance to interact with the page, are a ranking signal. Acceptable formats include cookie consent banners (legally required), age verification gates, and small banners that do not obscure content. Full-screen pop-ups triggered on page load are not acceptable and have been a ranking factor since 2017.

15. Mobile-Friendly Forms

If your site has forms, test them on mobile. Use appropriate input types (type="email", type="tel", type="number") so mobile keyboards display the correct layout. Ensure form fields are large enough to tap accurately. Reduce form length where possible: every additional field on mobile is a friction point that reduces completion rates. This is a conversion issue as much as an SEO one.

Mobile SEO Checklist: Accessibility and Structured Data

These two areas are consistently under-prioritised in mobile SEO work, which is a mistake. Accessibility improvements have a documented positive effect on crawlability and rankings. Structured data helps Google understand and surface your content in rich formats that improve click-through rates.

16. Accessibility Fundamentals

Alt text on images, proper heading hierarchy, sufficient colour contrast, and keyboard navigability are accessibility requirements that also benefit SEO. Moz’s analysis of accessibility and SEO overlap makes the case clearly: many accessibility fixes directly improve how search engines read and rank your content. This is one area where doing the right thing and doing the commercially sensible thing are the same thing.

I raised this point in a client review once and was met with the usual pushback about prioritisation and resources. My response was that if you are not willing to make your site usable for people with disabilities, you should at least be willing to do it because it improves your rankings. Use whatever argument works internally. The outcome is the same.

17. Schema Markup Implementation

Structured data does not directly improve rankings, but it improves the appearance of your listings in search results, which affects click-through rates. Relevant schema types for most sites include Article, Product, FAQ, Review, BreadcrumbList, and LocalBusiness. Validate your markup using Google’s Rich Results Test. Ensure schema is present on mobile pages, not just desktop templates. Check for errors in Search Console’s Rich Results section regularly.

18. Local SEO for Mobile

Mobile search has a strong local intent component. “Near me” queries are overwhelmingly mobile. If your business has a physical presence, your Google Business Profile needs to be complete and accurate. Your site should include LocalBusiness schema with consistent NAP (name, address, phone) data that matches your GBP listing. Location pages, where relevant, should be optimised for mobile and load quickly. This is basic but frequently neglected.

Mobile SEO Checklist: Monitoring and Ongoing Maintenance

A checklist completed once is a snapshot. Mobile SEO requires ongoing monitoring because sites change, Google’s algorithms update, and new pages are added that may not inherit your optimisations. Build the monitoring into your regular workflow rather than treating it as a one-time audit.

19. Google Search Console Mobile Usability Report

Check this monthly. It flags specific pages with mobile usability issues including text too small to read, clickable elements too close together, and content wider than the screen. Set up email alerts so you are notified when new issues appear. Do not wait for a quarterly audit to discover that a template change three months ago broke mobile usability on 400 product pages.

20. Core Web Vitals Field Data

Search Console’s Core Web Vitals report shows field data collected from real Chrome users. This is more valuable than lab data from Lighthouse because it reflects actual user experience across a range of devices and connections. Monitor both mobile and desktop segments separately. A page can pass Core Web Vitals on desktop and fail on mobile, and it is the mobile data that matters for mobile-first indexing.

21. Crawl Audits

Run a crawl audit using a tool like Screaming Frog or a platform like Semrush at least quarterly. Configure the crawler to use a mobile user agent so you are seeing what Googlebot Smartphone sees. Look for broken links, redirect chains, missing meta tags, duplicate content, and pages returning non-200 status codes. The Optimizely SEO checklist is a useful reference for structuring a comprehensive audit process if you want a broader framework to work from.

22. Third-Party Script Audit

Third-party scripts are one of the most common causes of mobile performance degradation. Tag managers, chat widgets, analytics platforms, advertising pixels, and social sharing scripts all add weight and execution time. Audit what is firing on your pages, remove anything that is not actively used, and consider loading non-critical scripts after the page has finished rendering. I have seen sites cut their mobile load time by 30% simply by removing tags that had been left in the tag manager after campaigns ended. No one had cleaned up. No one owned it.

That last point is worth sitting with. Most mobile SEO problems are not caused by ignorance of best practices. They are caused by poor governance, unclear ownership, and the accumulation of small decisions that no one revisited. A checklist is only useful if someone is accountable for working through it.

Mobile SEO does not exist in isolation. If you want to see how it connects to keyword strategy, link building, and content depth, the Complete SEO Strategy hub pulls all of it together in one place.

What Most Mobile SEO Checklists Miss

Most mobile SEO checklists stop at the technical layer. Pass the mobile-friendly test, hit the Core Web Vitals thresholds, fix the usability errors in Search Console, and move on. That is necessary but not sufficient.

What separates pages that rank from pages that merely qualify to rank is whether the content actually serves mobile intent. Mobile users often have different contexts than desktop users. They may be in a physical location, mid-task, with limited time and attention. A page that answers a query comprehensively on desktop may still underperform on mobile if the structure requires too much scrolling to reach the answer, if the most relevant information is buried below the fold, or if the calls to action are positioned for desktop behaviour patterns.

When I was judging the Effie Awards, one thing that consistently separated effective campaigns from technically competent ones was whether the work was built around how people actually behave, not how marketers assumed they would behave. The same principle applies to mobile SEO. You can pass every technical test and still produce an experience that does not serve the user. Google’s algorithms are increasingly good at detecting that gap.

Review your top mobile landing pages in Search Console. Look at the queries driving traffic to those pages. Then open those pages on your phone, not in a browser emulator, on an actual device, and ask honestly whether the page delivers what the query implies. That qualitative check is not in most checklists, but it is where a lot of mobile SEO value is left on the table.

For a broader view of how off-page factors interact with your on-page and technical work, Semrush’s off-page SEO checklist covers the link and authority side of the equation. And if you want to understand how accessibility improvements translate into measurable SEO gains, Moz’s piece on the ROI of accessibility is worth reading alongside this checklist.

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