Pages that sell, on your domain, wired to the CRM behind them.
Drag elements onto the page, or paste your own HTML. Every form and checkout writes into your CRM: one account, one contact record, no connector.
Start free
Build the page, take the payment, and keep the lead in one place.
Describe the page to AXL or edit it visually. Add forms, quizzes and checkout without embeds. Every response and order lands in the same CRM.
- Build. Start with AI, drag and drop, or write custom HTML and CSS.
- Sell. Put checkout, promo codes and an order bump directly on the page.
- Capture. Forms and quizzes write answers into the same contact record.
- Improve. Use A/B tests, revisions, traffic analytics and UTM data.
See layout and publishing details
A site can hold many nested pages on your own domain. Published pages are server-rendered, so a crawler receives HTML rather than an empty shell.
Choose per page: use the Default layout for separate desktop, tablet and mobile editing, or the Custom layout for raw HTML and CSS. The AI writes Custom pages and can patch one section without rebuilding everything.
Connect your own agent →Domain, page, draft, publish.
- 01 A domain comes first Add the A record AXL shows, or take a platform subdomain. SSL is automatic. Settings → Domains
- 02 Add the page Pick its parent: a page under /blog lands at /blog/your-post. Sites → Pages
- 03 Build it Start from a block or page template, drag elements, paste HTML, or brief the AI. The page editor
- 04 Preview the draft The link is secret and renders noindex, so nothing leaks. Page → Preview
- 05 Publish Visitors get the published copy; your draft keeps moving. Page → Publish
What ships on its own, and what you write yourself.
Reusable templates can apply the same head markup across your pages. Longer pieces on pages and SEO →
| The thing | Ships on its own | You add it through head HTML |
|---|---|---|
| Title and meta description | Yes, but always page name - site name | No separate SEO-title field. Write the page name as the title, and budget for the suffix. |
| robots.txt, sitemap.xml with lastmod, per-page noindex | Yes. robots.txt is editable per site; the sitemap covers published pages | Nothing |
| Open Graph tags and WebSite structured data | Yes. OG fields are page settings | Nothing |
| html lang, favicon, cookie banner, 404, search-console verification, redirects | Yes. Redirects are set per page and per domain | Nothing |
| Canonical tag, Twitter Cards | No | One reusable block in the page's head HTML |
| Article-level structured data (BlogPosting) | No | Written at publish time by your template |
Head and body injection, four levels
Account-wide, site-wide, per-page, and full passthrough on a Custom page. This is where analytics, a pixel, a canonical tag or a schema block go.
Images in the media library get a permanent CDN URL. Other files (a PDF lead magnet, a downloadable pack) get a link that expires after six hours. Plan a gated download as a product.
Search visibility and custom head code live in separate page settings tabs.
What people ask before they move a site.
Either. Custom pages accept raw HTML and CSS, published byte-for-byte. One rule: a lead form and a checkout block are wired through literal class names. Style them freely, but do not restructure them or they render without submitting.
The foundations ship server-rendered, and the table above lists them. The gap worth planning for is the canonical tag: the platform never emits one, so your head HTML carries it.
A blog here is a set of pages under a /blog parent. Categories, tags and index pages are pages you maintain, not a taxonomy the platform generates. Know that trade before you migrate.