What an automated website builder automates, and what stays yours

Seven things that run without you

Automation is only useful if you know what it covers. Here is the list, in the order it happens.

None of these is a feature you switch on. They are part of how every site is built, on every plan.

• Writing. Every page is written from a conversation, from your answers, not from a stock template.
• Linking. Related pages link to each other, with breadcrumbs on every page.
• Schema. Structured data on every page says who you are and what you offer.
• Sitemap. Generated for you, so you never write one by hand.
• The check. A check that runs before anything publishes, validated against Google Search Essentials and modern web standards.
• Lead delivery. Every form submission goes to the CRM, chat tool, SMS, email or webhook you connect, signed.
• SSL. The certificate for your own domain is issued for you.

Four decisions the builder will not make for you

Automation stops at the decisions that should be yours. There are four.

Each lead has a status and a note you can edit on the Leads screen, so the team can see who has replied. Every lead across every site exports to a spreadsheet, CSV or Excel, in one click.

• The plan. You see the pages and the cost of the build before it runs, and you approve it.
• The brand. Your color, logo and hero image are set by you, through the in-app assistant. It does not guess.
• The legal pages. You upload terms and privacy, and they publish exactly as given. The builder does not write legal, medical or financial advice.
• The reply. A lead lands where you work. Answering it is your job, not the builder's.

Publishing can run on a schedule you set

A site can be scheduled to publish at a date and time in your own time zone. Set it and walk away; the publish happens when you said.

Every publish keeps a version you can roll back to. So a scheduled publish that turns out wrong is a roll back away from fixed.

Follow-up emails exist, and they are off by default

There is an option to send follow-up emails to leads who have gone quiet. It is off until you turn it on.

If you do turn it on, every lead gets a one-click stop. That is deliberate: chasing a quiet lead is a choice your business makes, not one the builder makes for you.

Lead delivery proves itself before a real lead depends on it

Connecting a CRM needs no sign-in screen. You paste one credential you generate yourself, then press Send test lead. The test arrives, or it does not, and you know before a real lead flows.

Every delivery is signed, so your end can check that it came from your site. HubSpot, Zoho and Pipedrive deliveries update an existing contact by email instead of creating a duplicate.

The places a lead can go: HubSpot, Salesforce, Zoho CRM, Pipedrive, GoHighLevel, Mailchimp, Kit, ActiveCampaign, Slack, Microsoft Teams, SMS, email, or any webhook.

Counting visits and conversions without adding a cookie

Page views and conversions are counted on the server. No analytics script and no cookie is added to your site unless you add your own.

If you want Google Analytics 4, paste your measurement ID in one field. On sites that show a banner, the tag loads only after a visitor accepts cookies. A Google Search Console token goes in another field.

What automated does not mean here

It does not mean a drag-and-drop editor, which is not offered. It does not mean an online store checkout, blog posts, or a language other than English. None of those exist today, and we say so here.

It also does not mean the site publishes without you. The build waits for your approval, and publish waits for your click or your schedule. Everything else is genuinely useful automation, and none of it is a surprise.