marketing changes, as pull requests.

from ticket to merged, then a verdict.

1. 01

   A ticket with a brief

   From a report, a loop or you: page URL, headline, sections, calls to action, schema and design notes.

2. 02

   A pull request

   The agent reads the repository, reuses its components and icons, writes the change and opens a pull request.

3. 03

   A preview

   Cogny Sites builds a preview deployment and posts the URL on the pull request.

4. 04

   A visual check

   A visual review browses the preview and flags gaps against the brief, like a missing section or a CTA below the fold.

5. 05

   You merge

   Or ask for a refinement in writing and it pushes a new commit. Pull requests never merge themselves.

6. 06

   A verdict

   Merging moves the ticket to analysis. Search Console and GA4 decide: worked, partial, didn't work or inconclusive.

what it ships well.

• Pages

  Landing pages, articles, comparison pages and FAQ sections, built from your own components.

• Search details

  Meta titles, schema markup and internal links, the small changes that add up.

• Your conventions

  It reads the repository's own CLAUDE.md or AGENTS.md, and can be kept to one directory of a monorepo.

• Broken builds

  Fix Builds lets it repair a failed build on its own pull request, up to a number of attempts you set.

what you ask for, in plain words.

• “Build a landing page for our spring campaign, with an FAQ and a demo form.”

  A new page from your own components, opened as a pull request with a preview.

• “Rewrite the meta titles on the ten pages with the lowest click-through rate.”

  Read from Search Console, changed in code, measured seven days after the merge.

• “Add FAQ schema to the pricing page and link it from the three top blog posts.”

  Schema markup and internal links in one diff.

• “Write a comparison page against our main competitor.”

  A full page in your site's layout. You review the claims before you merge.

what to expect.

• Text first

  It can generate images, but not at the level of a human creative. Upload your own assets and let it place them.

• It can misread a spec

  A singular slug where you wanted plural, a section in the wrong order. The review step is for that; a written refinement fixes it.

• Locked stacks

  Client-side apps and no-code builders block both the agent and search crawlers. WordPress works, with posts landing as drafts.

• Credits

  Coding is the most credit-intensive thing Cogny does. A meta-title rewrite costs a few credits; a full page, a couple of hundred.

built for server-rendered sites.

Next.js on Vercel, Netlify or Cogny Sites is the target. Cogny Sites builds Next.js, static, Remix and Astro, with a preview for every pull request. You can keep hosting elsewhere and use it only for previews.

Setup: GitHub, Cogny Sites and CMS sites