Forum Moderators: Robert Charlton & goodroi
I just entered [www...] .pubcon.com/blog/ [no space], WebmasterWorld did the rest.
It's a form of indirect link, usually used to disincentivise spammers, but also by those who fear 'passing page rank' to anyone except their sister :)
I don't see why it should cause duplicate content, however.
Please note I did not say would or does, the weasel word I used was can.
Remember it is all in the weasel words.
Could have, would have, should have, and did have could all be the same but they don't need to be ;-).
Exactly?
Mouseover a few links - are they the same?
Maybe even look at the source code ... is it the same?
What URL shows in your browser? the whole address, or just your URL?
If everything is the same, and the URL is bringing people to your site, I don't think you should worry; someone has placed that link on a page instead of your direct link ... but it looks like no harm was done.
If anything is different, however ...
>What URL shows in your browser? the whole address, or just your URL?
just my url
i feel much better now
Thanks a lot Quadrille and theBear!
Is there any scenario where a cross-domain 302 "should be" listed under the source url, rather than the target url? Heck, even within the same domain. I've never understood what challenges keep 302 handling from being just that simple for Google. But it's been years and years with no definitive fix, so there must be some complication that I'm not seeing.
One characteristic I noticed in almost all these 302 situations, is that the source url includes the "hijacked" domain's address - often in a query string or some end section of the source url.
?
But it will be back after 6 months, sticked for a long time in the index.....
Another thing I picked up on is this:
www.google.com/search?q=allinurl:imdb.com/r/
These are 302 redirects that are being crawled and cached... the content is amazon.com’s, however.