Mobile SEO

Mobile SEO is making your site work well on a phone. That means it loads fast, text is readable without zooming, buttons are big enough to tap, and nothing annoying covers the content. Google now uses the mobile version of your site to decide rankings — so if your mobile site is broken, your rankings suffer. I have seen sites lose 30% of organic traffic overnight after a poorly executed responsive redesign that hid content from Google. The fix is boring but effective: use a responsive layout, keep content identical across devices, and compress images until they look good but load under one second. Do not treat mobile SEO as a separate project. It is part of the same [technical SEO](/technical-seo/) effort. If you are still running a separate m-dot site with [301 redirects](/301-redirect/), migrate to responsive as soon as possible. It simplifies crawling and avoids [duplicate content](/duplicate-content/) issues. The [Core Web Vitals](/core-web-vitals/) update made page speed a ranking signal for mobile, so if your site feels sluggish on a 4G connection, you are penalised. I measure by loading my site on an actual phone over a throttled connection, not on a desktop emulator. For example, I had a client whose mobile site had a hamburger menu that hid the main navigation. Google could not crawl the links inside, so those pages never got indexed. That is the kind of problem that does not show up in a desktop test. Always test on a real device.

Mobile SEO matters for every site because of mobile-first indexing, but it matters most when your audience predominantly uses phones. Check your analytics: if mobile traffic is over 50%, prioritise mobile SEO above everything else. For e-commerce, a slow mobile checkout loses sales. For local businesses, mobile searches for 'near me' are huge. For content sites, mobile users have shorter attention spans; if your page takes more than three seconds to load, half of them leave. There is a counter-argument: some B2B sites get most traffic from desktop, but Google still indexes the mobile version. So even B2B pages must be optimised. I have seen a software company lose rankings because the mobile site stripped out the pricing table and replaced it with a 'call us' button. Google could not see the pricing, so it could not match the query. If you have different content on mobile, you will lose. The decision rule: run a content parity audit quarterly. Use a tool like Screaming Frog to crawl both versions (if separate) or use a browser extension to compare rendered HTML. If you find discrepancies, fix them within the week. Also check that nothing is blocked by [robots.txt](/robots-txt/) — I once found a site that accidentally blocked all CSS on mobile via the robots.txt disallow. The mobile pages rendered as plain text for Google but looked fine in a browser, confusing both the search engine and the owners.

Early on, I treated mobile SEO as a separate checklist item — run the mobile-friendly test, fix the errors, move on. I did not realise that content parity matters just as much. I had a client whose desktop page had a rich FAQ section with structured data, but the mobile version only showed the first three questions. Google indexed the mobile version and lost the FAQ schema entirely. That cost the client featured snippets for months. Another mistake: I used to think lazy-loading all images was a performance win, but I learned that aggressive [lazy-loading](/performance-optimization/) can hide content from Google if the scroll is not triggered. Now I lazy-load only below-the-fold images and use native loading attributes. I also ignored tap targets. On a directory site, the mobile menu had links spaced 2mm apart. Users kept tapping the wrong link. I had to increase spacing to at least 8mm. Finally, I assumed that because my desktop and mobile site were responsive, they were identical. They were not — CSS media queries hid some text on small screens. Google saw different content. I now test by rendering the mobile version in a headless browser and comparing the text content to desktop. Content parity is not something a single tool can guarantee; you have to audit manually or with a script.