What is the mobile version of a website called?

For years, the answer to "what is the mobile version of a website called?" was simple: an m-dot site. If you visited a business on your phone in the early 2010s, you were often redirected to a stripped-down copy living at a subdomain like m.example.com — a completely separate website built just for mobile visitors.

Google's own documentation calls this configuration "m-dot URLs" and lists it as one of three mobile site setups the search engine officially recognizes. According to Google Search Central, the three configurations are:

• Responsive design — the same HTML served on the same URL regardless of device, with the layout adapting to screen size
• Dynamic serving — one URL for everyone, but the server delivers different HTML based on user-agent sniffing and the Vary: user-agent HTTP header
• Separate URLs — different HTML on different URLs per device, with the desktop URL always serving as the canonical and the mobile version as the alternate

At the time, the m-dot approach made intuitive sense. Phones had small screens, slow connections, and limited processing power, so building a lighter, simpler second site felt like the obvious fix. Small business owners especially liked the logic: keep the desktop site untouched, spin up a mobile version, and reach customers wherever they are.

The mechanics were straightforward, too. The server detected whether a visitor was on a smartphone and redirected them to the mobile URL, relying on the same user-agent detection and Vary headers used in dynamic serving. No redesign of the main site required — just a parallel property.

But maintaining two sites meant maintaining two of everything: two sets of URLs, two content updates for every price change or new service, and two chances for things to fall out of sync. As Google's Webmaster Relations team noted, "with more sites moving towards responsive web design, many webmasters have questions about migrating from separate mobile URLs, also frequently known as m-dot URLs."

The approach also created real technical debt. Migrating away from an m-dot setup later requires 301 redirects configured on a per-page basis, self-referential canonical tags, and the removal of mobile-specific redirects and headers — a project, not a quick fix. It's a key reason modern providers like AI Business Sites build a single responsive site instead of separate versions, eliminating the split-site problem before it starts.

The m-dot era answered the question with a second website. Today, the answer is one site that adapts — and that shift changed how every business approaches mobile.

For years, running a separate mobile site meant maintaining two of everything — two URLs, two content sets, two sets of analytics headaches. Google has quietly made that approach a liability, and the industry has followed. Today, the recommended answer is one site that adapts to every screen.

Google officially recognizes three mobile configurations: responsive design, dynamic serving, and separate m-dot URLs. But its Search Central documentation is blunt about which one it prefers: responsive web design, because it's "the easiest design pattern to implement and maintain." A responsive site serves the same HTML on the same URL regardless of device, letting fluid grids, flexible images, and CSS media queries reshape the layout to fit the screen — an approach originally defined by Ethan Marcotte, according to Google's developer advocates.

The bigger reason for the shift is how Google now reads your site. Under mobile-first indexing, Google crawls with its smartphone agent and uses only the mobile version of your content for indexing and ranking. As Google's documentation explains, only the content shown on the mobile site is used for indexing. If your m-dot site trims content that exists on desktop, those pages may simply not rank for the keywords you're missing — a quiet, invisible loss of traffic that most site owners never notice until rankings slip.

A single responsive site eliminates that risk by design, because there's no way for mobile and desktop content to drift apart. It also simplifies the technical plumbing:

• No 301 redirect migrations from m-dot URLs to responsive URLs, page by page
• No conditional redirects, Vary headers, or user-agent sniffing to maintain
• No separate canonical rules — the desktop URL always serves as canonical on m-dot setups, adding complexity responsive sites avoid
• One URL structure for analytics, reporting, and link building

Google's own Webmaster Relations team notes that moving to a responsive site makes "maintenance and reporting much easier" down the road — one reason so many webmasters have migrated away from m-dot configurations entirely.

This is why modern site builds, including the sites AI Business Sites creates for small businesses, are responsive by default: one site, every screen, no content gaps for Google to penalize. If your business still runs a separate mobile version, the safest move is a proper migration — 301 redirects per page, self-referential canonical tags, and removal of mobile-specific configurations — so nothing gets lost in the transition.

Running two websites sounds like a small technical detail. In practice, it's a second full-time job that most business owners never signed up for.

Every page you publish has to exist twice — once on your desktop site, once on your m-dot site. And they can't just look similar; they need matching content. Google's official documentation is blunt about why: with mobile-first indexing, "only the content shown on the mobile site is used for indexing." If your mobile version trims content, your rankings quietly suffer.

The tagging rules add another layer of fragility. Google requires that "the desktop URL is always the canonical, and the mobile version is the alternate of that URL," per its mobile configuration guidelines. Get those canonical and alternate tags wrong on a single page, and you can end up competing against yourself in search results.

