301 redirects using .htaccess

Hey Guys, I've got to redirect a couple of pages on a site for SEO and am not sure the best format to code it in. I've looked up a bunch of so-called tutorials and they all say what a 301 redirect does but nothing as far as how to code it....
For example, the courses page on the site is not there anymore cause they are now selling through a third party sooooo
www.bliqm.com/courses.html -> needs to redirect to -> www.bliqm.com/lss_blended.html
How would I got about doing that???
Thanks in advance!
by the way the site is http://www.bliqm.com if needed.

Here's a page that tell you how to add the .htaccess file.
http://iweb.dailynews.webege.com/PHPparseerror.html
On the image below you see what lines to add. Lines 6-8 are the ones you need :
!http://iweb.dailynews.webege.com/Howto_publish_to_a_subdomain_with_iWeb_files/Smultronhtaccess.png!
More info here :
http://httpd.apache.org/docs/1.3/howto/htaccess.html

Similar Messages

301 redirect becomes 302

I am attempting to perform a 301 redirect using the standard
code:
<cfheader statuscode="301" statustext="Moved
Permanently">
<cfheader name="Location" value="TheNewURL">
The redirect occurs -- but the web server is interpreting it
as a 302 instead. What could the problem be?

Any thoughts on this? Am I doing something wrong?

Question on 301 redirects

In MX 7, I am attempting to do 301 redirects, using the
attached code placed in application.cfc. The code works perfectly
-- just as long as the files I'm attempting to redirect remain
physically present. If they are removed or renamed, though, I get a
404 error. If the redirected files can never go away, doesn't that
partially negate the utility of a 301 redirect? Is there any way
around this?

I see what you're trying to do, but the 404 condition trips
(I would think
by the web server, even before the CF server is involved?)
before the
Application.cfc has a chance to do the 301.
You should probbably define a 404 template that then palms
processing off
to your 301 template, as needs must.
Adam

Htaccess 404 and 301 redirect

I have a muse website hosted on windows azure.
I have created a .htaccess file and added o the root.
The webpage is still not redirecting to the 404 error page or my 301 redirect that i have set

Hi Kurian,
You can Go to Server Settings>>Settings>> Missing Template Handler and setup the same.
To use the missing template handler with IIS, the Custom Error page of your website must be configured to use the page. For this example, we'll assume a directory name of /errorpages and a file named missingtemplate.cfm. Therefore, the path to the missing template handler will be /errorpages/missingtemplate.cfm.
The steps below explain how to configure IIS to use the template for the Custom Error page:
1.          Right-click on the website in the IIS Management Console, then select Properties.
2.          Select the Custom Errors tab.
3.          Select the 404 in the HTTP Error column and click Edit Properties...
4.          Select URL from the Message type dropdown and enter /errors/missingtemplate.cfm in the URL text box.
5.          Click OK.
6.          Right-click on the website again and select Properties.
7.          Select the Home Directory tab and click the Configuration... button.
8.          Select .cfm from the list and click the Edit button.
9.          Check the "Check that file exists" checkbox.
10.          Restart IIS and the ColdFusion Server.
Regards,
Anit Kumar

ADVICE needed --- use 301 Redirect or revert to HTM from HTML ?

Due to ignorance, I now have two versions of the same website online, the only difference being one is all HTM while the newer one is HTML
The original was built using DW MX2004 with all pages having an HTM extension while DW CS5.5 has all pages with an HTML extension.
Obviously I want to replace the old with the new but don't know how to.
Should I use a 301 redirect in the new folder and upload it with the relevant details ie. Redirect 301/index.htm http:// www.cumbria-dog-training.com/ index.html OR rename the new pages with an htm extension and hope that they've not been crawled yet ( they were uploaded 2 hours ago)
I'd be very grateful for any good advice as I'm staring into a rather dark hole at the moment.
Paull

