Mobile SEO: how to check, fix, and improve your mobile rankings

Why mobile SEO is non-negotiable in 2026

Google switched to mobile-first indexing for all websites in 2024, which means the mobile version of your site is the version Google crawls, indexes, and uses to determine your rankings. If your desktop site has content that is not present on mobile, that content is effectively invisible to Google. If your mobile site loads slowly or is difficult to use, those problems affect your rankings on all searches, not just mobile ones.

More than 60% of web searches now originate from mobile devices. For local and retail searches, that figure is higher still. A site optimised only for desktop is conceding the majority of search traffic to competitors who have addressed mobile performance. This is not a future concern; it has been the default state of Google's ranking system for several years.

Mobile SEO is not a separate discipline from standard SEO. It is the baseline. Core Web Vitals thresholds, page speed requirements, and usability standards all apply first to the mobile version of your site. Desktop performance matters, but it is scored against a more lenient standard than mobile in Google's page experience evaluation.

Running a mobile SEO audit is the right first step before investing in content creation or link building. If your mobile site has significant usability or speed issues, every other SEO activity you do is limited by that underperformance. For the full context of how mobile fits within a broader site audit, the website SEO health check guide covers every layer of the process in sequence.

How to test your site's mobile performance

Testing mobile performance requires checking two distinct areas: technical performance metrics and usability. Technical metrics measure speed and stability. Usability checks whether the page is actually readable and navigable on a small screen. Both matter, and they can fail independently of each other; a fast page can still be unusable, and a visually clean page can still be dangerously slow.

Google PageSpeed Insights

PageSpeed Insights is the standard starting point for mobile performance testing. Enter any URL and the tool returns both lab data and real-world field data from Google's Chrome User Experience Report. The lab data shows the performance your page achieves in a controlled test. The field data shows how real users experience it. Both are scored, and discrepancies between the two are worth investigating because they often indicate inconsistent server performance or variable network conditions affecting real users.

The most important outputs from PageSpeed Insights are the Core Web Vitals scores: Largest Contentful Paint, Cumulative Layout Shift, and Interaction to Next Paint. Each one has a threshold that separates Good from Needs Improvement from Poor. Pages in the Poor zone for any metric are at a ranking disadvantage in mobile search results.

PageSpeed Insights also returns an Opportunities list ranked by estimated time savings. Work through this list from top to bottom. The highest-ranking opportunities almost always involve image optimisation, eliminating render-blocking resources, and reducing unused JavaScript. Tackle these before addressing lower-impact items.

Google Search Console Mobile Usability report

Search Console's Mobile Usability report shows which pages on your site have mobile usability errors detected by Google's own crawler. It categorises errors including text too small to read, clickable elements too close together, content wider than screen, and use of incompatible plugins. Each error category links to the affected URLs so you can prioritise fixes by the number of pages affected. Access Search Console through the Google Analytics platform or directly at search.google.com/search-console.

Semrush Site Audit mobile checks

Semrush Site Audit includes mobile-specific checks as part of its broader technical audit. It flags pages with viewport configuration issues, non-mobile-friendly tap target sizes, and slow mobile load times. The advantage over PageSpeed Insights is that Semrush audits your entire site rather than one URL at a time, giving you a site-wide picture of mobile issues rather than a page-by-page investigation. Explore the platform at Semrush.

Ahrefs Site Audit

Ahrefs Site Audit identifies mobile-relevant technical issues including pages missing a viewport meta tag, which is the most basic mobile configuration requirement. It also surfaces slow pages and pages with large uncompressed images that are the most common cause of poor mobile load times. The crawl data integrates with Ahrefs' backlink and keyword ranking data, so you can cross-reference your slowest mobile pages with the pages that are receiving the most traffic or have the most backlinks, prioritising fixes where the performance impact is highest. See the full tool review at Ahrefs.

Common mobile SEO issues and fixes

Most mobile SEO problems fall into one of five categories. Identifying which ones affect your site and fixing them in order of impact produces the fastest ranking improvement.

Missing or incorrect viewport meta tag

The viewport meta tag tells the browser how to scale the page on a mobile screen. Without it, the browser renders the page at desktop width and the user has to zoom and scroll horizontally to read anything. Every page on your site should include the following tag in the head section:

<meta name="viewport" content="width=device-width, initial-scale=1">

