Free ProfitsLocal subdomain
No customer DNS. We create the record and attach Cloudflare Pages.
- Best when you want the site public now
- Example: dark-shepherd.profitslocal.com
- Good for review, launch, and ads before final domain cutover
Domain guide
Pick the least risky launch address.
Fast launch and safe DNS are not always the same thing. Use a ProfitsLocal subdomain when speed matters; use your own domain only when you know which public address should carry the new site.
Start domain setupYour subdomain
Example: menu.yourbusiness.com. Add one CNAME to the Pages target.
- Keeps your current root domain and email setup untouched
- You add one CNAME record
- Usually the safest path for restaurants with an existing website
Your root domain
Example: yourbusiness.com. We inspect DNS and email before changing root records.
- Use only when the new site should replace the current homepage
- We review email/DNS dependencies first
- Safer after a short operator check than a blind record swap
One form, three matching fields.
Use the order ID, checkout email, and client slug from your project record. We match all three before we touch any public domain.
Exact next step, not vague DNS advice.
For customer domains, we reply with the exact host and target to use. For root domains, we first confirm whether email or legacy records need protection.
One CNAME record.
Host: menu Target: your-pages-project.pages.dev This leaves yourbusiness.com alone while making menu.yourbusiness.com public.
Check old site and business email first.
If the root domain already powers email, booking, or a legacy site, we review those dependencies before any live cutover. This is why root domains are intentionally slower than subdomains.