Hi
Go into your dreamweaver preferences, (Edit - Preferences) and select the 'New Document' category, there you will see your default extension, change this to .htm and change any documents you have already created to the htm file type, (don't forget the dot before the htm file type).
On new sites you create, I would recommend changing this preference back to html for those sites.
PZ

Webmaster tools change of address 301 redirect failed using domain forward

I'm having trouble with webmaster tools recognising our domain name change.
We've recently updated website and done a name change from www.qldtshirt.com.au to www.qtco.com.au. I am using domain forwarding so qldtshirt.com.au forwards to qtco.com.au (aswell has with www.) and every thing works perfectly.
www.qldtshirt.com.au/products/polo-shirts/cool-dry-fabric forwards to:
http://www.qtco.com.au/products/clothing/polo-shirts/cool-dry-fabric
We have about 4000 301 redirects setup in URL Redirects:
/products/business-and-corporate/desk-and-office/100-organic-cotton-pencil-case to
/products/gifts-incentives/desk-and-office/100-organic-cotton-pencil-case
so on and so on....
I've verified all sites in webmaster tools however when change of address from www.qldtshirt.com.au to www.qtco.com.au webmaster tools presents this error:
"301 redirect failed. We detect that the root address of your old site (www.qldtshirt.com.au) does not yet redirect to the root address of your new site (www.qtco.com.au). For more information use the Fetch as Google tool."
It works perfectly fine for the end user, anyone know why and how to fix please?

Hi, I have found this same situation. Did you have any luck finding a solution?
Thank you

301 redirects and iWeb index page

Our site has grown and we will be changing our domain name and hosting co. (We are keeping the old domain active for a while at MME before we change domain name and hosting) I will need to redirect traffic for a while so as not to lose those who have just bookmarked us. Will just redirecting on the index page that iWeb creates (post publish) do that without creating a mess of our page rankings at Google? Currently we are in the top 15 responses for our search terms. Or should i create some other type of redirect? 301? (via cname or htaccess) will that ding me at google? Thanks- try to keep it as simple as possible - I don't code - I experiment and Apple has made it easy.
jy

What I would do is purchase the hosting and see if you can have more than one add-on domain. Most web hosts let you do this on one account so it doesn't cost you any more money. You are doing this because you will need a .htaccess file to set up your 301 redirects properly. This is what you should do;
1) Register your new domain and publish your site to it.
2) Create a webmaster tools account for BOTH your old and new domain name.
3) Create a 301 redirect for each individual page to the new corresponding page on your new domain. This can be done with a few lines in your .htaccess file. The file should be in your root folder of your OLD domain. Put this on your .htaccess file (NOTE: This assumes you will have the exact same website structure on the new domain);
RewriteEngine ON
RewriteRule ^(.*)$ http://mynewdomain.com/$1 \[R=301,L\]
OPTIONAL: Use Google's canonical tag on each one of your pages to avoid any issues with duplicate content. Link the old page to it's new corresponding page. This is optional but recommended if you can;
<link rel="canonical" href="http://www.newdomain.com/newpage.html" />
4) Login to your Webmaster Tools account and select your OLD domain. Then select 'Site Configuration' and then 'change of address'. Follow the steps provided (which are basically what I told you above). Step 4 in there is the important one.
5) Submit a sitemap for your new website. This will make sure you know when Google has indexed your new website.
6) Important: Even though you have done everything properly there is a chance your rankings will change. To help prevent this, update as many third party links as you can to your new site. This won't be possible for all links since you won't have control over them but you should try contacting the website owners who have linked to you to update their links. You should also try getting new links to your new domain.
You can find all the sites you have linked to you by logging into your webmaster tools account and clicking your OLD domain. Then go to 'Your site on the web' and then to 'Links to your site'.
Nothing will be instant here, it will take a few days for everything to update but the above is the way Google recommends you do it.
HTH

301 redirect question

I have a website with a couple thousand pageloads a week and
a google rank of 5.
I have set up a blog on the same server in a directory and
now want to move the blog to the domain name and have the traffic
and the rank go to the blog rather than the website.
Some say do 301 redirect.
Some say just move your blog index.php.
Some say erase the WWW.domain redirect, leave THAT as the
website and use the NO-WWW.domain for the blog?
Any advice on this please?
RJ

Thanx Sonjay!
The website is not going under, it is important, but the blog
is more important regards bringing in search results. I want the
arrival to the blog and then go to the website if they want.
I tested the 301 htaccess and it worked fine, page rank
carried over and worked instantly. But I had not figured that about
1000 links and graphic pointers are now wrong! :) Not quite sure
what to do about that.
I have most everything for the website in the root and quite
a bit of the blog there too, I suppose I could move most everything
in the root to domain/blog/?
rackjite.com is my domain, and serendipity is the director
the blog is in.
So I though I would try the PHP redirect in the index.htm
file.
<?php
header( 'Location: http:/rackjite.com/serendipity/' ) ;
?>
I tried that with the index.php and no slash and so forth
with no luck. I put it at tippity top as required and it doesnt do
anything at all. I do not know if this is a good way of doing it
but I did want to see what actually happened. If the page rank went
with it?
I also wonder about putting the blog index.php into the root
and what would happen. Does it still default to index.htm? if there
is a index.php.
My firend with the WWW suggestion has always been a bit weird
about WWW. He is a WWW advocate of sorts and I dont really know
what the point is, but it is colored by his prejudice for using
WWW.
Im confused on how best to do this.
One other thing to ponder, the webpage has a grank of 5 and
the blog even now has google rank of 4, how important is that
difference?
I have quite a few links out there to the domain, perhpas I
could just ask for new links under the blog name and hope they will
add that too? Been around long enough to know that wont work very
well though... :)
thanx again
RJ

301 redirect - best way?

