Domains and publishing

Your free address, connecting your own domain, the DNS records to add, and what pressing Publish actually does.

Your website has up to two addresses, and they behave differently on purpose.

Your free address — your-business.maxaibuilder.com. It always shows your latest work, the moment you make it. Search engines are told to ignore it through both the page metadata and a robots.txt rule that blocks crawling, but anyone with the link can open it, which makes it the right thing to send a colleague.
Your own domain — your-business.com, once you connect one. Your website is published to it automatically the first time it verifies; after that it only changes when you press Publish.

That split is what makes the builder safe to experiment in. Visitors to your live site keep seeing the last version you published, however much you change in the meantime.

Shared organization plans

The new shared organization plans are being prepared and are not yet open for purchase. Once your organization is explicitly moved to one, its published-project limit is shared across Websites, Forms and Games: one for Free or Flex, five for Lite and fifty for Pro. Drafts and edits do not use extra slots, and publishing changes to an already-published project still works at the limit. Existing per-website plans are unchanged.

If publication is refused because the organization is full, keep your draft and either upgrade the organization or remove a published project you no longer need. A deleted project releases its slot once its live content is confirmed offline; delayed cleanup can briefly keep the slot occupied. Contact support if that does not finish.

Until the website is live, an In development strip runs across the very top of the dashboard, above the navigation, so the development address and publishing controls remain visible on every tab while you work. It disappears the moment the website goes live.

Once your own domain is connected and you have published, the live domain is one click away, always in a new tab:

On the dashboard, the globe button beside a live website's ⋯ menu opens its live domain. Until the website is live, that button opens the development address instead. The ⋯ menu keeps both: Open preview and View live website.
On the website's Overview page, the green Open live site button sits above Open dev site.
In the builder's top bar, the globe button to the right of the open-in-new-tab button opens the live domain, while the open-in-new-tab button keeps opening the development address.

A domain that is connected but has never been published is not live, so none of these live links appear for it.

Open Domain & publishing from the builder menu under Website, or from your website's page on the dashboard.

Once your website is live, its own-domain card appears before the free development address so the address visitors use is the first thing on the page. Manage DNS is shown there as a disabled preview of the upcoming control; keep managing records with your current DNS provider for now.

Your free address

Every website gets one, chosen from its name when it was created. You can change it: type a new label and save. Two things to know before you do.

The old address is released immediately. There is no forwarding from it. If you have already shared the old link, keep it.
Your pages are updated with it. A website names itself in its own files — the canonical link on every page, robots.txt, sitemap.xml, llms.txt. Changing the address rewrites those too, so nothing is left pointing at an address that no longer resolves.
Your dashboard links change with it. The website's pages in the dashboard use the same name as its free address, so after a change you are taken to the same page at its new link. A bookmark to the old dashboard link stops working; open the website from your dashboard and bookmark it again.

Some labels are reserved for the platform and cannot be used; you will be told if the one you want is taken.

The free address is a development surface, so its /robots.txt always blocks all crawlers and every page is marked not to appear in search results. These protections are applied by the platform and cannot be weakened by a website edit. Your connected domain keeps the indexing and visibility settings you chose for the live website.

One thing that is not instant. Your pages update the moment you change them, on your free address as on your own domain. Pictures, stylesheets and fonts are held for a few minutes on servers close to your visitors, which is what makes a website load quickly wherever it is opened from. If you swap an image and still see the old one, give it five minutes — or open the preview in the builder, which never waits.

Connecting your own domain

Before a domain is connected, its Domain page shows two choices together: register a new domain through Max, or connect a domain you already own.

Connecting a domain needs a paid plan. On the Free plan the button sends you to your organization's billing page instead.

Enter your domain — your-business.com, without https://. You will be connecting both the bare domain and its www. form.
Add the DNS records you are shown. These live at whoever you bought the domain from — the registrar's DNS panel, or your DNS provider's. The page lists each record with its type, name, and value, ready to copy.
Press Verify. Checking runs as often as you like; DNS changes usually take a few minutes to propagate, and occasionally up to a few hours.

There is no fourth step. The moment all three checks pass, we publish your website to your domain for you. The page shows Publishing your website while it is copied there, and tells you it is live only once your domain actually shows it — you are never told the domain is ready while it is still showing nothing. Checking also continues in the background, so you can close the page and come back to a live website.

If your website could not be published at that exact moment — you had not built anything yet, or it was mid-save — the page says so plainly and gives you a Publish now button to finish it.

The record table appears as soon as the domain is added. Until you select a DNS provider, the page shows broadly compatible A records for the main domain and www. If you use Cloudflare, select Cloudflare to switch the table to its preferred flattened CNAME records. Selecting any other listed provider keeps the compatible A setup and labels the instructions for that provider.

Changing a connected domain

Select Change domain, enter the replacement address, and review the confirmation before continuing. The confirmation names both addresses. Once you confirm, the current address stops connecting to this website immediately and the replacement address begins its own DNS verification. The old address is not forwarded automatically.

The records, and what each is for

You will be given a handful of records across three purposes:

Domain ownership — a TXT record proving you control the domain.
SSL certificate — a CNAME record used to issue the HTTPS certificate. Your site is served over HTTPS; there is no separate certificate to buy or renew.
Website traffic — a CNAME pointing your domain at the platform's routing hostname, and the same for www..

