|Duplicate pages across mulitple domains - I used noindex|
|azn romeo 4u|
| 6:37 am on Sep 6, 2010 (gmt 0)|
I got a widget site that shares forum db's. Right now I have two sites that share one db. One old site, and one new site. The original db had already 2,000,000 posts in it. I only share certain community forums with the other new site.
The new site will suddenly have 1,000,000 plus new pages in it. And I just started it 3 weeks ago. However I put noindex in all those pages. How will this effect my new site and my old site?
Should I put nofollow as well.
I do this, because I have a forum network of widget sites that uses a Single Sign on System. It uses vbulletin software. I wanted to do this, because I wanted my users to have their information transfered to other forums without having to start fresh. This way they always have their reputation and post count. And those shared forum, which is like genearl chat, tech, spam, etc etc, which doesn't have to deal with the main widget, can be used by the entire network. This way each new site doesn't have to start it's own common forums all over again. This way they can interact with the other forums.
So bascailly, am I in deep doodoo here? For wanting to share my forums? Even though i have noindex and/or nofollow?
| 9:16 am on Sep 6, 2010 (gmt 0)|
I recommend using noindex and nofollow, or even disallow.
If you have a large volume of duplicate content then you might have big canonicalisation problems.
|azn romeo 4u|
| 2:44 pm on Sep 6, 2010 (gmt 0)|
So definately nofollow for sure then? I don't think I can use disallow in robot text, because the vbulletin 3.8x url's would make that extremely difficult.
| 8:08 pm on Sep 6, 2010 (gmt 0)|
Personally I think it's a bad idea all round, google isn't going to like it and in general I'm not sure what you're offering visitors if it's duplicated content.
If you want users to be able to carry across their information, logins and reputation it me be an idea to only copy across the user tables and not the post tables.
imo nofollow is a little pointless, it doesn't stop google indexing that page, only the link. It is entirely possible for all of those pages to still be indexed.
noindex should be fine but I would also advise disallow.
| 8:38 pm on Sep 6, 2010 (gmt 0)|
No one has yet mentioned a canonical link tag with the absolute original address. Cross-domain canonical tags are supported (only by Google for now). Depending on your situation altogether, it is another possible way to go
|azn romeo 4u|
| 10:08 pm on Sep 6, 2010 (gmt 0)|
Well, my other way of stop indexing, is making the particular shared forums members only viewable.
I do it, because it is easier for the members to interact with each other from both sites. I don't do it for the google. Members on each site only visit one site. They don't cross visit the two sites. But the forums that i share across the sites, can be discuss commonly.
Disallow and canonical have to go in robot txt right? Not possible to work with vbulletin. Since they use thread.php?id=12354 for links. I don't think I can separate or make them differentiate.
| 10:38 pm on Sep 6, 2010 (gmt 0)|
Is an option to create your new forum framework on the old domain, then simply frame it on the new domain maybe?
| 10:57 pm on Sep 6, 2010 (gmt 0)|
|Disallow and canonical have to go in robot txt right? |
The canonical link tag goes in the <head> section. See [googlewebmastercentral.blogspot.com...]