Technical SEOHeadless CMS
Sitemaps that stay honest after CMS edits
How we split sitemaps by collection and invalidate them on publish so search engines always see accurate URLs and timestamps.
The Blog
Responsive design isn't a feature, it's a ranking signal
Web performanceTechnical SEO
Most businesses assume their site "works on mobile." But Google's mobile-first indexing means the mobile version is the version, and the gap between technically responsive and genuinely mobile-optimised is where rankings and conversions are lost.
The shift
Google indexes the mobile version, not the desktop version
Since Google completed its move to mobile-first indexing, the mobile version of your site is what gets indexed, ranked, and evaluated. Not the desktop version. Not both. Mobile.
This means every SEO signal Google measures, content quality, page speed, structured data, internal links, is evaluated against the mobile experience. If content is hidden on mobile, Google may not see it at all. If Core Web Vitals fail on mobile but pass on desktop, you have a ranking problem.
Most Australian businesses get more than 60% of their traffic from mobile devices. Yet the desktop experience is still what gets designed first, reviewed by stakeholders on their laptops, and signed off in boardrooms on large screens. The version that matters most to Google is often the version that gets the least attention.
The gap
"Responsive" doesn't mean "mobile-optimised"
A responsive site adjusts to different screen sizes. A mobile-optimised site is designed to work well on small screens with touch input and variable network conditions. The difference is significant.
Responsive is a CSS behaviour, fluid grids, flexible images, media queries. It handles the layout. But layout is only part of the mobile experience. Touch targets, font sizes, content hierarchy, image loading, and interaction speed all matter independently of whether the layout adapts.
A site can be technically responsive, every element fits the screen, while still delivering a poor mobile experience. Tiny tap targets that frustrate thumbs. Text that requires pinching to read. Images loaded at desktop resolution over a mobile network. Navigation that works with a mouse but not a finger.
Google evaluates both. The layout adaptation is table stakes. The quality of the mobile experience is where rankings are won or lost.
The signals
How responsive design affects your SEO directly
Google doesn't have a single "responsive design" ranking factor. Instead, responsive design affects multiple ranking signals simultaneously. Understanding which ones matter most helps prioritise the right fixes.
- 01Core Web Vitals on mobile
Google measures Core Web Vitals on mobile devices specifically. LCP (loading speed) is affected by serving desktop-sized images to mobile viewports. CLS (layout shift) is affected by elements that resize unpredictably across breakpoints. INP (interaction speed) is affected by JavaScript that blocks touch responses. A site that passes CWV on desktop can fail on mobile, and mobile is what Google uses for rankings.
- 02Content parity
Content hidden on mobile via display: none or collapsed behind interactions may be deprioritised or ignored by Google. If your desktop site shows detailed service descriptions but the mobile version truncates them, Google indexes the truncated version. Internal links hidden on mobile don't pass PageRank the same way. The mobile content is the content.
- 03Viewport and mobile-usability signals
A missing viewport meta tag means mobile devices render the page at desktop width and scale it down. Google flags this as a mobile-usability failure. Touch targets smaller than 48×48 pixels, text requiring zoom to read, and horizontal scrolling all contribute to negative mobile-usability signals that affect how Google evaluates the page.
- 04Page speed on mobile networks
Mobile devices typically operate on slower, higher-latency networks than desktop. Images not sized for the viewport, render-blocking resources, and heavy JavaScript bundles have a disproportionate impact on mobile load times. Our image pipeline serves correctly sized WebP images per viewport specifically because of this, a 1920px desktop image has no place loading on a 375px phone.
The approach
Component-level, not page-level
Most teams treat responsive design as a page-level concern, "make the homepage work on mobile." We treat it as a component-level concern. Every block in the CMS library is responsive independently. The hero component handles its own breakpoints. The numbered grid handles its own. The comparison table handles its own.
This means responsive behaviour is tested and maintained per component, not per page. When a new page is assembled from existing blocks, it's responsive by default because every block already is. There's no "make this page mobile-friendly" task — it's built in.
For images, responsive behaviour goes deeper than CSS. The sizes attribute is set per component based on layout context. A full-width hero gets different sizes than a card thumbnail. The browser uses this to download the right image for the viewport, not the largest available image regardless of screen size.
Touch targets, font sizes, and spacing are part of the design system, not afterthoughts applied per page. A button is always tappable. Body text is always readable. Spacing always accounts for thumb reach and small screens.
The business impact
Why this matters beyond SEO
Mobile-first design isn't just an SEO play. For most Australian businesses, the majority of first impressions happen on a phone. A prospective client searches for your service, finds your site, and makes a judgement within seconds, on a 6-inch screen, possibly on a train, probably distracted.
If the site loads slowly, the text is too small, the navigation requires precision tapping, or the content they need is hidden behind a hamburger menu three levels deep, they leave. They don't resize their browser or try again on a laptop. They go to the next result.
The businesses that treat mobile as the primary experience, not a scaled-down version of desktop, are the ones that convert mobile visitors into enquiries. Good responsive design isn't a technical checkbox. It's revenue.