Gen8

Maintaining website content

Capability · route: native

Pages that stay current without anyone publishing unnoticed

Website content quietly becomes outdated: a price is wrong, a service has a different name, a page has lacked a clear next step for months. This workflow tracks that backlog and proposes the change. Publishing remains a separate human action.

Book an introduction
  • Scoping first, then a proposal
  • EU hosting
  • You stay in control
A large rounded rectangle with green bands at the top and bottom, an orange middle band and a dark green hook on the left.

Website

At a glance

Route: native
Control: human approval
Systems: Gen8 websites, WordPress, Framer

What happens

From signal to proposal

The workflow reviews the pages you have designated and compares them with the correct source: your service overview, a product list or new text from a meeting. Where text differs or is missing, it writes a concrete proposal: this paragraph becomes that paragraph, this page lacks a next step, this title is too long for a search result.

Each proposal shows the difference from the current text. An editor approves, edits or rejects. Only then is the page updated, and you take the site live yourself — publishing never happens as a by-product of a workflow.

How it works

Step by step

  1. Selection

    You designate the pages included and the authoritative source. Pages you do not designate stay out of view.

  2. Compare

    The workflow puts the current text beside the source and notes what is outdated, contradictory or incomplete on each page.

  3. Proposal

    A concrete text proposal per page showing the difference, plus a short reason why it improves on the existing text.

  4. Editing

    An editor approves, edits or rejects. Rejected proposals remain in the log so you can see what was considered.

  5. Publish

    Approved text is saved. Taking the site live is a separate action performed by a person.

Limits

Where it stops

The workflow invents no facts. If a source lacks a price, date or name, it reports that absence rather than writing something plausible. It does not redesign the site or change its navigation, theme or structure. It does not publish itself. And it does not review legal texts: terms, privacy notices and disclaimers always go through a person responsible for them.

Evidence

What we can demonstrate

Gen8 has its own website tools that let a workflow read and update pages of a website Gen8 builds with agents, and its own integrations with WordPress and Framer. That is why the route here is native. The choice between building yourself and maintaining with AI is discussed in a website with AI or building it yourself.

Frequently asked questions

Can the workflow write new pages too?

Yes, as drafts. A new page is created in the same way as a change: as a proposal an editor reads first.

Does this work on a site outside Gen8 too?

WordPress and Framer have their own integrations. Other systems use a custom route; check the integrations.

Does the site go live automatically after approval?

No. Approval saves the text. Publishing is a separate action a person deliberately performs.

Bring one process.

Together we assess whether this workflow fits your situation, the management its route requires and where people must keep making decisions.

Book an introduction
  • Reply within one business day
  • No obligation