GoDaddy Website Builder Tutorial: Start to Publish

Most GoDaddy tutorials teach you the clicks. The clicks are not the hard part — the order is. Do the four setup jobs below before you open the template gallery and the build runs start to finish without rework; skip them and you will rebuild pages you already published. This walkthrough covers the whole flow, from an empty account to a live site you have actually tested, and it hands off to the single-task procedures in this manual rather than repeating them. Everything here refers to the Websites + Marketing editor, which is what GoDaddy currently sells. The menu path in is My Products, then expand Websites + Marketing, then Manage, then Edit Website.

Set these four things before you open a template

Job one: choose the tier against the wall your site will hit, because two of those walls change how you build. A free site publishes to a godaddysites.com subdomain, carries GoDaddy's advertising, and has no HTML section and no checkout — so if your plan involves an embedded booking widget or a product page, you are on a paid tier, and it is cheaper to know that now than after ten pages exist. The walls are mapped one by one in our free-tier limits guide, and the four plans are priced at their renewals in the plans comparison.

Job two: name the inbox. Every form on a GoDaddy site carries its own Send Message To address, and the most common failure in this entire procedure is notifications routed to an address nobody opens. Decide which address receives which form before you build any of them.

Job three: write the page list on paper. The editor stacks pre-built sections onto pages, so a page you invent halfway through costs you a navigation rethink and a round of relinking. Five pages is the usual starting shape: home, services, about, contact, and one page for whatever your business is actually asked about most.

Job four: list your embeds. Anything the stock sections cannot do — a scheduling widget, a live map with custom pins, a third-party form — needs an HTML section, and custom code is a paid-plan feature. Listing the embeds now means you place them as you build rather than retrofitting them into finished pages later.

The build order that avoids rework

Open the editor and Airo will already have generated a starter site at signup — theme, copy, images, core pages — so you are editing rather than starting from a blank canvas. Work in this sequence. Theme first, because a theme is styling laid over content that lives in its own layer; swapping it later is safe, but choosing it first means every section gets judged against the look you actually have. Pages second, created as the full list from job three, so navigation settles once. Sections third, page by page, top to bottom. Text last — it is edited in a side panel rather than inline, and pouring finished words into finished layouts beats reflowing layouts around finished words. The theme procedure, including the swap-with-content-intact behavior and the backup it triggers, is in our templates walkthrough.

Before you start, check the table below against your page list. It is the same four tiers priced elsewhere in this manual, read here as capability rather than cost.

Publish, then test what you published

Nothing you do in the editor reaches visitors until you press Publish at the top right. That is the most useful fact in this manual, because it means the working copy and the live site are separate objects and you can be as messy as you like in the first one.

Once published, run the checks in this order. Load the live address in a private browser window, because your own browser will serve a cached copy and make a stale page look current. Submit your own contact form with a reply address you control, confirm the notification email arrives — check the spam folder, where first-time form mail usually lands — and then confirm the same submission is sitting in the Conversations inbox. The full form procedure, including which fields can be renamed and which two cannot be deleted at all, is in our guide to adding a form. Open every page on a real phone rather than a narrowed desktop window, particularly any page carrying an embed. Then click every navigation item and every button on the site, including the ones you are certain about.

If a check fails, do not start editing over the top of the damage. The builder gives you Undo and Redo in the top bar for the mistake you made a minute ago, and Site History under Settings for the state the site was in last Tuesday — with nothing in between, so pick the right tool before you click. Save a manual backup before anything structural. And if you have not bought a plan yet, the seven-day Premium trial from GoDaddy's builder page opens the whole paid feature set, which is the honest way to find out whether your embed list works here before the first invoice exists.

Jobs this tutorial hands off

Adding code and third-party widgets

The HTML section accepts HTML, CSS, and JavaScript, and it is where iframes, chat widgets, review feeds, and third-party forms belong. Two rules save afternoons: prefer percentage widths so an embed shrinks politely on a phone, and never paste an analytics or advertising pixel into a code section — those connect through the editor's Settings area instead and fire sitewide. The procedure is in our guide to adding HTML.

Taking the site down again

Unpublish, under Settings, swaps the whole site for a Coming Soon page while every page stays editable behind it. It does not touch your billing, which keeps renewing at full price whether the site is public or not — that catches people out constantly. Deleting is a different act with no undo and no recycle bin. The unpublish procedure covers the safe version.

When the builder is the wrong tool

If your embed list keeps growing, or the sections refuse to arrange themselves the way the design in your head needs, the problem is the builder rather than your build order. Owners who want to arrange things themselves generally get further on Hostinger's Premium builder plan, at a $2.99 monthly intro on a 48-month term, which runs a grid editor with real drag-and-drop. That is a platform decision rather than a tutorial step, and it is worth making before you build, not after.