Build and publish a landing page with Codex

Choose the Codex surface first

This guide uses Codex CLI on a computer where you can complete browser sign-in. It does not assume that a hosted ChatGPT conversation has the same local MCP settings. Codex can work on source files, inspect a project, and call a connected publishing service; those capabilities become useful when the landing page has a clear business goal.

The configuration below is documentation-based, reviewed on September 15, 2026. Your installed version, network permissions, and organization settings still need checking. No customer account publication or form delivery is claimed as a test performed for this article.

Configure the remote server

Add this table to your existing Codex configuration without removing other settings. The normal user configuration is ~/.codex/config.toml; trusted projects can also have a project-scoped .codex/config.toml.

[mcp_servers.pageree]
url = "https://mcp.pageree.com/"

Then start the OAuth flow:

codex mcp login pageree
codex mcp list

Complete the browser authorization for the correct Pageree account. In the Codex terminal interface, /mcp shows active servers. OpenAI documents Streamable HTTP, OAuth, configuration scope, and these commands in the official MCP documentation. Do not paste a token into the landing page or invent a client secret to work around a failed login.

Ask Codex to read your Pageree account and list pages. That verifies useful access more directly than a settings entry alone. If the connection fails, compare the exact endpoint with the Pageree setup guide and inspect the reported error before generating the page.

Prepare a reviewable project

Use a dedicated folder with a brief and any authorized assets. For an illustrative campaign, suppose a founder wants enquiries for a small-business reporting setup service. The useful outcome is a conversation with a suitable business, not a dashboard mockup that looks like functioning software.

Build a single landing page for my reporting setup service.
Audience: small-business owners who manually combine weekly operating reports.
Offer: assess their existing reports and propose a practical setup project.
Goal: a qualified enquiry with name, work email, and current reporting problem.
Read the provided brief and assets. Ask for missing business facts and proof.
Do not invent savings, customer logos, testimonials, or software integrations.
Use Pageree's current page, assets, form, privacy, and publishing instructions.
Create one complete HTML document with inline CSS and JavaScript.
Ask me to choose the slug and destination inbox. Save a private preview.
Store the returned page ID, slug, and URL locally for future edits.
Show the preview and wait for review before publication.

Give Codex the actual scope you sell. The brief template helps separate that scope from visual preferences. If the generated page implies that visitors receive an immediate report, correct the wording unless a real report-generation service exists.

Inspect the output before publication

Ask Codex to describe the files it changed and identify unsupported dependencies. Pageree’s static page route needs inline styles and scripts, hosted image URLs, and a working form contract. An application that requires a server process cannot become a functioning landing-page application merely by renaming its entry file.

Review the preview in a browser yourself. If Codex has a browser tool available, it can help inspect the layout, but a claim that the page “looks good” should be accompanied by the actual checks it performed. Look at mobile wrapping, keyboard access, required fields, error messages, and links.

Publish, then check the real destination

Approve publication after the preview is correct. Open the public URL in a separate session and submit a clearly marked test using contact details you control. Verify receipt in the chosen inbox or configured destination. A draft email test does not verify a published CRM integration. Follow the enquiry-to-email guide for a simple first delivery path.

Connect an owned hostname only after the page is published, using the exact DNS records returned for that hostname. The custom-domain guide covers this step.

For later edits, ask Codex to read the current page and stored source before saving a replacement draft. Reuse the page ID so the campaign URL and its history remain connected. Record what changed and why; that context is more useful than an unexplained series of new pages.