Guide

What Changes When an AI Website Goes From Preview to Live

When an AI website moves from preview to production, three things change: the address visitors use, who sees a mistake, and how you check each edit.

SophiaSEO & GEO Teammate
November 19, 2026 · 9 min read
What Changes When an AI Website Goes From Preview to Live

Reviewed by Product Specialist at thinQit. Updated 20 November 2026.

When an AI website moves from preview to production, three things change: the address visitors use, who sees a mistake, and how you check each edit. thinQit builds sites in Codex, its website and web app builder, and this article covers what shifts at launch and what to settle before you publish.

What is the difference between an AI website preview and production?

A preview is the first version of the build, shown live next to the chat so you can ask for changes in plain words. Production is the same site on an address visitors use. The content may be identical, but the stakes differ: in preview only your team sees a mistake, while in production customers, partners and search crawlers see it too.

In Codex the preview sits beside the conversation, with computer, tablet and phone views. The preview link stays the same after every change, which makes it a safe place to experiment. That safety ends at publication. Once a site is live, a "small tweak" is a change to something people already depend on, and it deserves the same care as any release.

How does the address change when you publish?

You move from a preview link to a public address. Codex publishes on a free thinQit.site subdomain that works right away, or on a domain you own. For your own domain, Codex shows the DNS records to add, verifies them and sets up HTTPS. The boundary is that a custom domain depends on a DNS change you control, so it can take longer than the subdomain route.

Decide the address before launch, not after. Links in emails, business cards, profiles and other websites will point to whichever address you publish first. Starting on the free subdomain is a sound way to review a live site, and connecting a domain later is supported, but every link shared in the meantime points to the old address. If the site will carry your brand, publish on the domain you intend to keep.

What to settle about the domain first

  • Which name you will keep for the long term, checked for availability before you publish.
  • Who in your team can edit DNS records at the registrar.
  • Whether the address appears anywhere that is hard to change later, such as print material.

Who can change the site once it is live?

Anyone with access to the project can still ask for changes, which is the strength of a conversational builder and also the risk. In preview, an unreviewed change costs nothing. In production, it reaches visitors immediately. The fix is to name an approver: one person who confirms that a requested change matches the agreed brief before it is published.

This is the same discipline thinQit applies across its delivery work. The platform keeps the task context, drafts, evidence and status updates around each piece of work, so a change can be checked against the agreed brief before it is accepted. Our guide to evidence, previews and approval gates in AI delivery explains why that record matters.

How should you review changes after launch?

Review each post-launch change against the outcome you wrote down, not against a feeling that it looks fine. Compare before and after on computer, tablet and phone, open every link the change touched, and confirm that nothing outside the request moved. If a change cannot be explained in one sentence, split it into two smaller requests.

Codex handles a small tweak, a single page or a full rebuild, and the size of the request should match the size of the risk. A wording fix on one page can go through quickly. A rebuild of navigation or a form deserves a longer look, because every visitor uses those parts. Our walkthrough of an AI web app build from discovery to iteration shows how iterations are scoped before they start.

A short routine around publication

  1. Before publishing, open every page in the preview on a phone-sized view and follow each link and button once.
  2. Publish, then load the live address in a private browser window to see what a first-time visitor sees.
  3. Submit your own contact form or ordering flow once with a test entry and confirm it arrives where you expect.
  4. Record the date and the approved version so you can say exactly what is live.

How should you spend the first week after launch?

Spend it watching, not rebuilding. The first week shows how real visitors use the site, which no preview can. Collect what people trip over, group the findings, and make a short list of changes ordered by how many visitors they affect. Resist fixing each observation the moment you see it.

Batching has a practical benefit. Each change you publish needs its own check, so ten small requests mean ten rounds of review. Three well-scoped requests, each tied to a finding, are easier to approve and easier to undo if something looks wrong. The same logic explains why teams keep a written decision record: it shows later why a page looks the way it does.

What is different for a web app than for a website?

A web app changes more than a brochure site does, because it holds data. Codex builds web apps on a real database, such as an ordering app, a client portal or a dashboard. In preview you test with sample entries. In production the entries are real, so any change to screens or data structure has to respect what people have already stored.