The traffic record points at a stable routing name rather than a raw IP address, so if the underlying infrastructure ever moves, your DNS keeps working untouched.

If your DNS provider will not put a CNAME on a bare domain, look for ALIAS, ANAME, or "CNAME flattening" — most providers offer one of them. If yours truly offers none, the page also shows an A record you can use for the bare domain instead. Prefer the CNAME wherever it is available.

The three status cards

Once a domain is entered, three cards tell you where you stand:

Domain — we can confirm you control this web address.
Security — HTTPS is protecting visitors to your website.
Website traffic — your domain is sending visitors to us.

All three go green when the domain is ready. Until then, the card that is still checking tells you which record to look at.

What visitors see while the domain is connecting

Opening your domain during setup is the first thing most people do, so the address answers with a short page that says where it has got to rather than an error:

Still connecting — your DNS records have not finished verifying. Nothing to press: the website appears there on its own once they do. DNS changes usually take a few minutes and can take up to 48 hours to reach everyone.
Almost ready — the domain is verified, and nothing has been published to it yet. Press Publish and the page is replaced by your website.
Being built — a free address whose website has no pages yet.
No website at this address — the address is pointed here, but no website has claimed it. Add the domain on this page and finish its DNS setup.

The page carries your website's name and colour, never any mention of Max AI Builder, and it tells search engines not to index it, so nothing half-finished can be found in a search.

Publishing

The publish button is at the top right of the builder, and its label tells you where you stand:

Publish — this website has never gone live.
Publish changes — you have edits your live site has not received yet.
Published — your live site matches what you are looking at.

Pressing it takes the current state of your website and makes it the version your domain serves. Your free address is unaffected — it was already showing this work.

You do not have to press it to go live in the first place: connecting a domain publishes your website to it once, by itself. Publish is how every change after that reaches your visitors.

If you publish before connecting a domain, the version is marked published and waits. Once you connect a domain, it goes live there.

Publishing takes a moment

After you press Publish, your website is copied to your domain before anyone is told it is live. You see Publishing your website — in the panel that opens in the builder and on the Domain page — and both change to Your website is live the moment your domain shows the new version. You can keep working meanwhile; if you close the panel, a message tells you when it is done.

A small website is live within seconds. A very large one — thousands of pages — takes a minute or two, sometimes a few. While a new version is on its way, visitors keep seeing the one you published before, so nothing goes missing in between.

If publishing does not go through

The Domain page and the publish panel tell you why, in one of two ways:

Something in your website needs a change. The message names the file and what is wrong with it — for example a file type a website cannot contain. Ask the assistant to fix it, then publish again.
Something went wrong on our side. You will read: "Something went wrong on our side while publishing your website. Our team has been alerted and will fix it as soon as possible. Please try again shortly." We have been told automatically; you do not need to report it. Press Publish again on the Domain page in a little while.

Either way, if your domain was already showing an earlier version, it keeps showing that one.

When your live site falls behind

Once your own domain is connected, the builder tells you the moment the two drift apart. A small bar rises from the bottom of the canvas saying You have unpublished changes, and it stays until they agree again. It only appears when there is a real difference: a website without a connected domain has no live site to fall behind, and the bar never shows there.

The bar gives you both ways out.

Publish — the same thing the button at the top right does. Your live site catches up with what you are looking at, and the bar goes away.
Cancel changes — the other direction. Your website goes back to exactly what your domain is serving right now, and the bar goes away because there is nothing left to publish.

Cancel changes asks you to confirm first, because it replaces everything on your screen. Your live site is not touched by it: it was already showing the version you are going back to, and visitors see nothing change. Nothing is thrown away either — the version you cancelled stays in your website's history behind the one you came back to, so the numbering only ever moves forward.

What is not part of publishing

Some things apply as pages are served rather than being built into a version, so they take effect immediately on both addresses without republishing:

Page content is the opposite. If you changed a page and your live site does not show it, you have not published.

How your pages stay fast

Visitors' browsers keep a copy of your photos, fonts, and styles, so the second page they open and every return visit paints from their own device instead of downloading everything again. Pages themselves are always fetched fresh, so an edit you publish shows up on the first load after publishing finishes — usually a few seconds after you press Publish.

The one thing to know: if you replace a picture but keep the same file name, a visitor who already had the old one may see it once more before their browser picks up the new file, and it can take up to five minutes to reach everyone. Uploading the new picture under a new name — which is what the media library does when you swap one — shows the new picture immediately.

Older versions

Every publish keeps the version behind it. The platform retains your recent versions plus whatever is currently published, so an unlucky publish is never the end of the story — ask the assistant to change what went wrong, or restore an individual file from its history.

Security and transfers — strict HTTPS for a connected domain.
Redirects — keeping old links working after a rebuild.

Uptime monitoring

Point your uptime monitor at /max-ai-health-check on your published domain. A healthy published site returns HTTP 200 and exactly {"service":"maxaibuilder"}. The response is not cached. The previous /maxaibuilder-healthcheck and /cmsmax-healthcheck paths remain available while existing monitors are updated. This checks that a site build with a homepage is available; it is not a test of all links or third-party services on the website.