Creogen runs the site after launch.
Building, CMS work, audits, search visibility, accessibility and performance in one operations layer, scoped to real pages instead of a report.
What Creogen is. Website intelligence and operations software for teams and agencies who are responsible for a marketing site after it launches. It combines visual building, CMS operations, continuous auditing, search and answer engine visibility, accessibility and performance in one place. It is in private development and opens first to agency partners. Creobot is separate: it is in private launch at creobot.ai and is usable without Creogen.
Why this exists
A site is a system, and nobody is running it.
A marketing site launches in good shape. Eighteen months later the pricing page contradicts the sales deck, three templates fail contrast, forty posts have no internal links, and the fastest page has quietly become the slowest. Nothing broke. It drifted, because drift is what happens when a system has no operator.
The tooling that exists is built for the launch, or built for reporting. Almost nothing is built for the middle, where somebody has to notice a problem and then go and change a page.
What happens instead
- The audit tool emails a PDF. Nobody opens the PDF.
- Analytics shows a drop. Nobody knows which page to change.
- The accessibility scan runs once, before a procurement review.
- The content plan lives in a document that stopped being true in March.
- The person who could fix it needs a developer, so it waits.
Modules
Nine jobs, one page model.
Each of these exists on its own somewhere. The point is that they share a page model, so a finding in one becomes an edit in another without a copy and paste in between.
Visual building
A canvas for composing and changing pages using the site's own components and design system, so a marketer can ship a section without opening a pull request.
CMS operations
Collections, structured fields, bulk edits and backfills. The work that scales badly by hand, which is why it is the first thing postponed and the last thing done.
Continuous audit
Findings tied to a URL and grouped by type. The fix opens beside the finding, which is the only reason anyone ever closes one.
SEO
Titles, descriptions, canonical URLs, heading structure, internal links and schema, checked against the page itself rather than against a generic checklist.
AEO
Answer engine work. A direct answer near the top of the page in plain sentences, questions asked and answered as real text, and claims specific enough to be quoted correctly.
GEO
Generative engine work. Being present and correctly represented inside generated answers, which leans on being quotable and specific rather than on keyword density.
pSEO
Pages generated from structured data through a shared template, where each page answers something specific and thin duplicates are caught before they publish rather than after a penalty.
Accessibility
Contrast, heading order, labels, alt text, focus order and keyboard paths, re-checked on every change. We ship this on our own site first, which is why this page has a skip link and a visible focus ring.
Performance
Core Web Vitals tracked per template rather than per page, so you find the template dragging forty URLs down instead of chasing one slow post.
Getting found is two different jobs now.
A person searching and a model answering are not solved by the same work. Both matter, and the second is where most sites are currently invisible.
Search engines
- Titles, descriptions and canonical URLs that are actually unique
- Heading structure a crawler can follow
- Internal links that connect related pages instead of orphaning them
- Schema that matches what is visible on the page
Answer and generative engines
- A direct answer near the top, in plain sentences
- Questions asked and answered as text, not behind hover or a canvas
- Claims stated with enough specificity to be quotable
- Structure that survives being stripped of its styling
Pages built from data
- Templates driven by a collection, so a hundred pages stay consistent
- Each page earning its place by answering something specific
- Thin duplicates flagged before they publish
Agency workflow
Built around twenty client sites, not one.
Twenty sites, four people, a retainer that promised ongoing improvement, and a month that keeps filling with something else. Creogen is aimed at that, not at a single in-house team with one site to look after.
Multiple sites in one place, findings triaged across all of them, and work a mid-weight team member can pick up without a developer unblocking them first.
Where it stands
- In private development. No public sign up, no free tier, no waitlist form that goes nowhere.
- Access opens through the agency partner programme first.
- Pricing is not set. We will not publish a number we would have to walk back.
Creogen questions.
No. It is in private development with no public sign up. The first accounts go to agency partners. If you want to be in that group, the partner page explains what we are looking for and the call is short.
No. It is about the two years after launch rather than the build. Webflow remains a good place to build sites and we still ship apps for it. Where Creogen connects to the platform you already use is one of the things partner feedback is deciding.
No. Assisted edits arrive as proposals with the evidence attached and a person approves them. Software that publishes to a live marketing site with nobody in the loop is a support ticket waiting to happen.
Pricing is not set. Early partners agree terms with us directly and keep them when the product opens up. We would rather say that than publish a number we have to walk back.
No. Creogen stays a Creoglyph product. You build the service, the strategy and the retainer around it and that revenue is yours. We would rather be blunt about this now than have it surface in a contract.
Have a website that keeps needing work?
Let us talk about turning that into an operating system instead of a monthly scramble.
Built by the two people who wrote the Webflow apps underneath it.