Lesson 13 of 16 · 35 min suggested practice

Publish a Lovable app and connect your domain

Deploy the tested version, verify it outside the editor, and connect a custom domain using the records supplied for your project.

By Ashley Kays · Reviewed November 19, 2026 · Independent learning guide

The answer: Publishing creates a live version of your project. Later code changes stay off that live version until you publish again. Verify the deployed URL before sharing it, then connect a custom domain if your plan supports it and test domain-specific behavior such as authentication redirects.

Choose the version and audience deliberately

Complete the release checklist and locate the version you intend to share. Open Publish in the editor, review the suggested address and intended audience, and inspect the security scan result. A public tutorial library needs public website access; private records still require their own authorization rules.

Finish publishing and retain the returned live URL. Do not confuse a preview link with the published site. Open the live address in a fresh browser session and confirm the page title, resource cards, and expected content match the version you reviewed.

Run a production smoke test

Search for a resource, change its topic filter, open the detail URL directly, refresh, and access the real file. Save an item and check local persistence. If the optional account version is enabled, verify sign-in and a saved-list action on the deployed domain.

A production failure can come from missing environment configuration, a file path, a route issue, or an authentication redirect. Collect the exact failing URL and behavior, then investigate that difference. Avoid rebuilding the entire project because one production setting differs from the preview.

Connect a domain using project-specific instructions

Custom domains are a paid-plan feature in the current publishing documentation. In the project's Domains settings, connect the hostname you control and follow the actual verification and routing records Lovable provides. The platform supports automatic setup or manual DNS configuration.

Do not copy a generic IP address from an old tutorial. Compare only the records relevant to the hostname being connected, and preserve unrelated email or service records. Domain connection and domain transfer are different actions; connecting does not require moving the registration to a new registrar.

Confirm the active domain and future update process

Wait for the domain to show as active, then check HTTPS, the primary address, resource paths, and login redirects. Verify any root-to-www or www-to-root behavior you configured. Use the intended primary address consistently in canonical tags and campaign links.

Make a small later change and publish it when ready. Confirm the update at the live address rather than assuming the preview has already replaced it. Keep the known-good version and a short release note so you can identify what visitors are seeing if a problem is reported.

Try this focused prompt.

Prepare Resource Shelf for publication using the tested version. Confirm the intended audience, current scan findings, real worksheet paths, and a live smoke-test checklist. After deployment, verify search, direct detail URLs, refresh, downloads, and saved favourites at the live URL. Explain where this project's exact domain verification and routing records are shown; do not invent DNS values. Once a custom domain is active, verify HTTPS, the primary address, and any account redirect settings.

Replace the sample context with your own approved facts. Review Lovable’s proposed changes before accepting them.

Evidence before the next step

Check your work.

  • The live URL serves the intended version.
  • The core workflow passes outside the editor.
  • Custom-domain records, HTTPS, and redirects are verified if configured.

Your checkmark stays in this browser. It records your own progress, not a certification.

Official sources & further reading

Reviewed November 19, 2026. Plans, terminology and interfaces can change; follow the linked documentation if your workspace differs.