Cross Domain Rel Canonical tags vs. Rel Canonical Tags for internal webpages
-
Today I noticed that one of my colleagues was pointing rel canonical tags to a third party domain on a few specific pages on a client's website. This was a standard rel canonical tag that was written
Up to this point I haven't seen too many webmasters point a rel canonical to a third party domain. However after doing some reading in the Google Webmaster Tools blog I realized that cross domain rel canonicals are indeed a viable strategy to avoid duplicate content.
My question is this; should rel canonical tags be written the same way when dealing with internal duplicate content vs. external duplicate content? Would a rel=author tag be more appropriate when addressing 3rd party website duplicate content issues?
Any feedback would be appreciated.
-
Excellent response. Thanks Michael.
-
Rel=canonical pointing to a different domain is essentially telling Google "here's the original copy of this article".
That's fine if you choose to reprint just the occasional bit of content from somewhere else.
It's also a fine strategy to use in a white-label system, where you might have the same content published across a number of sites, all branded differently.
But you want to use this sparingly. If you've got a site with 1000 pages, and 750 of those pages are rel=canonicalled back to another domain, essentially you're telling Google that most of your website is just republished stuff that somebody else wrote. That's not going to be a good signal for Google of the likely quality of the site in general.
If you're in a situation where you really do need to publish a lot of pages on multiple sites, and all of the sites do need to be found in search for SOME terms, then for those duplicated pages, I'd noindex them on the "copy" sites, so that in the example above, Google would only see and index 250 pages, all of which would be original content.
-
I have used rel=canonical on a few pages of content that were published on two of my websites. T
-
No, rel="canonical" is the same internally or cross-domain. You are just telling Google which copy of that content to serve, wherever it is. (And rel="author" is no longer used by Google to show authorship in results nor is it tracking data from content using that markup. http://searchengineland.com/goodbye-google-authorship-201975 https://plus.google.com/u/0/+JohnMueller/posts/HZf3KDP1Dm8 )
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
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
-
Are there any downsides to using a canonical tag temporarily?
I'm working on redesigning our website. One of the content types has a main archive page (/success-stories) containing all of the success stories (written by graduates of our program). Because we plan to have success stories for other people (non-graduates), I'm using category hierarchies (/success-stories/graduates and success-stories/nonprofits, for example). It will go one level deeper to organize graduates by graduation year (/success-stories/graduates/%year%). I think this will work out well. However, we won't have non-graduate success stories for a little while, probably at least a few weeks, which means that /success-stories and /.../graduates indices will contain the same content for a while. So my question is this: Will it hurt to use a canonical tag that points to /success-stories/graduates as the authority until the main archive page contains more than just graduates? Or would it be better to use a 302 redirect from /success-stories to /.../graduates until more diverse content is added?
Intermediate & Advanced SEO | | bcaples0 -
International Blog Structure & Hreflang Tags
Hi all, I'm running an international website across 5 regions using a correct hreflang setup. A problem I think I have is that my blog structure is not standardized and also uses hreflang tags for each blog article. This has naturally caused Google to index each of the pages across each region, meaning a massive amount of pages are being crawled. I know hreflang solves and issues with duplication penalties, but I have another question. If I have legacy blog articles that are considered low quality by Google, is that counting against my site once or multiple times for each time the blog is replicated across each region? I'm not sure if hreflang is something that would tell Google this. For example, if I have low quality blog posts: blog/en-us/low-quality-article-1
Intermediate & Advanced SEO | | MattBassos
blog/en-gb/low-quality-article-1
blog/en-ca/low-quality-article-1 Do you think Google is counting this as 3 low quality articles or just 1 if hreflang is correctly implemented? Any insights would be great because I'm considering to cull the international setup of the blog articles and use just /blog across each region.0 -
Why is rel="canonical" pointing at a URL with parameters bad?
Context Our website has a large number of crawl issues stemming from duplicate page content (source: Moz). According to an SEO firm which recently audited our website, some amount of these crawl issues are due to URL parameter usage. They have recommended that we "make sure every page has a Rel Canonical tag that points to the non-parameter version of that URL…parameters should never appear in Canonical tags." Here's an example URL where we have parameters in our canonical tag... http://www.chasing-fireflies.com/costumes-dress-up/womens-costumes/ rel="canonical" href="http://www.chasing-fireflies.com/costumes-dress-up/womens-costumes/?pageSize=0&pageSizeBottom=0" /> Our website runs on IBM WebSphere v 7. Questions Why it is important that the rel canonical tag points to a non-parameter URL? What is the extent of the negative impact from having rel canonicals pointing to URLs including parameters? Any advice for correcting this? Thanks for any help!
Intermediate & Advanced SEO | | Solid_Gold1 -
Should I use a rel=canonical to the home page
Hi guys, I have a site where the homepage is ranking for the term 'industrial flooring' around position 30 and the actual level 2 industrial flooring page is ranking well below at around position 60. I'm happy for the homepage to rank for this term and would like to see it improve, so here are my questions: 1: Is the existence of the level 2 page preventing the homepage from ranking higher due to keyword cannibalization etc.? 2: Would the use of the rel=canonical tag pointing from the level 2 page to the home page have a positive or negative impact on the homepage's rankings for 'industrial flooring'? 3: Is there anything else I'm missing? Greatly appreciated.
Intermediate & Advanced SEO | | Blaze-Communication0 -
Microsites: Subdomain vs own domains
I am working on a travel site about a specific region, which includes information about lots of different topics, such as weddings, surfing etc. I was wondering whether its a good idea to register domains for each topic since it would enable me to build backlinks. I would basically keep the design more or less the same and implement a nofollow navigation bar to each microsite. e.g.
Intermediate & Advanced SEO | | kinimod
weddingsbarcelona.com
surfingbarcelona.com or should I rather go with one domain and subfolders: barcelona.com/weddings
barcelona.com/surfing I guess the second option is how I would usually do it but I just wanted to see what are the pros/cons of both options. Many thanks!0 -
Canonical VS Rel=Next & Rel=Prev for Paginated Pages
I run an ecommerce site that paginates product pages within Categories/Sub-Categories. Currently, products are not displayed in multiple categories but this will most likely happen as time goes on (in Clearance and Manufacturer Categories). I am unclear as to the proper implementation of Canonical tags and Rel=Next & Rel=Prev tags on paginated pages. I do not have a View All page to use as the Canonical URL so that is not an option. I want to avoid duplicate content issues down the road when products are displayed in multiple categories of the site and have Search Engines index paginated pages. My question is, should I use the Rel=Next & Rel=Prev tags on paginated pages as well as using Page One as the Canonical URL? Also, should I implement the Canonical tag on pages that are not yet paginated (only one page)?
Intermediate & Advanced SEO | | mj7750 -
Google Author Biography Tag-Why Should I Pay Attention To The Author Biography Tag
Hello, I've reading all about Google's Author Biography tag but I am not sure how I can use this in my business. Can anyone explain ( in plain simple English) how I can leverage this tag? Is there any implications in SEO and higher rankings? Just trying to wrap my head around this concept and why it's important...or not. Thanks, Bill
Intermediate & Advanced SEO | | wparlaman0 -
How permanent is a rel="canonical"?
We are rolling out our canonicals now, and we were wondering: what happens if we decide we did this wrong and need to change where canonicals point? In other words, how bad of a thing is it to have a canonical tag point to page a for a while, then change it to point to page b? I'm just curious to see how permanent of a decision we are making, and how bad it will be if we screwed up and need to change later. Thanks!
Intermediate & Advanced SEO | | CoreyTisdale0