Canonical and Alternate Advice
-
At the moment for most of our sites, we have both a desktop and mobile version of our sites. They both show the same content and use the same URL structure as each other. The server determines whether if you're visiting from either device and displays the relevant version of the site.
We are in a predicament of how to properly use the canonical and alternate rel tags. Currently we have a canonical on mobile and alternate on desktop, both of which have the same URL because both mobile and desktop use the same as explained in the first paragraph.
Would the way of us doing it at the moment be correct?
-
That would normally be the case but not tonight.
LOL, I am picking up a lot of the UK Q&A I will be at BrightonSEO and search love London if any of you guys will be in the area I'd love to grab a pint?
sincerely,
Thomas
-
The reason we answered 'quickly' by the way is because we are in the UK - you were still in bed lol!
-
There is only ONE URL that is the point.
If they share the same URL then you only have one page of code so ONE canonical
Regards
Nigel
-
Sorry Nigel
was not trying to make this more complicated was just trying to make sure that we were all on the same page.
FYI if you need a method of adding the rel canonical to your website quickly you can use Google tag manager or if you want to add to the header
https://support.stackpath.com/hc/en-us/articles/360001445283-EdgeRules-Adding-a-Canonical-Header
-
So a self referencing canonical on both mobile and desktop versions of the site, regardless if they chuck out two version with the same content?
-
Hi JH
I'm sure Thomas means well with his multiple complicated posts but all of this is totally unnecessary.
Both sites are serving the same URL
You can't put a rel=alternative because there is nothing to point to.
Just put a self-referencing canonical. I said that 2 hours ago!
That is all.
Regards Nigel
-
Use a self-referencing canonical
https://blog.seoprofiler.com/google-recommend-self-referencing-canonical-tags/
Please let me know if you want me to remove the image below?
you can use this one if needed http://bseo.io/c1vMSv
-
I've been told to pass on a URL, thanks for your help Thomas!
-
Hey man I understand is a big deal
could you do me a huge favor and run your site through screaming frog SEO spider send me a couple of pages with the domains whited out so I can tell you 100% what to do in this situation because I am basing this on what you have told me and honestly I would like to look at what a tool can show me and that will tell me what I need to do.
Or you can tell me if the mobile version of the site hit's Google's index yes or no?
respectfully,
Tom
-
So both mobile and desktop require a self referencing canonical(in both headers)?
Sorry for the questions, just need to make sure! It's a very touchy subject!
-
The single self-referencing URL will work.
-
What URLs are you using with the “alternate” tag on?
You said
”1. We have multiple brand sites, that have a similar setup. They all have mobile and desktop versions of the sites running on the same URL, both of which show the same content.2. The server determines whether if you're on a desktop or mobile devices using the header information, and points the user to the site relevant files for the given device.”
thats Dynamic serving same URL
Dynamic serving is a setup where the server responds with different HTML (and CSS) on the same URL depending on which user agent requests the page (mobile, tablet, or desktop).
that would NOT give you the mobile or m.example.com & www.example.com different URLs
**But If you do have a different m.example.com & www.example.com URLs you should use this code or XML site maps **
for different URLs use this:
Annotations in the HTML
On the desktop page (http://www.example.com/page-1), add the following annotation:
<linkrel="alternate"media="only screen="" and="" (max-width:="" 640px)"<="" span="">href="http://m.example.com/page-1"></linkrel="alternate"media="only>
On the mobile page (http://m.example.com/page-1), the required annotation should be:
<linkrel="canonical"href="http: www.example.com="" page-1"=""></linkrel="canonical"href="http:>
This rel="canonical" tag on the mobile URL pointing to the desktop page is required.
Or
Annotations in sitemaps
We support including the rel="alternate"annotation for the desktop pages in sitemaps like this:
<urlsetxmlns="http: www.sitemaps.org="" schemas="" sitemap="" 0.9"<="" span="">xmlns:xhtml="http://www.w3.org/1999/xhtml">
<loc>http://www.example.com/page-1/</loc>
<xhtml:linkrel="alternate"media="only screen="" and="" (max-width:="" 640px)"<="" span="">href="http://m.example.com/page-1"/></xhtml:linkrel="alternate"media="only></urlsetxmlns="http:>You should have the same URL on mobile and desktop
You should have the same rel canonical tag on your URLs unless and this is a big unless you're talking about using Google AMP?
If the URL you want to be indexed is the same URL point everything to that URL if that makes it easier to understand.
respectfully,
Tom
-
Just to confirm, are we suppose to have a canonical on desktop and mobile or just desktop?
This would mean removing the alternate?
Want to confirm everything before iterating this across to others.
We are not using AMP, just a standard site setup.
-
Unless you are using AMP?
Then you would add
Linking pages with
In order to solve this problem, we add information about the AMP page to the non-AMP page and vice versa, in the form of tags in the .
Add the following to the non-AMP page:
<link rel="amphtml" href="https://www.example.com/url/to/amp/document.html">
And this to the AMP page:
<link rel="canonical" href="https://www.example.com/url/to/full/document.html">
are you using AMP pages?
https://support.google.com/webmasters/answer/139066?hl=en
https://www.ampproject.org/docs/fundamentals/discovery
I hope that helps you if not please let me know.
Respectfully,
Tom
-
Cool, that's what I thought when I heard your description I just wanted to be very thorough because sometimes you get very little information and I appreciate you letting me know that.
dynamic serving URLs are identical to each other so you should have a self-referencing canonical tag because the URL does not change the real canonical tag just decides what should be in the index and the same URL.
You're Rel canonical should be something like this example below
Example URL https://www.example.com/example-url/
because the end URL is the same and URL that you want to be indexed in Google you want to be certain that you have a self-referencing URL to prevent query strings and other things like that and you do not need to point a URL to an identical URL you just need a self-referencing canonical if that makes sense.
See: https://yoast.com/rel-canonical/
I hope that is of help,
Tom
-
Hi,
I can't give off too much information as it's not my call, but I can answer your questions without mentioning the brands.
1. We have multiple brand sites, that have a similar setup. They all have mobile and desktop versions of the sites running on the same URL, both of which show the same content.
2. The server determines whether if you're on a desktop or mobile devices using the header information, and points the user to the site relevant files for the given device.
3. Our sites would quite clearly fit in the dynamic serving category.
We have 301 redirects on none www to www and http to https.
-
This is the correct solution!
-
The URLs are identical it is just the content that is served that may be slightly different.
Since you can only specify one canonical for each URL it makes no difference. Just self-reference and that is it.
If you had to different URLs then it would be an issue where you woudl need a rel=alternative so there is nothing to worry about.
Regards
Nigel
-
You guys are fast I was going to answer this and had to do some other things but let me weigh in on couple things.
as you said
“We are in a predicament of how to properly use the canonical and alternate rel tags**. Currently we have a canonical on mobile and alternate on desktop, both of which have the same URL because both mobile and desktop use the same as explained in the first paragraph.”**
so what you’re saying is that you have a dynamic site so you don’t need to add “alternate"media” tags to the site.
https://developers.google.com/search/mobile-sites/mobile-seo/dynamic-serving
As it is not immediately apparent in this setup that the site alters the HTML for mobile user agents (the mobile content is "hidden" when crawled with a desktop user agent), it’s recommend that the server send a hint to request that Googlebot for smartphones also crawl the page, and thus discover the mobile content. This hint is implemented using the Vary HTTP header.
**you don’t need this **
Annotations in the HTML
On the desktop page (
http://www.example.com/page-1
), add the following annotation:<code dir="ltr"><linkrel="alternate"media="only screen="" and="" (max-width:="" 640px)"<br="">href="http://m.example.com/page-1"></linkrel="alternate"media="only></code>
On the mobile page (
http://m.example.com/page-1
), the required annotation should be:<code dir="ltr"><linkrel="canonical"href="http: www.example.com="" page-1"=""></linkrel="canonical"href="http:></code>
This
rel="canonical"
tag on the mobile URL pointing to the desktop page is required.Annotations in sitemaps
We support including the
rel="alternate"
annotation for the desktop pages in sitemaps like this:<code dir="ltr"><urlsetxmlns="http: www.sitemaps.org="" schemas="" sitemap="" 0.9"<br="">xmlns:xhtml="http://www.w3.org/1999/xhtml"> <url><loc>http://www.example.com/page-1/</loc> <xhtml:linkrel="alternate"media="only screen="" and="" (max-width:="" 640px)"<br="">href="http://m.example.com/page-1"/></xhtml:linkrel="alternate"media="only></url></urlsetxmlns="http:></code>
The required
rel="canonical"
tag on the mobile URL should still be added to the mobile page's HTML.**to be sure **
Are you willing to share your domain with us? Or one domain?
-
We're talking about multiple websites that all have the identical site structure or at least mobile and desktop site structure?
-
Your server is making the change for you?
-
Would you be kind enough to install this plug-in on chrome in order for you to show a couple examples of the canonical and the URL?
- https://chrome.google.com/webstore/detail/portents-seo-page-review/babgchcegnkbiojmdpnoilficladccfm?hl=en-US
- https://chrome.google.com/webstore/detail/link-redirect-trace/nnpljppamoaalgkieeciijbcccohlpoh?hl=en
In addition, would you be kind enough to run your site through the two tools here ( 100% free and very easy to use)
If you would not mind doing this and sending screenshots it would mean a lot to us and getting your canonical's straightened out.
screenshots https://snag.gy/ then upload to http://imgur.com/
everything is on the same server I'm assuming?
Of the three below how would you categorize your site?
- https://developers.google.com/search/mobile-sites/mobile-seo/separate-urls
- https://developers.google.com/search/mobile-sites/mobile-seo/dynamic-serving
- https://developers.google.com/search/mobile-sites/mobile-seo/responsive-design
Respectfully,
Tom
-
-
Would this mean we need canonical only on desktop or mobile site?
-
You are right - you could only use teh rel=alternate if there was an m. version or similar
Regards
Nigel
-
The self referencing canonical advice was solid and I 100% agree with it. The rel=alternate advice, I felt would cause problems (IMO). But as we all know, fiddly issues like this are highly subjective
-
Then there is no problem simply putting a self-referencing canonical. There is in effect no mobile version as there is a single URL so no need for a rel=alternate.
It's an even easier solution. Well, there isn't a problem in the first place.
rel=alternate is only necessary if you have two different URLs! The fact they are the same takes away the problem.
Regards
Nigel
-
Your problem is that you have two different sites loading on the same URL. If you are returning both the mobile and desktop / laptop site on the same URL, you would be expected to be using responsive design. In-fact, you may have re-invented another different way to implement responsive design which is probably, slightly less fluid yet slightly more efficient :')
Since your mobile and desktop pages both reside on exactly the same URL, I'd test the page(s) with this tool (the mobile friendly tool) and this tool (the page-speed insights tool). If Google correctly views your site as mobile friendly, and if within PageSpeed insights Google is correctly differentiating between the mobile and desktop site versions (check the mobile and desktop tabs) then both URLs should canonical to themselves (self referencing canonical) and no alternate tag should be used or deployed. Google will misread the alternate tag, which points to itself - as an error. That tag is to be used when your separate mobile site (page) exists on a separate URL, like an 'm.' subdomain or something like that
Imagine you are Googlebot. You are crawling in desktop mode, load the desktop URL version and find that the page says, it (itself) is also the mobile page. You'd get really confused
Check to see whether your implementation is even supported by Google using the tools I linked you to. If it is, then just use self referencing canonical tags and do not deploy alternate tags (which would make no sense, since both versions of the site are on the same URL). When people build responsive sites (same source code on the same URL, but it's adaptive CSS which re-organises the contents of the page based upon viewport widths) - they don't use alternate tags, only canonicals
Since your situation is more similar to responsive design (from a crawling perspective) than it is to separate mobile site design, drop the alt
-
The problem with this is, where you say "corresponding mobile URL" - there isn't one as OP has stated that, two different source codes (pages) can be rendered on the same URL depending upon the user's screen size / user-agent (however they are detecting mobile, and serving different pages)
-
Hi JH
This is very straightforward.
Use the following annotations:
- On the desktop page, add a rel=”alternate” tag pointing to the corresponding mobile URL. This helps Googlebot discover the location of your site’s mobile pages.
- On the mobile page, add a link rel=”canonical” tag pointing to the corresponding desktop URL.
It is that simple and doing this will not create duplicate content
More here: https://developers.google.com/search/mobile-sites/mobile-seo/separate-urls
Regards Nigel
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
-
How to deal with canonicals on dup product pages in Opencart?
So I have a seriously large amount of duplicate content problems on my Opencart site, and I've been trying to figure out the best way to fix them one by one. But is there a common, easy way of doing this? Because frankly, it is a nightmare otherwise. I bought an extension which doesn't appear to work (http://www.opencart.com/index.php?route=extension/extension/info&extension_id=20468&utm_source=ordercomplete&utm_medium=email&utm_campaign=wm), so now I'm at a loss.
Intermediate & Advanced SEO | | moon-boots0 -
Is Google ignoring my canonicals?
Hi, We have rel=canonical set up on our ecommerce site but Google is still indexing pages that have rel=canonical. For example, http://www.britishbraces.co.uk/braces/novelty.html?colour=7883&p=3&size=599 http://www.britishbraces.co.uk/braces/novelty.html?p=4&size=599 http://www.britishbraces.co.uk/braces/children.html?colour=7886&mode=list These are all indexed but all have rel=canonical implemented. Can anyone explain why this has happened?
Intermediate & Advanced SEO | | HappyJackJr0 -
Partial duplicate content and canonical tags
Hi - I am rebuilding a consumer website, and each product page will contain a unique product image, and a sentence or two about the product (and we tend to use a lot of the same words in different ways across products). I'd like to have a tabbed area below the product info that talks about the overall product line, and this content would be duplicate across all the product pages (a "Why use our products" type of thing). I'd have this duplicate content also living on its own URL's so they can be found alone in the SERP's. Question is, do I need to add the canonical tag to this page, since there's partial duplicate content on the product pages? And if I did that, would my product pages go un-indexed?? I understand how to handle completely duplicated content, it's the partial duplicate that I'm having difficulty figuring out.
Intermediate & Advanced SEO | | Jenny10 -
Alternative Markup Challenge. Can anyone help?
I have a challenge around alternative markup. We currently operate a single domain with geo-targeted folders and alternative markup implemented. We are now now looking to expand this out to non-English content. Current Implementation; All generic English language content hosted on the main domain, with x5 English language content variations (locales) available under a folder structure (.com/en-us/ etc.). Alternative markup is in place for all locales within the HTML, implemented automatically by developers via the CMS. Locale folders geo-targeted via GWT and Bing WT. Planned Launch; Introduction of 5 new non-English locale folders (e.g. /de-de/ etc.), targeted to their respective country and language. Content language will be mixed, with around 1/10 of pages translated and the other 9/10 of pages (business listings) having their body content remain in English, with headers / footers translated. Locale folders will be geo-targeted via GWT and Bing WT. Folder and markup usage TBC. Options; Folders; Implement folder structure /de/, attempting to indicate country but not language (issue; usually a single identifier indicates language, not country?). Implement /de-de/ folder structure to match the English locales and maintain correct country targeting (issue; some content is not in language). Alternative markup; Do not make use of markup at all. Implement CMS based automated markup on all English and non-English content throughout the locale (e.g. /de-de/), but exclude English language versions (e.g. /en-gb/). Attempt manually implementing markup to bridge the English and non-English locales, potentially creating future issues with new content going live and content being removed. A heavy risk. Current approach is webmaster tools targeting, a /de-de/ folder structure and automated implementation of markup. This means English language URLs will have markup and non-English language URLs will have markup, but they will not match up (e.g. English pages will never have markup for non-English language content). If you minds haven't melted, what's your thoughts? Any help is much appreciated.
Intermediate & Advanced SEO | | HelloAlba0 -
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.
Intermediate & Advanced SEO | | TheEspresseo0 -
Using rel=alternate hreflang element on ccTLDs
We have multilingual websites with some content variations but 60% of the content on site remains the same. Is it still advisable to use:rel=alternate hreflang option on ccTLDs when ccTLDs are in itself strong signal for Google to display result in respective countries 1. example.com 2. example.co.uk 3. example.co.jp 4. example.de
Intermediate & Advanced SEO | | CyrilWilson0 -
What is the best canonical url to use for a product page?
I just helped a client redesign and launch a new website for their organic skin care company (www.hylunia.com). The site is built in Magento which by default creates MANY urls for each product. Which of these two do you think would be the best to use as the canonical version? http://www.hylunia.com/pure-hyaluronic-acid-solution
Intermediate & Advanced SEO | | danielmoss
or http://www.hylunia.com/products/face-care/facial-moisturizers/pure-hyaluronic-acid-solution ? I'm leaning on the latter, because it makes sense to me to have the breadcrumbs match the url string, and also it seems having more keywords in the url would help. However, it's obviously a very long url, and there might be some benefits to using the shorter version that I'm not aware of. Thanks in advance for sharing your thoughts. Best, Daniel0 -
No index, follow vs. canonical url
We have a site that consists almost entirely as a directory of videos. Example here: http://realtree.tv/channels/realtreeoutdoorsclassics We're trying to figure out the best way to handle pagination and utility features such as sort for most recent, most viewed, etc. We've been reading countless articles on this topic, but so far have been unable to determine what might be considered the industry standard. Two solutions seem to stand out... Using the canonical url on all the sorted and paginated pages. However, after reading many blog posts, it seems that you should NEVER use the canonical url to solve the issue of paginated, and thus duplicated content because the search bots will never crawl past the first page leaving many results not in the index. (We are considering ruling this method out.) Another solution seems to be using the meta tag for noindex, follow so that a search engine like Google will crawl your directory pages but not add them to the index themselves. All links are followed so content is crawled and any passing link juice remains unchanged. However, I did see a few articles skeptical of this solution as well saying that there are always better alternatives, or that there is no verification that search engines obey this meta tag. This has placed some doubt in our minds. I was hoping to get some expert advice on these methods as it would pertain to our site. Thank you.
Intermediate & Advanced SEO | | grayloon0