Timeline for Going multisite with www prefix
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 31, 2017 at 10:08 | vote | accept | Lucio Crusca | ||
| Mar 31, 2017 at 10:09 | |||||
| Oct 25, 2016 at 15:19 | answer | added | Christopher Corrales | timeline score: 0 | |
| Oct 13, 2016 at 6:24 | comment | added | Lucio Crusca | My customer, who believed to be a SEO expert, was wrong. There's a setting in the Google console that allows you to tell Google the domain name has changed. Then we ended up removing the www, but our solution does not answer my question (what problems could arise otherwise?). | |
| Sep 29, 2016 at 14:29 | comment | added | Lucio Crusca | I'm no SEO expert either, but my customer, who is very much into SEO, is sure that such a change disrupts the pagerank because Google sees duplicate content and that it takes months before it settles down and rebuilds the same pagerank. Months with lower pagerank, in my customer's language, means lots of money loss. | |
| Sep 29, 2016 at 14:24 | history | edited | Lucio Crusca | CC BY-SA 3.0 |
deleted 2 characters in body
|
| Sep 29, 2016 at 12:56 | comment | added | C C | I hit this too, but unfortunately don't remember the exact issue it caused -- but there was an issue and I remember thinking "wow they were not kidding about this". I ended up using AWS Route53 as a custom DNS and pointer from www to the non-www domain. Alternatively I believe you can achieve what you want with a rewrite rule added to .htaccess (to point www.example.com to example.com). Finally, I'm no SEO expert but I'm surprised to hear that a simple change from www to non-www would make Google cough up a hairball. | |
| Sep 29, 2016 at 9:39 | history | edited | Lucio Crusca | CC BY-SA 3.0 |
added 1 character in body
|
| Sep 29, 2016 at 8:19 | history | asked | Lucio Crusca | CC BY-SA 3.0 |