Use your own website address
A custom domain replaces the default Fieldified website address with an address such as:
www.yourbusiness.comIt can make the website easier to remember, strengthen the business identity, and consolidate search visibility under a domain controlled by your company.
Before connecting a domain
Confirm that:
- The Fieldified website has been published.
- You own or can purchase the domain.
- You can access the domain provider’s DNS settings.
- You know whether the domain already hosts a website.
- You know whether business email uses the domain.
- The company name and contact details are complete.
The custom-domain option becomes available after the website is published.
Start domain setup
- Open Marketing Tools > Website.
- Open website settings.
- Select Add Custom Domain.
- Choose Purchase a Domain or Connect an Existing Domain.
Purchase a new domain
- Select Purchase a Domain.
- Search for the preferred name.
- Review available extensions and pricing.
- Select the domain.
- Confirm the registrant and contact information.
- Complete checkout with the domain partner.
- Return to Fieldified.
The partner registers and manages the domain. Review:
- Initial registration term
- Renewal price
- Automatic-renewal setting
- Registrant ownership
- Transfer policy
- Cancellation process
Use a business-controlled email for the registrar account so domain access does not depend on one employee.
Connect an existing domain
- Select Connect an Existing Domain.
- Enter the domain without a page path.
- Continue to domain detection.
- Select the identified domain provider.
- Sign in to the provider when prompted.
- Review the DNS changes.
- Approve the connection.
The connection tool can add the required records automatically when the provider supports it.
If the provider is not detected, choose it from the list or continue to manual setup.
Connect the domain manually
Fieldified displays the DNS records required for the website. The exact values can change, so copy them directly from the setup screen.
The records commonly include:
- A
CNAMEforwww - One or more
AorALIASrecords for the root domain - A verification record when required
To add them:
- Open the DNS manager at the domain provider.
- Find the records for the root host, usually shown as
@. - Find the record for
www. - Remove only conflicting website records identified by the setup flow.
- Add the records displayed by Fieldified.
- Leave the provider’s default TTL unless the setup specifies another value.
- Save the DNS changes.
- Return to Fieldified.
- Confirm that the records have been added.
- Start verification.
Copy hosts and values exactly. Do not add the domain name twice if the provider automatically appends it.
Protect business email records
Website DNS changes should not remove email configuration.
Do not delete or overwrite:
MXrecords- Email-provider verification records
- SPF
TXTrecords - DKIM records
- DMARC records
If the root host has a conflicting record and you are unsure whether it supports another service, ask the domain provider or an administrator before changing it.
Common provider navigation
The labels differ by provider, but the required workflow is similar.
GoDaddy
Open the domain, select DNS, then manage the root and www records.
Squarespace Domains
Open the domain dashboard, then locate DNS Settings or Custom Records.
Wix
Open Domains, select the domain, then open Advanced > Manage DNS Records.
Cloudflare
Open the domain and select DNS > Records. When adding the website records, use the proxy setting shown in the Fieldified instructions; verification can fail when the initial record is proxied unexpectedly.
When the provider interface differs, search its help center for “add A record” and “add CNAME record.”
Wait for DNS and HTTPS
DNS changes can appear quickly but may take up to 48 hours to propagate globally.
After DNS verification, Fieldified provisions an HTTPS certificate. During this period:
- The old address can still appear for some visitors.
- The custom domain can show a temporary security or connection error.
- Root and
wwwcan begin working at different times.
Do not repeatedly replace valid records while propagation and certificate issuance are in progress.
Verify the finished connection
Test:
https://yourbusiness.comhttps://www.yourbusiness.com- Mobile and desktop browsers
- A private browser window
- Request or booking forms
- Navigation links
- HTTPS without certificate warnings
Confirm that one domain version redirects to the preferred version instead of serving duplicate independent pages.
Existing websites and domain conflicts
Connecting the root domain to Fieldified replaces the website currently served from that address.
Before connecting:
- Back up the existing website.
- Inventory current DNS records.
- Decide whether the Fieldified site should use the root domain or a subdomain.
- Plan redirects for important old pages.
- Preserve email and third-party service records.
A subdomain such as book.yourbusiness.com can be used when the primary website should remain elsewhere.
Search engines, canonical URLs, and sitemaps
Fieldified marks the custom domain as the preferred canonical address for published pages.
Canonical URLs tell search engines which domain should receive indexing and ranking signals when the same page can also be reached through a Fieldified subdomain.
A technical sitemap can continue to reference the Fieldified-hosted address while canonical tags point to the custom domain. When configured correctly, search engines can:
- Crawl the hosted pages
- Identify the custom canonical URL
- Consolidate duplicate signals
- Prefer the custom domain in search results
Check the page source or search-console inspection when the wrong domain continues appearing after recrawling.
Disconnect or replace a domain
Before disconnecting:
- Record the current DNS values.
- Prepare the replacement website or address.
- Plan redirects.
- Confirm continued domain renewal.
- Avoid deleting email records.
After disconnecting, update the DNS records at the provider. The domain remains registered until it is cancelled or expires with the registrar.
Troubleshooting
Domain cannot be verified
- Confirm the exact displayed host and value.
- Remove conflicting root or
wwwrecords. - Check whether the provider appended the domain twice.
- Disable an unsupported proxy during verification.
- Wait for DNS propagation.
Root works but www does not
Review the www CNAME and any conflicting www A record.
www works but root does not
Review the root A, ALIAS, or ANAME records shown by Fieldified.
Email stopped working
Restore the previous MX, SPF, DKIM, and DMARC records. Website setup does not require replacing email records.
Certificate warning persists
Confirm that DNS points only to the values shown in Fieldified, then allow time for certificate issuance. Contact support with the domain and verification status if it persists.