epeeme
commented
5 years ago Added appropriate lines to .htaccess and tested;
>>> http://www.epee.me
> --------------------------------------------
> 301 Moved Permanently
> --------------------------------------------
Status: 301 Moved Permanently
Code: 301
Connection: close
Content-Type: text/html
Content-Length: 705
Date: Mon, 11 Nov 2019 08:44:51 GMT
Server: LiteSpeed
Location: https://epee.me/
>>> https://epee.me/
> --------------------------------------------
> 200 OK
> --------------------------------------------
Status: 200 OK
Code: 200
Connection: close
X-Powered-By: PHP/5.6.40
Content-Type: text/html; charset=UTF-8
Date: Mon, 11 Nov 2019 08:44:51 GMT
Server: LiteSpeed
Alt-Svc: quic=":443"; ma=2592000; v="39,43,46", h3-Q039=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-23=":443"; ma=2592000
`
via Google Analytics
First detected: 30-Oct-2019 08:13:28
Property epee.me is receiving data from redundant hostnames. Some of the redundant hostnames are:
epee.me
www.epee.me
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 set up correctly, or that your filter is working as intended.