Publish a website and connect a domain

Local export creates files on your computer. Remote publishing sends the built website to a hosting account you control. MODO currently has integrations for Cloudflare Pages, Netlify, GitHub Pages and Vercel.

These integrations have automated coverage against simulated provider APIs. That does not certify your account permissions, plan, DNS zone or the current behavior of every live provider. Start with a disposable test site.

Publish a first site

1. Test the page Preview and, preferably, a local web export.
2. Open Publish → Web and choose the provider.
3. Enter the required account and site identifiers, then Save destination.
4. Add the requested credential through the app's credentials controls. Do not put tokens in page content or project notes.
5. Choose the intended channel and use Prepare the publish.
6. Review checks, warnings, destination and any resources that will be created.
7. Confirm Publish only when that plan matches your intention.
8. Inspect the resulting job and open the verified site address.

A prepared plan is not an upload. If the project or destination changes, prepare a new plan. A successful file upload is also not proof that the public URL and HTTPS are ready.

Use a domain you already own

1. Publish and verify the provider's default address first.
2. Enter your domain in Custom domain and save it.
3. Use the domain controls to inspect the proposed association and confirm it.
4. Copy the expected DNS records into your registrar or DNS provider's dashboard.
5. Return to MODO and check the observed DNS and HTTPS results.

MODO does not buy domains or change registrar records for you. Use the recommendations for your specific provider and account; an apex such as example.com and a subdomain such as www.example.com may need different records.

Cloudflare Pages requires association before its CNAME setup. Providers may require ownership verification or a certificate to finish provisioning. Follow the current provider dashboard if its instructions differ from an old saved checklist.

Check the result

Domain readiness requires the correct site association, matching DNS and verified HTTPS. A certificate alone is not enough. MODO checks from this computer at the displayed time; that is not proof that DNS has propagated everywhere.

If a deployment uploaded files but its public check failed, inspect the job and domain status before retrying. Do not interpret an unverified URL as a completed release.

For a code repository without website hosting, use GitHub & export.