Tuesday, March 26, 2019

Should we use a 301 or a canonical tag in this use case? Need advice!

So we have a very specific use case I'd like extra opinions on... We had a second domain that hosted blogs for a company we acquired and we have just migrated all of that content to our main domain. There was a blog from 6 months ago that was an announcement for a new report which was published to both domains. When the consolidation happened, it triggered a duplicate content warning. In this instance, would you have unpublished the recently migrated version and done a 301 permanent redirect? Or would you have placed a rel=canonical tag?

I'd asked for a 301, but the team put in a canonical tag and it's still showing up in some of my crawl errors (ex. no H1 for the core post that has been on our site, not the migrated one, but it only triggered as an error after the canonical tag was put in place). I also still see it as a poor user experience in the fact that it's showing both duplicate posts on internal search on our website, and it's muddying our Google analytics for the success of that post. But I could be totally wrong on this one, I'm not sure.

What would you do in this case and why? Is the canonical the best solution? Should I be concerned about the crawl errors it's still triggering?

submitted by /u/hersheykm
[link] [comments]

from Search Engine Optimization: The Latest SEO News https://www.reddit.com/r/SEO/comments/b5x78v/should_we_use_a_301_or_a_canonical_tag_in_this/>

No comments:

Post a Comment