Forum Moderators: mack

Message Too Old, No Replies

Redundant Hostnames

Redundant Hostnames in Google Analytics

         

elvang

10:48 am on Apr 19, 2022 (gmt 0)

Top Contributors Of The Month



Hello everyone,
In Analytics there is a warning like

"Property xxxx xxxxx is receiving data from redundant hostnames. Some of the redundant hostnames are:
example.com
www.example.com
Redundant hostnames are counted as separate rows in reports, so hits that are going to the same page on your site from different hostnames will be split into multiple rows. With data split across multiple rows, traffic to specific pages will appear lower than it actually is.

To avoid this problem, consider setting up a 301 redirect from one of your redundant hostnames to the other, or create a search-and-replace filter that strips "www." from hostnames.

Google Tag Assistant Recordings can help you verify that your redirect is setup correctly, or that your filter is working as intended.

My question is:
1- To avoid this problem where should we do 301 redirect, on hosting or on CMS's admin? (CMS is not wordpress) Or is there any other solution apart from 301 redirect? (our primary domain is www.example.com)

2- Is this warning related to the properties on search console? Because in search console there are two properties:
1- example.com 2-https://www.example.com/ I added the second one to see the robots.txt file long time ago. Now, i dont need it. How can i remove the second one? Because it is not showing any information, i mean, when i click on this property (https://www.example.com/) on search console, it is browsing smt and this browsing never ends.

Thank you.

not2easy

12:31 pm on Apr 19, 2022 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



Google sees example.com and www.example.com as different (but potentially duplicate) domains so it dilutes the 'value' of each. To help complicate things, you can add on the protocol duplicates: http://example.com and http://www.example.com and https://example.com and https://www.example.com and you can see why you should send all of their traffic to one single version of your domain.

Google asks us to add "all" domains (versions of domains) to GSC, not because they will 'all' be indexed but so that you can identify problems such as multiple copies caused by no 301 permanent redirect or by a faulty redirect.

Because your domain is using a CMS, it will depend on how this issue is being managed in that CMS for how to correct it. Usually a domain handles that in its httpd.conf or the domain's root folder with a .htaccess file.

elvang

12:46 pm on Apr 19, 2022 (gmt 0)

Top Contributors Of The Month



Thank you

phranque

9:08 pm on Apr 19, 2022 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



a hostname canonicalization redirect in the server config will solve the "redundant hostnames" problem.