An AI auto-writing website is a content production system wrapped in a website, and the two must be specified separately. The build is commissionable when you can name who approves each draft, which fields the CMS must carry, and which tests prove the site is finished. This guide turns a vague request for an 'SEO website with AI content' into a brief and acceptance checklist you can send to suppliers before asking for a fixed estimate.
Separate Content Automation From Ranking Promises
AI writing tools generate drafts. They do not guarantee positions in search results, and no supplier should bundle the two into one promise. Split the contract into two tracks.
- Build track: the website, CMS, metadata, sitemap, analytics, lead forms and deployment. These are deliverables you can inspect and accept.
- Content track: the workflow that produces drafts, the review gates, the prompt templates and the publishing log. Also deliverables, but measured by process compliance rather than rankings.
Ranking outcomes depend on competition, domain history, search engine policy and quality judgements made outside the contract. Ask instead for process commitments you can verify: how many pages a batch covers, who reviews, how the revision loop works, and where the record of published content is kept.
Agree what GEO means in your project. Generative engine optimisation is a label covering content structure, entity clarity and machine-readable markup, not a separate guaranteed channel. Ask the supplier to list the concrete changes they will make — structured headings, answer-style sections, schema fields, internal linking — so you can check them at handover.
Search engines publish their own guidance on AI-generated content and spam policy, and it changes. Ask the supplier to confirm they follow the current published guidance, and verify current requirements with the search engine's own documentation rather than relying on a proposal.
Define the AI-Assisted Content Workflow and Human Review Gates
A workflow description is worth more than a feature list. Require a written flow with named stages and a gate at each one.
- Brief. Per-page brief covering target reader, the question the page answers, required sections, internal links and the call to action.
- Draft. The AI generates from the brief using stored prompt templates, not free-form chat.
- Fact and claim check. A human confirms every number, date, name and capability statement against a source the business owns. Unsupported claims are deleted, not softened.
- Editorial pass. A human edits for accuracy, tone and originality; the reviewer is a named role.
- Approval and publish. Only approved drafts reach the CMS as published; everything else stays in draft.
- Log entry. Record prompt version, model, reviewer, date and final URL.
Write the gates into the contract. Specify who the reviewer is by role, the maximum number of drafts in review at once, the expected review turnaround, and what happens when a draft fails the fact check.
Require the technical controls that make the feature operable: secure key handling so API keys never sit in the browser or the repository, usage limits per day or per batch, and logs of each generation request. The AI API integration quote checklist details the limits, logging and key-handling items to request.
Specify CMS, Metadata, Sitemap, Analytics and Lead Forms as Deliverables
The usual starting scope for an independent SEO/GEO website covers a homepage, service pages, lead form, CMS or admin panel, SEO metadata, sitemap, analytics and Cloudflare-ready deployment. Your brief should convert each phrase into an explicit acceptance item with an owner and a test.
| Deliverable | What to specify | How to verify at handover |
|---|---|---|
| CMS | Content types (page, article, service, author), fields per type, who can publish versus draft, whether edits are versioned | Log in as each role; create, edit, unpublish and restore one page; confirm version history |
| Metadata | Per-page title, description, canonical URL, Open Graph fields, and whether each is editable in the CMS | Edit metadata on one page, publish, and inspect the rendered page source |
| Sitemap and robots | Sitemap generated from published content only; robots rules stated explicitly | Confirm a draft page is absent from the sitemap and a published page appears |
| Analytics | Which tool, which events count as a lead, and who owns the account | Trigger a test submission and confirm the event appears in an account you own |
| Lead form | Required fields, spam protection, notification recipient, storage location, data handling note | Submit from an external network; confirm receipt and the stored record |
| Deployment | Hosting account ownership, environment separation, backup or export method | Take ownership of the accounts and run one restore or export |
Two ownership points decide whether you can change suppliers later: the domain and hosting accounts should be in your name, and CMS content should be exportable in a standard format. Get both in writing.
If the site will carry product or service data that later moves into a business system, plan the data model now. The spreadsheet to business system guide explains how to scope that migration before it becomes rework.
Set Acceptance Tests for Content Quality, Editing and Handover
Acceptance tests turn opinions into pass or fail. Agree them before development starts and attach them to the brief.
Content tests
- A sample of published pages is checked against the per-page brief: every required section present, the stated question answered in the opening, no claim the business cannot support with evidence.
- No page contains placeholder text, unverified numbers, invented customer names or fabricated citations.
- Duplicate or near-duplicate pages across languages are identified and handled deliberately rather than left to accumulate.
Editing tests
- A person outside the build team edits one page end to end using only the delivered documentation.
- The reviewer can reject a draft without developer involvement.
Handover tests
- Source code, documentation, prompt templates and the content log arrive together.
- Accounts for domain, hosting, CMS, analytics and AI provider are transferred to the client.
- The supplier walks through one complete content cycle live: brief, draft, review, approve, publish, log.
Record each result in a signed acceptance note. A supplier who resists written acceptance criteria is telling you how the project will be run.
Questions to Ask Before Comparing Fixed Estimates
Fixed estimates are only comparable when the scope behind them matches. Send the same brief to every supplier and ask these questions in writing.
- Which pages, templates and content types are included, and what is explicitly excluded?
- How many review cycles per page are included, and what happens after that?
- Who writes the prompt templates, and do I receive them?
- Which AI provider and model are used, and can I change provider later without a rebuild?
- Are usage limits and cost controls configured, and who pays the API bill?
- What does the handover pack contain, and are the accounts in my name?
- What are the acceptance tests, and who signs them off?
- What happens after launch — patching, content support, monitoring?
Two estimates that differ in price usually differ in review cycles, content volume or account ownership. Normalise those three before comparing anything else.
FAQ
Can an AI auto-writing website guarantee search rankings?
No. Content automation changes how quickly drafts are produced and how consistently they are structured. Ranking depends on competition, domain history, search engine evaluation and factors outside any build contract. Ask for process commitments you can verify — review gates, metadata control, sitemap correctness, page quality — and treat ranking projections as marketing rather than specification.
Who is responsible for AI-generated content published on my site?
The publisher is responsible for what appears under its name, which is why the human review gate matters. Require a named reviewer, a fact-check step against sources you own, and a log of who approved each page. Ask the supplier to state in the contract that drafts are never published without your approval, and confirm current disclosure and content rules with the relevant authority in your market.
What should I own at the end of the project?
The domain, hosting account, CMS account, analytics property, AI provider account and source code. Also ask for the prompt templates, the content log and the editorial documentation. Account ownership is the clearest test of whether you can change suppliers later without starting over.
How do I keep AI writing costs from running away?
Require usage limits per batch and per day, logging of every generation request, and a named person who approves large runs. Ask whether the API account is billed to you directly so consumption is visible, and ask for a documented off switch. The AI API integration service scope covers key handling, limits, logs and cost controls as named deliverables.
Brief to Send Before Requesting Estimates
Write down the site's purpose, the languages it must support, the page types and roughly how many of each, the content types the CMS must hold, and the lead-capture events you count as conversions. State your existing accounts — domain, hosting, analytics, AI provider — and which systems the site must connect to. Attach your review-gate rules and acceptance tests, then ask each supplier to respond to them point by point rather than with a headline figure.
Manboo Studio builds independent SEO/GEO websites with AI-assisted content workflows and the surrounding CMS, admin panel and AI integration work. If you are assembling this brief, you can compare the independent website development scope, then discuss requirements with your page list, language set and acceptance criteria in hand.