Then there's the plumbing most owners never see:

• Conditional redirects that must detect each visitor's device and route them to the right URL — and back again when they switch
• Vary: user-agent HTTP headers that tell crawlers which version of a page to fetch, and which break caching when misconfigured
• Per-page 301 redirect maps that must be maintained whenever either site changes

None of this creates value for customers. It's pure overhead that exists only because the site was split in two.

Analytics get murky too. Traffic, conversions, and search performance split across two URL sets, which means every report needs stitching before it means anything. Google's own migration guidance notes that moving to a responsive site makes maintenance and reporting much easier — a diplomatic way of saying the two-site setup makes both harder.

The maintenance burden compounds over time. Every new service page, blog post, or price update doubles in scope. Every redesign means redesigning twice. And when something breaks — a redirect loop, a missing canonical tag — it usually breaks invisibly, surfacing only as a slow rankings decline nobody can diagnose.

This is the quiet reason the industry moved on. A single responsive site, built the way AI Business Sites approaches it — one URL, one content set, layout adapting to any screen — eliminates the duplicate work entirely. You publish once, and the same page serves the customer on a phone, a tablet, or a desktop.

For a busy owner, that's the real argument: two sites means double the work and half the clarity. One responsive site means neither.

If your business still runs a separate m-dot site, you're maintaining two versions of every page — and Google has published a clear playbook for consolidating into one. The migration process is straightforward, but skipping steps can cost you rankings you've already earned.

The first step is setting up 301 redirects on a per-page basis, mapping each old mobile URL to its new responsive counterpart, as outlined in Google's official migration guide. Don't redirect everything to the homepage — each m-dot page should point to the equivalent page on the responsive site.

Next, configure self-referential rel=canonical tags on your responsive URLs. Google's Webmaster Relations team recommends this as a good practice during migration, ensuring search engines understand which URL is the definitive version of each page.

Finally, strip out the mobile-specific machinery your old setup required. Your migration checklist should include:

• Remove conditional redirects that sent mobile users to m-dot URLs based on user-agent detection
• Remove the Vary: user-agent HTTP headers that dynamic serving configurations depended on
• Verify full content parity — every page delivers the same content regardless of device

That last point matters more than most site owners realize. Under Google's mobile-first indexing system, only the content shown on the mobile version of your site is used for indexing and ranking. If your mobile pages carried less content than their desktop equivalents — a common shortcut on m-dot sites — those pages may not have ranked for all the keywords they deserved.

The payoff is simpler operations. As Google's migration documentation notes, moving to a responsive site makes maintenance and reporting much easier, because you no longer manage separate URLs for every page. One sitemap, one analytics view, one set of canonical rules.

This is also why modern site builds default to responsive design from day one — it eliminates the migration problem entirely. A site built on a framework like Next.js, the approach AI Business Sites uses for client builds, serves one URL and one set of HTML to every device, with layout handled by CSS rather than redirects and separate content. If you're starting fresh, that's the configuration Google recommends: the easiest pattern to implement and maintain, with no parity gaps to police.

What a Mobile-First Business Website Looks Like Today

A responsive website automatically adjusts its layout, images, and content to fit any screen size, from smartphones to desktop monitors, using fluid grids and flexible images. This approach eliminates the need for separate mobile URLs like m.example.com, which Google identifies as one of three recognized mobile configurations but no longer recommends. Instead, responsive design uses a single URL and HTML code that adapts via CSS media queries, making it easier to implement and maintain.

Google’s mobile-first indexing means the search engine primarily uses the mobile version of your site’s content for ranking and indexing, so ensuring content parity between mobile and desktop views is essential for visibility. A responsive site built with the viewport meta tag set to width=device-width, initial-scale=1 establishes a 1:1 relationship between CSS pixels and device-independent pixels, allowing content to scale properly across devices. For optimal readability, content should determine breakpoints rather than targeting specific device widths, with ideal column width falls between 70 to 80 characters per line.

• Fluid grids that resize proportionally
• Flexible images that scale within containers
• CSS media queries that apply styles at defined breakpoints
• Viewport configuration for proper mobile rendering
• Content-driven breakpoints instead of device-specific ones

For small businesses, a mobile-first responsive site means faster load times on cellular networks, consistent branding across devices, and a unified SEO strategy that avoids duplicate content issues. It also supports local search performance by delivering the same structured data and location information whether accessed from a phone or laptop. AI Business Sites builds every site with this mobile-first responsive foundation, ensuring 85+ pages launch fully functional and optimized for lead capture on any device — no separate mobile site to manage, no content to duplicate, and no risk of mobile-first indexing penalties.