Are you a Google Analytics enthusiast?
Share and download Custom Google Analytics Reports, dashboards and advanced segments--for FREE!

www.CustomReportSharing.com
From the folks who brought you High Rankings!
More SEO Content
International SEM | Social Media | Search Friendly Design | SEO | Paid Search / PPC | Seminars | Forum Threads | Q&A | Copywriting | Keyword Research | Web Analytics / Conversions | Blogging | Dynamic Sites | Linking | SEO Services | Site Architecture | Search Engine Spam | Wrap-ups | Business Issues | HRA Questions | Online Courses
Serving Different Content To Search Engine Spider?
Started by
eggman2001
, Mar 25 2008 06:21 PM
10 replies to this topic
#1
Posted 25 March 2008 - 06:21 PM
One of my client's competitors appears to be serving full page content to googlebot, but a login page to anyone else that requests these articles. Is this tactic kosher?
#2
Posted 25 March 2008 - 06:27 PM
It's called cloaking, and is generally frowned upon by the search engines (but not always).
#3
Posted 26 March 2008 - 09:38 AM
It seems like a lot of sites do this. While it would increase the amount of search engine traffic, I wonder how much good it does for the site. It's certainly at least a little irritating for the user. At the same time, it encourages the user to subscribe/register.
#4
Posted 26 March 2008 - 01:45 PM
Can you see the full page content in Google's cache?
#8
Posted 06 April 2008 - 10:30 AM
Very helpful. Thanks.
#9
Guest_ErinDecker_*
Posted 22 April 2008 - 09:29 AM
Would this be an example of requesting not to be cached?
We have suspicions that a competitor is cloaking their site with ours, but we are having a difficult time proving it. I am able to see a cache in Google when I search for them and it appears legit, but in their source code, they have included the above.
Any thoughts on tell-tale signs of cloaking besides the "no cache" one?
Thanks!
QUOTE
<meta http-equiv="Cache-Control" content="no-cache" />
We have suspicions that a competitor is cloaking their site with ours, but we are having a difficult time proving it. I am able to see a cache in Google when I search for them and it appears legit, but in their source code, they have included the above.
Any thoughts on tell-tale signs of cloaking besides the "no cache" one?
Thanks!
#10
Posted 22 April 2008 - 11:35 AM
That one isn't going to affect the search engines Erin. And yes I realize it's confusing since everyone refers to it as caching and that one says no-cache. That particular instruction is for browsers however.
A no cache instruction for the spiders would be part of the meta robots tag. And would look like
On the larger issue of cloaking, the easiest way to sort out if someone is cloaking or not if they're not allowing the engines to cache or archive content is to set up a browser to emulate Googlebot, etc. Even this wouldn't figure out those that trigger in the originating IP number, but most cloakers triger on the user-agent, not the IP number.
A no cache instruction for the spiders would be part of the meta robots tag. And would look like
CODE
<meta name="robots" content="noarchive">
On the larger issue of cloaking, the easiest way to sort out if someone is cloaking or not if they're not allowing the engines to cache or archive content is to set up a browser to emulate Googlebot, etc. Even this wouldn't figure out those that trigger in the originating IP number, but most cloakers triger on the user-agent, not the IP number.
#11
Guest_ErinDecker_*
Posted 24 April 2008 - 08:06 AM
Thanks Randy!
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users









