Google's Matt Cutts And JavaScript Redirects

There are a number of different optimization techniques webmasters use to try and improve their search engine rankings, some acceptable (white hat SEO), some not (black hat SEO). One of the suspect methods, using JavaScript redirects, Matt Cutts: Gadgets, Google, and SEO blog (hat-tip to http://www.techgroups.com/search-engine-optimization/search-ngines.htm If you have JS turned off, when you arrive to this page, you see a great deal of what Matt refers to as gibberish, masking itself as "legitimate" content. By taking a closer look at the page in question, you find this gibberish is actually content that's been scraped from other pages, and its being used to game the search engines. However, this is not the point Matt is trying to get across. Matt is not only concerned with the spam page, he also has issue with the use of a JavaScript redirect that forwards visitors to the TechGroups.com home page, a clear example of how to misuse such a tool. Here is a Mazda protege pr5 Add (which seems to target some of the following keywords: grossing films google page rank, page rank google, page rank algorithm ? sextracker page rank) Deep web Google site query and look at all the results. So that people who may unknowingly employ methods like these, Matt offers some high-risk tactics to avoid when optimizing your site:

• Don't use programs that automatically generate doorway pages.

• It especially looks bad if the doorway pages are gibberish.

• It really especially looks bad if the content you use is scraped content.

• If you're considering scraping content, doing it in the SEO industries is one of the worst places to do it.

• If you scrape SEO content and end up scraping a couple spam pages, you may get noticed even more because someone is investigating the other spam pages.

and then:

• If you make lots of pages, don't put JavaScript redirects on all of them.

• If you're doing JavaScript redirects, don't obfuscate the code-it just makes people think that you're doing things after lots of deliberate consideration.

• If you do obfuscate code, ask yourself: can a regular person still look at this code and tell what it's doing without even knowing JavaScript?