Case Study: Here's How Moving to Responsive Design Website Helped Our Brand - Moz

This SEO case study documents a successful optimization initiative, providing actionable insights for practitioners. The documented approach demonstrates how strategic SEO implementation drives measurable results.

Initial Situation

Understanding the starting point is essential context for evaluating any case study. This documentation covers the initial challenges, competitive position, and business objectives that shaped the SEO strategy.

Strategy and Approach

The strategic approach combined multiple SEO disciplines to address identified opportunities. Key decisions around prioritization and resource allocation provide a template for similar initiatives.

Implementation

Moving from strategy to execution required specific technical implementations, content development, and process changes. This case study documents the practical steps that translated strategy into action.

Results and Learnings

The outcomes demonstrate effectiveness through measurable improvements in rankings, traffic, and business metrics. Analysis of successes and challenges provides learning value for practitioners.

Case studies like this contribute to the SEO knowledge base, helping practitioners learn from documented real-world experiences.

Source: https://moz.com/ugc/case-study-heres-how-moving-to-responsive-design-website-helped-our-brand

Practitioner notes on the move to responsive

The strongest argument for responsive design is consolidation. With a separate mobile site you have two URLs for every page, two sets of signals to reconcile, and a web of redirects and cross links that has to be maintained perfectly or value leaks. Responsive collapses all of that into a single URL that adapts its layout to the viewport, so every link, share, and citation points at the same place.

The technical foundation is small and well established: a viewport meta tag so the browser uses the device width, fluid layouts built with relative units and modern CSS layout, and responsive images that hand the browser a set of sources so it can pick an appropriately sized file. The point of responsive images is to avoid shipping a desktop sized file to a phone, which is one of the most common ways a technically responsive site ends up slow.

That leads to the honest caveat. Responsive design solves the indexing and signal problems, but it does not make a page fast on its own. A fluid layout can still load megabytes of images, blocking scripts, and heavy fonts. After a responsive migration the work shifts to performance, and the right yardstick is Core Web Vitals measured on real devices rather than a fast laptop. The difference between what your lab tools report and what users experience is covered in the field versus lab data guide, and Largest Contentful Paint is usually the first metric to watch, explained in the LCP guide.

What has changed since this case study

Responsive design is now the default recommendation, and the separate mobile URL pattern has largely been retired. Because Google indexes the mobile version of every site, a single responsive document is the simplest way to guarantee parity between what desktop and mobile users and crawlers see. Google also retired its standalone Mobile Friendly Test tool at the end of 2023 and now folds that checking into Lighthouse and the URL Inspection tool, so the way you validate has changed even though the responsive recommendation has not. For a current overview of crawler behaviour on mobile, see the mobile SEO FAQ, and if you are on WordPress the speed up WordPress guide covers the performance follow up.

Responsive versus the alternatives

For most sites the first row is the right answer. The other two solve narrower problems and add operational cost that responsive avoids.

Frequently asked questions