Mobile Site Architecture
Ankit Agarwal · Head of Marketing
Mobile site architecture is how a site's pages, URLs and internal links are organized and served on phones, including responsive, dynamic or m-dot setups.
What is Mobile Site Architecture?
Mobile site architecture is the way a website’s pages, URL structure and internal links are organized and delivered to smartphone users and crawlers. It includes the serving configuration (responsive design, dynamic serving or separate mobile URLs), the navigation and linking that mobile templates expose, and how deep important pages sit from the homepage on mobile.
Because Google indexes the mobile version, mobile architecture is now simply site architecture as Google sees it. A link that only exists on desktop does not help Google find or rank a page.
Architecture decisions are hard to undo, so they deserve attention early in a redesign. Choosing responsive design, keeping URLs stable and planning how menus and hubs will work on small screens prevents the most common mobile SEO problems before any content is written.
How it works
| Setup | URL | HTML | SEO risk |
|---|---|---|---|
| Responsive | Same | Same | Lowest |
| Dynamic serving | Same | Varies by device | Medium (needs Vary header, parity) |
| Separate URLs (m-dot) | Different | Different | Highest (redirects, annotations, parity) |
Beyond the setup, good mobile architecture means:
- Shallow depth: key pages reachable in a few taps and links from the homepage.
- Consistent links: the same internal links on mobile as on desktop, even if presented in menus or accordions.
- Breadcrumbs: compact breadcrumb trails that show hierarchy and add internal links.
- Hub pages: topic or category hubs that group related content for both users and crawlers.
Examples
- For example, a B2B SaaS site’s desktop mega-menu links to 60 solution and integration pages, but the mobile menu shows only six top-level items, and the rest load on tap via JavaScript. Under mobile-first indexing, many integration pages lose internal links. Rendering the full menu in HTML and adding an integrations hub restores them.
- A company migrates from m.example.com to responsive design, redirecting each mobile URL to its single responsive URL and removing alternate annotations.
Best practices
- Choose responsive design for new builds and migrations.
- Crawl with a smartphone user agent and compare link counts per page against desktop.
- Use hub pages and breadcrumbs to keep depth shallow without overloading menus.
- Keep the URL structure the same across devices.
Common mistakes
- Removing “secondary” links on mobile that actually carry internal link equity.
- Running dynamic serving without the Vary: User-Agent header, which can cause caches to serve the wrong version.
Related terms
- Site Architecture
- Mobile Site Navigation
- Mobile Redirects
- Internal Linking
- Breadcrumbs
- URL Structure
Sources
Frequently asked questions
What are the three mobile configurations?
Responsive design serves the same HTML on the same URL to all devices and adapts with CSS. Dynamic serving uses the same URL but sends different HTML depending on the user agent, which requires a Vary: User-Agent header. Separate URLs serve mobile pages on a different host such as m.example.com, linked with canonical and alternate tags.
Which mobile configuration is best for SEO?
Google recommends responsive design because it is the easiest to implement and maintain, uses one URL per page and avoids parity, redirect and annotation errors. Dynamic serving and separate URLs are supported but carry more risk of mismatched content. Migrating to responsive design is usually worth it.
How does mobile architecture affect internal linking?
Google discovers and evaluates pages through the links on the mobile version. If mobile templates drop footer links, related content modules or breadcrumbs that exist on desktop, deeper pages get fewer internal links and may be crawled and ranked less.
