The door is open. Build something.
A domain, ChatGPT, and a little initiative.
We'll show you the way.
Your domain and ChatGPT plan may cost money. The initiative is yours.
No perfect prompt required. Start with what you have, make it your own, and keep improving it.
Register a domain for your business or idea. Already own one? Keep it. You don't need to buy it again or transfer it.
Register a new name with a domain registrar, such as Cloudflare. Registration and renewal have a cost. If you already own a name, keep access to your registrar account—you may need it for the next step.
Create a Cloudflare account and add your domain. Its Free plan can handle DNS—the records that tell visitors where your website lives.
Copy your existing DNS records into Cloudflare, including email records, before changing anything. At your registrar, replace the nameservers with the exact pair Cloudflare assigns to your domain. Wait for Cloudflare to confirm activation. Domains registered through Cloudflare already use its nameservers.
Open ChatGPT Sites and tell it what you want. Add your real business details, photos, services, and style. Review the result. Ask for changes. Repeat.
Your business name, audience, services, location, logo, contact details, and photos you have permission to use. Describe what visitors should do. Choose a ChatGPT plan and workspace with Sites access; Business is an option for teams, not a requirement for everyone.
Build accessibility in from the start. Ask for readable contrast, keyboard navigation, clear labels, useful image descriptions, and layouts that work on small screens.
Copy the accessibility promptAsk ChatGPT to target WCAG 2.2 AA and explain what it tested. Automated checks and a prompt alone do not establish conformance. Review keyboard and screen-reader behavior and test with people who use assistive technology.
Review the words, images, links, and buttons. Publish through Sites, choose the intended audience, and confirm visitors can open the site.
Test your mobile layout, contact links, forms, and primary action. New Sites start private; choose public access when the site is ready for everyone. Test the visitor experience while signed out. Publishing is a live deployment.
In your Site's settings, choose Add domain. Enter your domain, then add the exact DNS records Sites provides in Cloudflare. Refresh the domain status until it verifies.
You can enter the records yourself or ask ChatGPT to help through your browser after you sign in. Use the exact records supplied for your domain; don't guess the values. Custom-domain availability depends on your workspace. Keep existing email and unrelated service records intact.
It’s Memphis. We have enough already.
It’s self-serve now. Do it yourself.
Copy a prompt. Fill in your details. Have a conversation.
@Sites Build a website for [business or idea], for [audience]. Help visitors [main action]. Use these real details: [services, location, contact information, photos, and style]. Make it clear, mobile-friendly, and easy to use. Ask me for any essential information that's missing. Save a version without deploying it so I can review it first.
Target WCAG 2.2 AA across my site. Check color contrast, keyboard navigation, visible focus, heading structure, form labels, image alt text, zoom, reduced motion, and mobile layouts. Fix the issues you find. Tell me what you tested and what still needs manual accessibility review.
Help me connect [my domain] to this published Site. My DNS is managed in Cloudflare. Get the exact records from Sites, check the existing setup, and preserve my email and other services. Verify the domain and HTTPS status, then check that the site works for its intended visitors.
Sites and custom-domain features depend on your plan and workspace. Check the current Sites guide. For accessibility, use the WCAG 2.2 reference alongside automated and manual testing.
Six months from now, open ChatGPT and say:
“Change the website.”
That's the point.