The Map tab: sections, forms, data and connectors, and what a change touched
The Map tab draws the page you're building as a graph: every section, the forms inside them, the addresses those forms post to, the data each one stores and the connectors it feeds. After each change it marks what was added, changed or removed, and writes one line in the run log saying whether everything that existed before is still there.
The question it answers
When you ask an AI builder for "a shorter homepage", it may well comply by quietly dropping the section that held your contact form. The preview looks fine; the form is simply gone, and the first sign is a week without enquiries. A website structure map makes that kind of loss visible, because it shows the parts of a site that matter for what it does, not how it looks, and compares them before and after every change.
What the map shows
The Map tab sits next to Code in Pro mode. Its header gives the file, its size, the design system and a count of sections, forms, routes and connectors. Below are five linked columns:
| Column | What's in it | When it's empty |
|---|---|---|
| Sections | Every section of the page in order, from the header to the footer | Never: every page has sections |
| Forms | Each form, named (booking, contact, newsletter, sign-in), with the fields it sends | No forms on this page |
| API routes | The addresses the forms post to, such as /api/bookings | Nothing posts anywhere |
| Data stored | What each route keeps: Bookings, Messages, Subscribers, sign-in links, with the field names | Nothing is stored |
| Connectors | The tools switched on for the project, linked to the routes or data they receive | None wired, with a pointer to the dashboard's Connectors |
Lines join each section to its forms, each form to its route, and each route to the data it stores and the connectors it feeds. It's the quickest way to answer "where does this form actually go?" without reading code. Which tools can be wired in is covered on form connectors.
After a change: added, changed, removed
Every time a change is applied, whether you asked for it in words, edited the page visually or restored a version, the Map compares the new page with the one before it. Items are marked with a legend of Added, Changed and Removed, so a section whose content was rewritten shows as changed and a new FAQ shows as added.
It also checks that nothing that existed before has gone missing by accident. Every section, form and link from the previous version is looked for in the new one. A removal passes when the change asked for it: if you removed the pricing feature, losing the pricing section and the links that pointed to it is expected. Anything else that disappeared is reported. New in-page links that point at a section that doesn't exist are reported too.
The line in the run log
The result is summarised in one line under the change, with a button that opens the Map:
- Nothing broke. All the sections, forms and links from before are still here, and every in-page link lands, with the numbers of each.
- Check this: followed by what's missing after the change, such as the contact section or a booking form.
- Broken link: an in-page link that now points nowhere.
- Removed as asked, Added and Changed, listing the sections involved.
For screen reader users the result is announced too: either "Nothing broke" or a prompt to check the run log. If the line says something went missing, version history has the version from before the change, one click away.
Limits
- One page at a time. On a site with several pages, the Map shows the page open in the preview. Opening another page maps it fresh, with nothing to compare.
- Changes, not first builds. A full new build has no previous version to compare against, so it gets a map but no before-and-after line.
- Structure, not looks. It compares sections, forms and links. It won't notice that a colour changed or that a paragraph reads worse.
- It doesn't send anything. The map shows where forms are wired; it doesn't test that a submission arrives. Publish and send a test, as described in testing a website contact form.
- Pages from the design engine. The Map reads design-engine pages; it isn't drawn for model-written apps.
Questions people ask
Where is the Map tab?
In Pro mode, next to the Code tab above the canvas. Switch from Simple to Pro to see it.
Can I see which tools receive my booking submissions?
Yes. The Connectors column shows each tool you've switched on, joined to the routes or data it receives.
What does Nothing broke actually check?
That every section, form and link from the version before the change is still present, apart from anything the change removed on purpose, and that every in-page link points at something that exists.