URL redirecting domains
-
Hi
Is there anything wrong/dangerous forwarding a clutch of domains to a sub page (landing page) on a different domain ?
Say Brand X buys Brand Z and wants to close down Brand Z site but have Brand Z domain fwd to a landing page (explaining the company acquisition) on Brand X site. In addition Brand Z had a few related but unused domains forwarding to Brand Z doman & now also wants those fwd'd to the new landing page on brand X
Since the reasons for doing this forwarding are legitimate company reasons relating to an acquisition i would have thought it should be ok but can anyone think of a reason why could be bad since i remember in the old days peeps used to redirect domains for seo reasons so worried fwd'ing a load of domains could cause some sort of negative flag with big G ?
Also do domain redirects transfer the authority/juice from the old site/domain to the new destination page (new landing page on brand x site) similar to how a 301 redirect works ?
Many Thanks
Dan
-
Good stuff ! thanks for all your help Aleyda
-
Your registrar usually gives you the option to choose if it's a temporary or a permanent situation so it forwards with 302 or 301 depending on that. Nonetheless, you can check directly yourself very easily with: http://web-sniffer.net/ by taking a look at the HTTP response header of the forwarded domain (and see if it's a 301). Good luck with the new domain
-
Thanks Aleyda
yes have done this already
Im just trying to establish if this acts like a 301 still in regard to the passing of old domains authority to the new url being fwd'd to ?
Thanks
Dan
-
Hi Dan, my domain registrar let me forward to any URL (not necessarily another domain root) so there shouldn't be an issue to do it. I recommend that you check with your registrar if you can do the same with yours. Thanks
-
Thanks Aleyda
Its going to redirect/forwarding to a specific landing page on the new domain, not the domain itself
Many Thanks
Dan
-
Hi Dan! Thanks for the clarification. This change it all really and is pretty straightforward then: You should directly go to your domain registrar and set the "Domain Forwarding" option to go to the new domain.
-
Hi Aleyda
Thanks so much for spending the time to write such a detailed and informative reply
However its the domain being redirected not the pages, since all the old pages have been removed from the web & hosting shut down (due it being an acquisition & not a migration). This means no opportunity for a .htaccess file as far as i understand since that requires a server to sit on doesnt it? and there isnt one anymore.
So we have just redirected the old domain to a landing page on the acquiring companies website via standard domain forwarding within the dns control panel. Do you know if this will act like a 301 i.e. transfer the old domains authority to the landing page ?
Many Thanks
Dan
-
Hi Dan,
What is is important in these types of scenarios is that you make sure that the redirects are relevant from a user and SEO perspective, since although the link popularity from the old pages will pass by just 301-redirecting them to their new location, what it is important to preserve is also the relevance of these redirects, since these old pages could be already not only externally linked, but also ranking for keywords relevant to their specific content, so if you do a "bulk" redirect to a new page that is not optimized for these keywords (and is very unlikely that a single page is optimized and relevant for a high diverse amount of content and keywords that are at the moment covered through many different pages) you will lose those rankings.
Because of this, take a look at which are the keywords bringing organic traffic to the "old pages" you want to redirect and what you should do to preserve this organic traffic is to redirect them to the new pages on your new domain that also cover these topics, so they will still be relevant for them and when you redirect to them, you won't not only refer the popularity but also keep the rankings and make sure that your users are finding that they were looking for (or at least, something similar).
In case you need to provide information to your users telling them that they're being redirected since the old pages have been migrated because of an acquisition, you can do it so through a message "banner" like the one that Yahoo uses here to warn visitors that they have been redirected to another language version, in a non-intrusive way.
The best way to implement 301-redirects is server side. In case you're using an Apache server then you will need to edit your .htaccess file that you can access easily via FTP for example, and should be located in your root domain.
If you would redirect your old domain pages to a new one preserving the URL structure you would be able to do this with rewriting rules, very straightforward in this case:
Options +FollowSymLinks
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www.olddomain.com$ [NC]
RewriteRule ^(.*)$ http://www.newdomain.com/$1 [R=301,L]Nonetheless, if you need to implement them in a page to page level, since the URL names of in the new domain are not the same than in the old one, you might need to implement them in a page to page basis:
Options +FollowSymLinks
RewriteEngine On
RewriteRule ^oldurl.html$ http://www.newdomain.com/newurl.htmlI hope this helps!
Aleyda
-
Many Thanks Sorina !!
I thought 301 redirects are on the .htaccess file which requires a file lstill to be on a server containing the 301 instruction. Since the server/hosting is being deleted then i cant see how its possible to leave a 301 redirect on there and the redirect hence must take place in/on the dns record ?
-
From what I saw Google makes efforts in identifying sneaky domain redirection techniques, so I believe when you do a legit one like you described above there are no risks.
As for domain redirects/301 redirects - these aren't different redirect types, just different way of saying it. What a consider a "domain redirect" must be a 301 redirect in order to pass link juice. If you have doubts about how these work, contact your hosting provider to make sure what they call "domain redirect" is actually a 301 http responce status code that the server sends out for that domain.
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
-
Same URL names in one domain
Hi All, I have 9 different subdirectories for languages in the same domain example: www.example.com/page.html www.example.com/uk/page-uk.html www.example.com/es/page-es.html we are implementing hreflang tags for the languages. I know it is better to translate URLs, but we won't for now, because all the NON-ASCII characters. But we are thinking to get rid of the dashes on the languages URL: -uk or -es, so it will be: www.example.com/page.html www.example.com/uk/page.html www.example.com/es/page.hrml would this be a problem? to have same page names even if they are in different subdirectories? would we need to add canonical tags, at least for the main domain URLs? www.example.com/page.html Thank you, Rachel
Technical SEO | | RaquelSaiz0 -
301 Redirects Showing As 307 Redirects
Hi, Our clients are adamant that they have set up 301 permanent redirects on their websites, but when we check using Screaming Frog and various online HTTP status code checkers they are showing as 307 temporary redirects. Examples;
Technical SEO | | Webpresence
http://www.lifestylelifts.co.uk/home-lifts/
http://www.terrylifts.co.uk/ Again, the client says they are seeing 301 redirects. Why are we seeing 307's? Who is right? Very puzzling, any theories would be very much appreciated 🙂 Thanks in advance. Lee.0 -
Changed domains, saw significant drop in domain authority
Hello, A little over a month ago we switched our domain from A to B. The original was .com and the new one is at a .tech for good measure. We have meticulously done 301 redirects page by page but there has been a massive drop in traffic and I checked here to see that we've gone from a 30 domain authority to a 9. The company is a few months over 1 year old, but we're really looking at traffic accumulated in just about 8 months for the old domain. Is there any way to recover some of the old juice in this one other than the re-directs? Our number of backlinks have also severely dropped despite re-directs.
Technical SEO | | SteveSaf0 -
Changing URLs
As of right now we are using yahoo small business, when creating a product you have to declare an id, when we created the site we were not aware that you will not be able to change the id but also the ID is being used as the URL. we have a couple thousand products in which we will need to update the URLs. What would the best way to be to fix this without losing much juice from our current pages. Also I was thinking that if we did them all in a couple weeks it would hurt us a lot, and the best course of action would be to do a slow roll out of the URL changes. Any help is appreciated. Thank you!
Technical SEO | | TITOJAX0 -
Old domain still being crawled despite 301s to new domain
Hi there, We switched from the domain X.com to Y.com in late 2013 and for the most part, the transition was successful. We were able to 301 most of our content over without too much trouble. But when when I do a site:X.com in Google, I still see about 6240 URLs of X listed. But if you click on a link, you get 301d to Y. Maybe Google has not re-crawled those X pages to know of the 301 to Y, right? The home page of X.com is shown in the site:X.com results. But if I look at the cached version, the cached description will say :This is Google's cache of Y.com. It is a snapshot of the page as it appeared on July 31, 2014." So, Google has freshly crawled the page. It does know of the 301 to Y and is showing that page's content. But the X.com home page still shows up on site:X.com. How is the domain for X showing rather than Y when even Google's cache is showing the page content and URL for Y? There are some other similar examples. For instance, you would see a deep URL for X, but just looking at the <title>in the SERP, you can see it has crawled the Y equivalent. Clicking on the link gives you a 301 to the Y equivalent. The cached version of the deep URL to X also shows the content of Y.</p> <p>Any suggestions on how to fix this or if it's a problem. I'm concerned that some SEO equity is still being sequestered in the old domain.</p> <p>Thanks,</p> <p>Stephen</p></title>
Technical SEO | | fernandoRiveraZ1 -
Removing Redirected URLs from XML Sitemap
If I'm updating a URL and 301 redirecting the old URL to the new URL, Google recommends I remove the old URL from our XML sitemap and add the new URL. That makes sense. However, can anyone speak to how Google transfers the ranking value (link value) from the old URL to the new URL? My suspicion is this happens outside the sitemap. If Google already has the old URL indexed, the next time it crawls that URL, Googlebot discovers the 301 redirect and that starts the process of URL value transfer. I guess my question revolves around whether removing the old URL (or the timing of the removal) from the sitemap can impact Googlebot's transfer of the old URL value to the new URL.
Technical SEO | | RyanOD0 -
Do search engines treat 307 redirects differently from 302 redirects?
We will need to send our users to an alternate version of our homepage for a few hours for a certain event. The SEO task at hand is to minimize the chance of the special homepage getting crawled and cached in the search engines in place of our normal homepage. (This has happened in the past so the concern is not imaginary.) Among other options, 302 and 307 redirects are being discussed. IE, redirecting www.domain.com to www.domain.com/specialpage. Having used 302s and 301s in the past, I am well aware of how search engines treat them. A 302 effectively says "Hey, Google! Please get rid of the old content on www.domain.com and replace it with the content on /specialpage!" Which is exactly what we don't want. My question is: do the search engines handle 307s any differently? I am hearing that the 307 does NOT result in the content of the second page being cached with the first URL. But I don't see that in the definition below (from w3.org). Then again, why differentiate it from the 302? 307 Temporary Redirect The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field. The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand the 307 status. Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI. If the 307 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
Technical SEO | | CarsProduction0 -
Domain Alias
I have a client that picked up a bunch of keyword rich domain names and he wants to point them to his current corporate site as domain aliases. Could this in anyway negatively or positively effect his SEO? or ranking? Thanks - Kyle Chandler
Technical SEO | | kchandler1