> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inploi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Using a branded domain on your careers site

> How to point a custom branded domain (e.g. careers.acme.com) at your inploi careers site by adding the domain in Studio and updating your DNS records.

When your careers site is ready to go live, you switch it from the inploi staging URL (for example `yourcompany.inploi.app`) to your own branded domain (for example `careers.acme.com` or `jobs.acme.com`). Using your own domain keeps the candidate experience on your brand from the first click.

The switchover is a two-step process: inploi adds the domain in Studio, then your IT or domain team updates your DNS records. Once DNS propagates, the switch happens automatically.

## Choosing your domain

Before the switchover, confirm the subdomain format you'd like to use. Common options are:

* `careers.acme.com`
* `jobs.acme.com`

Once confirmed, share this with your inploi contact so it can be configured in Studio ahead of go-live.

## Step 1 — inploi configures the domain

This step is handled by inploi (usually your CSM or account manager).

<Steps>
  ### Confirm your go-live date

  Let your inploi account manager know your intended go-live date at least 48 hours in advance. They'll confirm your site is ready and provide the CNAME value your IT team needs.

  ### Open the domain settings in Studio

  Go to **Settings → Domain**.

  ### Enter your chosen domain

  Enter the branded domain you want to use (e.g. `careers.acme.com`).

  ### Share the DNS records with your IT team

  Studio displays the exact DNS records your IT team needs to configure. Share these so they can complete Step 2.
</Steps>

## Step 2 — Update your DNS records

Share the following with whoever manages your domain — usually an IT admin.

<Steps>
  ### Log in to your DNS provider

  This is the service where your domain is managed (e.g. GoDaddy, Cloudflare, or 123-reg).

  ### Create a new CNAME record

  * **Type:** `CNAME`
  * **Name / DNS entry:** your chosen subdomain (e.g. `careers` or `jobs`)
  * **Target / Value:** `{client}.inploi.app` — inploi will confirm the exact value to use
  * **TTL:** 3600 (or "Auto" / leave as default)

  ### Remove any old inploi CNAME record

  If there is an existing **CNAME** record pointing to `hosting.inploi.com`, delete it.
</Steps>

<Note>
  The exact location of DNS settings varies by provider. If you're unsure where to find them, search "\[your provider name] how to add a CNAME record".
</Note>

## After the DNS update

* The switchover happens **automatically** once DNS propagates.
* This usually takes around **15 minutes**. Most changes complete within a couple of hours.
* In rare cases it can take up to **48 hours**.

Once your IT team has made the change, let your inploi account manager know. They'll verify the domain is pointing correctly and confirm the site is live.

<Note>
  Your staging site (the `yourcompany.inploi.app` URL) continues to work after the switch. You can use it internally for testing and review at any time.
</Note>

<Warning>
  Avoid making the DNS change late on a Friday. If something needs checking, it's easier to get support during the working week. Aim for a Tuesday–Thursday go-live.
</Warning>

## What to do if it doesn't work

If the domain isn't resolving after 48 hours:

1. Double-check that the CNAME value was entered exactly as provided, with no extra spaces or characters.
2. Confirm the change has propagated using a tool like [dnschecker.org](https://dnschecker.org).
3. Contact your inploi account manager with a screenshot of the current DNS record.

<Snippet file="contact-support.mdx" />

## Related articles

* [Google for Jobs](/integrations/publisher/google-for-jobs)
* [Adding a Navigation Item](/studio/cms/faqs/add-a-navigation-item)
* [SEO and discoverability](/studio/cms/faqs/seo-and-discoverability)