# Make mydomain.com redirect to www.mydomain.com **URL:** \ **Category:** Ask us anything\ **Tags:** dns\ **Created:** [April 3, 2023, 10:42am UTC](https://community.weweb.io/t/make-mydomain-com-redirect-to-www-mydomain-com/2166 "2023-04-03T10:42:57Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![lancelot](https://avatars.discourse-cdn.com/v4/letter/l/cab0a1/32.png) [@lancelot](https://community.weweb.io/u/lancelot)\ **Post date:** [April 3, 2023, 10:42am UTC](https://community.weweb.io/t/make-mydomain-com-redirect-to-www-mydomain-com/2166/1 "2023-04-03T10:42:57Z")
Hi, Currently I am using WeWeb on a custom domain and it works fine, except that I have to always put “www.” before the domain: [https://www.mydomain.com](https://www.mydomain.com) works but [https://mydomain.com](https://mydomain.com) doesn’t. How do I configure my DNS settings in Google Domains in order to make the non “www” url redirect to the “www.” ? It is easily doable on Webflow but I can’t find a way to do it on WeWeb. Thanks in advance 🙂 Lancelot ---
**Author:** ![Marc](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/marc/32/30_2.png) [@Marc](https://community.weweb.io/u/Marc)\ **Post date:** [April 4, 2023, 10:01am UTC](https://community.weweb.io/t/make-mydomain-com-redirect-to-www-mydomain-com/2166/2 "2023-04-04T10:01:24Z")
Hi @lancelot, WeWeb does not offert this option. If you when your naked domain to redirect to the “www” domain, you can try what is described here : [https://support.google.com/sites/thread/141806277/how-to-redirect-naked-domain-to-www-subdomain?hl=en](https://support.google.com/sites/thread/141806277/how-to-redirect-naked-domain-to-www-subdomain?hl=en) I did not test this because I don’t have a Google Domain account. Each domain name provider will have a different way to handle this use case. ---
**Author:** ![brandon](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/brandon/32/2804_2.png) [@brandon](https://community.weweb.io/u/brandon)\ **Post date:** [July 11, 2023, 12:53am UTC](https://community.weweb.io/t/make-mydomain-com-redirect-to-www-mydomain-com/2166/3 "2023-07-11T00:53:09Z")
> [@Marc](#): > > WeWeb does not offert this option. I just migrated my Bubble site over to WeWeb and am now realizing what a huge headache this is causing. All of the links I have created around the web have pointed to the non-www version of my domain using a secure protocol (https). Since WeWeb doesn’t allow me to secure the non-www version of my domain, if anybody clicks on an existing link of that version, it will go to a dead page and there is nothing I can do about it. So it’s forcing me to try and manually update as many links as I can, which is a lot of links! Really really hope WeWeb can offer a solution to this sooner than later! ---
**Author:** ![raydeck](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/raydeck/32/384_2.png) [@raydeck](https://community.weweb.io/u/raydeck)\ **Post date:** [July 11, 2023, 2:30am UTC](https://community.weweb.io/t/make-mydomain-com-redirect-to-www-mydomain-com/2166/4 "2023-07-11T02:30:23Z")
What are you using for your DNS registry? There’s an option here to stand up a server for the sole purpose of 301-redirecting all traffic from the base URL to the www one. Google domains for example seems to support that out of the box, but others might vary. ---
**Author:** ![brandon](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/brandon/32/2804_2.png) [@brandon](https://community.weweb.io/u/brandon)\ **Post date:** [July 11, 2023, 4:12am UTC](https://community.weweb.io/t/make-mydomain-com-redirect-to-www-mydomain-com/2166/5 "2023-07-11T04:12:09Z")
Oh that’s interesting! I’m using Namecheap for all of this. Currently have the www and the SSL CNAME records (as WeWeb instructs) setup and then, based on what I’ve read, I’ve got a URL Redirect Record setup as follows: ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/c/c10e51d5b72f894cf7cac61e1e39dd8d44b921cf.png) It seemed with Bubble the redirect was handled not at the DNS level, but on the server level so I was able to simply point records for the @ and www and both were taken care of SSL wise. So right now [http://techaudit.tv](http://techaudit.tv) redirects just fine to [https://techaudit.tv](https://techaudit.tv) but if I try the secure non-www ([https://techaudit.tv](https://techaudit.tv)) you can see that it goes nowhere. ---
**Author:** ![raydeck](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/raydeck/32/384_2.png) [@raydeck](https://community.weweb.io/u/raydeck)\ **Post date:** [July 12, 2023, 1:27pm UTC](https://community.weweb.io/t/make-mydomain-com-redirect-to-www-mydomain-com/2166/6 "2023-07-12T13:27:54Z")
I wonder if you can work it with an ANAME record. Looks like namecheap might support it? [https://www.namecheap.com/support/knowledgebase/article.aspx/10128/2237/how-to-create-an-alias-record/#:~:text=An%20ALIAS%20record%20](https://www.namecheap.com/support/knowledgebase/article.aspx/10128/2237/how-to-create-an-alias-record/#:~:text=An%20ALIAS%20record%20)(also%20known,other%20records%20on%20that%20name. ---
**Author:** ![petyaaa6](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/petyaaa6/32/2678_2.png) [@petyaaa6](https://community.weweb.io/u/petyaaa6)\ **Post date:** [August 2, 2023, 5:34pm UTC](https://community.weweb.io/t/make-mydomain-com-redirect-to-www-mydomain-com/2166/7 "2023-08-02T17:34:15Z")
Hi Brandon! Any chance you found a solution for this? ---
**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\ **Post date:** [August 21, 2023, 8:41am UTC](https://community.weweb.io/t/make-mydomain-com-redirect-to-www-mydomain-com/2166/8 "2023-08-21T08:41:41Z")
Hi @petyaaa6 👋 Yes, he did and shared the solution here: [TUTORIAL – How to link a custom domain to a WeWeb app - #26 by brandon](https://community.weweb.io/t/tutorial-how-to-link-a-custom-domain-to-a-weweb-app/214/26) I’ll be updating the user docs and recording a video tutorial this week so it’s easier for everyone to find the information in the future! ---
**Author:** ![what.gift](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/what.gift/32/8069_2.png) [@what.gift](https://community.weweb.io/u/what.gift)\ **Post date:** [October 2, 2024, 6:24pm UTC](https://community.weweb.io/t/make-mydomain-com-redirect-to-www-mydomain-com/2166/9 "2024-10-02T18:24:32Z")
I think I’m going mad! Somethings changed. I hadn’t got round to setting up the Cloudflare redirect yet as discussed here, but was about to. However, the redirect is _now_ happening… _by itself_. Has either WeWeb or GoDaddy made some sort of change to facilitate this does anyone know? I did recently enable languages and now my domain is now 301 redirected to the langauge version **/en/**. Perhaps that’s it and changed something, but it’s really odd it’s now forwarding from [what.gift](https://what.gift) to [https://www.what.gift/en/](https://www.what.gift/en/) as it wasn’t working like this a few weeks ago and I’ve not changed any other settings. I’m only asking, as I now don’t know whether I actually need to setup Cloudflare. I don’t like not knowing how something works. ---
**Author:** ![Matto](https://avatars.discourse-cdn.com/v4/letter/m/67e7ee/32.png) [@Matto](https://community.weweb.io/u/Matto)\ **Post date:** [October 3, 2024, 4:22am UTC](https://community.weweb.io/t/make-mydomain-com-redirect-to-www-mydomain-com/2166/10 "2024-10-03T04:22:01Z")
I haven’t done the hack to work around this issue but wanted to note it hasn’t automatically been fixed for me - still won’t find the site without the www.