This is the single most basic mobile configuration requirement. Audit tools including Semrush and Ahrefs will flag any page missing it.

Text too small to read

Google flags text smaller than 12 pixels as too small to read on mobile without zooming. The fix is to set your body text size to at least 16 pixels in your CSS and ensure that paragraph text throughout your content templates meets this threshold. Heading text should scale proportionally. This is a CSS change that takes minutes to apply and eliminates the error across all pages using the same template.

Clickable elements too close together

Buttons, links, and navigation items need sufficient spacing on mobile so that a finger tap activates the intended element rather than an adjacent one. Google's mobile usability guidelines recommend a minimum tap target size of 48 by 48 pixels with at least 8 pixels of spacing between targets. Check your navigation menu, in-text links, and any call-to-action buttons for spacing violations. This fix is applied in CSS by increasing padding on interactive elements and ensuring sufficient line-height on inline links within paragraphs.

Content wider than the screen

Content overflow forces horizontal scrolling, which is one of the most common causes of poor mobile usability scores. It typically occurs when elements have fixed pixel widths defined in CSS, when images are not set to scale responsively, or when embedded content like videos or iframes have hardcoded dimensions. Replace fixed pixel widths with percentage or max-width values. Set images to max-width: 100% and height: auto to make them responsive. Replace hardcoded iframe dimensions with a responsive wrapper.

Intrusive interstitials

Pop-ups and overlays that cover the main content on mobile immediately after a page loads from a search result can attract a ranking penalty. Google specifically targets interstitials that obscure the main content before a user has had a chance to see it. Cookie consent banners that comply with legal requirements are excluded from this rule. Newsletter pop-ups, app download banners, and promotional overlays that appear immediately are the most common offenders. Delay non-essential pop-ups until the user has scrolled at least 50% down the page, or trigger them on exit intent rather than on page load.

Blocked resources

If your robots.txt file blocks Googlebot from accessing CSS or JavaScript files, Google cannot render your pages correctly and may see a broken or incomplete mobile layout. Check your robots.txt for any disallow rules affecting your stylesheet or script directories and remove any that are preventing Google from accessing resources needed to render the page. Google's URL Inspection tool in Search Console shows you a screenshot of how Google renders any URL, which confirms whether rendering issues are present.

Mobile page speed optimisation

Page speed is the mobile SEO factor with the most consistent and measurable impact on both rankings and user behaviour. A one-second improvement in mobile load time typically reduces bounce rate meaningfully and improves conversion rate. The following fixes address the most common causes of slow mobile load times.

Image optimisation

Uncompressed images are the single most common cause of slow mobile load times. The fix has three components: compress images before upload, serve them in modern formats, and size them correctly for the device displaying them.

1. Compress all images using a tool or build pipeline that reduces file size without visible quality loss. For most photography, a quality setting of 75 to 85% in WebP produces a file 25 to 35% smaller than an equivalent JPEG at the same visual quality.
2. Serve images in WebP format where possible. WebP is supported by all major browsers and produces smaller files than JPEG or PNG at equivalent quality. Most modern CMS platforms including Webflow, WIX, and Squarespace convert images to WebP automatically on upload.
3. Use responsive images with the srcset attribute to serve smaller image files to mobile devices. A header image displayed at 1400 pixels wide on desktop does not need to be served at that resolution to a phone with a 390-pixel screen. Serving the correctly sized image reduces file transfer by 60% or more in many cases.
4. Implement lazy loading for images below the fold. Images that do not appear in the initial viewport do not need to load before the page is usable. Adding loading=lazy to image tags defers their load until the user scrolls toward them.

Eliminate render-blocking resources

Render-blocking resources are CSS or JavaScript files that prevent the browser from displaying any content until they have fully downloaded and executed. Every render-blocking resource adds to the time before a user sees anything on the page, directly affecting Largest Contentful Paint scores.

1. Add async or defer attributes to non-critical JavaScript tags. Async loads the script in parallel and executes it as soon as it downloads. Defer loads in parallel and executes after the HTML has been parsed. Use defer for scripts that do not need to run immediately.
2. Inline critical CSS, the styles needed to render the above-the-fold content, directly in the HTML head rather than loading them from an external stylesheet. Load the full stylesheet asynchronously after the initial render.
3. Remove unused CSS and JavaScript. Most sites load stylesheet rules and script functions that are never used on most pages. PageSpeed Insights identifies the specific files and estimates the potential savings for each one.

