301 Not Allowed...Other Solutions?
-
A client's site where both the www. and non-www. versions are both being indexed. The non-www. version have has roughly 1000 or so links where the www. version has over twice as much pointing back to the site. In addition, the www. version has higher domain authority.
Their programmer has suggested that they can't implement 301's permanent redirects across their site for a few reasons.
My question is, what would be the best alternative to block/redirect the non-www. version from being indexed yet still pass link-juice?
-
Hey James - I am curious as to why you think a 'canonical tag' wouldn't be a "long term fix"?
-
Thanks for the responses everyone. Everyone seems to be in agreement that a '301' is the proper course of action and should be explained that way.
I just have never run into a developer opposing the idea. So, thanks again for the feedback!
-
1st of all if the developer says he won't use the 301 then he's one very strange developer it's the basic of frontend development. But that being as it is, 301 is the best and most viable option but you do have a few other:
- tell GWT your prefered domain.
- have the devloper make a dynamic rel canonical, something like this (in php)
' ?>
in the above situation he of cause would have to make a function called checkURL to test for if the url begins with http://www and returns the right formatted version. and tell GWT what domain you prefer.
But again the only right way is a 301 and it's ridiculously simple to make.
-
If you properly communicate why 301 Redirects are the only proper solution, and you continue to run up against a dev who makes up pie in the sky technical "reasons" why they can't, then the question is whether they respect you enough, put enough value in your view, recommendation.
Setting that aside, the canonical tag, coupled with going into Google Webmaster Tools and setting the www version as the preferred version will help, but as has been pointed out, not in anything close to resembling an ideal way.
For long term sanity, I highly recommend you explore why you're getting the resistence. Is it because the dev feels threatened, or doesn't want to do the work? Setting up server-wide 301 Redirects is NOT that difficult or time consuming for anyone who knows what they're doing. So you may want to provide them links to the "how-to" for their particular server configuration.
If they are lazy, you'll need to find a way to show the decision maker(s) that failing to implement them is costing the company revenue.
-
My Advice is to make a deck/ business case for the programmer show him the problems with having two versions of the website indexed. I have encountered a few developers who are not really in tune with the whole issues around duplicate content and SEO. I think the best idea is to act on the same page, show the developer some respect, show him the design is good but then also educate him about SEO.
If you do a cononical tag, sorry to say but it is not going to be a long term fix, it will just be a short term fix.
Try and push for the 301's.
-
I have never encountered a developer who resisted using a redirect for the non-www URLs to the www form. If you have access to the server, the change should be able to be made.
If you decide not to use a 301,use a canonical tag to identify the correct version of the page. I would also use both Google and Bing Webmaster Tools to indicate which URL format you wish to use.
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
-
Phasing in new website on www2 domain - 301 plan
Hi, I work for a large company and we're planning to phase in a new website. The idea is to develop key journeys on the new site and serve them on a www2 domain, removing them from the old website which is served on the www domain. The reason for this is because the old website is over 2,000 pages, and the management want to see new, improved journeys sooner rather than later. So, rather than launching all new pages and journeys at the same time, which will take a long time to design and develop, key journeys will move across to the new site / design sooner and made available to visitors. Whilst the overall journey might be a bit disjointed in parts (i.e. sending people from old to new site, and vice versa) I can't see a better way of doing it... Once all new content is complete, 301s will be implemented from old content on www. to new content www2. Once the phasing is complete, and all new content is in place on www2, 301s will be implemented to point everything back to www. Does anybody see any problems with this approach? Or any ideas on how to better handle this situation? Thanks Mozzers!
Intermediate & Advanced SEO | | RWesley0 -
301 re-direct affect on SERPS
Hi Moz Community, please can I hit you with a scenario and get your thoughts? We have a client site - clientsite.com - with reasonable rankings for some of our client's target search terms/branded terms. We have built language specific subdomains - it.clientsite.com, de.clientsite.com - which have been manually translated into local languages. These subdomains have robots 'noindex' as we only want to drive traffic to clientsite.com. We've installed a geo location tool on clientsite.com that 301s visitors to the appropriate subdomain, so content is served in their local language. clientsite.com will be the 'catch all' for locations where sub domains have not yet been created. If Google crawls clientsite.com and is 301ed to a sub domain, will we lose SERPS? The sub domains will have the same content (99% the same content anyway) as clientsite.com, but in local languages. Cheers guys. Steve
Intermediate & Advanced SEO | | steviechat1 -
Redirect 301 still works?
Hi, yesterday a friend said that 301 redirects does not transfer your page rank or domain autorithy anymore. I could'nt find anything in internet saying it, but I decided to ask you guys, since I think you are very reliable. so, 301 redirects wroks for transfer page rank, and i can create better domains and transfer everything, or this strategy is gone forever now?
Intermediate & Advanced SEO | | chablau0 -
Moving to a new domain name - 301 redirect NOT an option
Hi everyone My question concerns moving from an old to a new domain name without losing all previous SEO efforts. I am aware that a properly executed 301 redirect is the answer and way to go as well as telling Google about it in Webmaster Tools. However, what is the situation, if you do not own the old domain name anymore? If you have no means of getting back the old domain name and wanting to basically mask/switch the already existing website to the new domain name, will search engines penalise the "new site" as a duplicate, since the "old site" is still in the search engine rankings? I know that not being able to execute a proper 301 redirect and starting out with a new domain means a fresh start, but what is the best way to minimise the negative impact (if any)? Basically dropping the sites' current content and starting out new in favour of the new domain name is not really an option. Even if you were to take the content from the old site and place it on another site, this would surely be seen as duplicate too. Anyone thinks that Webmaster Tools/Google is savvy enough to spot the difference when the "old site" gets removed and the "new one" added instead (in Webmaster Tools). I read something along the lines about having your host point the DNS from the old site to the new one. Could something like be helpful? Thanks all in advance for your help and input!
Intermediate & Advanced SEO | | Hermski0 -
Images Returning 404 Error Codes. 301 Redirects?
We're working with a site that has gone through a lot of changes over the years - ownership, complete site redesigns, different platforms, etc. - and we are finding that there are both a lot of pages and individual images that are returning 404 error codes in the Moz crawls. We're doing 301 redirects for the pages, but what would the best course of action be for the images? The images obviously don't exist on the site anymore and are therefore returning the 404 error codes. Should we do a 301 redirect to another similar image that is on the site now or redirect the images to an actual page? Or is there another solution that I'm not considering (besides doing nothing)? We'll go through the site to make sure that there aren't any pages within the site that are still linking to those images, which is probably where the 404 errors are coming from. Based on feedback below it sounds like once we do that, leaving them alone is a good option.
Intermediate & Advanced SEO | | garrettkite0 -
301 page into a 404
Hi I have a job board site and the way the site is built means that I cant 404 job pages once they have expired. To combat this Im looking to 301 the pages into a 404 page.Do any of you have any experience with this? Are there any potential pitfalls to doing a 404 this way? Thanks
Intermediate & Advanced SEO | | AndrewAkesson0 -
Cannot 301 redirect, alternatives?
Hi, the company has changed it's name so now under a different domain. All pages have been 301 redirected on a 1:1 basis apart from the home page. For some reason IT cannot 301 redirect the old home page to the new website home page. At suggestions? Perhaps canonical it? Meantime the old home page copy has been changed to say the company name has changed and a link to the new website. Any help greatly appreciated.
Intermediate & Advanced SEO | | Richard5550 -
Setting Up Google Analytics for domains with 301
I have a client with a google analytics account that is a mess. domaina.com domainb.com 302's to domaina.com domainc.com 302's to domaina.com domaind.com 302's to domaina.com I thought the client was doing 301s on all these domains to the primary domain. I have logged into there analytics account and found data is being tracked on the other domains i.e domainb,c,d.com etc. How is it possible that google analytics is tracking data on these domains when no analytics code has been created and the urls are redirecting to domaina.com? Also there are not sites on these domains so for webmaster tools should I enable domain verification through a cname on the dns? Also I can I best setup a way to track traffic coming from say domainb.com? Whats the best step by step guide to use to set this up.
Intermediate & Advanced SEO | | JohnW-UK0