Why your site loses traffic
when people search on phones
Most websites bleed organic traffic from mobile users without realising it. A slow page, a mis-sized tap target, or a crawl error that only shows up on 4G — these are the problems we work through in detail across three focused modules. No theory loops. No padding. Just the actual mechanics.
Three modules, one clear direction
Each module focuses on a specific layer of mobile SEO — from how Google crawls a phone-first page, to what Core Web Vitals actually measure in practice, to structured content that answers voice and featured-snippet queries.
How Googlebot actually sees your mobile page
There's a persistent assumption that if a site renders fine in a desktop browser, it's fine. It isn't. Mobile-first indexing means Google's crawler evaluates the mobile version of your page as the canonical source of truth. If your mobile HTML is missing structured data, canonical tags, or key heading text that appears only in a desktop-only block, your rankings take the hit — not just on phones.
In this module we set up real crawl simulations using Google Search Console and Screaming Frog's mobile emulation mode. You'll see exactly what the bot reads versus what a human sees, and map out where discrepancies cause ranking gaps.
- Mobile-first vs. desktop-first indexing explained with crawl logs
- Rendering gaps: JavaScript-hidden content and lazy-loaded images
- Canonical and hreflang setup on responsive vs. separate-URL sites
- Structured data that transfers to mobile crawl correctly
- Live audit exercise using Search Console's URL Inspection tool
Core Web Vitals on a real 4G connection
Google's page experience signals aren't measured on your office fibre line. They're measured in the Chrome User Experience Report — field data gathered from actual users on actual devices. That distinction changes everything about how you diagnose and fix speed issues. A lab score of 95 in PageSpeed Insights can coexist with a failing LCP in the field if your CDN isn't configured for South African edge nodes, for example.
We pull real CrUX data for participant URLs and dissect what's dragging down LCP, CLS, and INP specifically on mobile. Then we walk through practical fixes: render-blocking resource elimination, image format optimisation, font-loading strategy, and layout stability during scroll.
- Reading CrUX data in PageSpeed Insights and Search Console
- LCP: identifying the element, reducing TTFB, preload hints
- CLS: font-swap side-effects, image dimensions, ad slots
- INP: interaction delays from third-party scripts
- Toolchain: WebPageTest, Lighthouse CI, DevTools throttle
Writing content that answers mobile and voice queries
Mobile searches skew shorter, more local, and increasingly conversational — especially as voice search through phones gains ground. That shift changes what "good content" looks like at a technical level. Featured snippets, People Also Ask boxes, and local pack results each have structural requirements that most content teams aren't consistently applying.
This module covers how to audit existing content for snippet eligibility, how to structure FAQ and how-to markup correctly, and how to identify the specific query patterns mobile users in your niche actually type. We'll use real Search Console query data from participant accounts during the discussion sessions.
- Mobile SERP features: featured snippets, PAA, local pack
- Conversational query patterns and long-tail mobile intent
- FAQ and HowTo schema: markup, eligibility, and validation
- Local SEO signals for mobile near-me queries
- Content gap analysis using Search Console mobile query filters
What past participants noticed after the program
The crawl module changed how I read Search Console. I'd been looking at the wrong signals for months — the rendering gap exercise made it obvious. Our mobile impressions started climbing about six weeks after we fixed the canonical issues we found.
I came in thinking I understood Core Web Vitals. The CrUX data session on the second module showed me I'd been optimising for lab scores, not field scores. That's a different problem and requires different fixes.
The voice query section was the most surprising part. I hadn't connected the structure of conversational searches to the actual content format. The FAQ schema workshop was hands-on and we shipped the markup the same day.
How to join the next cohort
Sessions run online so you don't need to arrange travel. If you're in the Pietermaritzburg area and prefer an in-person option, we occasionally open seats at our Cascades Lifestyle Centre space — mention that in the enquiry form and we'll confirm availability.
- Fully online — join from Pietermaritzburg or anywhere in SA
- Small cohorts — open discussion is the format, not lectures
- Access to session recordings and shared audit files
- Bring your own site — real data used throughout
- +27 33 342 5508 for direct questions before enrolling
