"What": What is your idea?

Landed on a ticket of a user that wanted to add www to their domain. They are a developer and they said that the www is better. The said:

But regarding the canonical version being www vs naked domain, I believe Wordpress has made a suboptimal choice, as the vast majority of websites I see include the www for their canonical version, and they have the naked domain redirect to www instead of the reverse. Here's hard evidence supporting this: https://www.bjornjohansen.com/www-or-not

The believe the www version is more common and standard.

"Why?": Why would this be impactful?

Although it could be problematic for SEO reasons and for users creating duplicated URLs, for those that prefer it it would be a good option to be able to add it after doing some changes on their site, as a WordPress.org site lets you do that. The user also shared the following:

As the article above shares, there is a problem with cookies. Cookies set from a hostname, will also be sent to all subdomains. I.e. if the website on “example.com” sets a cookie, the browser will also send this cookie when visiting “www.example.com”. So suddenly I'm stuck with all the wordpress cookies being visible to the rest of my subdomain services which is not ideal. As the article shares, unnecessary cookies hurts performance, and being forced to use the naked domain as the default causes a burden.

I suppose it's a matter of preference, but it's good to have the option. We told this user we would create a feature request for this. duplicate URLs, for those that prefer it, it would be a good option to be able to add it after making

"How?" How should this feature work?

To avoid problems with SEO we could let the user do the process using SSH, for example.