How one page gets generated, from the title down to the links

The title and description are written to fit the page

Every generated page starts with a title and a description of its own. They are written from your answers, and they fit the lengths the check expects.

The title is what a search result and a browser tab show. The description is the line under it. Both say what the page gives a reader, in words a reader would use.

They are not a template with the service name dropped in. A page about drain cleaning and a page about water heaters get titles that say what each page is for.

One main heading, then an answer near the top

Each page has one main heading. Under it sits the answer capsule: a short, direct answer to the question the page exists for. If someone reads nothing else, they read that.

The AI answer engines like ChatGPT and Google's AI answers read the same things search engines do: a clear heading and a direct answer near the top. The capsule is written for a person first. That a machine can read it too is a description of the page, not a promise about where it appears.

Sections and the questions people ask

The body is a set of sections, each with its own heading, each written from what you said about that service or that area. No stock paragraph, no filler to reach a word count.

Near the bottom come the questions people ask about that topic, with plain answers. They are written from a conversation too, so they answer what your customers actually ask rather than what a template guesses.

If a section is missing, ask the in-app assistant to add one. If a section is wrong, ask it to rewrite that one. The rest of the page stays as it was.

Schema, breadcrumbs and links put the page in its place

A page on its own is not a site. Each generated page gets structured data that says who you are and what you offer, breadcrumbs that show where it sits, and links to the related pages around it.

It also gets a clean address and a place in the sitemap. See schema markup for websites and website navigation structure for what those parts do.

Three pages you can add in one click

An About page, a Contact page and an FAQ page can each be added in one click. The in-app assistant writes them from what it already knows about your business, so you do not answer the same questions twice.

Like every page, the Contact page carries the lead form. Each submission is delivered to the CRM, chat tool, SMS, email or webhook you connected.

You can add them during the build or later. A site that launched without an FAQ page can have one added afterwards, written from the same answers.

Images are the one part of a page that can cost extra

The words on a page are covered by your plan. AI image generation is the only extra charge, and the exact amount is shown before anything is generated.

Your own photos cost nothing to use. The in-app assistant can set the hero image for you, and add a click-to-load hero video from a YouTube or Vimeo link.

A custom page from one line, or from your own paragraphs

Need a page the plan did not include? Give the assistant one line about its purpose, and it writes the page. Or write it yourself, in plain paragraphs, at no charge.

Either way the new page gets the same parts: title, description, heading, capsule, schema, links. And it passes the same check before it publishes.

Every page passes the same check, new or old

The check is validated against Google Search Essentials and modern web standards. A page that fails does not publish, and the assistant says why.

The uniqueness part of that check strips city, state and industry names before it measures. So a new area page cannot be an old one with the town swapped. It has to say something of its own, or it does not go live.

Later edits go through the same gate. Ask the assistant to rewrite a section and the page is checked again. It is a check that runs before anything publishes, every time.