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!
Founder & CEO at Schleicher Marketing
Technical SEO, eCommerce, CRO/UX Design, Migrations, Shopify+, Digital Strategy
Entrepreneur In Residence at StartupSD.org -
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
-
Ranking dropped after changing title tag
I recently changed my company's site homepage title tag to make it start with our target keyword. The page was originally at page #7 or #8 and dropped to page #17 directly after I changed the page title. Is this normal? Is it's a temporary drop or should I change it back to the previous title.
Intermediate & Advanced SEO | | ForumOne0 -
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 -
Google Ignoring Canonical Tag for Hundreds of Sites
Bazaar Voice provides a pretty easy-to-use product review solution for websites (especially sites on Magento): https://www.magentocommerce.com/magento-connect/bazaarvoice-conversations-1.html If your product has over a certain number of reviews/questions, the plugin cuts off the number of reviews/questions that appear on the page. To see the reviews/questions that are cut off, you have to click the plugin's next or back function. The next/back buttons' URLs have a parameter of "bvstate....." I have noticed Google is indexing this "bvstate..." URL for hundreds of sites, even with the proper rel canonical tag in place. Here is an example with Microsoft: http://webcache.googleusercontent.com/search?q=cache:zcxT7MRHHREJ:www.microsoftstore.com/store/msusa/en_US/pdp/Surface-Book/productID.325716000%3Fbvstate%3Dpg:8/ct:r+&cd=2&hl=en&ct=clnk&gl=us My website is seeing hundreds of these "bvstate" urls being indexed even though we have a proper rel canonical tag in place. It seems that Google is ignoring the canonical tag. In Webmaster Console, the main source of my duplicate titles/metas in the HTML improvements section is the "bvstate" URLs. I don't necessarily want to block "bvstate" in the robots.txt as it will prohibit Google from seeing the reviews that were cutoff. Same response for prohibiting Google from crawling "bvstate" in Paramters section of Webmaster Console. Should I just keep my fingers crossed that Google honors the rel canonical tag? Home Depot is another site that has this same issue: http://webcache.googleusercontent.com/search?q=cache:k0MBLFcu2PoJ:www.homedepot.com/p/DUROCK-Next-Gen-1-2-in-x-3-ft-x-5-ft-Cement-Board-172965/202263276%23!bvstate%3Dct:r/pg:2/st:p/id:202263276+&cd=1&hl=en&ct=clnk&gl=us
Intermediate & Advanced SEO | | redgatst1 -
Best Practices for Homepage Title Tag
Hi, I would like to know if there is any update about the best practices for the homepage title tag. I mean, a couple of years ago, it was still working placing main keywords in the homepage title tag. But since the last google SERP update, the number of characters that are being shown were reduced, and now we try to work with 55 and 56 characters. That has reduced our capacity of including many keywords on the title tag. Besides, search engines are smarter now to choose the correct inner page to show in SERP. But I am wondering if the Homepage Title should have a branded orientation or should include main keywords, cause it is still working that strategy. I would appreciatte any update in this issue. Thank you!
Intermediate & Advanced SEO | | teconsite0 -
Is a 301 Redirect and a Canonical Tag on Uppercase to Lowercase Pages Correct?
We have a medium size site that lost more than 50% of its traffic in July 2013 just before the Panda rollout. After working with a SEO agency, we were advised to clean up various items, one of them being that the 10k+ urls were all mixed case (i.e. www.example.com/Blue-Widget). A 301 redirect was set up thereafter forcing all these urls to go to a lowercase version (i.e. www.example.com/blue-widget). In addition, there was a canonical tag placed on all of these pages in case any parameters or other characters were incorporated into a url. I thought this was a good set up, but when running a SEO audit through a third party tool, it shows me the massive amount of 301 redirects. And, now I wonder if there should only be a canonical without the redirect or if its okay to have tens of thousands 301 redirects on the site. We have not recovered yet from the traffic loss yet and we are wondering if its really more of a technical problem than a Google penalty. Guidance and advise from those experienced in the industry is appreciated.
Intermediate & Advanced SEO | | ABK7170 -
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 -
Wildcard Redirects & Canonical Tags
I have an interesting situation. Current URLs Example1: www.domain.com/red-widgets-cid-1234.html
Intermediate & Advanced SEO | | NakulGoyal
www.domain.com/red-widgets-cid-1234-1.html
www.domain.com/red-widgets-cid-1234-1-1.html Canonical on All Above URLs:
www.domain.com/red-widgets-cid-1234.html New URL:
www.domain.com/red-widgets-cid-4567.html Current URLs Example2: www.domain.com/red-widgets-cid-1234+10.html
www.domain.com/red-widgets-cid-1234+10-1.html
www.domain.com/red-widgets-cid-1234+10-1-1.html Canonical on All Above URLs:
www.domain.com/red-widgets-cid-1234+10.html New URL:
www.domain.com/red-widgets-cid-6789.html Current URLs Example3: www.domain.com/red-widgets-cid-1234+10+5.html
www.domain.com/red-widgets-cid-1234+10+5-1.html
www.domain.com/red-widgets-cid-1234+10+5-1-1.html Canonical on All Above URLs:
www.domain.com/red-widgets-cid-1234+10+5.html New URL:
www.domain.com/american-red-widgets-cid-6789+5.html I want to make sure all variations of the above URL redirect to the new URLs. However, as you see in Example 3, we are dealing with variables that are passed on. (+5 in this case). Question 1: What wildcard 301 redirect / regular expression can I use to tackle these ? Question 2: If we redirect www.domain.com/red-widgets-cid-1234+10+5.html to www.domain.com/red-widgets-cid-6789+5.html and www.domain.com/red-widgets-cid-6789+5.html contains the canonical tag www.domain.com/american-red-widgets-cid-6789+5.html, any concerns or red flags here ?0 -
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