Your own domain on the door.
Every schedule starts on an eventschedule.com subdomain. Enterprise lets you fix your own plate over it: serve the schedule directly on events.yourdomain.com with HTTPS issued for you, or point the domain at it through Cloudflare. Behind the door, nothing about your schedule changes.
Behind the door, nothing moves
A custom domain is not a migration and not a second copy of anything. A request arriving on your domain is matched to your schedule and served by the same routes as before. What changes is the address on the way back out: links, feeds, the JSON the calendar loads, and the page a card payment returns to are all rewritten to your domain.
Your links
events.yourdomain.com/summer-social
Event pages keep the slug you set on the event. Only the host in front of it is different.
Your feeds
events.yourdomain.com/feed/ical
The iCal and RSS feeds serve from your domain, and every event inside them links back to it.
Your checkout
events.yourdomain.com/...
A ticket buyer is handed back to your domain when payment finishes, not to a subdomain they have never seen.
Two ways to fix a plate
One screws the plate to the door itself. The other hangs a sign in the lobby that points at the room. Both put your domain in front of your audience; they differ in what happens after the click.
Direct mode
RecommendedThe plate on the door
Requests land on your domain and are served there. One CNAME record at your registrar is the whole DNS job, and the certificate is issued for you once that record resolves. Your domain stays in the address bar on every page of the schedule, so it becomes the address search engines record for it.
Status moves from Setting up to Active on its own. Nothing to install and no proxy to maintain.
Redirect mode
CloudflareThe sign in the lobby
Cloudflare answers for your domain and forwards each request, path and all, to your schedule URL with a 301. Past naming the domain in your settings, the work happens in your Cloudflare dashboard, HTTPS comes with their free plan, and a link to one event still lands on that event.
Because visitors end up on your eventschedule.com URL, that URL stays the canonical one for search.
| Direct | Redirect | |
|---|---|---|
| What visitors see | Your domain, on every page of the schedule. | Your domain for one hop, then your eventschedule.com URL. |
| Where pages are served | On your domain. The request is matched to your schedule and served by the same routes as before. | On your eventschedule.com URL. Cloudflare forwards the request with a 301. |
| HTTPS | A certificate is issued for you once the DNS record resolves. | Included free through Cloudflare's free plan. |
| DNS you add | One CNAME record at your registrar. | Cloudflare nameservers, two proxied A records, and a 301 forwarding rule. |
| Canonical URL for search | Your domain, once the status reads Active. | Your eventschedule.com URL. The redirect points at it, so it stays the address of record. |
Cutting the letters
Four steps in either mode, and the only thing you ever type into Event Schedule is the domain itself. Everything else happens where your DNS lives.
Direct mode
One CNAME-
01
Name the domain
In your schedule settings, type the domain you own and choose Direct.
-
02
Open DNS at your registrar
GoDaddy, Namecheap, Cloudflare, anywhere. You are looking for the DNS records screen.
-
03
Add one CNAME
Name it @ for the root, or a label like events. Point it at the hostname the settings panel shows you.
-
04
Wait for the record
Usually minutes, up to 48 hours. HTTPS is provisioned automatically once the record resolves.
Redirect mode
Free Cloudflare plan-
01
Name the domain
In your schedule settings, type the domain you own and choose Redirect.
-
02
Move DNS to Cloudflare
Add the domain to Cloudflare and point your registrar at the nameservers it gives you. The free plan is enough.
-
03
Add proxied A records
One for the root and one for the wildcard, both proxied, so Cloudflare can answer for the domain.
-
04
Forward with a 301
A page rule that forwards to your schedule URL and keeps the path, so a link to one event still lands on that event.
Three house rules, whichever mode you pick
- The domain has to be one you own. Buy it wherever you like; Event Schedule does not sell domains.
- An eventschedule.com host is rejected, and a domain can only be attached to one schedule at a time.
- Delete the schedule and the domain is released from the platform, so you can point it somewhere else.
Both routes are written out step by step in the Custom Domain Setup guide, including the exact Cloudflare records and page rule.
Not live until the plate is on
Direct mode has a state, and your schedule settings show it plainly rather than leaving you to guess. Until it reads Active, your subdomain keeps serving the schedule exactly as before: the old sticker is still the address right up to the moment the plate goes on, so nothing is ever offline while DNS catches up.
Saved
You entered the domain and chose Direct. The domain is registered with the platform that terminates HTTPS.
Setting up
The settings panel shows a Setting up badge while the record propagates and the certificate is issued.
Active
The plate is on. Your domain now serves the schedule, and it becomes the canonical URL for search.
If it takes a while
DNS usually propagates in minutes and can take up to 48 hours. The status is re-checked for you every few minutes, so Setting up becomes Active without you refreshing anything.
If it fails
A record that cannot be verified shows Setup failed next to your schedule URL. Fix the record, save the domain again, and the request to provision it is made again.
What the plate covers
A domain is only worth having if everything your audience touches sits behind it.
The whole guest portal
Every page an audience sees
The schedule itself, every event page, and the guest actions on them: RSVPs against your per-date capacity, ticket checkout, a shared link to one date. In Direct mode all of it is served on your domain, not framed or proxied from somewhere else.
Subscriptions
Feeds on your host
The iCal and RSS feeds are served from your domain, and each event they carry links back to your domain too.
Payments
Checkout comes home
Card payment finishes and the buyer is returned to your domain, so the receipt page is on the address they trusted.
Search
One address, recorded once
Two hosts serving the same listings is the classic way to split your own search results. Event Schedule picks one and states it: in Direct mode, once the status is Active, your domain is the canonical URL for the schedule and its events, and the sitemap is generated on your host. In Redirect mode the 301 points at your eventschedule.com URL, so that one stays canonical and your domain is a doorway.
No ads
Nobody else advertises here
Paid plans carry no ads at all, and a request on a custom domain is excluded from ads whatever the plan says.
The last badge
Take our name off the page too
The domain handles the address bar. Two more settings handle what is inside the frame: white label removes the Powered by badge, and custom CSS lets you finish the styling yourself. Both start on the Pro plan and are included with Enterprise.
Part of Enterprise
Custom domains sit on the Enterprise plan at $29 a month, next to the AI features, internal and unlisted events, and a team of up to five people. Free and Pro schedules use their eventschedule.com subdomain, which is a perfectly good address to publish from while you decide.
Removing the Powered by badge starts on Pro at $9 a month. Compare the plans
Free forever. Upgrade when you're ready.
Zero platform fees on ticket sales. You only pay Stripe's processing fee.
See all plansFrequently asked questions
Everything you need to know about custom domains.
How do I set up a custom domain?
There are two modes. In Direct mode you enter the domain in your schedule settings, choose Direct, and add a single CNAME record at your registrar pointing at the hostname the settings panel shows you. HTTPS is provisioned automatically once that record resolves. In Redirect mode you move the domain's DNS to Cloudflare, add proxied A records for the root and the wildcard, and create a 301 forwarding page rule to your schedule URL that keeps the path.
Do I need to buy a domain separately?
Yes. You need to own a domain name from any domain registrar. Event Schedule does not sell domains, but any domain you own can be used. Two limits are worth knowing before you start: an eventschedule.com host is rejected, and a domain can only be attached to one schedule at a time.
Is SSL/HTTPS included?
Yes, and at no extra cost in either mode. In Direct mode a certificate is provisioned automatically once your CNAME record resolves. In Redirect mode HTTPS is included free through Cloudflare's free plan.
Which plan includes custom domains?
Custom domains are available on the Enterprise plan, which is $29 a month. Free and Pro plans use the default eventschedule.com subdomain. You can upgrade at any time from your account settings. Removing the Event Schedule badge is a separate thing and starts on Pro.
How long does setup take, and what if it fails?
DNS usually propagates in minutes but can take up to 48 hours. While it does, the domain reads Setting up in your schedule settings, and the status is re-checked for you until the certificate is live. If the record cannot be verified the status reads Setup failed, so you can correct the record and save the domain again to retry.
Does a custom domain change how search engines see my schedule?
In Direct mode, yes, and that is the point: once the status reads Active, your domain is the canonical URL for the schedule and its event pages, and the sitemap is generated on your host. Redirect mode is different. It sends a 301 to your eventschedule.com URL, so that URL stays the address of record and the custom domain is a doorway to it.
Are ads ever shown on my custom domain?
No. Paid plans never carry ads at all, and requests that arrive on a custom domain are excluded from ads regardless of plan, so a lapsed subscription cannot put someone else's advert on a domain you own.
Free to start
Take the name first. Add the plate later.
Claim your subdomain now and publish from it for as long as you like. When you want your own domain on the front, Enterprise screws it on and the schedule behind it never moves.
No credit card required