Before we go on how to handle the 404 message, we should know what it is "404".
Message 404 is part of the "HTTP Status Messages", where when a browser
requests a service from a web server, an error might occur. The list of "HTTP
status messages" you can see in the table below:
Message | Explanation | |
1xx | 100 Continue | The server has received the request headers, and the client should proceed to send the request body. |
101 Switching Protocols | The requester has asked the server to switch protocols | |
103 Checkpoint | Used in the resumable requests proposal to resume aborted PUT or POST requests | |
2xx | 200 OK | The request is OK (this is the standard response for successful HTTP requests) |
201 Created | The request has been fulfilled, and a new resource is created | |
202 Accepted | The request has been accepted for processing, but the processing has not been completed | |
203 Non-Authoritative Information | The request has been successfully processed, but is returning information that may be from another source | |
204 No Content | The request has been successfully processed, but is not returning any content | |
205 Reset Content | The request has been successfully processed, but is not returning any content, and requires that the requester reset the document view | |
206 Partial Content | The server is delivering only part of the resource due to a range header sent by the client | |
3xx | 300 Multiple Choices | A link list. The user can select a link and go to that location. Maximum five addresses |
301 Moved Permanently | The requested page has moved to a new URL | |
302 Found | The requested page has moved temporarily to a new URL | |
303 See Other | The requested page can be found under a different URL | |
304 Not Modified | Indicates the requested page has not been modified since last requested | |
306 Switch Proxy | No longer used | |
307 Temporary Redirect | The requested page has moved temporarily to a new URL | |
308 Resume Incomplete | Used in the resumable requests proposal to resume aborted PUT or POST requests | |
4xx | 400 Bad Request | The request cannot be fulfilled due to bad syntax |
401 Unauthorized | The request was a legal request, but the server is refusing to respond to it. For use when authentication is possible but has failed or not yet been provided | |
402 Payment Required | Reserved for future use | |
403 Forbidden | The request was a legal request, but the server is refusing to respond to it | |
404 Not Found | The requested page could not be found but may be available again in the future | |
405 Method Not Allowed | A request was made of a page using a request method not supported by that page | |
406 Not Acceptable | The server can only generate a response that is not accepted by the client | |
407 Proxy Authentication Required | The client must first authenticate itself with the proxy | |
408 Request Timeout | The server timed out waiting for the request | |
409 Conflict | The request could not be completed because of a conflict in the request | |
410 Gone | The requested page is no longer available | |
411 Length Required | The "Content-Length" is not defined. The server will not accept the request without it | |
412 Precondition Failed | The precondition given in the request evaluated to false by the server | |
413 Request Entity Too Large | The server will not accept the request, because the request entity is too large | |
414 Request-URI Too Long | The server will not accept the request, because the URL is too long. Occurs when you convert a POST request to a GET request with a long query information | |
415 Unsupported Media Type | The server will not accept the request, because the media type is not supported | |
416 Requested Range Not Satisfiable | The client has asked for a portion of the file, but the server cannot supply that portion | |
417 Expectation Failed | The server cannot meet the requirements of the Expect request-header field | |
5xx | 500 Internal Server Error | A generic error message, given when no more specific message is suitable |
501 Not Implemented | The server either does not recognize the request method, or it lacks the ability to fulfill the request | |
502 Bad Gateway | The server was acting as a gateway or proxy and received an invalid response from the upstream server | |
503 Service Unavailable | The server is currently unavailable (overloaded or down) | |
504 Gateway Timeout | The server was acting as a gateway or proxy and did not receive a timely response from the upstream server | |
505 HTTP Version Not Supported | The server does not support the HTTP protocol version used in the request | |
511 Network Authentication Required | The client needs to authenticate to gain network access |
Is there any effect of 404 on google page rank?
As far as I read from an article officially released by google, it has no impact.
But do you think is good if there is a message 404 on your blog?, I think
it's not good, visitors will feel disappointed because they felt deceived by
you. You are the owner of the blog, and you are the one who should fix the
error. Be professional even though it's just a free blog. Hold on to the
principle of "What You See Is What You Get", Give your visitors what they want,
what they see in the google search results. If that page has been deleted or due
to other factors, give a reason.
How do I know there is a page on my blog that indicated 404?
There are 2 ways I use to indicate
the 404 message on my blog:
- Viewing a report message from
google webmaster.
- Tests using the Google search engine.
- Tests using the Google search engine.
1. Viewing a report message from
google webmaster.
If you've using the google webmaster, you are certainly familiar
with its features. Usually we will automatically be notified if there is
something happen on our blog. For example, in the case we are discussing today.
On the picture above is one example of that happening on our website, and we
solved the problem immediately.
To check the health of your blog, go to "health >> Crawl Errors". If there
are errors, it will be shown in a graph and show you pages error.
Errors that occur on your cache link due to changes on the year and month archive.
If you find errors like the picture above, write all the list of error posts
to be corrected (we will discuss how to handle it later).
2. Tests using the Google search engine.
You can use google search engine to find the missing or removed page. Type "site:www.yourdomain.com".
The image above is just an illustration.
Point your cursor on each item of the search results. If the preview cache
does not appear, it means the link to that page no longer exists. Please note,
this method is less effective because of limited number of searches (usually 10
to 11 pages only). Mark the pages url that were removed.
How to fix the problem
I use four ways to fix the problem
above:
- Removing the cache thru google webmaster (This method is valid only if the post was removed).
- Redirect invalid URL cache to a
valid address.
- Block the URL using robot.txt, or
- Block the URL using robot.txt, or
- Block the URL using meta tag.
Of the four methods above, here I just explain 2 methods only.
1. Removing the cache thru google
webmaster.
Login to your google webmaster!
Select the cache of blog you want to delete.
2. Redirect invalid URL cache to a valid address.
This method is valid between the link on your blog only and you
are the administrator of the blog. Remember, this way we used if there is a
change in the year and month archives only which resulted in 404.
Go to "settings" on your blog (Follow the instructions as shown below).
Go to "settings" on your blog (Follow the instructions as shown below).
On the "Custom redirects", click "Edit"
There are two inputs are "From" and "To"
From = URL address is invalid
To = Valid URL address (live)
For example, an invalid address is yourblog.blogspot.com/2012/01/post-a.html,
and the live address is yourblog.blogspot.com/2012/02/post-a.html,
then you make changes like the example below
From = /2012/01/post-a.html
To = /2012/02/post-a.html
Change of the year and month on the post can occur due to
editing we do.
Hopefully this tips can help you. Remember: do not ignore 404!
Keyword: How
to solve 404 | How to redirect the page on blogger | Tips to solve the problem
404 | Techniques redirect | Redirect techniques
|
You may also like: