Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Duplicate Title tags even with rel=canonical
-
Hello,
We were having duplicate content in our blog (a replica of each post automatically was done by the CMS), until we recently implemented a rel=canonical tag to all the duplicate posts (some 5 weeks ago).
So far, no duplicate content were been found, but we are still getting duplicate title tags, though the rel=canonical is present.
Any idea why is this the case and what can we do to solve it?
Thanks in advance for your help.
Tej Luchmun
-
Has this ever been done? Would be very handy.
-
Hi Sean,
Thanks a lot for your reply.
Indeed having the rel=canonical pointing to the wrong page would be another issue. What David Lee suggested me is using the rel=canonical on both the original post and the duplicate post. This can be set programmatically instead of the ignore button.
But surely, the ignore button would be much more easier, in some situations. Please keep us update once this ignore feature has been implement.
Thanks again for your help.
Tej Luchmun
-
Hi Sheena,
Yes, Moz Crawl Diagnostics Report is showing duplicate title tag for the content that already have a rel=canonical tag.
I contacted them, and they suggested that i should include the canonical tag on the duplicate and original post, where both tags are pointing to the original post.
I have not yet tested it out, but hopefully, this should solve the issue.
Thanks again for your help.
Tej Luchmun
-
Thanks a lot Karl, indeed with the canonical tag, neither the title nor the content becomes a duplicate.
It's just the MOZ crawl issue that raised the alarm.
Thanks again.
Tej Luchmun
-
Hi Tej,
Thanks for writing us on this! So Sheena and Karl are both correct. Although, an REL Canonical may solve the issue with Google it is still technically a duplicate title tag. When designing the tool we found that having the crawler pick up the REL Canonicals can be problematic for a coding and SEO standpoint. It is often possible that an REL Canonical will be directed to an incorrect page and since our crawler is so literal it would have issues recognizing the canonical was bad.
Our product staff is aware of this and they hope to get to a place where we provide an ignore feature, so if you feel that the tag was implemented correctly you can select ignore and we will no longer report that issue for that page.
I know that this is not ideal for many customers, but hopefully our solution will be comprehensive enough to encapsulate many of the solutions SEO's have found for these issues.
Hopefully this helps and if you have any other questions or concerns let me know.
Have a great day!
-
Do you mean that your Moz Analytics Crawl Diagnostics Report is showing duplicate titles for pages that have rel=canonical? If so, this is something I noticed a few months ago & brought up to the Moz team. I believe it's something they're working to implement/somehow allow us to 'check off' pages in the report that we've already implemented a solution for. Also, if this is your situation, I think you should add your experience / request to Moz's feature request forum.
I hope this helps!
-
Technically it is still a duplicate title tag, you just won't be getting penalised for it that's all.
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
-
Hreflang and canonical tag for new country specific website - different base domain
I have a little different situation compared to most other questions which asks for hreflang and canonical tags for country specific version of websites. This is an SEO related question and I was hoping to get some insight on your recommendations. We have an existing Australian website - say - ausnight.com.au now we want to launch a UK version of this website - the domain is - uknight.co.uk please note, we are not only changing from .com.au to .co.uk.... but the base domain name as well changed - from ausnight to uknight as you can understand, the audience for both websites is different. Both websites has most pages same with same contents.... the questions I have is - Should we put canonical tag on the new website pages? If we don't put canon tag on new website pages, what is the impact on the SEO ranking of current website? I believe we need to put hreflang tag on both websites to tell google that we have another language version (en-au vs en-gb) of the same page. Is this correct?
Intermediate & Advanced SEO | | TinoSharp0 -
Title tag: Long tail words or keyword dilution?
Hi all, I am a newbie to SEO. Lately, I have been struggling to optimize my title tag. Ones say that we should have long tail words in title tags because long tail words improve click through rate and generate quality leads. On the other hand, ones say that putting other words in the title tag will dilute the main keyword that my page ranks for. Do keywords really dilute each other in the title tags? I am really confused. Let me give this an example: Web Design Services | Company Name Web Design Services with Conversion Focused | Company Name Which one would you prefer and why? Thank you. 😄 Best, Raymond
Intermediate & Advanced SEO | | Raymondlee0 -
Switching from HTTP to HTTPS: 301 redirect or keep both & rel canonical?
Hey Mozzers, I'll be moving several sites from HTTP to HTTPS in the coming weeks (same brand, multiple ccTLDs). We'll start on a low traffic site and test it for 2-4 weeks to see the impact before rolling out across all 8 sites. Ideally, I'd like to simply 301 redirect the HTTP version page to the HTTPS version of the page (to get that potential SEO rankings boost). However, I'm concerned about the potential drop in rankings, links and traffic. I'm thinking of alternative ways and so instead of the 301 redirect approach, I would keep both sites live and accessible, and then add rel canonical on the HTTPS pages to point towards HTTP so that Google keeps the current pages/ links/ indexed as they are today (in this case, HTTPS is more UX than for SEO). Has anyone tried the rel canonical approach, and if so, what were the results? Do you recommend it? Also, for those who have implemented HTTPS, how long did it take for Google to index those pages over the older HTTP pages?
Intermediate & Advanced SEO | | Steven_Macdonald0 -
When is it recommended to use a self referencing rel "canonical"?
In what type of a situation is it the best type of practice to use a self referencing rel "canonical" tag? Are there particular practices to be cautious of when using a self referencing rel "canonical" tag? I see this practice used mainly with larger websites but I can't find any information that really explains when is a good time to make use of this practice for SEO purposes. Appreciate all feedback. Thank you in advance.
Intermediate & Advanced SEO | | SEO_Promenade0 -
Best way to implement canonical tags on an ecommerce site with many filter options?
What would be the best way to add canonical tags to an ecommerce site with many filter options, for example, http://teacherexpress.scholastic.com? Should I include a canonical tag for all filter options under a category even though the pages don't have the same content? Thanks for reading!
Intermediate & Advanced SEO | | DA20130 -
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 -
Rel=canonical tag on original page?
Afternoon All,
Intermediate & Advanced SEO | | Jellyfish-Agency
We are using Concrete5 as our CMS system, we are due to change but for the moment we have to play with what we have got. Part of the C5 system allows us to attribute our main page into other categories, via a page alaiser add-on. But what it also does is create several url paths and duplicate pages depending on how many times we take the original page and reference it in other categories. We have tried C5 canonical/SEO add-on's but they all seem to fall short. We have tried to address this issue in the most efficient way possible by using the rel=canonical tag. The only issue is the limitations of our cms system. We add the canonical tag to the original page header and this will automatically place this tag on all the duplicate pages and in turn fix the problem of duplicate content. The only problem is the canonical tag is on the original page as well, but it is referencing itself, effectively creating a tagging circle. Does anyone foresee a problem with the canonical tag being on the original page but in turn referencing itself? What we have done is try to simplify our duplicate content issues. We have over 2500 duplicate page issues because of this aliasing add-on and want to automate the canonical tag addition, rather than go to each individual page and manually add this tag, so the original reference page can remain the original. We have implemented this tag on one page at the moment with 9 duplicate pages/url's and are monitoring, but was curious if people had experienced this before or had any thoughts?0