Write These Facts Down Before an AI Builds Your Page

A bakery owner types one sentence into an AI page builder: write a landing page for my bakery. A moment later there is a finished page with a hero, a row of feature cards, a short FAQ and a contact form. It reads well. It mentions fresh ingredients and quality you can taste. Nothing on it is false, and nothing on it would help a single customer decide to walk in on Saturday morning.

That page is the normal result, and the tool did its job. It was asked for a bakery page and it wrote the average of every bakery page it has seen. What it lacked was the dozen facts that only the owner knows and never typed.

I build this kind of tool, so take the bias into account: NWM CMS generates pages and blog posts with AI, and I think that is useful. I also think it moves the hard part of a website from design to the brief. When a page takes seconds to make, the only thing that separates a useful page from filler is what you tell the generator before it starts.

Why generic pages are a real cost now

A vague page used to cost you a few customers who clicked away. Today it also costs you with the machines that read pages on a customer's behalf. When someone asks a search engine or an AI assistant which bakery near them makes gluten-free bread, the answer is assembled from pages that state things plainly. A page that says quality you can taste gives that assistant nothing to repeat. A page that says gluten-free sourdough, baked Tuesday and Friday, order by noon the day before, gives it a sentence it can quote.

So the facts sheet below serves two readers at once: the person deciding whether to visit, and the software deciding whether to mention you.

The facts sheet: write it once, use it everywhere

Before you generate a single page, open a plain document and answer these. Short answers are fine. Specific answers are mandatory.

1. What you sell, using the names customers use. Not solutions or offerings, the actual things: sourdough loaf, custom birthday cake, a box of pastries for the office, wholesale bread for cafés.
2. Where you work. The neighbourhoods or towns you serve, and the ones you do not.
3. Prices, or at least starting prices. If you truly cannot publish a price, write what the price depends on.
4. Hours and lead times. Order by noon the day before is a fact a customer can act on.
5. What you do not do. No delivery on Sundays. No wedding cakes above three tiers. Refusals build more trust than claims.
6. The question you answer on the phone most often, and your honest answer to it.
7. How someone becomes a customer: call, form, walk in, message. One primary route.
8. Anything checkable that proves you are real: the year you opened, a license number, the street you are on, the name of the person who answers the phone.

Eight answers, maybe twenty minutes of work. Paste them into the brief every time you generate a page or a blog post, and the output changes character. The AI stops inventing a bakery and starts describing yours.

Keep the second language on the same facts

Bilingual businesses get the worst version of the generic-page problem. The English page gets the attention, and the Spanish page becomes a translation of a translation, missing the price change from last month and the new opening hours. Customers who read Spanish end up with worse information than customers who read English, which is the opposite of what the second language was for.

The facts sheet fixes that too, provided both languages are generated from it. In NWM CMS every page ships in English and Spanish by default with a language switcher, and the page describes it as bilingual without translation plugins. That removes the plumbing problem. It does not remove the discipline problem: when a fact changes, change it in the sheet first and regenerate or edit both versions the same day. If you run the two languages as separate pages, the hreflang rules for bilingual sites decide which version shows up for whom.

What to check before you publish anything generated

• Every number on the page. Prices, hours, years, quantities. A generator will produce a plausible figure if you did not give it one, so any figure you did not supply should be deleted or verified.
• Every promise. Same-day, guaranteed, best in town, trusted by thousands. If you would not say it to a customer's face, remove it.
• Testimonials and reviews. If the generator wrote one, delete it. Only real reviews from real customers belong on the page.
• The form. Submit it yourself and confirm the inquiry arrives where your team will see it.

That last check is where a CMS connected to your CRM pays for itself. The NWM CMS page states that form submissions land in FracMO CRM as contacts, so the person who fills in your new landing page becomes a record in your pipeline instead of an email someone has to forward. Test it anyway. A form that silently fails is worse than no form, because you will read the silence as no demand.

Where the AI helps and where you stay in charge

The generator is good at structure and first drafts: laying out a page, writing a clean version of a paragraph you described badly, producing the Spanish version, drafting SEO titles and meta descriptions. The CMS page also lists an AI blog writer that publishes on a cadence, with you approving the drafts. That approval step is the important part, and I would not switch it off.

You stay in charge of the facts and the voice. If the draft sounds like it could belong to any business in your category, go back to the facts sheet and ask what is missing. Usually it is a price or a refusal.

There is also an honest case for not using any CMS at all. If your business needs one page that changes twice a year, a single well-written page and a phone number may be all you need, and a page builder adds nothing but a login. A CMS earns its place when you publish regularly: new services, seasonal offers, landing pages for campaigns, a blog.

A twenty-minute exercise before your next page

Take your current homepage and highlight every sentence that could appear, unchanged, on a competitor's site. Then, for each highlighted sentence, write the specific fact it was trying to say. What remains after that exercise is your facts sheet in rough form, and it will make every generated page better, in any tool.

If you want to try it on the tool I build, the NWM CMS page has the details. Bring the facts sheet, not a one-sentence prompt.

← Back to all articles