Welcome to the Q&A Forum

Well rather the amount of links each page of the sitemap.html is allowed to have. For example, If I have a huge site, I don't want to place all links on 1 page, I would probably break them out to allow the crawlers some breathing room between different links.

we have a lot of pages that we want to create crawlable paths to. How many links are able to be crawled on 1 page for sitemap.html

We have a directory site with multiple listings. Currently, our page structure is fragmented for each of the tabs (about, products, reviews, etc) with canonicals going back to the main listing page. This includes the reviews as well. Review aggregate is marked up and the stars are rendering in the SERPs.

We are planning to break out reviews to /reviews and including a paginated series, then all of the tabs (about, products, NOT reviews) will be javascript loading content so no more fragmented URLs.

Right now, I suspect that the stars are rendering on the main listing page because the review page that is currently fragmented has a canonical back to the main listing page. The main listing page also is marked up with the review aggregate. if we break out /reviews, all of the reviews will live on /reviews.

If we break out /reviews to it's own URL, will we have to have a small amount of reviews on the main listing page to have the stars render in the SERPs for the main listing page?

Hey everyone,

I have another question regarding duplicate content. We are planning on launching a new sector in our industry to satisfy a niche. Our main site works as a directory with listings with NAP. The new sector that we are launching will be taking all of the content on the main site and duplicating it on a subdomain for the new sector.

We still want the subdomain to rank organically, but I'm having struggles between putting a rel=canonical back to main site, or doing a self-referencing canonical, but now I have duplicates.

The other idea is to rewrite the content on each listing so that the menu items are still the same, but the listing description is different. Do you think this would be enough differentiating content that it won't be seen as a duplicate?

Obviously make this to be part of the main site is the best option, but we can't do that unfortunately.

Last question, what are the advantages or disadvantages of doing a subdomain?

Great response Nigel and thank you so much for your insight!

Hi Nigel,

I got some more responses from other sources and it seems like duplicating a new site IS a bad idea.

Let's say we canonical to website A so that Google knows that the main page is on site A. Would Website B have chances to index & rank? I've heard that canonical is just a signal to Google. Google will ultimately determine which page they will want to show even if the canonical is there. Is this true?

Hi Nigel,

Thanks for the response again! I understand that you may have had sites that had shared content, but what was the scale of these websites? Do you think if Website A was a huge authority that this issue won't be as big of a deal?

We're talking millions of sessions per month.

Hi Nigel,

Thanks for the response again! I have a few questions:

• Why do you think I will destroy Site A? If that logic is true, theoretically, wouldn't you be able to copy someones site 100% and cause it to get destroyed?
• Have you seen any examples of this before?

I don't mean to neglect your advice, I'm just hearing different things from different people and need an accurate response in order to make the right decision.

Hey Nigel,

Thanks for your answer! Just to give some reference, Website A is currently up and has been up for a long time. It is getting A LOT of traffic and we don't want to risk anything on website A which is ranking REALLY well. Also, Website B is being made because of legal issues (can't really get into it) but it's best if we keep them as separate entities.

Because we're looking at scale for 1000s of pages to rewrite content, that doesn't seem like an option. And yes, we will be pulling all of the content from Website A to Website B.

Is the only solution to create completely new content for Website B? Will I face any issues with Website A at all whichever strategy I choose?

Unfortunately, there is no way around it

I think, imo, the best option is to just use the same domain, but that is really something we aren't able to do.

iframe sounds interesting, but we do still want the content (at least the menu of products) indexed.

Changing the content is also out of the question. Way too hard to scale with how many we would have to change.