How far can I push rel=canonical?
-
My plan: 3 sites with identical content, yet--wait for it--for every article whose topic is A, the pages on all three sites posting that article will have a rel=canonical tag pointing to Site A. For every article whose topic is B, the pages on all three sites posting that article will have a rel=canonical tag pointing to Site B.
So Site A will have some articles about topics A, B, and C. And for pages with articles about A, the rel=canonical will point to the page it's on. Yet for pages with articles about B, the rel=canonical will point to the version of that article on site B. Etc.
I have my reasons for planning this, but you can see more or less that I want each site to rank for its niche, yet I want the users at each site to have access to the full spectrum of articles in the shared articles database without having to leave a given site.
These would be distinct brands with distinct Whois, directory listings, etc. etc.
The content is quality and unique to our company.
-
I think I'd start slowly in that case. Keep the relationship aspect in mind, too. Even if all three companies know the writer/client and are aware of the relationship, sooner or later one of these articles is going to take off. If one site gets the SEO credit and the other two sites aren't ranking, there may be friction. Even if the work is spread out evenly and all high-quality, you don't control (ultimately) what content finally sticks and is successful. I just think things could get weird all-around if you send every article three places and only one gets credit.
-
These are technically different companies with different products, all of which are in the securities industry. They are each founded by different groups of individuals, however my client is common among them and happens to be a fantastic writer. Many of the articles would add value to the readers of some of the other sites. I am hoping to develop a common command center so that in the editor for a given article he is able to just check off which of his sites the article will be published at, and which is to be considered canonical. So the sites will have different aesthetics and navigation, product pages, and other company-specific content, and not every article will show up on every site, however many will show up at multiple sites.
The idea of phasing in common articles with the cross-domain canonical strikes me as wise, and then just noindexing the non-canonical versions if I run into trouble.
-
Ah, understood. So, yes, in theory cross-domain canonical does handle this. I know major newspapers that use it for true syndication. There is risk, though, depending on the sites and content, and there is a chance Google will ignore it (moreso than in-domain canonical). So, I mostly wanted you to be aware of those risks.
META NOINDEX is safer, in some respects (Google is more likely to honor it), but if people start linking to multiple versions of the content, then you may lose the value of those inbound links on the NOINDEX'ed content. Since it's not showing up in search results, that's less likely (in other words, people are going to be most inclined to link to the canonical version), but it's a consideration.
It's really tough to give a recommendation without understanding the business model, but if you absolutely have to have separate sites and you feel that this content is valuable to the visitors of all three sites, then cross-domain canonical is an option. It's just not risk-free. Personally, I'd probably start with unique content across the three domains, then phase in the most useful pieces as duplicates with canonical. Measure and see how it goes. Don't launch 1,000 duplicates on three sites in one day.
-
Budget not an issue, although skilled labor is.
-
Very helpful, thank you!
There is in fact a legal reason why the sites must be distinct from each other and strong marketing reasons why we do need more than one site.
I should mention that although the pages hosting the shared articles will be 99% identical, each site will have other content distinct from the others.
I am open to dropping my idea to share an article database between the sites and just having unique content on each, although I have to wonder what the use of cross-domain canonical is, if not to support this kind of article syndication.
-
Completely agree with dr Peter. If you really need to separate those domains it should be a really good reason.
In my past I used to have many EMD domain to get easy traffic thanks to the domain name boost in serps and so those sites were ranking without many efforts, but after google heading more towards brands this kind of strategy is really time and money consuming.
It really depends on how much budget you may spend on those sites, but normally consolidating the value in one bigger site is the best way to build a brand and achieve links and ranks nowadays.
-
I tend to agree - you always run the risk with cross-domain canonical that Google might not honor it, and the you've got a major duplicate content problem on your hands.
I think there's a simpler reason, in most cases, though. Three unique sites/brands take 3X (or more, in practice) the time and energy to promote, build links to, build social accounts for, etc. That split effort, especially on the SEO side, can far outweigh the brand benefits, unless you have solid resources to invest (read that "$$$").
To be fair, I don't know your strategy/niche, but I've just found that to be true 95% of the time in these cases. Most of the time, I think building sub-brands on sub-folders within the main site and only having one of each product page is a better bet. The other advantage is that users can see the larger brand (it lends credibility) and can move between brands if one isn't a good match.
The exception would be if there's some clear legal or competitive reason the brands can't be publicly associated. In most cases, though, that's going to come with a lot of headaches.
-
Hi all, I think that your alternatives would be:
- one big site with all the thematics. In that way all users can access all content without leaving the site, no need for noindex no need for canonicals since you won't have dupe content
- three sites with specialized articles in each one. You may change slightly your design to give the user the feeling that the site is different but in the same network. Then you may interlink those sites as useful resources. Not optimal since they'll have a huge interlinking,
- as you said noindex the non canonical article. Remember that the noindex tag will prevent indexation not crawling because google will need to crawl your page to know that it should not index it. So you may add meta "noindex,nocache,follow" in the header and be sure that the juice is still flowing in your site.
-
Hmm, ok that's helpful.
The content would be identical with the possible exceptions of a very slightly different meta title and site footer.
What's my alternative to a setup like this? One site, one brand? Noindex the non-canonical article versions?
What I dislike about noindex is that it means inbound links to the non-canonical article versions bring me no benefit.
-
I believe you are playing with fire here... to me this looks like you are trying to manipulate search engines.
If you read the article About rel="canonical" on Google Webmasters Support, you will see they say rel="canonical" link element is seen as a hint and not an absolute directive
Also in the same article they specify that rel="canonical" should be used on pages with identical content. Are you sure in your case the pages have identical content (per total) or just identical articles?
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
How (or if) to apply re canonical tags to Shopify?
Anyone familiar with Shopify will understand the problems of their directory structure. Every time you add a product to a 'collection' it essentially creates a duplicate. For example... https://www.domain.com/products/product-slim-regular-bikini may also appear as: https://www.domain.com/collections/all/products/product-slim-regular-bikini https://www.domain.com/collections/new-arrivals/products/product-slim-regular-bikini https://www.domain.com/collections/bikinis/products/product-slim-regular-bikini etc, etc It's not uncommon to have up to six duplicates of each product. So my question is twofold: Firstly, should I worry about this from an SEO point of view? I understand the desire to minimise potential duplicate content issues and also in focussing the 'juice' on just one page per product. But I also planned on trying to build the authority of the collection pages. If I request Google not to index the product pages which link off the collections, does this not devalue these collections pages? Secondly, I understand the correct way to fix these is using 'rel canonical' tags, but I'm not clear about HOW to actually do this. Shopify support has not been very helpful. They have provided two different instructions, so just added to the confusion (see below). Shopify instruction #1: Add the following to the theme.liquid file... <title><br />{{ page_title }}{% if current_tags %} – tagged "{{ current_tags | join: ', ' }}"{% endif %}{% if current_page != 1 %} – Page {{ current_page }}{% endif %}{% unless page_title contains shop.name %} – {{ shop.name }}{% endunless %}<br /></title>
Intermediate & Advanced SEO | | muzzmoz
{% if page_description %} {% endif %} Shopify instruction #2: Add the following to each individual product page... So, can anyone help clarify: The best strategic approach to this inherent SEO issue with Shopify (besides moving to another platform!)? and If 'rel canonical' tags is the way to go, exactly where and how to apply them? Regards, Murray1 -
Does a non-canonical URL pass link juice?
Our site received a great link from URL A, which was syndicated to URL B. But URL B is canonicalized to URL A. Does the link on URL B pass juice to my site? (See image below for a visual representation of my question) zgbzqBy
Intermediate & Advanced SEO | | Choice1 -
Yoast & rel canonical for paginated Wordpress URLs
Hello, our Wordpress blog at http://www.jobs.ca/career-resources has a rel canonical issue since we added pagination to the front page and category-pages. We're using Yoast and it's incorrectly applying a rel-canonical meta tag referencing page 1 on page 2, 3, etc. This is a known misuse of the rel-canonical tag (per Google's Webmaster Blog - http://googlewebmastercentral.blogspot.ca/2013/04/5-common-mistakes-with-relcanonical.html, which says rel-canonical should be replaced with rel-prev and rel-next for page 2, 3, etc.). We don't see a way to specify anywhere in Yoast's options to correct this behaviour for page 2, 3, etc. Yoast allows you to override a page's canonical URL, otherwise it automatically uses the Wordpress permalink. My question is, does anyone know how to configure Yoast to properly replace rel-canonical tags with rel-prev and rel-next for paginated URLs, or do I need to look at another plugin or customize the behavior directly in my child theme code? This issue was brought up here as well: http://moz.com/community/q/canonical-help, but the only response did not relate to Yoast. (We're using Wordpress 3.6.1 and Yoast "Wordpress SEO" 1.4.18)
Intermediate & Advanced SEO | | aactive0 -
What is the difference between link rel="canonical" and meta name="canonical"?
Hi mozzers, I would like to know What is the difference between link rel="canonical" and meta name="canonical"? and is it dangerous to have both of these elements combined together? One of my client's page has the these two elements and kind of bothers me because I only know link rel="canonical" to be relevant to remove duplicates. Thanks!
Intermediate & Advanced SEO | | Ideas-Money-Art0 -
Canonical Meta Tag
Can someone explain how this works and how necessary is it? For example, I have a new client, who is ranking WITHOUT the www in their domain, but they have a good deal of backlinks already that have www in it. When I set up google webmaster tools I made 2, one for WWW and one for WITHOUT and there are diffenet numbers of backlinks for each. I have no idea what do about this or if I should even do anything. Thanks
Intermediate & Advanced SEO | | TheGrid0 -
Canonical URL Question
Hi Everyone I like to run this question by the community and get a second opinion on best practices for an issue that I ran into. I got two pages, Page A is the original page and Page B is the page with duplicate content. We already added** ="Page A**" />** to the duplicate content (Page B).** **Here is my question, since Page B is duplicate content and there is a link rel="canonical" added to it, would you put in the time to add meta tags and optimize the title of the page? Thanks in advance for all your help.**
Intermediate & Advanced SEO | | DRTBA0 -
Rel Alternate tag and canonical tag implementation question
Hello, I have a question about the correct way to implement the canoncial and alternate tags for a site supporting multiple languages and markets. Here's our setup. We have 3 sites, each serving a specific region, and each available in 3 languages. www.example.com : serves the US, default language is English www.example.ca : serves Canada, default language is English www.example.com.mx : serves Mexico, default language is Spanish In addition, each sites can be viewed in English, French or Spanish, by adding a language specific sub-directory prefix ( /fr , /en, /es). The implementation of the alternate tag is fairly straightforward. For the homepage, on www.example.com, it would be: -MX” href=“http://www.example.com.mx/index.html” /> -MX” href=”http://www.example.com.mx/fr/index.html“ />
Intermediate & Advanced SEO | | Amiee
-MX” href=”http://www.example.com.mx/en/index.html“ />
-US” href=”http://www.example.com/fr/index.html” />
-US” href=”http://www.example.com/es/index.html“ />
-CA” href=”http://www.example.ca/fr/index.html” />
-CA” href=”http://www.example.ca/index.html” />
-CA” href=”http://www.example.ca/es/index.html” /> My question is about the implementation of the canonical tag. Currently, each domain has its own canonical tag, as follows: rel="canonical" href="http://www.example.com/index.html"> <link rel="canonical" href="http: www.example.ca="" index.html"=""></link rel="canonical" href="http:>
<link rel="canonical" href="http: www.example.com.mx="" index.html"=""></link rel="canonical" href="http:> I am now wondering is I should set the canonical tag for all my domains to: <link rel="canonical" href="http: www.example.com="" index.html"=""></link rel="canonical" href="http:> This is what seems to be suggested on this example from the Google help center. http://support.google.com/webmasters/bin/answer.py?hl=en&answer=189077 What do you think?0 -
Is having a canonical tag for the link that IS the canonical a negative thing?
Throughout our site, canonical tags have been added where needed. However, the canonical tags are also included for the canonical itself. For example, for www.askaquestion.com, the canonical tag has been added as www.askaquestion.com. Will this have a negative impact or does it not really matter whether there is such a loop?
Intermediate & Advanced SEO | | kbbseo0