Analyzing potential SEO problems on large sites
When you are dealing with really large sites that get millions of visits, it can be a daunting task to see potential problems. The advent of Google’s Webmaster Tools has helped with identification of problems. However it’s not perfect, especially when you have millions of pages. Thus going back to basics can be the best way to check your logic.
If you are linux savvy, I would recommend grep’ing through you log files and start with the simple things. Here are a few examples of what you can look for.
more access_log | grep Googlebot | grep 302 > somenewfile this is a great way to see if you have any potential redirects that may be causing problems. 302’s are still notorious for causing issues.
You can also look for simple errors, like a 404
more access_log | grep Googlebot | grep 404 > somenewfile
I recently went through several sites and found an abundance of errors just by diligently looking at a small sample of logs. All you need is about 100meg’s or so, for a decent sample size.
If you are linux savvy, I would recommend grep’ing through you log files and start with the simple things. Here are a few examples of what you can look for.
more access_log | grep Googlebot | grep 302 > somenewfile this is a great way to see if you have any potential redirects that may be causing problems. 302’s are still notorious for causing issues.
You can also look for simple errors, like a 404
more access_log | grep Googlebot | grep 404 > somenewfile
I recently went through several sites and found an abundance of errors just by diligently looking at a small sample of logs. All you need is about 100meg’s or so, for a decent sample size.
Labels: in house seo, seo
by Aaron Shear
0 Comments:
Post a Comment
<< Home