Custom Domain Setup Guide

Why a Custom Domain Matters

Using a custom domain changes more than the address bar.

It helps you:

• build on an owned brand surface,
• reinforce trust with readers,
• accumulate search value on your own domain,
• and make future migration or expansion easier.

In short, a custom domain turns your site into infrastructure you control instead of a page that lives inside someone else's brand.

Before You Start

Make sure you have:

• a domain you control through a registrar or DNS provider,
• access to edit DNS records,
• the right Postion plan for custom domains,
• and a clear decision about whether you want a subdomain or a root domain.

If you are choosing between blog.yourdomain.com and yourdomain.com, most creators should start with the option that is easiest for their current brand and technical setup.

Choose Your Domain Pattern

Option 1: Subdomain

Example: blog.yourdomain.com

This is often the simplest route because it usually relies on a straightforward DNS record and is easier to isolate from an existing main website.

Subdomains are a good fit when:

• your main site already exists elsewhere,
• you want to launch faster with lower DNS risk,
• or you need a content property that is separate from your marketing site.

Option 2: Root Domain

Example: yourdomain.com

This creates the strongest single-domain brand surface, but it can be more sensitive to DNS provider rules and existing records.

Choose this when:

• the Postion site is your main web presence,
• you want all direct and search authority focused on one domain,
• or you are intentionally replacing an older site at the root.

Recommended Setup Flow

Step 1: Add the Domain in Postion

In your site settings, open the domain area and add the custom domain you want to use.

Once added, Postion will show the exact DNS records required for that domain pattern.

Use the dashboard values as the source of truth rather than copying generic DNS values from memory.

Step 2: Update DNS with Your Provider

Open the DNS management area at your registrar or DNS host and create the records shown in Postion.

The exact record type depends on whether you are connecting:

• a subdomain,
• a root domain,
• or both root and www together.

Two important rules:

1. Remove or update conflicting older records if they point somewhere else.
2. Match the record name and value exactly as shown in your dashboard.

Step 3: Wait for DNS Propagation

DNS changes are not always immediate. Some providers update quickly, while others take longer to settle globally.

During this window, verification may fail even if the settings are correct.

That usually means "wait and recheck," not "start over."

Step 4: Verify the Domain in Postion

Once the DNS records are live, return to the dashboard and run the verification step.

Successful verification confirms that the domain points correctly and is ready for the next stage of setup.

Step 5: Allow SSL to Finish Provisioning

After verification, Postion can provision HTTPS for the domain.

You should treat this as part of the same workflow:

• DNS points correctly,
• verification succeeds,
• SSL finishes,
• then the domain is ready for live traffic.

Step 6: Set the Domain as Primary

If this domain should be the main public address of your site, mark it as the primary domain in Postion.

This matters because your canonical public URL should be consistent across sharing, search, and future content publishing.

Provider Notes That Save Time

Cloudflare

If you are using Cloudflare, make sure the DNS record behavior matches the setup instructions in Postion. In many cases, you will want DNS-only behavior during setup so verification and SSL can complete cleanly.

Namecheap, Squarespace Domains, and Similar Registrars

These providers usually work fine, but the main risk is editing the wrong DNS area or leaving older conflicting records in place.

Double-check:

• the record name,
• the target value,
• and whether the provider automatically created defaults that now conflict.

Common Problems and What They Usually Mean

The Domain Will Not Verify

Usually caused by:

• an incorrect DNS value,
• an old conflicting record,
• a record added to the wrong host name,
• or propagation not being finished yet.

HTTPS Is Not Ready Yet

Usually caused by:

• DNS still not fully settled,
• proxying or CDN behavior interfering with validation,
• or verification not fully completing first.

The Wrong Site Appears

Usually caused by:

• browser cache,
• stale DNS cache,
• or the domain still pointing to an older destination.

A Good Post-Launch Check

After the domain is live:

1. Open the domain in a fresh browser session.
2. Confirm it resolves over https.
3. Check that your main pages load correctly.
4. Confirm the domain you expect is the one being shared and indexed.
5. Update any external links, newsletters, or social profiles that still point at the old address.

Recommended Next Reads

• Setting Up a Custom Domain for lower-level implementation context
• SEO & Discovery to make the most of your owned domain
• Migration Guide if you are moving from another platform at the same time