i've been reading about 301 redirects which talk about modifying either .htaccess or httpd.conf but none of the suggestions i've found are working... my goal: if someone enters example.com, i want the server to change the url to www.example.com
i've read server admin does not do 301 permanent redirects. does anyone know the best way to do this? thanks.

Hi Scott,
I recommend not doing major edits to the config files in the /etc/apache2/sites directory. These are sometimes 'auto-cleaned' of custom edits by Server Admin when editing and committing through it (very annoying). Here's what I did that works well for me and has not been auto-cleaned so far:
1) Make a dir /etc/apache2/users
2) Make new files in that dir that have names based on your server's web users, e.g. myuser.conf (should not be system users, and not have their web directories in the /Library/Webserver area, IMHO).
3) Add *Include "/etc/apache2/users/myuser.conf"* to the end of and inside of the <VirtualHost> directive in your site config file in question from /etc/apache2/sites dir.
4) Add all your custom edits to the user file you need, in this case the 301 redirect (see below for my favorite add-www-301 redirect). If using BBEdit, make sure to re-lock the files when done, but you can leave them open.
5) In Terminal run +apachectl -t+ to make sure you have no syntax errors in your config edited files, or the Apache will crash when you try to restart it, taking your sites off-line.
5) Open /var/log/apache2/error_log, with +tail -F -n 50 /var/log/apache2/error_log+ or in Console on the server.
5) Then, in Server Admin under Web -> Sites, make a trivial change and reverse it (like checking then un-checking a box) as this allows you to gracefully restart Apache without screwing up the Webcache feature (see Web PDF docs about not using +apachectl graceful+ ).
6) Go back to your Apache error log and make sure Apache did not crash. If it did, reverse your edits and restart Apache again.
Here is my favorite add-www-301 redirect:
<IfModule mod_rewrite.c>
RewriteEngine On
# Google canonical redirect
RewriteCond %{HTTP_HOST} ^\[^\.\]+\.....?$ \[NC\]
RewriteCond %{HTTPS} !^on$ \[NC\]
RewriteRule ^(.*)$ http://www.%{HTTP_HOST}$1 \[R=301,L\]
RewriteCond %{HTTP_HOST} ^\\[^\.\\]+\.....?$ \[NC\]
RewriteCond %{HTTPS} ^on$ \[NC\]
RewriteRule ^(.*)$ https://www.%{HTTP_HOST}$1 \[R=301,L\]
</IfModule>
As opposed to other redirects that state the name of the domain, this will cover sites that have multiple domains assigned to them and up to four letters in the TLD (like .info). Also, it handles https redirects as well. Always adding (or removing) the www is important to keep your sites page ranking in Google from being diluted by the non www use (or use) of the base domain. You may already know this, of course.
The new book http://buildingfindablewebsites.com/ explains this well, though its mod_rewrite solution in limited. Caveat: HTTPS part may not work well with older browsers that do not support HTTP 1.1.
Larry

Moved Podcast Feed - 301 Redirect partially working

Recently moved our RSS feed.
Old - http://www.edgemerechurch.org/wordpress/feed
New - http://edgemerechurchorg/feed/podcast
I modified .htaccess file to include 301 redirect from old feed to new one.
Posts on the new feed are showing in iTunes
Two issues:
1. Links
"Podcast Website" links point to the old webpage in both iTunes, iTunes Store, and iTunes preview.
I am using Wordpress and Blubrry plugin
How is the podcast website determined?
Is it determined by the podcast file location?
Is there a way to change it?
2. Album Cover Art
Updated album cover art has propagated to iTunes app and iTunes program. However the iTunes store and iTunes preview (online) still shows old OLD album art work. https://itunes.apple.com/us/podcast/id639715033?i=335063000&mt=2
I'm not sure why the art is not updating in iTunes Store and iTunes preview (which I think are connected).
Is there a way to force the iTunes store to update?
Website: http://edgemerechurch.org
Old Feed site: http://edgemerechurch.org/wordpress (this was set up as a podcast only site) I want to incorporate them both into one.
Thanks for any help.

The original feed URL you give redirects to the new URL you give, except that you have left out the dot before 'org'.
However this is not the feed that the Store is using. That is at
http://feeds.feedburner.com/EdgemereChurchOfChrist
This has episodes up to 7 February, and an image which is the same as that shown in the Store. The feed at
http://www.edgemerechurch.org/feed/podcast
has five episodes dated 8th February, and a different image. So basically you've been updating the wrong feed. I'm not sure how you got yourself into this position; probably you need to update Feedburner to using the latter feed, but if you want to retain the older episodes in the Store you will have to add them to that feed first.

301 Redirections - Proper way to set up?

