filipino-talent.com
Final step

Connect your subdomain

Your subdomain is published, but that is only half the job. DNS tells the internet where to look; your host also has to agree to answer for your new address. Until you do this, opening https://yourname.filipino-talent.com shows an error (Cloudflare Pages shows 522 Connection timed out; others show a 404 or a host error page).

Pick the host where your portfolio lives and follow the steps. It takes about a minute.

GitHub Pages
username.github.io
Go to steps →
 Cloudflare Pages
project.pages.dev
Go to steps →
 Vercel
project.vercel.app
Go to steps →
 Netlify
site.netlify.app
Go to steps →
Using Wix, Canva, WordPress, or another builder? This service only connects hosts that let you attach a custom domain for free through a plain CNAME. Wix needs a paid plan and its own DNS records, so it is not supported here. Move your page to GitHub Pages, Cloudflare Pages, Vercel, or Netlify — all free — then come back to this page.

GitHub Pages

  1. Open your repository, then go to Settings → Pages.
  2. Under Custom domain, type yourname.filipino-talent.com and click Save. GitHub adds a CNAME file to your repository.
  3. Wait a few minutes. GitHub runs a DNS check and shows a green checkmark when it finds the record we published.
  4. Once it passes, tick Enforce HTTPS. The certificate can take up to an hour the first time.
Notes: one custom domain per Pages site. For a project site (username.github.io/reponame), the subdomain still routes to that repository. Do not add the CNAME file before we publish DNS — it is already published by the time you reach this step.

Cloudflare Pages

  1. Open your Pages project in the Cloudflare dashboard.
  2. Go to Custom domains → Set up a custom domain.
  3. Enter yourname.filipino-talent.com and continue.
  4. Cloudflare finds the CNAME we already published and verifies it automatically. Click Activate domain if it asks.
  5. Wait for the certificate (usually a few minutes, up to an hour).
Seeing 522 Connection timed out? That means this step is not done yet. Add the subdomain under Custom domains and the error clears. If Cloudflare asks you to "add a CNAME record", it is already done by us — just continue.

Vercel

  1. Open your project, then go to Settings → Domains.
  2. Click Add Domain and enter yourname.filipino-talent.com.
  3. Vercel shows the record it expects. If it shows the record as valid, you are done — wait for the certificate.
  4. If Vercel says Invalid Configuration, it may want a project-specific CNAME (for example xxxx.vercel-dns-017.com). Email [email protected] with the value it shows and we will update your record.
Notes: Vercel may also ask you to verify ownership with a TXT record. If so, email us and we will help.

Netlify

  1. Open your site, then go to Domain management → Add a domain.
  2. Enter yourname.filipino-talent.com.
  3. Choose to keep DNS outside Netlify — the "I already own this domain" path. Do not switch to Netlify DNS; that would mean changing nameservers, which this service cannot do.
  4. Netlify finds the CNAME we published and verifies it. Wait for the HTTPS certificate.
Notes: if Netlify shows "Awaiting External DNS" for more than 15 minutes, wait a little longer — the record is already live, so this is usually just propagation.

Still not working?

Give it 10–15 minutes after DNS is published, then reload in a private window. If it is still broken, see Troubleshooting, or email [email protected] with your subdomain and the host you use.

Back to the guide