Hi everybody,
Sorry for that stupid question but I have issues with english and cant really get something…
I have a website with unique content in all pages. Do I still need to set a global canonical page URL?
Thx
Hi everybody,
Sorry for that stupid question but I have issues with english and cant really get something…
I have a website with unique content in all pages. Do I still need to set a global canonical page URL?
Thx
Hi @ITryMyBest
The following are the Do’s and Don’ts when it comes down to canonical tags
DO’s
Do include a canonical tag on every page, without exception. All pages (including the canonical page) should contain a canonical tag to prevent any possible duplication.
Even if there are no other versions of a page, then that page should still include a canonical tag that links to itself.
Do canonicalize mobile pages to desktop. Use a canonical tag and a rel=”alternate” tag to signal that a mobile version and a desktop version of the same page should be treated as one entity in search results. Google explains more about this in the [Google Developers Mobile Guide] (Mobile-first Indexing Best Practices | Google Search Central | Documentation | Google for Developers).
Do canonicalize paginated pages to consolidate weight
There are two options here. Which option you choose depends on how you want your content to be indexed.
Hosting on both HTTP and HTTPS and canonicalizing to HTTPS means you will maintain your HTTP URLs, but Google will index and direct traffic to your HTTPS pages. You’ll essentially be running one domain on HTTP and another on HTTPS, but Google will only index the HTTPS version.
However, this option means:
While using a 301 redirect to direct Google and users from your alias domain to your primary one is the best option, if you can’t do this for any reason (for example, if you don’t want to redirect users as well) then canonicalizing is imperative.
Having separate web and print versions of the same content can cause duplicate content issues, but a 301 redirect isn’t appropriate as you still want users to be able to stay on the print version. So a canonical tag to show Google which version of the content should be indexed is perfect for this situation.
Be consistent in whether you use a slash or no slash at the end of the URL, and don’t mix your cases: use upper case characters consistently, or don’t use them at all. Similarly, use character codes (ampersands etc) consistently, or don’t use them at all.
Using relative URLs in canonical tags can mean that Google will ignore them. As Google explain in their 5 common mistakes with rel=canonical post, using a relative URL in a canonical tag – for example example.com/cupcake.html – implies that the page you want to be indexed in search results is https://example.com/example.com/cupcake.html, which doesn’t make sense.
Remember that Google sees the HTTP/HTTPS and www/non-www version of a URL as a separate page.
They can be in both if they are the same, but if there is more than one and they are different, both will be ignored. See our guide to canonical tags for more information on how to implement them.
Canonicalizing your international content to one primary version might mean that all users in all regions and using all languages will be shown the same version in search results, no matter what their browser settings are. Canonicalizing a page with hreflang may mean the page cannot be indexed and will not be returned in search results.
Don’t
John Mueller discussed this in a recent Google Webmaster Hangout:
“[For example,] if you have an ecommerce site where you have one page that lists all of your items and from there it links to all your individual product pages, then if we don’t have any other form of navigation to those product pages, and we’re only focusing on the first page of that paginated set, then we might miss links to those individual product pages.
“On the other hand, if you have a normal navigation on the website and you have this long paginated set and you’re only indexing the first page then we’ll still find those individual product pages anyway through the normal navigation. So it kind of depends on your website what you want to achieve.”
Only include canonical URLs in your main Sitemaps. If you want newly-canonicalized URLs to be recrawled so that Google picks up the change quicker, then it’s worth including them in the Sitemap in the short-term (perhaps in a separate Sitemap). However, it’s recommended that you remove them when the change has been indexed to avoid any misreporting of your index counts.
Canonicalizing expired pages isn’t the best option, no matter how you do it. For example:
If the canonical URL returns anything other than a 200 status then Google will probably just ignore the canonical tag. This also reduces crawl efficiency because Google has to follow canonical tags for no reason, wasting crawl time.
There should only ever be one canonical version of the same content. If you canonicalize one page to another canonicalized page, your tags will probably be ignored completely.
The purpose of a canonical tag is to avoid duplicate content issues by indicating when two pages have the same content on URLs that Google sees as separate pages. Google specify that: “A large portion of the duplicate page’s content should be present on the canonical version,” so the canonical page and the canonicalized pages should include the same content.
If the content on the canonical page is significantly different from the content on the canonicalized page, Google might ignore your canonical tags completely.
For reference Check out
Thx for your answer and for that ressource. I really didn’t exept there was so much with the canonical tag
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.