For developers or sysadmins experienced with the command line, get High Availability and Root Access for your application, service, and websites with Cloud VPS Hosting<\/a><\/p>\n\n\n\n Some common uses of a 301 .htaccess redirect<\/strong>:<\/p>\n\n\n\n You have the ability to setup redirects for a domain in your cPanel<\/a> interface one link at a time. You can also add the redirects manually by modifying your .htaccess<\/strong> file directly.<\/p>\n\n\n\n On a Linux server you would use your .htaccess<\/strong> file<\/a> to implement a 301 redirect for your pages.<\/p>\n\n\n\n Click here for steps getting to .htaccess file<\/p>\n\n\n\n To redirect individual files, like example.com\/oldfile.htm<\/strong> to newfile.htm<\/strong> you can use a 301 redirect like this: To redirect one specific file to another domain such as example.com\/oldfile.htm<\/strong> to example.net\/newfile.htm<\/strong>: If you had an old domain such as example.com<\/strong>, and now you decided you actually want to use example.net<\/strong> for the website. You could setup a 301 redirect for the entire domain, so that old links to example.com<\/strong> carry over.<\/p>\n\n\n\n Code in the example.com<\/strong> domain\u2019s .htaccess<\/strong> file: A search engine like Google would see example.com<\/strong> and www.example.com<\/strong> as essentially two separate websites. They recommend you pick one version you\u2019d like search engines to display and using a 301 redirect<\/a> is a possible option.<\/p>\n\n\n\n If you have a lot of links on the web where people are linking to your site as example.com<\/strong>, but you would like your visitors to instead end up at www.example.com<\/strong> you can force this version of your domain with these rules: If you have a lot of links on the web where people are linking to your site as www.example.com<\/strong>, but you would like your visitors to instead end up at example.com<\/strong> you can force this version of your domain with these rules: To re-direct all of one type of file to another, such as example.com\/file.php<\/strong> to example.com\/file.htm<\/strong> You should now know how to properly setup 301 permanent redirects on your website to help ensure that search engines and visitors coming to your site from older links can still get to your new content.This entry was posted in Website<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Setting Up a Permanent 301 Redirect in .htaccess A permanent 301 redirect in your .htaccess file lets search engines and others know that an old link has been replaced by a new one. It\u2019s the recommended method for directing traffic from an existing page. For developers or sysadmins experienced with the command line, get High Availability and Root Access […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[7],"tags":[],"_links":{"self":[{"href":"https:\/\/wiki.activenet.sk\/index.php\/wp-json\/wp\/v2\/posts\/116"}],"collection":[{"href":"https:\/\/wiki.activenet.sk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wiki.activenet.sk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wiki.activenet.sk\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/wiki.activenet.sk\/index.php\/wp-json\/wp\/v2\/comments?post=116"}],"version-history":[{"count":1,"href":"https:\/\/wiki.activenet.sk\/index.php\/wp-json\/wp\/v2\/posts\/116\/revisions"}],"predecessor-version":[{"id":117,"href":"https:\/\/wiki.activenet.sk\/index.php\/wp-json\/wp\/v2\/posts\/116\/revisions\/117"}],"wp:attachment":[{"href":"https:\/\/wiki.activenet.sk\/index.php\/wp-json\/wp\/v2\/media?parent=116"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wiki.activenet.sk\/index.php\/wp-json\/wp\/v2\/categories?post=116"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wiki.activenet.sk\/index.php\/wp-json\/wp\/v2\/tags?post=116"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Getting to your .htaccess file<\/h2>\n\n\n\n
Redirect individual files<\/h2>\n\n\n\n
Redirect 301 \/oldfile.htm \/newfile.htm<\/code><\/p>\n\n\n\n![\"single](\"https:\/\/www.inmotionhosting.com\/support\/images\/stories\/htaccess\/301-redirect\/single-file-301-redirect.gif\")
<\/figure>\n\n\n\nRedirect 301 \/oldfile.htm https:\/\/example.net\/newfile.htm<\/code><\/p>\n\n\n\n![\"single](\"https:\/\/www.inmotionhosting.com\/support\/images\/stories\/htaccess\/301-redirect\/single-file-domain-301-redirect.gif\")
<\/figure>\n\n\n\nRedirect an old domain to a new domain<\/h2>\n\n\n\n
RewriteEngine on
RewriteCond %{HTTP_HOST} ^example.com [NC,OR]
RewriteCond %{HTTP_HOST} ^www.example.com [NC]
RewriteRule ^(.*)$ https:\/\/example.net<\/strong>\/$1 [L,R=301,NC]<\/code><\/p>\n\n\n\n![\"full](\"https:\/\/www.inmotionhosting.com\/support\/images\/stories\/htaccess\/301-redirect\/full-domain-301-redirect.gif\")
<\/figure>\n\n\n\nForce www. version of domain to be used<\/h2>\n\n\n\n
RewriteEngine on
RewriteCond %{HTTP_HOST} ^example.com [NC]
RewriteRule ^(.*)$ https:\/\/www.example.com\/$1 [L,R=301,NC]<\/code><\/p>\n\n\n\n![\"force](\"https:\/\/www.inmotionhosting.com\/support\/images\/stories\/htaccess\/301-redirect\/force-www-301-redirect.gif\")
<\/figure>\n\n\n\nForce non www. version of domain to be used<\/h2>\n\n\n\n
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www.example.com [NC]
RewriteRule ^(.*)$ https:\/\/example.com\/$1 [L,R=301,NC]<\/code><\/p>\n\n\n\n![\"force](\"https:\/\/www.inmotionhosting.com\/support\/images\/stories\/htaccess\/301-redirect\/force-non-www-301-redirect.gif\")
<\/figure>\n\n\n\nRedirect all files with certain extension<\/h2>\n\n\n\n
RewriteEngine On
RewriteCond %{REQUEST_URI} .php$
RewriteRule ^(.*).php$ \/$1.htm [R=301,L]<\/code><\/p>\n\n\n\n![\"file](\"https:\/\/www.inmotionhosting.com\/support\/images\/stories\/htaccess\/301-redirect\/file-extension-301-redirect.gif\")
<\/figure>\n\n\n\n