Welcome to the Q&A Forum

Jim's comment is spot on! Definitely focusing on those things is of top importance since many times the organic play can push past the local one.

Something that might be helpful when it is time to clean up NAP is a YEXT package (if you don't already have one). The highest package is $499 per year, but definitely worth the hassle of trying to handle a good chunk of your citations across some of the main local sites. You can easily update the NAP in one place, then it will populate to all the directories in your particular package.

Here is a list of the directories in their network: http://www.yext.com/network/publisher-network

As a side note, one place you might be sure the NAP info is updated and that is not in the YEXT publisher network is YellowPages.com (YP).

I would also sign up for Moz Local ($49 per year) since they have a connection directly with the main data aggregators.

Best of luck!

I'd say before you utilize the canonical element It might be worth the dev time to choose one or the other and have the CMS configured to either drop the '/content/' in the urls or just stop creating the versions without '/content/'.

I'm sure you've already considered that, I'm just saying that is the way I'd go. Remember, the canonical element is just a suggestion so won't guarantee the results you are after. Better to just address it in the CMS or stop creating the duplicates. Good luck!

Even if the penalty doesn't seem to be affecting things right now, I would definitely go through the "sustained effort" Matt talks about in the video and start contacting the webmasters to have them removed. Matt also mentioned that "we might take action on some of those anchors." Have you seen traffic to any individual pages that have these links pointing to them decrease at all? What if in a future update these links to start to affect traffic.

Even though overall traffic seems to be OK now, I'd say better safe than sorry, go through the effort to get those links removed and do the reconsideration request. That way, they won't become an issue in the future.

I'd say before you utilize the canonical element It might be worth the dev time to choose one or the other and have the CMS configured to either drop the '/content/' in the urls or just stop creating the versions without '/content/'.

I'm sure you've already considered that, I'm just saying that is the way I'd go. Remember, the canonical element is just a suggestion so won't guarantee the results you are after. Better to just address it in the CMS or stop creating the duplicates. Good luck!