SEO Recommended URL Standardization

Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall

Before I begin to collect feedback on the BigDaddy data center, I would like to talk briefly about the views on standardization, "www versus non-www", redirection, repeat URLs, 302 "hijacking", so that our discussions have a common basis.

Q: What is a standardized URL? Why use such a strange word?

A: I'm sorry, this is a strange word; this is what Google calls it inside. Standardization is the process of selecting the best URL in several options, usually the home page. For example, most people would consider the following URLs to be of the same nature:

* www.example.com

* example.com/

* www.example.com/index.html

* example.com/home.asp

But from a technical point of view, these URLs are different. The above Urls,web server returns completely different content. When Google "standardizes" specific URLs, we try to choose the one that looks most representative from a set of similar URLs.

Q: So how can I make sure that Google can pick out the URLs I want?

A: It is helpful to pick out the URL you want and to use this URL to access a particular Web site thereafter. For example, do not let the same input link half point to http://example.com/and the other half point to http://www.example.com/. Instead, pick a URL that you like, and always use this format in your internal links.

(Translator Note: Now you can use webmaster Tools for "Console > Tools > Set preferred domain Name").

Q: What else can I do besides that?

Answer: For example, if you want your default URL to be http://www.example.com/. So, you can set up your Web server so that if someone requests http://example.com/, it generates a 301 (permanent) redirect, linking to http://www.example.com/. This will help Google understand which URL you want to use as your standard. If your site changes frequently (such as dynamic content and blogs, etc.), then adding a 301 redirect may be more convenient for search engines to locate and capture.

Q: If I want to remove domain.com but want to keep www.domain.com, should I use the URL Cleanup tool to remove this domain name?

A: No, absolutely not. For any one of the WWW domain names, or non-WWW domain names, the deletion of the result may cause the domain name to be unrecoverable within the next six months. Never do that. If you would like to use the URL removal Tool to remove the WWW domain name or non-WWW domain name, but actually deleted all of your domain name, please send a re-collection request, and declare that you use the URL removal Tool accidentally removed the entire domain name, now requires a new collection.

Q: I noticed that you did not use the 301 Redirect to turn your site from the non-WWW version to the WWW version, why didn't you?

A: Actually, I did it on purpose. I noticed this a few months ago, but decided not to adjust myself, or ask Google employees to help me get it done. I might end up with a 301, but at least so far it's a helpful experiment.

Q: So when discussing "www and non-www," Do you think this is a standardized type? Is there any other way to standardize URLs?

A: There are many ways, but most people don't and don't need to notice. Search engines can automate tasks such as retaining or removing trailing slashes, converting URLs from uppercase to lowercase, or deleting session IDs from BBS or other software (even if you omit the sessions ID, many BBS can still function correctly).

Q: Let's talk about the "inurl:" operator. Why does everyone think that if inurl:mydomain.com shows some results that are not from mydomain.com, then he must be hijacked?

A: Earlier, if you saw someresult.com/search2.php?url=mydomain.com, sometimes it would contain content from mydomain. This can happen if the someresult.com URL is a 302 redirect to mydomain.com and we decide to display a result from someresult.com. Since then, we have changed the way we inspire, dramatically reducing the chance of displaying the 302 redirect source URLs. We have gradually adopted a framework for processing redirection, which almost always shows the destination URL. Yahoo usually handles 302 redirects in a way that shows the URL of the destination, and we are in the process of transitioning to a similar heuristic. Please note that Yahoo retains the power to handle the exceptions that appear during the redirection process, and Google will do the same. According to our analysis, we will show less than 0.5% of the total probability of URL sources in the 302 redirection process (basically, when we have enough reason to believe that the URL source is correct).

Q: So, what about the supplements? Will the supplemental materials incur Google's penalty?

Answer: No.

(Translator Note: Supplements have become history.) Please read the supplementary material to mainstream.

Q: There are some of my pages in the supplemental results, but the pages are old. What am I going to do?

A: If I had changed, I wouldn't have spent too much energy on it. If the page has been deleted, I will make sure that there is a 301 redirect pointing to the location of the new page. If it does disappear, I'll make sure the server returns a 404 error message about the pages. After that, I won't spend any more energy. When Google finally crawls those pages, it finds the changes. But as we crawl through our own supplemental results for longer intervals, you may not see updates for a while.

That's all I can think of right now. Soon, I'll talk more about 302 and inurl: examples to help you understand this problem more specifically.