Quote:
Originally Posted by ilu
What do you mean by that Sadu ?
|
This one can be important on many sites important, but ignored by most.
POST is when you submit a form with some data - for example a search form.
Say your site has it's own custom made search on there. You type in what you are looking for "apple ipod" and press search. The website takes you to
www.example.com/search.php and displays the ipod search results. Cool.
Technically what has happened is your browser has requested search.php from the server along with the keywords you are looking for. This is called a POST request.
When Googlebot requests search.php it won't send the keywords with the request, so it will see a page saying "Please enter some keywords for your search" and index that. Googlebot will be getting your content via a GET request.
A far better approach is to have your search results page programmed with a nice URL like
www.example.com/search/apple-ipod.htm or even
www.example.com/search.php?keywords=apple%20ipod is better than nothing.
You guessed it, this page has "Apple Ipod" for the title, H1 heading, URL, meta description, and hopefully a page full of matching relevant search results. The page is pimped for ranking for this phrase. All you need to do is point a link at the page and Google will cache it, and your search results pages will start ranking.
Whenever you see a site that has "Last ten searches made..." on their siite, chances are they are pointing links to their search results page so they can get cached.
It's good for the user too - they can now bookmark a search results page which they couldn't do before. And if they press the refresh button, they won't get that annoying browser message asking them if they want to re-post the form data (a message which means absolutely nothing to most people).
This is one of many examples of GET vs POST for SEO. It does need to be used with caution though.
Linear Mode
