How to set up a mobile website: first review your existing architecture and mobile display needs

When setting up a mobile website, first check whether you have a single site or separate URLs for desktop and mobile, then decide whether you need different content or simply need the same content to adapt to the screen. If your main requirement is to adjust the presentation, consider responsive design first. If you must keep two versions, you will need to handle device detection, redirects, and page mapping. The following guidance draws on the architectural explanations in the supplied material, without treating historical articles as current search rules.

Review your existing website before building a separate mobile version

Before you begin, divide the issue into three areas so that a poor mobile display does not automatically lead to adding another website:

• URLs: Do mobile and desktop visitors use the same URLs? Is there already a separate version identified by m or mobile?
• Presentation: Do you need to reformat the same content, or serve different HTML depending on the device?
• Maintenance: Can you modify the original site? If you keep two versions, are you willing to manage the relationships between their pages on an ongoing basis?

One poster on Warrior Forum described an old website built with FrontPage and a separate mobile version later built with WordPress. The mobile version then appeared in desktop search results and did not display well. The poster felt that the main site should have been revamped instead, but did not want to rebuild it because retirement was approaching. This is an individual case, not evidence that adding a mobile version will necessarily cause the same problem. Nor does the poster’s assessment establish the cause of the issue.

The three architectures differ in content delivery and maintenance

A 2022 Semrush article outlined three setup options that can help explain the differences:

• Responsive design: Uses the same URLs and HTML, with CSS adjusting the presentation to suit the device. The article listed benefits including easier link sharing, reduced maintenance, and no need for redirects to switch to a mobile version.
• Dynamic serving: Uses the same URLs, but the server sends different HTML depending on the device. Care is needed when determining which version to serve; the article warned that mobile devices might receive the desktop version, affecting the user experience.
• Separate URLs: Desktop and mobile versions have their own URLs, with the server detecting the device and redirecting it to the appropriate version. The article noted that this approach takes more time to manage and that redirects may slow loading.

So, if you simply need the same content to adapt to different screens, consider responsive design first. If limitations of the original site mean that both versions must be retained, you need to check not only how the mobile version looks, but also how the two versions are served.

If you already have two sets of URLs, clarify page mappings before changing tags

The same 2022 article explained separate URLs as follows: mobile pages use rel=”canonical” to point to their corresponding desktop pages, while desktop pages use rel=”alternate” to point to their corresponding mobile pages. This was the article’s technical advice at the time, not a current official rule verified here, nor a requirement for all websites to apply it.

In a situation like the forum example above, first clarify which pages correspond to one another, where the current tags point, and whether device-based redirects serve the expected version. The supplied material contains neither inspection results nor a record of a successful fix for that site, so there is no basis for promising that removing a particular tag will make the desktop version reappear in search results.