Custom Domains and Subdomains

By default, your TimelyChurch website is accessible at a path-based URL like timelychurch.com/c/your-church-slug. You have two ways to give your church a more memorable address: a TimelyChurch subdomain (yourchurch.timelychurch.com) or a custom domain you own (www.yourchurch.com). This guide covers both.

Note: Custom domains are available on qualifying plans. If you do not see the domain settings option, your current plan may need to be upgraded.

How Website URLs Work

TimelyChurch supports three URL styles, in order of priority:

If a verified custom domain is configured, it takes priority. Otherwise, the subdomain is used if enabled. The default path-based URL always works as a fallback.

Where Domain Settings Live

Domain settings live on the Church Profile page, not in a separate "Custom Domain" tab. Go to Church Profile and expand the Web Address section. This is where you find the URL slug, subdomain, subdomain toggle, and custom domain fields. Some plans also expose these as a settings card on the church profile screen.

Heads up: There is no dedicated "Custom Domain" tab in the settings menu. If you cannot find domain controls there, open the Church Profile page and look for the Web Address section.

Subdomain Setup (yourchurch.timelychurch.com)

A subdomain is the simplest way to upgrade your URL. It does not require DNS changes -- TimelyChurch handles everything.

Step 1: Choose a Subdomain

1. Open Church Profile.
2. Expand the Web Address section.
3. In the Subdomain field, enter the prefix you want (e.g., gracecommunity).
   • Allowed characters: lowercase letters, numbers, and dashes.
   • Cannot start or end with a dash.
   • Must be 63 characters or less.
   • Must be unique across all TimelyChurch churches.

Step 2: Enable the Subdomain

1. Toggle Use Subdomain on.
2. The page shows a green preview of your live URL (for example, https://gracecommunity.timelychurch.com).
3. Click Save.

Your subdomain is live immediately. Visitors going to https://gracecommunity.timelychurch.com will see your church website.

Tip: You can configure a subdomain even if you also plan to use a custom domain later. The system always prefers a verified custom domain when present.

Custom Domain Setup (www.yourchurch.com)

A custom domain shows visitors your own web address. Setting one up takes three things: enter the domain in TimelyChurch, add DNS records at your registrar, then verify.

Step 1: Add Your Domain in TimelyChurch

1. Open Church Profile > Web Address.
2. In the Custom Domain field, enter your domain without http:// or https://.
   • Examples: www.yourchurch.com, gracecommunity.org, schedule.yourchurch.com
3. Click Save.

After saving, TimelyChurch generates a unique 32-character verification token for your domain. The token is shown alongside the DNS instructions on the Web Address card.

Step 2: Configure DNS Records

At your domain registrar (GoDaddy, Namecheap, Cloudflare, Google Domains, etc.) add two DNS records:

Record 1: TXT Record (Required for Verification)

Proves you own the domain.

Tip: Copy the verification token exactly. Even a single extra space will cause verification to fail.

Record 2: CNAME or A Record (Choose One)

Points your domain at TimelyChurch.

Option A: CNAME Record (Recommended)

Option B: A Record

Tip: CNAME records are recommended because they automatically follow any infrastructure changes on our side. A records require a fixed IP and may need updating later.

Step 3: Wait for DNS Propagation

DNS changes typically take 15 minutes to a few hours, sometimes up to 48 hours.

Step 4: Verify Your Domain

1. Return to Church Profile > Web Address.
2. Click Verify Domain.
3. TimelyChurch performs a DNS lookup:
   • The TXT record at _timelychurch.<your-domain> must match your verification token.
   • Either the CNAME or A record at <your-domain> must point to the correct destination.
4. If verification succeeds, your domain status flips to verified.

If verification fails, double-check the records and try again after waiting longer for propagation.

SSL / HTTPS

TimelyChurch verifies DNS records but does NOT issue or manage SSL certificates. TLS is a hosting/CDN-layer concern.

You are responsible for making sure your domain is served over HTTPS. The most common ways to do this:

• Cloudflare (free): Put your domain behind Cloudflare with the proxy enabled and Cloudflare provides a free SSL certificate. (See the Cloudflare note below.)
• Your hosting provider's TLS: Work with whoever serves HTTPS for your custom domain to install a valid certificate.

Important: Confirm with your hosting provider or CDN that TLS is configured for your custom domain before publishing your site to that URL. If you send people to a custom domain that does not have a valid certificate, browsers will show an SSL warning and visitors will leave.

A Note on Cloudflare

If you use Cloudflare for DNS, there are two viable setups:

• Proxy off (DNS Only, grey cloud): Cloudflare just resolves DNS. You are responsible for HTTPS at the destination.
• Proxy on (orange cloud): Cloudflare handles DNS, caching, and TLS termination -- it issues a free SSL certificate to visitors and connects to TimelyChurch behind the scenes. With this setup, set Cloudflare's SSL/TLS mode to Full (not "Flexible").

If you turn the Cloudflare proxy on for the CNAME record but Cloudflare's SSL mode is misconfigured, visitors may see a redirect loop or a "too many redirects" error. Pick one strategy and stick with it.

Changing Your Custom Domain

1. Open Church Profile > Web Address.
2. Update the Custom Domain field with the new domain.
3. Click Save.
4. The verification status resets and a new verification token is generated. Update your DNS records and verify again.

Removing Your Custom Domain

1. Open Church Profile > Web Address.
2. Clear the Custom Domain field.
3. Click Save.
4. Your website reverts to the subdomain (if enabled) or the default path-based URL.

Troubleshooting

Domain verification keeps failing

• Check DNS propagation: Use whatsmydns.net to confirm your records are visible globally.
• Verify the TXT record name: It should be _timelychurch, not the domain itself.
• Verify the TXT record value: Copy the verification token exactly. It is case-sensitive and rejects extra spaces.
• Wait longer: Some registrars take up to 48 hours.

Website not loading on custom domain

• Confirm the domain is verified in Church Profile > Web Address.
• Check the CNAME/A record: It must point to the value shown on the card.
• Cloudflare users: Decide on proxy on or proxy off. If proxy is on, SSL/TLS mode must be Full.
• Clear your browser cache or try an incognito window.

SSL certificate warning in the browser

• TimelyChurch does not issue certificates. Verify TLS is configured at your hosting/CDN layer.
• If using Cloudflare proxy, switch SSL/TLS mode to Full and wait a few minutes for the edge certificate to provision.
• If you manage HTTPS yourself, confirm your certificate is valid and has not expired.

Next Steps

• Publishing Your Website -- Manage what is live on your site
• SEO Settings -- Make sure search engines find your new domain