Hi - I have an quick and hopefully easy 301 redirect question.
Here is the duplicate title Notice from Webmaster Tools (and this is also showing duplicate content in SEOMoz).
So obviously I need to do a 301 redirect.
The top level menus on the site point to the /about version and not the index.html
the /index.html is NOT the one I want to use for the 301 if possible - does anyone have a suggestion for how to accomplish this?
Thanks!

Have you just tried doing the basic issue there and changed title tags?
Had someone ask this on the forums before and over complicating looking at 301's when they just changed names of items and page titles and fixed it
Not sure what you mean about /about etc.
If you have an about page you got several pages related to it? You have a dropdown menu? So you made a folder /about and the landing page index.html?
If not and it is just one page and you did that you do not need to. /about as a page is all you need.
You got to remeber that when you post on the forums you see all your information and sites, we do not so you need to be detailed or exact in your posts so we can get to the same pooint as you in our heads

Redirection through .htaccess

hi,
i have developed a spring project. I am using apache tomcat 5.5.27. I have to redirect my home site to another web page. So, I am using .htaccess to perform. My .htaccess file has
Options +FollowSymlinks
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_URI} !/maintenance.html$
RewriteRule .* /maintenance.html [R=307,L]
In the above code, i know that, all request to the project is redirected. i have saved the file as ".htaccess" and i have placed the file in the root directory of the project. But, i have not redirected to maintenance.html page.
Please, guide me to do.

You need to ask in Apache/Tomcat forums. This is forum for iplanet/ Sun ONE 6.1/Sun Java System Web Server 7.x servers.

Content managed 301 redirects

I am trying to work out the best way to allow content authors to create and manage 301 redirects within the CMS. We are using GSF for friendly URLs, but they also want to be able to (for example) create a catchy URL to be distributed on print media that will redirect to an existing page within the site (or potentially to a page on an external site).
I know that I cannot change the response headers in the JSP, and so am looking at the best way to do so within the existing software stack. The GSTAlias class appears to be almost what I need, but only supports 302 redirects, not 301.
My current though is that I will implement a custom filter (which will compare the incoming URL against the list of redirects that it retrieves from WCS and send a 301 if needed) and insert it into the filter chain, but I was hoping to get some feedback on this and see if anyone had done this before or knew of a better way to do it.
Cheers,
Stephen

Previously I've done redirects exactly like you, using a custom filter which was installed on the Satellite servers.
My implementation ended being a bit more complicated since all code using friendly URLs had to be executed within a cached code block due to an earlier design decision. What I ended up with was a setup where the templates could generate some output that could be interpretted by the filter. Like #R#301#http://somepage.com# which the filter picked up. Unfortantely that approach required me to read through the output of the pages and add some caching to often requested URLs in order avoid parsing through the content again.
If you have GSF on your site as well, you might have a look at com.fatwire.gst.foundation.httpstatus.HttpResponseStatusFilter which enables you to communicate status codes from the ContentServer. Note that proper redirects are not supported, or at least not implemented.
Also this requires your code to make the decision in a XML based wrapper, since you cannot communicate response codes from JSP.
If the requirements are quite simple, you can create a basic asset type containing the URL to match and where to redirect to and in your XML wrapper do a very simple sql lookup which should give you enough performance in order to have this executed in an un cached element. The SQL cache will save you for the common requested URLs.
Please note, that if you are running remote satellite servers I am not quite sure how this will work, if they support handling other response codes and if they can handle additional information found in a 301 redirect.

301 redirect shows as 302

Hello,
I'm trying to do a 301 redirect from one page to another
using this code. But when I view the http headers, it's showing up
as a 302 redirect. What's going on?
Thanks.

Any thoughts on this? Am I doing something wrong?

301 Redirect

I have a few years of Dreamweaver design experience and am
fairly well versed in html, css, etc. However, I have never had to
create a 301 redirect. I have purchased a .com and .org for a
non-profit site I am building and therefore, would like anyone who
types in the .com to be redirected to the .org. Any advice would be
greatly appreciated.

.oO(PeteC)
>cabett wrote:
>> I have a few years of Dreamweaver design experience
and am fairly
>> well versed in html, css, etc. However, I have never
had to create a
>> 301 redirect. I have purchased a .com and .org for a
non-profit site
>> I am building and therefore, would like anyone who
types in the .com
>> to be redirected to the .org. Any advice would be
greatly appreciated.
>
>Best to do that with a DNS alias - talk to your host.
No. That would lead to duplicate content. A 301 is the
correct way to
handle such things. On Apaches all it needs is a simple
directive in a
.htaccess file on the .com site (assuming that both sites are
hosted on
different servers or at least on different vhosts):
RedirectPermanent /
http://example.org/
If both domains resolve to the same server and the same
directory, then
it might require mod_rewrite to make sure that the redirect
is only
triggered when the .com is requested.
Micha

301 redirects using .htaccess

Similar Messages

Maybe you are looking for