What a website maker should actually make

Three words, three different promises

An editor gives you a canvas. You place boxes and type into them. The output is whatever you managed to make.

A builder adds hosting, a domain step and some ready layouts to the canvas. It still expects you to write the words.

A maker should make the thing. Website Builder Studio is closest to that word. You answer questions, and the pages, links, schema and form are made from your answers.

None of the three words is wrong. They just describe how much of the work is left to you when the trial ends. The rest of this page is the list of what should come out.

Pages that are written, not filled in

The first thing a maker should make is the page itself: a title, a description, one main heading, the copy, an answer capsule near the top, and the questions people ask.

Here those are written from a conversation about your business. A uniqueness check strips city, state and industry names before it measures. A page that is only a swapped town scores as a copy and does not publish.

You still decide what is true. The builder writes from what you said, and the in-app assistant changes any line when you ask.

Links between the pages

A single page is a flyer. A site is pages that point to each other. Each service page should link to the areas it covers and back to the services list.

The builder wires internal links between related pages and adds breadcrumbs, so a visitor and a search engine can both find their way.

Breadcrumbs sit at the top of each page and show where it lives. Search engines read them the same way you do.

Structured data that says who you are

Structured data, often called schema, is a small block of facts a machine can read: your name, what you offer, where you are. Search engines and the AI answer engines like ChatGPT and Google's AI answers read it.

Every site the builder makes carries it, written from the same answers as the pages. You never edit the block by hand.

Ask the in-app assistant what the structured data on your site says and it explains it in plain words.

A form that actually reaches you

A form that lands in a folder nobody opens is decoration. A maker should deliver each submission where you work.

Here a lead form is on every page. Each submission goes to HubSpot, Salesforce, Zoho CRM, Pipedrive, GoHighLevel, Slack, Microsoft Teams, SMS, email or any webhook. You paste one credential, and a Send test lead button proves the connection before a real lead flows.

Every delivery is signed. Every lead has a status and a note on the Leads screen, and you can export every lead to a spreadsheet in one click.

A sitemap and a real not-found page

A sitemap is a list of your pages that search engines fetch. A not-found page should say so with a real 404 status, not a cheerful home page that pretends the address exists.

Both are made for you. The sitemap covers every page, and every site has a branded not-found page served with a real not-found status.

The sitemap is what you hand to Search Console. Paste your verification token into the one field for it, and the site carries it.

A checklist to judge any maker's output

Run this on any tool's trial, including ours. It takes ten minutes and does not need a developer.

• Open two pages and read the titles in the browser tab. Are they different and specific?
• Does each page have exactly one main heading, and does it say what the page is about?
• Swap the town name out in your head. Is the page still different from its sibling?
• Type a wrong address. Do you get a real not-found page, and does it return 404?
• Fill in the form. Where did it land, and how long did it take to arrive?
• Can you export the leads and download the site files, or are they trapped?
• Is there a check that runs before anything publishes, and does it tell you why a page failed?