Anyone else see a redundant hostnames message in GA this morning?

[Sika22]

Message reads as follows:

Property sqlsentry.com is receiving data from redundant hostnames. Consider setting up a 301 redirect on your website, or make a search and replace filter that strips "www." from hostnames. Examples of redundant hostnames: sqlsentry.com, www.sqlsentry.com.

We have had our preferred domain set to www for months and I've never seen this error before today.  A quick search shows others getting this as well.  I did notice our 301 is no longer working so I am going to set that back and see what happens.

[Bryan_Loconto]

Interesting... I'm not getting this message on any properties in our account. But thank you I will keep an eye out in case something pops up on us!

I wonder why your 301 would no longer be working though...

Is there anything you can remember that was done that could have caused that? Was your htaccess file modified without your knowledge?

Kind of troubling I'd say. Set that back and see if that message clears up for you!

[Sika22]

Unfortunately I have no way of knowing what the developers do so they could have modified it.  I've asked that it be righted.  Thanks!

[Bryan_Loconto]

Eww that's scary!

Is this your site or a clients site that you are working on? If an outside developer or team of devs are working on a project that you own or one that is for a client of yours, I would request that you are consulted prior to any changes like that.

Less hands in the cookie jar the better as you know. However, I know that isn't always the scenario but if a cookie gets a bite taken from it, I'd like to know who did it and when they did it at the very least.

I hope fixing the 301 clears up the issue you are having in GA!

[Sika22]

I actually just work for this company and have shifted from a support role into an SEO role.  I agree about less hands in the cookie jar but as you said, it doesn't always work that way

[shendison]

Saw this recently on a site with a WordPress installation added in a subdirectory. The root domain was set up with the www but /blog was not...

[Sika22]

Thanks.  We made sure a 301 redirect is in place but the error is still there.  It's been days now.  I'm not sure what else to do.