Serve your site from a subdomain, using Google Domains

4 minute read

Hosting your site under a custom domain is a great option to make your project look more polished. This post will outline the steps to set up your project under a subdomain, using Google Domains.

In the example we will be using, our goal is to switch hosting from to If you are looking for instructions on hosting at your root website, including the www subdomain, then take a look at this post.

Starting Point

If you don’t already have a site setup, you can follow this tutorial to setup a Blazor WebAssembly site. That’s where I started, but you should be able to follow this tutorial no matter what framework you are using for your site.

You should be starting with a site at [username][projectName]


At this point, you probably have a subdomain name selected. If you don’t, standard URL naming rules apply, and the actual name deserves some consideration. I prefer legibility over brevity, but its a personal choice. What is important to know, is that you can only configure a subdomain once. What that means, is that if you have multiple projects, you couldn’t plan to host them all under a subdomain like this apps.[site].com/[project] with each project hosting on a different project. On the other hand, something like [project].apps.[site].com should be ok, though I wouldn’t add the extra complexity to the URL without reason.

To get everything configured, start by going to and selecting the DNS page.

Next, we are going to add a CNAME to the Custom resource records section. If you haven’t heard the term CNAME before, it is short for Canonical Name, which means this is the name of record for your site. The actual hosting location is effectively an implementation detail which your users and search engines don’t need to be concerned with. For a CNAME record, the left entry is your subdomain, and the right is the domain where the site is actually being hosted. Note, that the domain is does not include the project name any more. We specify only [username] as the domain name.

If you noticed that the Syntetic Records section allows configuration of subdomain forwarding, I want to confirm that you don’t need to touch that section.

After you click Add, if you see an extra period after the domain name, it isn’t a problem.

Next, we open the settings in our GitHub project.

Scroll to the GitHub Pages section and enter the custom domain, using the same subdomain configured in google. NOTE, we can’t turn on https yet, because it will take about a day for GitHub to have a Let’s Encrypt certificate issued for your custom domain.

2021 Edit. Looks like the certificates get issued much faster now, so you may not need to wait very long.

Saving the custom domain has created a CNAME file, in the branch and folder you configured for GitHub Pages hosting.

At this point, Google and GitHub are in agreement that GitHub is serving your project at the subdomain you configured. In my experience, this change went into effect pretty quickly.

You may have another step to get your site showing up at the new address if you initially had it running at GitHub Pages. During your initial setup, you may have had to configure the base href for you project so it was not / but /[projectname]. This is no longer needed. In my case, I was using a GitHub Action step to set up the href (from the Blazor tutorial mentioned above). Removing this was my last step to getting this project to show up at

Don’t Forget to return tomorrow to enable https. This is very important. Browsers and search engines may penalize your site for being unencrypted. It could be marked as unsafe or may be ranked lower in search results.

Final State

Your site should now be hosted, with https, at your new subdomain. Happily though, the old URL is still going to work.

  • You can direct all traffic to the subdomain.
  • Any existing links which pointed to the page directly on will continue to work just fine.


Leave a Comment

Your email address will not be published. Required fields are marked *