Site Health Engine (website build)

What it does

The Site Health Engine takes a new or redesigned website from strategy to launch: the sitemap, page wireframes, the design system (tokens, Figma Make prompts, Webflow class plans), the page content, and the pre-launch technical QA. Nexus produces every planning and build artifact; the visual design in Figma and the build inside the Webflow Designer stay with a person.

Set it up

"What's left to set up for the site build engine?" shows which steps are done for the client and the next one to do.

1. Website — Give the client's website URL.
2. Go-to-market strategy (G2M) — Build it from the website, or import an existing strategy doc.
3. Brand identity — Build it from the website and any brandbook (brand-identity agent).
4. Design system (Lumos / Relume) (optional) — Pick the Webflow design system the build uses.
5. CMS target (optional) — Where the site is built (for CMS collections and publishing).
6. Google Search Console (optional) — For indexation checks after launch.

The G2M and the brand identity are hard requirements: every later stage reads them, and the sitemap agent stops without them. A keyword universe is optional but sharpens how each planned page is checked against search demand (see the keyword universe guide).

Steps marked ✋ need a person:

• ✋ Choose the design system the Webflow build uses: Lumos or Relume (see the design system guide).
• ✋ Review and approve the sitemap sheet, then the wireframe doc.
• ✋ Do the visual design in Figma (with the Figma Make prompts Nexus writes) and build the site in the Webflow Designer.

Your Nexus team turns the engine on once the required steps are done.

Use it

Say "Build a website for the client." Nexus checks where the project stands and walks through it one stage at a time, waiting for approval between stages:

1. Sitemap — the pages the site should have, in a sheet you edit and approve.
2. Wireframe — section-by-section blueprints for each page type, in a doc you approve.
3. Design system — pick Lumos or Relume, then compile tokens, Figma Make prompts and the class plan.
4. Content — one content item per approved page, each drafted and approved separately.
5. Build and launch — the CMS collection schemas, schema markup and SEO plan, then a launch QA on the staging site.

Lost track? "Where is the client's website build?" lists what's done and the next step.

Need only one page, not a whole site? Use a page content structure, or a Nexus Pages preview (each has its own guide).

Troubleshooting

• The sitemap run stopped straight away. The G2M or the brand identity isn't on file. Build those first (G2M and brand identity guides).
• A design tool says the wireframe isn't approved. Most design-system steps read the approved wireframe. Approve it first, or use the freeform Figma Make prompt, which doesn't need one.

Prompts

• "What's left to set up for the site build engine?"
• "Build a website for the client."
• "Where is the client's website build?"

Machine twins: /help/site-build-engine.json · /help/site-build-engine.md · /help.json · /llms.txt

Reviewed 2026-10-15. In Slack, ask Nexus how do I … and it answers from this guide, with where your company stands.