Pseudo static
&http://www.aliyun.com/zixun/aggregation/37954.html ">nbsp; As the name suggests, pseudo-static is relatively real static speaking.
Usually we want to better ease the pressure on the server, and enhance the friendly side of the search engine. All the content of the article generated static pages.
But some friends in order to display some information in real time. Or you want to use a dynamic script to solve some problems. You cannot display the content of a Web site in a static way.
But this loses the friendly side of the search engine. How to find a middle method between the two, which produces pseudo static technology.
is to display a static page form of. html, but it is actually handled by a dynamic script such as ASP.
One of my ideas is to use the IIS 404 error handling mechanism to achieve. This is much more flexible than rewrite technology.
First, set the site properties-Self-tuning error
Locate HTTP Error 404, and then edit the property-> message type Select Url->url to fill in "/index.asp" or your error-handling page.
This way, for example, when a user or spider accesses the http://tech.todo.net.cn/12345.html (12345 is the article in the database ID). Because some pages do not exist, 404 errors are triggered. turned to index.asp.
In index.asp Riga
Currdomain=request.servervariables ("Http_host") ' Current access domain name
Currurl=replace (Request.ServerVariables ("query_string"), "404;http://" &CurrDomain& ": 80", "") ' Current access URL
This time the Currurl should be: 12345.html.
That way, you get the page that the user is trying to access. And then extract the article ID (should be: 12345), with regular, here is not much to say.
Then go to the database to extract the content of the article. Output to the page, OK.
This way, the URL that the user or spider sees is still the URL that he accesses. And we can use the dynamic technology to deal with the content. This is the result we want.
It's easier said than done. But that's the basic idea.
Because of the industry reasons, the following content is for SEO.
"Lee":
Static page: Can better ease the pressure of the server, can enhance the friendly surface of search engines and included quality.
Dynamic page: Can display the information in real time, can use the script program to solve the problem flexibly.
We are not difficult to find, for SEO, dynamic page is not conducive to optimization.
"Disadvantages":
Static pages: Large space storage, delete, update these HTML content will cause a lot of disk I/O operations, as well as a large number of disk fragmentation, or even disk bad.
Dynamic pages: Can cause dead loops, unfriendly to search engines.
It is not difficult to find that the dynamic page is still to be given up by us.
But it seems that this time static pages can not please the road. Therefore, pseudo static technology is derived.
Pseudo-Static is actually handled by a dynamic script, showing a static page form in HTML.
Pseudo-Static Implementation method:
1, use isapi_rewrite for dynamic link rewrite HTML static URL.
2, IIS 404 error handling mechanism: Through the custom error, to our prepared processing page.
PS: Why do search engines do not like the URL with a question mark?
The previous Dynamic Web page has such a loophole, spiders go out, called "Search Robot Trap." Because the search engine is afraid because of the question mark to enter the dead loop, so many times with the question mark address search engine will not go in, pseudo static for search engines, because the address does not have a question mark, so its effect and static Web page.
All we said to do is for SEO, its ultimate goal is to enhance the friendly side of the search engine.
But pseudo-Static also has its drawbacks. Because it is a regular judgment, it is not a real address. Are turned to be judged by the CPU, so a little bit more traffic will appear CPU overload.
To sum up, the Big bear here to leave a little experience:
1, because we do is in order to SEO, in the exclusion of dynamic page premise, pseudo static can also achieve static page effect, but also to avoid static pages can not solve a large number of disk I/O operations and disk fragmentation problems.
2, pseudo static large number of uses will increase CPU load, and we just provide to the SEO archiver use pseudo static on it.
3, those who do not have high concurrency and need SEO, but also need to be able to update the background dynamic site, pseudo static is no longer suitable.
Original article reproduced please specify the Source: (Chinese paper Publishing Network) http://www.lunwen36.com.