|
Webmaster Articles -
System Administration
|
|
Written by Danny Collins
|
|
URL redirection is a common and unfortunate necessity of running web sites. Sometimes sites go through renovation, and sometimes the entire infrastructure needs to be changed. Perhaps you're moving to more SEO-friendly URL's, or perhaps you just need to shuffle some files around for organizational reasons. Now if someone has an interior page of your site bookmarked, that person will get a "Page Not Found" error (also called a 404 error). New visitors can also become confused if they've reached your site from a deep link on another site, or from a search engine which now has an outdated index of your site. And that raises another problem - Google doesn't like it.
The Solution: 301 Redirect
Create a 301 redirect. This will allow you to redirect all of your old file locations to their new, proper locations. When the Google spider comes along, it'll also follow your 301 redirects, and this will let Google know that your pages have been moved, and the Google index will be updated with the new file locations.
|
|
Read more...
|
|
|
Webmaster Articles -
System Administration
|
|
Written by Jeff Dunn
|
|
Conveniences in this tutorial:
Yourdomain.com – replace with your domain
Console.html – page where the user is sent (we send our hotlinkers to a console hell page)
As explained in part 1, rewrite rules can help stop hot-linkers to your site and cut down on your bandwidth usage. The simple example explained in the part 1 is all most webmasters need, but the functionality of rewrite rules allows webmasters to have far more control over their websites.
In Part 2, I explained how the RewriteCond statement functions and gave more uses for it.
|
|
Read more...
|
|
Webmaster Articles -
System Administration
|
|
Written by Jeff Dunn
|
|
Conveniences in this tutorial:
Yourdomain.com – replace with your domain
Console.html – page where the user is sent (we send our hotlinkers to a console hell page)
As explained in Part 1, rewrite rules can help stop hot-linkers to your site and cut down on your bandwidth usage. The simple example explained in Part 1 is all most webmasters need, but the functionality of rewrite rules allows a webmaster to have far more control over a website.
|
|
Read more...
|
|
Webmaster Articles -
System Administration
|
|
Written by Admin
|
|
Conveniences in this tutorial:
Yourdomain.com – replace with your domain
Console.html – page where the user is sent (we send our hotlinkers to a console hell page)
A successful webmaster is always aware of the bandwidth his site uses and tries to reduce it any way he can to cut down on the amount of money paid to his host. One of the number one causes for using more bandwidth than a webmaster should is due to hot-linking and other forms of bandwidth stealing perpetrated by other webmasters, either evil or ignorant. Using Rewrite rules is the most common tip given to webmasters for reducing hot-linking.
|
|
Read more...
|
|
Webmaster Articles -
System Administration
|
|
Written by Jeff Dunn
|
|
Apache and other web servers allow the web server administrator to make per-directory configuration modifications as a convenience to the web site operator. This is usually done in the form of .htaccess files. As a webmaster, an .htaccess file is very useful as it allows you to change the actual pre-set server configuration, normally only set by the server administrator, to the specific configuration needed for your web site.
The configuration lines in the .htaccess file are the same as the configuration lines in the server configuration. When you edit an .htaccess file, you are actually editing the configuration for the web server, though your configurations are localized to the directory in which the .htaccess file is placed.
|
|
Read more...
|
|
|
|
|
|