Reduce server response time

A slow server response time adds latency before any page content can begin loading. Aim for a Time to First Byte under 200 milliseconds. The most common causes of slow server response are unoptimised database queries, insufficient server resources, and missing caching configurations. Hosting platforms vary significantly in base performance. Managed hosting providers like Bluehost and Hostinger offer server-side caching and performance optimisation as part of their managed WordPress plans, which typically reduces Time to First Byte without requiring manual configuration.

Mobile UX signals that affect rankings

Beyond technical performance, Google uses user behaviour signals from mobile searches as ranking inputs. These are harder to measure directly than Core Web Vitals, but the patterns are well-established enough to guide design and content decisions.

Bounce rate from search results

When a user clicks your result in Google, lands on your page, then immediately returns to the search results, that is a strong negative signal. On mobile, this happens most often when the page loads slowly, the content does not match the search query closely enough, or the text is too small or densely formatted to read quickly. Reducing bounce rate from organic search requires both technical speed fixes and content quality improvements working together.

Dwell time

Dwell time is the time a user spends on your page before returning to search results. Longer dwell time correlates with positive relevance signals. On mobile, short paragraphs, clear subheadings, and scannable formatting increase dwell time by making content easier to consume on a small screen. Long, unbroken blocks of text that read well on desktop often lose mobile users within the first few seconds.

Pogo-sticking

Pogo-sticking occurs when a user clicks your result, returns to the search results quickly, and clicks a competitor's result instead. It is a strong signal that your page did not satisfy the search intent. On mobile, this can happen for purely technical reasons; a page that hangs for four seconds while loading loses the user before the content is even visible. Addressing pogo-sticking requires identifying whether it stems from a speed problem, a content relevance problem, or both.

Readability on small screens

Readability on mobile is a combination of font size, line height, paragraph length, and colour contrast. A page that scores well on all four produces a reading experience that keeps users engaged longer. As a practical standard: body text at 16 to 18 pixels, line height of 1.5 to 1.6, paragraphs no longer than four sentences, and a contrast ratio of at least 4.5:1 between text and background. Checking colour contrast against WCAG AA standards using a free contrast checker catches issues that are invisible on desktop but highly visible on mobile screens in varied lighting conditions.

For sites built on CMS platforms like Webflow, WIX, or Squarespace, mobile-specific styling is controlled through responsive design settings and mobile breakpoint overrides. Check each template's mobile view and verify that font sizes, spacing, and layout behave correctly at 390 pixels wide, which covers the majority of current iPhone screen widths.

For WordPress sites, Rank Math provides on-page SEO scoring that includes readability checks, though it does not replace a full mobile usability audit. Pair on-page scoring with a Semrush or Ahrefs site crawl to cover both on-page and technical mobile issues in the same audit cycle.

What this means for your mobile presence

Mobile SEO performance is not a project you complete once. Page speed degrades as you add new scripts and plugins. New content may introduce formatting that breaks at mobile widths. Third-party tools you embed may introduce render-blocking resources you did not add yourself. Regular mobile audits catch these regressions before they compound into ranking problems.

The practical audit schedule for most sites is a PageSpeed Insights check on key landing pages monthly and a full Semrush or Ahrefs site crawl quarterly. After any significant site change, a new PageSpeed check on the affected pages confirms the change did not introduce new mobile performance issues.

For sites where mobile organic traffic is the primary acquisition channel, investing in Core Web Vitals improvement beyond the baseline Good threshold produces measurable ranking improvements against competitors who are only at the threshold. Google's ranking signals are comparative within a search result set, and a page that significantly outperforms its competitors on mobile speed has a structural advantage that is difficult to close quickly.

Connecting your mobile SEO work to a full website SEO health check ensures that mobile fixes are not being undermined by technical issues elsewhere on the site. A mobile-optimised page that is blocked from indexing by a robots.txt error or lacks a canonical tag pointing to the correct URL will not rank regardless of its Core Web Vitals scores. The mobile layer and the broader technical layer must both be clean for your optimisation work to produce its full effect.

For cookie consent tools that affect mobile page load times, CookieYes is designed to load asynchronously and avoid contributing to render-blocking delays, which makes it a practical choice for sites that need GDPR-compliant cookie consent without the performance penalty that some consent management platforms introduce.