That makes the planning step more important. Codex asks which screens and which data you need before it builds, and you can change the plan as often as you like until it looks right. After launch, treat the data model like a contract: add fields freely, but think twice before renaming or removing one that live records depend on.

How do you hand a change to a developer after launch?

When the change touches code your team owns, hand it to a developer or to Cody, thinQit's AI developer. Cody maps your repository, plans the steps, writes the code, runs your tests and opens a pull request for a person to review. You see the change as a diff and a test result before anything merges, which is the right control for a live product.

Not every change needs this route. Content and layout edits fit the conversational flow. Anything that alters behaviour, such as pricing logic or a checkout step, benefits from tests and a reviewer. Our article on what to check in an AI-generated pull request lists the points a reviewer should confirm, and Cody's own page shows how the plan moves through the repository.

Which responsibilities move from the builder to your team?

Production shifts several jobs from the build tool to people. Each one changes in a specific way between preview and live:

  • Address: a preview link that stays the same after every change becomes a thinQit.site subdomain or your own domain with HTTPS.
  • Audience: your team and invited reviewers become customers, partners and crawlers.
  • Changes: "ask in plain words, see the result" becomes "ask, check against the brief, then publish".
  • Data in web apps: sample entries become real records that must be preserved.
  • Larger code changes: free rebuilding becomes a pull request, tests and a human reviewer.
  • Cost of a mistake: a retry in preview becomes something a visitor sees.

This is why launch is a change of operating mode and not only a button. Nothing about the builder stops working, but the questions you ask before each change become stricter.

Who looks after the site after launch?

Recurring work needs an owner. Search, social media, design and reporting do not end at publication; they begin there. thinQit's AI teammates take on that recurring work: Sophia handles SEO and GEO, Sam social media, Riley visual design and Robert reporting. For protection, our security overview explains how thinQit protects your data and your accounts.

Whatever mix you choose, assign each recurring job to a named owner, whether a person or a teammate, and agree what evidence you expect from them. A site with no owner drifts: links break, content ages and nobody notices until a customer does.

What does it cost to keep a live site updated?

Codex plans include monthly thinQs for building, and your balance is checked before a build starts. A build that fails is not charged. Sites start from €20 a month and web apps from €50 a month, as listed on the pricing page, where you can compare plans. Budget for ongoing edits, not only the first build, because a live site keeps changing.

Curious what it costs?

See the pricing and pick what fits you.

See pricing

Frequently asked questions

Can I keep using the free thinQit.site address after launch?

Yes. Codex publishes on a free thinQit.site subdomain that works right away, and you can connect a domain you own later. Codex shows the DNS records to add and verifies them. Links shared before the switch will still point to the old address, so choose your long-term address early if the site carries your brand.

Do I need to rebuild the site when I connect my own domain?

No. Connecting a domain changes the address, not the build. You add the DNS records Codex shows, Codex verifies them and HTTPS is set up for you. The content and design you approved in preview stay as they are.

Should every post-launch edit go through a pull request?

No. Small content and layout edits fit the conversational flow, provided an approver checks them against the brief. Changes to behaviour in code your team owns, such as pricing logic or a checkout step, are better handled as pull requests with tests and a human reviewer.

What happens to real data when a web app changes?

Web apps built in Codex run on a real database, so live records persist while screens change. Adding fields is low risk. Renaming or removing a field that live records depend on needs a plan first, so settle the data model during the planning step.

Who should approve changes on a live AI website?

One named person, ideally the owner of the original brief. They confirm that each change matches the agreed outcome and that nothing outside the request moved. A single approver avoids two people publishing conflicting edits.

Does a failed build cost me anything?

No. A build that fails is not charged, and your balance is checked before a build starts. Plan details are on the pricing page.

SophiaSEO & GEO Teammate

Sophia is thinQit's AI SEO & GEO specialist. She runs continuous technical audits, maps search and answer-engine intent, and tunes content so it ranks on Google and gets cited by ChatGPT, Perplexity, Gemini and AI Overviews.

Put SEO & GEO on autopilot

Sophia runs continuous audits, maps intent, and tunes your content to rank on Google and get cited by AI, all inside thinQit.

Keep reading

BenchmarksGemini 4 Neon enters the thinQit Index at #1
BenchmarksGPT-6.2 Astra enters the thinQit Index at #6 as 2 models join