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
-
Page auto directing to /#/id0 but no 301 in place?
I'm a little perplexed and hope someone technically savvy can help. Wordpress site. Our page: www.curveball-media.co.uk/animation Redirects to: www.curveball-media.co.uk/animation/#/id0 I cannot see any reason for this. No 301s, nothing.
Intermediate & Advanced SEO | | curveballmedia0 -
Is it possible to direct HTTP www 301 to HTTPS non www?
I have a question that has been stumping me and if someone could help I would gladly buy your coffee for a month. I have a website that used to be www and http a year or two ago. Now it is https and non www. A lot of my older links point to the www and http version of my site. This results in two 301 redirects. I.e. A link on another site to my site points to http://www.mysite.com The network waterfall shows: http://www.mysite.com 301 -> http://mysite.com http://mysite.com 301 -> https://mysite.com https://mysite.com (finally) **2 part question. ** **--Do you think that this two 301 redirect hop would affect SEO performance? I can see it did affect page authority through Moz. ** --Is there away around this? I.e. to redirect http:// AND http://www directly to https:// with no hops in between. Thank you!
Intermediate & Advanced SEO | | Stodzy0 -
What strategies can you use when you're optimizing for 10 locations x 20+ services?
We have a client site (a dentist) that has 10 locations and 20+ services (braces, teeth whitening, cosmetic dentistry, etc, etc.). We're trying to figure out the ideal approach to optimally cover all their locations and services, but each option we consider has drawbacks: Optimize service pages for service name + each location name (or at least the biggest location names), with service name and location names in the title tag. That results in a too long title tag, plus possible user confusion, since they are searching for "braces richmond" but the title tag lists other cities, some of which are in a different state. Optimize service pages for service name + each location name, but don't include the locations in the page title. This is the current option being used, but it appears to be hurting the rankings at least a bit not having the location name in the page title. Create a page for each service + location combo. That will be 200+ pages, which will mean the pages will be deeper in the site, with less link juice. Create new domains for each location/state covered. But then we have to start over building link juice. How have other sites dealt with this? What has worked best and what hasn't worked?
Intermediate & Advanced SEO | | AdamThompson2 -
Do I need to re-index the page after editing URL?
Hi, I had to edit some of the URLs. But, google is still showing my old URL in search results for certain keywords, which ofc get 404. By crawling with ScremingFrog it gets me 301 'page not found' and still giving old URLs. Why is that? And do I need to re-index pages with new URLs? Is 'fetch as Google' enough to do that or any other advice? Thanks a lot, hope the topic will help to someone else too. Dusan
Intermediate & Advanced SEO | | Chemometec0 -
You're given 10,000 recipes and told to build a site--what would you do?
Say you were given a list of 10,000 recipes and asked to build an SEO friendly site. Would you build a recipe search engine and index the search results (of course making sure that IA and user engagement metrics are great)? Or, would you try to build static pages?
Intermediate & Advanced SEO | | nicole.healthline0 -
Is it worth re-doing SEO for all existent products
We have a website and when we started, we had no clue about SEO, nor did we really understand the full extent of CRO amongst other things. We have slowly learnt that there are many changes that need to happen to our site; however...do we need to re SEO all the content that is already on the website or can we purely start a fresh with the new products we feed through? The website is: www.onlineforequine.co.uk if you need to take a look at the kind of platform we are working with.
Intermediate & Advanced SEO | | onlineforequine0 -
Re-platform effects on Page Rank
We are performing a major replatform for an ecommerce client who has many top listings on page 1 in Google SERPs for very competitive terms. We are implementing a 301 redirect for all existing URLs that they have now to the appropriate new URLs, but the client is concerned with how deploying a new site with 100% new URLs and site structure will impact their Page Rank. From our experience, the 301 redirects should cover it but wanted to see if there is a way to predictively forecast page rank effects as a result of re-platforming.
Intermediate & Advanced SEO | | Bucktown0 -
A Blog Structure Dilemma We're Facing...
We're launching a pretty large content program (in the form of a blog) and have a structure issue: Big fans of Wordpress for efficiency reasons, but our platform doesn't allow hosting of a wordpess (or other 3rd party) blog on the primary domain where we want it. site.com/blog Here are the options: 1. Sub-domain: We can easily put it there. Benefit is we use the efficient Wordpress tools and very fast to setup etc. Downside is that the root domain won't get benefit of any backlinks to the blog (as far as I understand). I also don't believe the primary domain will benefit from the daily fresh/unique content the blog offers. 2. Custom Rig: We could create our own manual system of pages on the site to look just like our blog would. This would allow us to have it at site.com/blog and benefit from any backlinks and fresh content. The downside is that it won't be as efficient to manage. 3. External Site: Create a different site just for the blog. Same issue as the sub-domain I believe. User Experience is a top priority, and all of the above pretty much can accomplish the same UX goal, with #3 requiring a some additional strategy on positioning. Is #1 of #3 going to be a big regret down the road though, and is the backlink/content benefit clearly worth doing #2? (correct me if I'm wrong on my assumptions with #1 but at least with the backlinks I'm almost certain that's the case) Many thanks for your inputs on this.
Intermediate & Advanced SEO | | SEOPA0