Connect a Custom Domain to Your Website or Web App After Deployment

Review What Depends on the Live URL

Before changing the domain, use your AI coding assistant to identify anything in the project that depends on the live URL.

Production Domain Review

Finds everything in the project that depends on the live URL — site and app URL environment variables, authentication redirects, OAuth callbacks, CORS or allowed origins, API base URLs, webhooks, payment return and callback URLs, email confirmation and password-reset links, canonical/sitemap SEO configuration, and any hard-coded localhost, temporary, preview or old production URLs — changes nothing, and returns a short checklist of exactly what to update once the production domain is connected.

Review this project specifically for connecting its final production domain. Identify anything that uses or depends on the website URL, including: - environment variables containing site or app URLs - authentication redirect URLs - OAuth callback URLs - CORS or allowed origins - API base URLs - webhooks - payment return or callback URLs - email confirmation or password-reset links - canonical URLs, sitemap, or SEO configuration - any hard-coded localhost, temporary, preview, or old production URLs Do not change anything yet. Give me a short checklist showing exactly what needs to be updated after I connect the production domain.

Keep the checklist for Step 3.

Connect the Domain in Hostinger

Open the live project in Hostinger and choose Connect domain.

Hostinger Your live project Connect domain

Enter the domain you want to use and follow the connection flow.

Point the Domain's DNS at the Deployment

If the domain already uses Hostinger DNS, Hostinger can handle the required configuration.

If the DNS is managed somewhere else, such as Cloudflare or another registrar, add the required DNS records there instead.

IMPORTANT

Do not remove unrelated records used for email or other services.

NOTE

Hostinger allows Web Apps running on temporary domains to be connected to a custom domain afterward, and SSL is installed automatically once the connection completes.

Replace Temporary URLs With the Final Domain

Use the checklist from Step 1 to replace temporary or development URLs with the final domain where required.

Example production URL

https://yourdomain.com

Update the relevant services and production environment variables.

Pay special attention to:

Authentication redirects

OAuth callbacks

Supabase Site URL and Redirect URLs

CORS / allowed origins

Webhooks

Payment callbacks

Email links

Public site URL environment variables

IMPORTANT

If you change environment variables used during the build, rebuild or redeploy the project afterward.

Update Supabase Auth for the Production Domain

For Supabase Auth, the production Site URL should use the real domain.

Supabase Auth URL Configuration

https://yourdomain.com

https://yourdomain.com

Site URL

Required authentication redirect URLs should be added to the allowed list.

Verify the Production Domain

Open the production domain and verify:

The domain loads the correct website or web app

HTTPS is active

The root domain works

www works or redirects correctly where required

Important pages and routes work

Authentication redirects correctly

Forms and APIs work

External services use the correct production URL

Email still works if the domain has existing mail records

The temporary or old domain is no longer being used where it should not be

NOTE

DNS changes may not appear everywhere immediately. Hostinger states that propagation can take up to 24 hours in normal cases.

Your website or web app is now running on its production domain.