Build a website by giving Codex a specific brief, agreeing on the design system, testing the pages and publishing through your chosen host. The Machi Days tour business below is fictional. Treat its generated site as a draft to check, not a ready-made business or legal policy.
I got back from the gym and the website was done.
Not a landing page. A five-page site for a tour company — home, tours, about, FAQs, a contact form, privacy, terms. Metadata and responsive layouts were included in the draft. I'd written the brief, kicked it off, gone and trained, and come back to the finished thing.
I'd been watching everyone post their "$10k website" builds and I wanted to know whether Codex could genuinely do it. So I built one from scratch for a made-up Japanese walking-tour company called Machi Days, and filmed every step.
You don't need a technical background for this. I don't have one.
What Codex actually is
Codex is OpenAI’s coding agent. The recording uses a desktop workflow with connected publishing tools. For current app, command-line, editor and web access, use the official Codex documentation; the filmed interface is not the only supported route.
Check the current access and usage options for your account before installing. Features and connectors can differ between interfaces; do not assume every account matches the video.
That's the whole barrier to entry. If you've used ChatGPT, you can use this.
If you're weighing up which assistant to build with more generally, I've compared them properly in Claude vs ChatGPT for business — but for this particular job, Codex is the one with the plugins.
Connect Netlify and GitHub before you start
This is the step that turns "Codex wrote some code" into "my website is on the internet." Two plugins, both free to sign up for.
Netlify is the host. It's what puts your site on the web and keeps it there. Check Netlify’s pricing and usage limits for your site. Hosting, forms, traffic and other services may add costs beyond the domain.
GitHub is the backup. Think of it as Google Docs for code — it stores every version, so you can change things without breaking what's already live, and other people can work on it without stepping on you.
Install both, hit Authorise on each, then start a fresh chat. Now when you tell Codex to publish, it just does it — no exporting files, no dragging folders around, no working out what FTP means.
Keep credentials out of code and use environment variables or the host’s secrets settings. A private GitHub repository restricts who can see the source; it does not make a committed password safe. If a secret is committed, revoke or rotate it.
The brief is the whole job
These tools cannot read your mind. That sounds obvious, and it's still where most people's build falls apart — they type "build me a website for my business" and get something beige and generic back, then decide AI can't do it.
I spent real time on the brief before Codex wrote a single line. What went in:
- Business context — Machi Days is a tour company running small neighbourhood walking tours through Japan
- The primary action — check availability through an external booking platform. One goal, stated plainly
- The ideal traveller — who this is actually for
- The offers — the specific tours, what's in them
- Brand direction — the feel, the tone, what to avoid
- The exact path someone takes — land on the home page, compare tours, open a tour page, check availability
- Policies and operations — terms, refunds, what's a real commitment versus a placeholder
- SEO and site pages — what pages exist and what each one is for
When you're building a website you want to really think about the user's journey.
That's the difference between a site that looks like every other AI-generated site and one that actually belongs to your business. The brief is the work. The build is the easy part.
Give it design references or it comes out beige
Same principle, applied to how it looks. If you don't show it what good looks like, it picks something safe and forgettable.
So show it. Screenshot things you like and hand them straight to Codex. Five places I actually use:
- Pinterest — fastest for general mood and colour direction
- SiteInspire — full websites, properly curated
- Land-book — whole sites, but also broken down by section, so you can point at one specific block and say "like this"
- Motion.dev — the scroll and hover animations that take a site from flat to feeling expensive
- 21st.dev — free component templates you can copy the prompt from directly
If you've got real brand assets — your colours, your fonts, and especially your own photography — put those in too. Professional brand photography is one of the best things I've ever spent money on. If you're not there yet, Codex can generate placeholder images, and asking for "iPhone quality" gets you something that reads as real rather than glossy AI stock.
The design system step everyone skips
This is the part I skipped when I rebuilt my own site, and it's the part that costs you.
Without a design system, every new page gets designed from scratch. Your buttons drift. Your spacing wanders. Page four looks like a different company built it. You end up with a mishmash and you can't work out why it feels amateur.
So before it builds out the pages, tell Codex to set up a design system with reusable components. Buttons that all match. Consistent spacing. A type scale. Cards that share a shape.
You're not asking for every page to look identical. You're asking for them to look related.
Getting it on the web
Before publication, test the contact form from submission through receipt, every booking link, mobile layout and keyboard navigation. Check page titles, descriptions and canonical addresses, image descriptions, and the ownership of the domain and hosting account. Replace fictional details and have policies reviewed for the real service. A generated page is not an SEO result.
Up to this point the site only exists on your computer — that's what localhost means. Two sentences move it to the internet:
Ask Codex to publish it to a new private GitHub repo. Then ask it to use its Netlify plugin to put it live.
Because you connected those plugins at the start, it goes and does both. A couple of minutes later, the site is live and viewable from anywhere.
Then there's the URL problem. Netlify gives you something like your-site-name.netlify.app, and if you're running a real business that costs you credibility instantly. Buy a domain from Namecheap — mine are usually around $7 a year — and ask Codex how to point it at your site. It walks you through the DNS settings, which sounds technical and isn't. You're copying two values across.
Half an hour, and there's a real website at a real address.
Building it for a client instead of yourself
Everything above works the same if you're building for someone else. The difference is ownership, and you want to get it right at the start rather than untangle it later.
Set it up in their Netlify account. Have them buy the domain through their own Namecheap account. Then when the project finishes, it's a clean handover — they own their site, their domain, their hosting, and you're not the person holding the keys to a business you don't run.
If you're building this into a service you charge for, how to build an AI lead magnet that actually prints email subscribers covers the front half of that funnel.
FAQ
Do you need to know how to code to build a website with ChatGPT Codex?
No. You describe what you want in plain English and Codex writes and runs the code. I don't have a technical background and I built a full five-page site with working navigation, SEO, and a live domain. The skill you actually need is writing a clear brief, not writing code.
Is ChatGPT Codex free?
Check current Codex access in the official documentation linked above. Add the domain renewal, hosting usage and any paid integrations to your budget; a free prototype allowance does not prove a business site will cost nothing to operate.
How long does it take to build a website with Codex?
The Machi Days site took about half an hour of actual build time, though generating the images was the slowest part. What takes longer is the thinking beforehand — the brief, the design references, the path you want people to take. Rush that and you'll spend far more time fixing a generic site than you saved.
Where should you host a site Codex builds?
Netlify is the host used in this demo. Choose a host that supports your site and business use, then check its limits and pricing. If you use Vercel, Hobby is personal and non-commercial; a business page needs an appropriate plan.
Can you build a client website with Codex and hand it over?
Yes, and it's cleaner than most handovers. Set it up inside the client's own Netlify account and have them purchase the domain through their own Namecheap account. At the end of the project they own everything — site, hosting, domain — and you're not stuck as the permanent middleman.
If you want the full website setup skill — the one that asks you the right questions, takes your branding, and runs this whole build for you — it lives inside the Wright Mode membership, along with a room of women actually shipping this stuff.
