Custom domain

A custom domain lets you serve your hire pages from a URL you own — jobs.acme.com/senior-engineer instead of hire.page/acme/senior-engineer. Available on the Starter plan and above.

The page content is identical; only the URL changes. SEO, OG card, JSON-LD schema, and applications all work the same.

What you need

• A domain you own (subdomain like jobs.acme.com is recommended)
• Access to your DNS provider's control panel
• A workspace on Starter or above

The flow

1. Settings → Domain → Connect a custom domain
2. Enter the domain you want to use (e.g. jobs.acme.com)
3. We show you the DNS record to add — typically a single CNAME pointing at cname.hire.page
4. Add the record in your DNS provider
5. Click Verify in our UI

Important — current status: the DNS verification step is implemented as a stub in v2.0. The UI accepts the domain, stores it, and renders your hire pages with the configured hostname in the OG and SEO metadata, but automatic CNAME polling and Let's Encrypt issuance are not yet live. For early customers, we provision certificates manually after you've added the DNS record — typical turnaround is one business day. Contact support after adding the record. Self-serve verification is on the v2.1 roadmap.

Apex domains vs. subdomains

We strongly recommend subdomains (jobs.acme.com, careers.acme.com):

• They use a CNAME, which is the standard approach across modern hosting platforms
• They don't affect anything else on acme.com
• They're easy to retire if you move providers later

Apex domains (acme.com at the root) are technically supported but require ALIAS / ANAME / flattened CNAME (provider-dependent). Contact support for the specifics.

What changes after connecting

• Public hire page URL — moves from hire.page/<workspace>/<slug> to <your-domain>/<slug>
• OG sharing card URL — uses your custom domain
• JobPosting schema URL — uses your custom domain
• Email links — template variables like {{ hire_page.url }} use your custom domain
• Sitemap — served from your custom domain too

The workspace dashboard is always served from hire.page — custom domains are for candidate-facing pages only.

Redirects

By default, the old hire.page/<workspace>/<slug> URL keeps working and responds with a Link: rel="canonical" header pointing at your custom domain — search engines collapse the duplicate to your custom URL.

If you'd prefer a hard redirect, toggle Redirect hire.page URLs to my domain in Settings → Domain. This 301s the old URLs.

SSL / HTTPS

We provide a free Let's Encrypt certificate for every verified custom domain. There is no HTTP option — every custom domain is HTTPS-only.

DNS records

For most providers, this is the CNAME you'll add:

Type:   CNAME
Name:   jobs   (or whatever subdomain you chose)
Value:  cname.hire.page
TTL:    300

If you're on Cloudflare, make sure the proxy ("orange cloud") is off for this record. Set it to DNS-only (grey cloud).

Removing a custom domain

Settings → Domain → Disconnect. Your hire pages revert to serving from hire.page/<workspace>/<slug>. Delete the CNAME from your DNS provider to clean up.

Frequently asked

Can I use a custom domain on the Free plan?

No. Starter and above only.

Can I use multiple custom domains on one workspace?

Not in v2. One workspace, one custom domain.

What happens if my DNS record breaks?

The custom URL stops resolving for candidates. The hire.page URL still works as a fallback. We'll email the workspace owner if we detect the custom domain is unreachable.

Does my email come from my custom domain?

Not yet. Stage-triggered emails still send from a hire.page-managed address (with reply-to set to your custom address on Growth+). Custom sending domains are on the roadmap.

How long until DNS propagates?

Typically 5–60 minutes, occasionally up to 24 hours depending on your provider's TTL.