| 4:49 pm on Jun 8, 2008 (gmt 0)|
I'll have to beg Brett's forgiveness for dredging up the past but WebmasterWorld is actually one of the few cases where this very issue has been discussed and resolved with Google's Matt Cutts on his blog.
Matt said it was cloaking when WebmasterWorld originally put up a login page first, before showing any content. However, after Brett changed the code to show one page, the page Google indexed, and then show a login page if you tried to go further, it was no longer considered cloaking and resolved.
So based on that thread from Matt, what you're describing with facebook is definitely cloaking and against Google's rules unless they show you the exact page Google indexed before requiring a login. If you've already seen one page from a Google search and then get a login, it's perfectly legitimate to restrict access beyond a single access.
However, I just tried what you described and was able to view multiple members pages without any issue.
[edited by: incrediBILL at 4:57 pm (utc) on June 8, 2008]
| 10:08 pm on Jun 8, 2008 (gmt 0)|
"However, I just tried what you described and was able to view multiple members pages without any issue."
I know right, its like google is automatically loged in when it visits the page, so It looks at the site the same as a loged in user.
so one could argue that this could be done on anysite without retrubition from big G?
| 10:15 pm on Jun 8, 2008 (gmt 0)|
The cache I see is the same as the page the user sees, unless I'm missing something? Certain profiles (e.g. bands) seem to be public for everybody.
Note that I don't even have a facebook account, so I don't really know what I'm talking about on this one ;)
| 6:54 pm on Jun 17, 2008 (gmt 0)|
Same here, I don't have a facebook account either and I saw exactly what Google saw.
| 4:58 pm on Jun 23, 2008 (gmt 0)|
This was an interesting post - i was not familiar with the issue of cloaking....
any sense of how common this is? I would like to look more into this.