View 302 redirection from blocked Business.com

> Website redirection becomes a curse
 
Business.com is the largest commercial search engine and category on the Internet. It is well known for providing business information professionally, including nearly 0.19 million web pages. If you search in Google with the keyword "business", the website ranks first. However, in September 5, Business.com encountered a strange thing: its homepage changed from PR8 to PR0, And the homepage was not found in Google search results. Fortunately, only the homepage is "EVAPORATED", but fortunately the homepage returns to Google's search results on the next day, but PR is still 0.

The problem with Business.com lies in its redirection command. This website redirects business.com to www.business.com, which should have been permanent. We know that 301 is a permanent redirection, while 302 is a temporary redirection. This command can be used only when a website or webpage is temporarily moved to another location within 24 to 48 hours. However, Business.com mistakenly uses the "HTTP/1.1302 Object Moved" status code.

In fact, website redirection is very common. For example, if you apply for a new domain name because you are not satisfied with the original domain name, you can buy a domain name that is easy to be mistakenly spelled, to prevent customers from finding websites because of misspelled URLs. However, many users are suffering from "website disconnection" due to the incorrect redirection status code, just like Business.com. Despite their reasonable and reasonable reasons for redirection, if improperly used, your website may be blocked if Google mistakenly believes that multiple domain names are used to direct to the same website, the charge is "using repeated content to interfere with Google search results _ blank> website rankings ". Business.com is the best example. However, most websites that use the error redirect parameter are not as lucky as Business.com. A small redirection may make the website useless and can only start from scratch: re-applying for a new domain name, re-publishing a new website, and so on. Remember: _ blank> Google will never sympathize with anyone, even if they have no intention of making mistakes.

> How does the website server respond to Web browsing requests?
 
 
 
 
Let's take a look at the interaction process between users/search engines and websites. When a user or search engine sends a Webpage Browsing request to a website server, the server will:
1. Use the Domain Name Server (DNS) to convert the domain name to the IP address of the website, and then return it to the customer
2. Open an interface connection for this IP address set
3. Write down an HTTP data stream through this interface
4. receive an HTTP data stream in response to the request from the WEB server. The data stream contains a status code. The value of the status code is determined by the HTTP protocol. The "HTTP data stream" is also called "Header information )". The header contains the date and server type. Generally, there is a "200 OK" message. If everything is good, the network server will send the "200 OK" message and the request page. If a website has been redirected at this time, the server will include a response message such as "302 Moved Temporarily" or "301 Moved Permanent" in the header. The search engine determines Based on the content in the server header.

> Website redirection considerations
 
 
 
 
1. If you want to move files on the server to other places, you must correctly notify the search engine crawler with the following information:
-Target address: where are these files Migrated?
-"Move property": "temporarily removed" or "permanently removed"
2. For websites with multiple domain names, experts suggest using the 301 jump command to permanently redirect domain names that do not want to be promoted on the search engine.

> Make sure that the website implements correct 301 redirection.
 
 
 
 
For the correct implementation of 301 redirection, there are several methods for your reference:
1. Add the 301 redirection command to the. htaccess file.
2. Applicable to users who use Unix network servers. Use this command to notify the search engine spider that your site file is not under this address. This is a common method. Shape: Redirect 301/http://www.yourdomain.com/
3. Complete 301 redirection in the system administrator configuration area of the server software.
Applicable to users who use Windows Network Servers

 
4. The "mod_rewrite" technology is used.
The changes made through this technology will be reflected in the. htaccess file, such:
Options + FollowSymLinks
RewriteEngine on
RewriteCond % {HTTP_HOST} ^ yourdomain.com
RewriteRule ^ (. *) $ http://www.yourdomain.com/#1 [R = permanent, L]
5. Bind/local DNS
If you have the permission to edit and modify local DNS records, you only need to add a record to solve this problem.
If you do not have this permission, you can ask the website hosting service provider to set the DNS server accordingly.
DNS server settings
To direct aaa.domain.com to www.domain.com, you only need to add an alias record IN the DNS service, which can be written as aaa in cname www.domain.com.
If you need to configure a large number of virtual domain names, you can write them as * in cname www.domain.com.
In this way, all unconfigured records ending with domain.com can be redirected to www.domain.com.
6. use ASP/PHP to implement 301 redirection:
ASP:
Response. Status = "301 Moved Permanently"
Response. AddHeader "Location", "http://www.yoursite.com /"
Response. End
PHP:
Header ("HTTP/1.1 301 Moved Permanently ");
Header ("Location: http://www.yoursite.com /");
Exit ();
 

> Senior SEO expert Dan Thies's views and suggestions:
 
 
 
 
Dan Thies has a deep understanding of the problems encountered by Business.com, because he has had similar experiences. There is a member tracking script on his website. One of the member's sites maps to this tracking script through the 302 command, and the tracking script maps to his home page through 302. When "keyword research" is used in Google for search, his home page ranks in the top 10, but the address shows the Member's website. The results make him laugh: visitors access his website through Google search results, but he has to pay for these visits to the member! The problem is solved only when the robots.txt file is used to prohibit Spiders from tracking and accessing the member tracking script.
For Business.com, Dan Thies believes that there are still some problems with Google's 302 redirection processing, but it does not mean that Google does not allow 302 redirection. Business.com is not blocked or punished. They only return an error response ."

Dan Thies suggests: If the tracking URL/script is used, and the attacker redirects to a specific landing page, it is necessary to prohibit Spiders from accessing the second redirection in the robots.txt file. If no redirection is made to the tracking URL or script, but the external URL is copied, Spiders should be prohibited from accessing the tracking URL in the robots.txt file to prevent repeated content from being punished by the search engine.
 

> 301 redirection experience
 
 
 
 
Experience of a multi-domain website owner:
"I only have one website with the primary domain name www.domain.com. In addition, there are more than a dozen domain names, such as domain1.com, domain2.com, and domain3.com. All these subdomain names are mapped to www.domain.com, and all domain names correspond to the same IP address. In fact, I only have one site, and one site can only correspond to one. htaccess file. Obviously, it is impossible to directly modify the. htaccess file to achieve redirection. I used the following steps:
A. Separate domain1.com from domain.com to make it an ordinary independent website on the server.
B. Create a. htaccess text file for domain1.com and set the redirection code:
Redirect permanent/http://www.domain.com/
Upload the modified. htaccess file to the server where domain1.com is located.
This step can also be completed in the domain name control panel.
C. Enter the domain name control panel, release all the domain names originally bound to domain.com from domain.com, and then bind them to doamin1.com. In this way, these bound domain names use the. htaccess file of domain1.com, which means they are permanently redirected to domain.com.
Okay, you're done! That's easy!