Transitioning to responsive design--should we re-direct m.?
-
We are moving to responsive design--should we 301 re-direct all of the old m.domain URLs to the corresponding domain.com
-
Very well elaborated, maybe I should have done so myself in my original response.
Always try 301 to relevant pages in this situation but if the redirect rules prove a headache (and the site has little to no inbound links) to create then I would simply remove the subdomain and 301 to main domain homepage. Somewhat of a Time vs Overall Benefit issue, or in some cases a Cost vs Benefit issue.
If the m.domain variant has links pointing to it then it's always beneficial to 301 the links the refering sites are pointing to - I'd try to do this as an absolute minimum in this situation.
It is common for mobile versions of sites have no links pointing to them apart from redirects from the main site so in that situation a 301would likely have zero affect whatsoever.
-
I would 2nd William's response here. If there are any links/bookmarks pointing to your mobile pages, you'll want those 301s in the long term. And short term, any pages Googlebot mobile has indexed that are getting mobile search referrals will pass those users along accordingly (and signal to Google to update their index).
In short, yes - 301s would be the way to go.
One caveat: if it's a big undertaking to do this (if you can't match all subdomain requests with a .htaccess redirect pattern and you have a ton of pages, for example) I'd first take a look at the mobile search traffic, referral traffic and inbound links to your m. subdomain. This way you can determine how much you'll be losing out on if you don't set up the 301s. If your mobile site is new enough, not getting a tremendous amount of traffic and has no direct referral sources or inbound links, you may be able to get away without 301ing. I'd probably still push for them though.
-
Redirecting the old mobile version of your site to the new responsive design with 301 redirects would pass on any page authority to the corresponding page on domain.com and a responsive design is generally superior in terms of UX.
In my opinion it would be good practice to forward from an exiting mobile version to a new responsive version as per the serve one page to all devices guideline. Using a 301 redirect would be the correct way to do this.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Best Practices to Design Site Mock Up Using Wordpress Rather than Wireframes?
We are in the process of redesigning our real estate website. Our designer/developer is very quick and confident on Wordpress. He suggests designing directly on Wordpress and bypassing wireframes and a mock ups. He is very confident in his Wordpress abilities. Is it a mistake to take this approach? He has also asked that we select a real estate theme at this point. I would think that the theme would be selected after the wireframes and mock ups get done. But there are certainly different approaches. Are there best practices for redesigning a webiste; any suggestions? Are there significant risks/disadvantages to bypassing wireframes/mock ups? Thanks,
Intermediate & Advanced SEO | | Kingalan1
Alan Rosinsky0 -
Domain Change for a well positioned website... I'm a-scared
Hello, A few years ago I have "inherited" a website about a particular touristic area in Italy (the Langhe region) called langhe.net. The website is very well positioned, the domain has been registered in '97 and the overall SEO performance is pretty good (it ranks in the top #3 positions for all the main search queries in our niche). We are currently redesigning the whole thing, and one of the idea was to change the domain (and the name) of the website from langhe.net to lovelanghe.com (which we already registered). The reasons behind this decision are the following (most important first): Google prefer brands over keywords and "Langhe" is just a keyword LoveLanghe looks more memorable and "marketable" than just Langhe.net All our social presence is branded already as LoveLanghe (they were created years back under this name - I don't know why) We will do our due diligence work (301 everything, domain change in Search Console etc. etc.) but I'm still kind of worried that we will lose some ranking. So my question(s) are: do you think it's a good idea to change the domain when ranking is good and original domain is so old? how much ranking (approximately) are we going to lose? Thanks in advance 🙂 Best
Intermediate & Advanced SEO | | Enrico_Cassinelli0 -
Strange: page no longer present in SERPS and I'm not sure why
I indexed a new page last week and it ranked 1st The page is still live, still registering sessions in analytics, registering activity in search console Why is it no longer present for the keyword in ranked first for on Friday?
Intermediate & Advanced SEO | | Jacksons_Fencing0 -
Moving from M. to Responsive: Rel Alternate Considerations
Hey Guys, We’re in the process of transitioning our key traffic generating pages on our website from m. to responsive. Today, our site uses Google’s ‘Separate URLs’ method. Rel alternate on desktop pages to m. pages 302 redirects pushing mobile visitors to m. pages Canonical on m. pages back to desktop pages As we make the transition to responsive we’ll be taking the following steps: Removal of 302 redirects pushing mobile visitors to m. pages 301 redirects from m. pages to desktop pages With those changes in mind, I’d love to get the communities opinion on how to best handle the real alternate attribute on desktop pages. I'm considering leaving the rel alternate attribute in place on desktop pages for 30-90 days so that search engines continue to see the alternate version without the 302 redirects in place, crawl it, and as a result discover the 301 redirects more readily. If we remove the 302 redirects as well as the rel alternate, then my feeling is that search engines would just index the responsive page accordingly and be less likely to catch the 301 redirects pointing from the m. pages and make the transition of mobile pages in search indices take longer than necessary. Ultimately, I'm probably splitting hairs and getting a bit nuanced because I believe things will work themselves out whether we leave the rel alternate or remove it but I thought it would be great to get any opinions or thoughts from community members that have made a similar transition. Thanks in advance for stopping by and providing your thoughts. All the best,
Intermediate & Advanced SEO | | TakeLessons
Jon PS - for your reference, the only mention that I was able to dig up in Q&A for a move from m. to responsive are the following: Redirecting M Dot Mobile Website to Responsive Design Website Questions SEO Concerns From Moving Mobile M Dot site to Responsive Version?0 -
Site re-design, full site domain A/B test, will we drop in rankings while leaking traffic
We are re-launching a client site that does very well in Google. The new site is on a www2 domain which we are going to send a controlled amount of traffic to, 10%, 25%, 50%, 75% to 100% over a 5 week period. This will lead to a reduction in traffic to the original domain. As I don't want to launch a competing domain the www2 site will not be indexed until 100% is reached. If Google sees the traffic numbers reducing over this period will we drop? This is the only part I am unsure of as the urls and site structure are the same apart from some new lower level pages which we will introduce in a controlled manner later? Any thoughts or experience of this type of re-launch would be much appreciated. Thanks Pete
Intermediate & Advanced SEO | | leshonk0 -
Looking for re-assurance on this one: Sitemap approach for multi-subdomains
Hi All: Just looking for a bit of "yeah it'll be fine" reassurance on this before we go ahead and implement: We've got a main accommodation listing website under www.* and a separate travel content site using a completely different platform on blog.* (same domain - diffn't sub-domain). We pull in snippets of content from blog.* > www.* using a feed and we have cross-links going both ways, e.g. links to find accommodation in blog articles and links to blog articles from accommodation listings. Look-and-feel wise they're fully integrated. The blog.* site is a tab under the main nav. What i'd like to do is get Google (and others) to view this whole thing as one site - and attribute any SEO benefit of content on blog.* pages to the www.* domain. Make sense? So, done a bit of reading - and here's what i've come up with: Seperate sitemaps for each, both located in the root of www site www.example.com/sitemap-www www.example.com/sitemap-blog robots.txt in root of www site to have single sitemap entry: sitemap : www.example.com/sitemap-www robots.txt in root of blog site to have single sitemap entry: sitemap: www.example.com/sitemap-blog Submit both sitemaps to Webmaster tools. Does this sound reasonable? Any better approaches? Anything I'm missing? All input appreciated!
Intermediate & Advanced SEO | | AABAB0 -
Can re-directs decrease your rankings??
Hi Guys, I need some advice here please - I have the chance to put some links on a few websites to my website in hope it will help with my rankings.. BUT - I have noticed that the webstites are being re-directed to another websites.. so my questions is ; Can re-driects decrease your rankings?? Thanks Gareth
Intermediate & Advanced SEO | | GAZ090 -
What are the best strategies to organize a htaccess full of 301 re-directs
I have a client with a htaccess file that is a total mess! What are the best practices to organize all the re-directs, and make it more manageable in the future. Any resources would be appreciated.
Intermediate & Advanced SEO | | anchorwave0