Mobile SEO: 8 Things Developers Forget

· 6 min read

TL;DR — Key Takeaways

  • •Google uses mobile-first indexing — if your site is broken on mobile, it's broken for rankings.
  • •The viewport meta tag is not optional. Without it, mobile browsers render your desktop layout at 980px wide.
  • •Touch targets need at least 48x48 CSS pixels of tappable area. Tiny links frustrate users and hurt engagement metrics.
  • •Core Web Vitals are confirmed ranking factors, and mobile scores are almost always worse than desktop. Test both.

Over 60% of web traffic is mobile. Google switched to mobile-first indexing years ago, meaning it primarily uses the mobile version of your content for ranking and indexing. And yet, I still see developers treating mobile as an afterthought — "it works on my laptop, ship it."

Here are 8 mobile SEO issues I see constantly when running audits. Most of them take minutes to fix but can have a significant impact on your rankings.

The 8 Things

Every one of these is a real issue I've found on production sites built by experienced developers.

1. Missing or Broken Viewport Meta Tag

This is the most fundamental mobile issue, and it still trips people up. Without the viewport meta tag, mobile browsers assume your page was designed for a desktop and render it at ~980px wide, then zoom out to fit the screen. Everything looks tiny and requires pinch-zooming.

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

That single line tells the browser to match the screen width and start at 1x zoom. Without it, your responsive CSS does nothing — the browser never triggers your mobile breakpoints because it thinks the screen is 980px wide.

Pro tip: Never set maximum-scale=1 or user-scalable=no. It breaks accessibility by preventing users with low vision from zooming in. Google also flags it as a mobile usability issue.

2. Non-Responsive Design

Having the viewport tag is step one. Step two is actually making your layout respond to different screen sizes. Common failures:

Test your site at 375px wide (iPhone SE) as a minimum. If anything overflows or requires horizontal scrolling, it's broken.

3. Touch Targets Too Small

Fingers are not mouse cursors. Google's mobile usability guidelines specify that touch targets should be at least 48x48 CSS pixels, with at least 8px of spacing between them. This applies to:

/* Minimum touch target size */
.nav-link {
  min-height: 48px;
  min-width: 48px;
  padding: 12px 16px;
}

/* Ensure spacing between adjacent targets */
.footer-links a {
  display: inline-block;
  padding: 8px 12px;
  margin: 4px;
}

4. Font Sizes Too Small

If your body text is below 16px on mobile, users have to zoom in to read it. Google flags text smaller than 12px as a mobile usability issue, but honestly, anything below 16px is uncomfortable on a phone screen.

Also watch out for form inputs. On iOS, if your input font size is below 16px, Safari automatically zooms in when the user taps the field — and doesn't zoom back out. This is one of the most common mobile UX complaints, and the fix is trivial:

input, select, textarea {
  font-size: 16px; /* prevents iOS auto-zoom */
}

5. Ignoring Core Web Vitals on Mobile

Your desktop Lighthouse score might be 98, but what's your mobile score? Core Web Vitals — Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP) — are confirmed Google ranking factors, and mobile scores are consistently worse than desktop.

Common mobile-specific performance killers:

Pro tip: Always test mobile performance on a real device over a 4G connection, not just Chrome DevTools with throttling. Real-world mobile performance is consistently worse than simulated.

6. Not Understanding Mobile-First Indexing

Mobile-first indexing doesn't mean "Google checks if your site works on mobile." It means Google uses your mobile version as the primary version for everything — indexing, ranking, snippet generation. If content exists on your desktop version but not on mobile, Google may not see it at all.

Common pitfalls:

7. AMP Is Dead — Stop Using It

Accelerated Mobile Pages had a good run. Google no longer gives AMP pages preferential treatment in search results, the "Top Stories" carousel is open to all pages, and the AMP lightning bolt icon is gone. If you're still maintaining AMP versions of your pages, you're doing extra work for zero benefit.

Focus that effort on making your regular pages fast instead. A well-optimized Next.js or static site will outperform AMP pages in Core Web Vitals anyway.

8. Structured Data That Breaks on Mobile

Structured data (JSON-LD) itself doesn't change between mobile and desktop — it's in the HTML head. But the content it references needs to be visible and accessible on mobile. If your structured data references a breadcrumb navigation that's hidden on mobile, or an FAQ section that requires JavaScript to expand, Google may flag inconsistencies.

Also, test your structured data with Google's Rich Results Test — it has separate tabs for mobile and desktop rendering. Check both.

Quick Mobile SEO Checklist

Run through this before every launch.

Catch mobile SEO issues before your users do

AuditMyPage checks your viewport tag, meta tags, structured data, and 16+ other SEO elements in one scan. Free, no signup required.

Audit your site — Free