Can your marketing team edit the website with AI agents?

You have seen marketing teams ship pages by prompting Claude or Cursor. You have also seen what happens when there is no guardrail: a new shade of blue, a second H1, a slug change with no redirect. Yes, your marketing team can edit the website with AI agents, and it can be safer than a visual builder, not riskier, when the site lives in git on Astro or Next.js, the agent reads a rules file, design tokens keep it on-brand, every change is a pull request with a preview, and main is protected. The rules file, tokens, and protected main are what keep design and SEO intact.

This page is for heads of marketing and founders who want their team to ship site changes by asking Claude or Cursor, and who worry it will wreck the design, the brand, or rankings. It pairs with measured migration off Webflow, Framer, WordPress, or Ghost: migration gets you to code; this is how marketing edits after cutover.

What it looks like on a normal Tuesday

Tuesday morning, a marketer asks the agent to add a customer logo to the homepage and tighten one answer in the pricing FAQ. The agent reads the rules file, edits the MDX or page component, and opens a pull request. A preview link lands in Slack or email. Someone opens it on their phone, checks the logo crop and the FAQ wording, leaves a comment or approves, and merges. The change is live in minutes, with history in git if you need to roll back.

Thursday, the same flow catches a mistake before production. The agent used an h2 where the page pattern expects a single h1, or it reached for a gray that is not in your token file. The preview looks wrong. Nobody merges. The agent fixes the branch. You never debugged JSX. You rejected a page that was not ready.

That rhythm is why we like previews over "trust the diff." Marketing reviews the real URL, not a wall of green text.

The five pieces that make it safe

The site lives in git, built on Astro or Next.js

Content is files the agent can read and change: MDX, React components, markdown with frontmatter. Every change has history. You can revert a bad merge without rebuilding the site in a CMS. Astro fits content-first marketing sites; Next.js fits when marketing shares UI or middleware with the product. The engagement shape is the same either way once you are on code.

A rules file the agent reads first (CLAUDE.md, AGENTS.md, or design.md)

Voice, page patterns, what not to touch, SEO rules, where components live. The agent should load this before it edits. A pointer beats a paragraph in chat that disappears next session. For how DESIGN.md and taste profiles fit product UI, see DESIGN.md and Taste Profile. For marketing pages, the same idea applies: one normative file the agent cannot skip.

Design tokens and a fixed set of sections

The agent assembles approved blocks with approved colours and spacing instead of inventing layouts. Tokens are not optional decoration. They are the list of values the agent is allowed to use. How we wire tokens for Tailwind is design tokens and Tailwind v4. Sections are the repeating patterns on your site: hero, proof strip, FAQ, CTA. New pages remix sections; they do not spawn one-off CSS.

Every change is a pull request with a preview

Nobody edits production directly. Vercel (or your host) builds a preview URL per branch. Marketing approves the preview. Engineering is not in the loop for copy and logo swaps unless something breaks the build.

Main is protected

A human approves merges to main. Agents propose; people publish. Branch protection is boring infrastructure and it is the whole game.

Keeping SEO intact when an agent edits

Put SEO rules in the same file the agent reads for brand:

• Do not change URLs or slugs without a redirect plan.
• One H1 per page; headings follow the page template.
• Unique title and meta description per route.
• Keep JSON-LD and structured data unless the task explicitly updates it.
• Alt text on images; no empty decorative alts on content images.
• Internal links only to live URLs on your domain.
• No duplicate pages or orphan routes that compete with money URLs.

Previews are where you catch violations: view source on the preview, spot-check the title tag, click internal links. For redirect maps and cutover SEO, use the migration page rather than relearning it here: Webflow, Framer, WordPress → custom.

How we run clearly.design this way (and how TeamUp does)

We edit clearly.design purely through agents. There is no CMS. We describe a change in plain language, an agent opens a PR, we check the preview and merge. Rules and tokens live in the repo. We do not ask marketing to touch the deployment pipeline.

TeamUp (hireteamup.com) migrated off Webflow. Their team was new to GitHub and pull requests but wanted to learn. Today agents are the only way they edit the site. There is no CMS; a planned Sanity setup is on hold because content in the repo plus agent edits plus previews covered what they thought a CMS was for. You may not need a CMS if your team will review previews. Several other clients edit this way too (more technical teams, unnamed).

Content belongs in the repo. Once the guardrails exist, a Slack bot or an assistant like Grok Bot can take a request from idea to preview link without you opening an IDE.

Review a documented PR, not a hand-check

You do not click through every corner of the site to bless an agent's work. A good agent PR carries a plain-language summary, what it tested, screenshots of the changed page, and a preview link. You read the summary, open the preview on desktop and mobile, and merge or send one round of fixes.

We document that pattern on our own repo. PR #132 (pre-redesign audit offer page) is a public example: summary, test plan, hero and comparison screenshots, and a walkthrough recording attached to the PR. Crop your internal PRs the same way for stakeholders: no secrets, no tokens, no private client data. You are reviewing a story about the change, then confirming the preview matches.

Optional rules excerpt (shape, not a paste of our whole file):

## Marketing site
Before editing pages under src/, read CLAUDE.md and the resource/article
patterns. Use existing sections and Tailwind tokens only. Every change is a
branch and PR with a preview; do not commit to main.

Do you have to leave Webflow, Framer, or WordPress?

Honest answer: visual builders have their own AI features and are the right call for some teams. Visual web builder for marketing teams is the decision guide when marketing still needs a canvas.

Agent editing with PR previews really needs the site in code. If you are already on Next.js or Astro, add the guardrails above. If you are not, that is the migration. The measured path off builders is Webflow, Framer, WordPress, or Ghost → custom. Framer vs custom development is the fork before you leave; this page is what "who edits it after?" looks like on the custom side.

When this is not a good idea

Skip this workflow if nobody on the team will review previews. Agents are not a substitute for judgment. If the site changes twice a year, a simpler process may be enough.

Very large editorial teams with many authors and multi-step legal approval may still want a headless CMS. That is fair. TeamUp shows non-technical teams can learn the PR flow when someone owns the habit of opening the preview.

How Clearly helps

We set this up as part of the engagement and customise it to how your team wants to work:

• Migrate the marketing site to code (or tidy an existing Astro or Next.js site).
• Write the rules file and connect DESIGN.md or marketing-specific patterns.
• Set up tokens, sections, previews, and branch protection.
• Connect Slack or an assistant so requests become preview links.
• Keep designing with you on new pages, campaigns, and product marketing.

That is not a separately priced "AI workflow project." It ships inside the subscription: Standard $4,995/mo and Advanced $7,495/mo on pricing. Book a discovery call when you want an honest read on migration plus agent editing. For keeping marketing and product one brand while you iterate, see marketing and product UI consistency.