Perplexed by last MOZ crawling duplicate content errors

[max.favilli]

In the last crawler issues report from MOZ I can see many many pages listed as duplicate content with 0 duplicate urls.

Like this: http://imgur.com/fbikRVq

I am puzzled, what does it mean?

[MansfieldMarketing]

We had the same concern and asked MOZ support this question: Why are we getting duplicate content warnings for pages that are clearly different?

We received the response below. Our takeaway is that we will continue to take these warning into consideration, but apply our own expertise to determine if action is needed.

Response from support: Thanks for reaching out, and sorry for the confusion! Duplicate content is always kind of a tricky issue. While you or I can qualitatively determine that there are differences between these pages, crawlers are dependent on more quantitative means to determine duplicate content. When they view the pages, one part of the process is to examine the similarity of the pages' code and look for close matches to determine duplicates; this appears to be the issue here. I stuck these URLs into a similar page checker (http://www.webconfs.com/similar-page-checker.php), and it indicated that there was quite a high degree of similarity.

[max.favilli]

But was your report showing the list of url considered duplicate of that url?

In my case on the right I have the duplicate url, but on the left (where the list of other url the crawler consider duplicate should be) there's written 0 page duplicate, and the list is empty.

I am aware even if two pages looks different to me could be considered duplicate by rogerbot, but in the past it was always showing the number of duplicate pages found and the list of duplicate url.

[MansfieldMarketing]

We have not had that happen. All the "Duplicate Content" items list a number of duplicates that's > 0.

It is possible that Moz is buggy.

[jameskais]

Hi Max and Doug - this is currently being recognized as a bug and we have it currently being worked on as we speak. Sorry for the confusion in the short term!

[max.favilli]

Thanks for the answer/update.

[max.favilli]

Even in the last crawl report the bug is still there, any idea when it will be fixed?