Localized content is served on EACH domain ==> problem: duplicate content vuln

There are more problems arising from this.

The language selector block always displays a flag for the installed languages,
but it should only display the flag for the TRANSLATED languages,
otherwise this leads (once again) to duplicate content

e.g. check this german post here

http://www.marketingfan.at/suchmaschinen/seo/text-link-aufbau/spammy-blo...

which does NOT have an english translation (so far)

but the flag "english" is displayed, and leads to an url that should not exist
(germanish url on english domain)

These problems again

* cause duplicate content issues in search engines
* cause confusion with readers finding german content on english domains

Hi Robert,

thanks for your comprehensive feedback!
and sorry for mixing up support request (for the similar entries module)
and the bug that duplicate content is served on multiple domains.

I made a mistake in the initial post - the problem is on the domains

http://www.marketingfan.com (english)
and
http://www.marketingfan.at (german)

in addition to the problems with similar entries, the more major issue
from my point of view is that the language selector provides a lanugage selection
(in the other language) even if the content has NOT been translated.

so if you take a look at this post

http://www.marketingfan.at/suchmaschinen/seo/text-link-aufbau/spammy-blo...

there's flag presented, which links to the .com domain with the german url alias
and also the german content

That doesn't make sense from a user's view
and even more it's a problem as google detects duplicate content across the domains
marketingfan.at and marketingfan.com then

>In every case it is possible to write a customized block selector if you want.
Yes - I want :-) what do I need to do?

Goal should be that the block selector

- displays a flag for EACH translation
- if a translation is not present for a node, then the flag may not be displayed
- if lanugage locale selection is made by domain (as I use it - great feature! thanks!)
and the url alias for language 1 is called up on domain for language 2, then a 301 redirect
must be issues to redirect the user and search engine (google) to the correct language domain

the last point is especially important to make sure all plugins/add modules not (yet) compatible with
localizer don't make the dupe content problem worse

I'd love to help with implementation if you point me to the right places!

Robero, will you also come to DrupalCon2007 in Barcelona in Sept?

best,christoph

Hi Roberto,

no, I'm using 5.x-1.9

Hi Roberto,

no, I'm using 5.x-1.9

Robert,

let's forget the "similar entries" module - this is a second issue that has nothing to do with this problem.

The issue is, that Localizer is serving up content on domains that do not relate to their language.

So if I got two domains,

domain.de for german
domain.us for english

and I set these up in the localizer config, I except localizer to server only pages
of the appropriate language.

This means, if

domain.de/english-node is called, it should 301 redirect to domain.us/english-node

if

domain.us/german-node is called, it should 301 redirect to domain.de/german-node

to make sure only the language content written for a domain is served up on it.

christoph

ADD: the problem is already caused by localizer, BECAUSE it generates links wrong

on domain.de/german-node it generates a link to domain.us/german-node which does not make sense at all...

got it now?

Roberto, thanks - I'll help with testing as soon as you got it ready

any news roberto?

HI Roberto,

what did you change?

it's still the same problem

when I call up an english node on the german domain, it's presented as if everthign was fine.

what I expected was that when an english node is loaded on german domain, it does a redirect to the english domain

I turned on "switch by node language" but this hasnt' changed behaviour

can you comment on what you changed in this version?

thanks
christoph

Roberto, sorry, but it appears nothing has changed...

Still the site serves the german content on the english domain,
when using the german nodeids/urls on the english domain.

Again, expected behaviour would be a redirect to the german domain

roberto,

I looked into your code and I have a hard time finding even the place where the header-redirect is made for the particulr page if the content is not in the correct language as the current domain... can you point me to the correct code lines?

still no redirects and duplicate content issue in full effect on both domains mentioned :(

Thanks Juan!

notice to all - the MarketingFan installation is already patched, so what you see when clicking above link
and it's redirect to the proper .com domain is already because of that patch.

This patch also removes the wrong links in the language,
which used to show links to pages (i.e. for german) even if that node did not have a translation