Welcome to the Q&A Forum

Thanks Adam Is there a problem with using noindex as noted in my original post? Having read a bit about canonical now and watched matt cutts video, the advice is to use other forms of redirect, e.g. 301, first, 'rel=”canonical” link element is seen as a hint and not an absolute directive' However, is not feasible that client can manually upload an ediited .htacess file with new 301 redirect each time and article is uploaed, acorss different domains. So, what i am trying to say is, what would be the best method in my situation? Matt

Perhaps HTML5 tags are used as one of the signals in determining which piece of source code is what. Seeing how easily one could manipulate these tags, I don't think it'll be a strong signal though. Of course it can be a good guidance for future web developers to identify pieces of source code! Google is able to read CSS files (for example to determine if a link is hidden), but I don't think it will parse these files and apply them to the webpage to determine the visual layout of it. I think it would require a great amount of processing power (and time) to actually render a webpage, rather than sort out the pieces based on the source code like I described in my answer above. Glad I could help!

When you have visitor submitted pages, you don't control the amount of content. I'm just trying to assess how much I need to add to those pages to make them unique pages/better quality. Thank you for your response.

1. Yes 2. Using google analytics 3. Google organic search. 4. It's not site wide but it's prevalent on pages that we did not do the AJAX change to Thanks!

Thanks Wissam, that's cleared that up. On my blog page I don't have the same URL so it will count it in the body text. Many Thanks

Anna, were you able to figure this out? If not, we're happy to help if you can give us some more details, examples, or a URL.

I can't see why there would be a penalty, but if you give us an example of the code or plugin/solution you're using, we can research it a little and see if there are any problems.

They will be treated as seperate sites, to us www1 and www may seem very similar but to Google it will be two separate things. Even http:// and http://www. can be two different sites. So from that point of view I say you are safe given that you're not duplicating content in ways that I may not be aware currently.

I'd focus on the satellite sites.  You can handle many of the duplicate product issues by using a cross-domain rel canonical from the niche site to the old site.