If you keep up with my posts on Search Engine Watch, you will notice that I regularly talk about how site performance can be a significant driver in SEO, especially with Google. Many large companies take this data for granted; they are worried about up time and browser performance. Which in most cases is a good thing, however a search engine like Google may be testing your response rate and attempting to predict your level of capacity. In both IIS and Apache it is possible to throttle a search engine so it crawls at a lower level. In most cases this application or module may produce a 500 server busy error. Search engines interpret this as an end user experience and may limit the number of pages and or keywords that may rank at the same time. This practice ensures users commonly find an active page when they click on a listing. How fast are your servers?
Labels: google, seo, seo mistakes
- Name: Aaron Shear
- Location: San Francisco, California, United States
I have been in the search industry since the late 90’s, no not 10-20 years. My career started early in the search Day’s at Inktomi, where I supported large search portals. For example, MSN, AOL, iWon, Hotbot, CNet too name a few.
After Inktomi I became a freelance consultant. I consulted for a few of the Top SEO’s around 2002 time frame; obviously the market has changed since then. After consulting I joined a small SEO firm called SEO Inc as the CTO. At SEO Inc. I successfully optimized some of the largest clients including IGN, Sony, VEGAS.com, Beaches and Sandals Resorts to name a few.
Even though SEO Inc was a ton of fun, I still wanted the ultimate SEO challenge. I moved on as the global head of SEO for Shopping.com an eBay company. This challenge was an interesting one, how do I optimize a site with 50 million products? Every month I helped the business grow by leaps and bounds.
I am now consulting for mostly enterprise e-commerce clients.
Yes there is more too me than this profile shows, but you will just have to ask.
View my complete profile
1 Comments:
This post has been removed by a blog administrator.
Post a Comment
<< Home