Ghost
Agents write and refresh your posts, and set the canonical tags and schema most platforms will not let them touch. You decide what goes live.

Each local area page used to take us half a day to create and optimize.
With SEOmatic, we can create hundreds of pages in the same time, which helps our clients make the best use of their budget.
It's transformed how we deliver scalable SEO solutions.
Will Hawkins
Marketing Director, Digi-Business UK
Agents read your Search Console data, do the work, and prove what actually moved. You decide what ships.
14-Day Free Trial. $1 card check, refunded. Cancel Anytime.
Agents write new entries and improve the ones you already published. Every edit merges into your existing fields rather than replacing them, so nothing you did not ask to change gets lost.

SEOmatic connects to your Contentful space with a CMA token. Agents write new entries and improve existing ones, merging changes into the fields already there rather than replacing the entry wholesale.
All integrations are included in every plan. Plans start at $99/month. See pricing.
A Contentful space and a Content Management API token with write access, generated under Settings > CMA tokens. You will also need your Space ID and the environment name, usually master.
Visit our blog to learn more about programmatic SEO and how it can help your business generate more traffic, leads, and sales.
SEOmatic connects to your Contentful space through the Content Management API, then works on the entries you already have.
Step 1: In Contentful, go to Settings, then CMA tokens, and generate a personal token with write access.
Step 2: In SEOmatic, go to Connections and select Contentful. Paste the token along with your Space ID and environment, then pick the content type to work in.
Step 3: Agents read your Search Console data, find what is holding those entries back, and propose the changes with the reasoning attached.
Step 4: You approve what you want. The entry is updated and published as two steps, and if the publish half fails you are told the entry is sitting as a draft rather than being told it shipped.
New entries written from research, plus rewrites of the title, body, slug and meta on ones already published.
Contentful overwrites an entry's fields on write. Agents read it first and merge, so unsent fields survive untouched.
If your model calls it seoTitle rather than metaTitle, the change is written where your template actually reads it.
The agent arrives switched off and starts in approval mode. It earns more rope only when you give it.
SEOmatic reads the entry back from Contentful, so the before and after you approve is the real stored content.
Any change rolls back to its previous value. Low-risk edits that cost you traffic revert on their own.
Edits are written into your space's default locale field by field, leaving other locales of that field intact.
Saving and publishing are separate calls in Contentful. If the publish fails you are told it is still a draft.
Every write carries the version it was based on, so a colleague editing the same entry is never silently overwritten.
Contentful replaces an entry's fields wholesale on write, which is how integrations quietly delete the parts they were not editing. Agents read the entry first and merge into it, so a meta change stays a meta change.

Every capability your product has is something people search for by name. Agents check which ones have real demand, write an entry for each, and your front end renders them however it already renders everything else.

Customer stories are the pages buyers read last and teams write least. Agents draft them into your content model, and keep the titles and meta sharp as the ones that rank start to slip.

Every term your readers look up is an entry you do not have yet. Agents check which ones people actually search for, write the definitions, and revisit them as the set grows.
Will an edit wipe fields the agent was not changing?
No, and this is the thing to get right on Contentful. A write to Contentful replaces an entry's fields wholesale, so an integration that sends only the two fields it changed will delete everything else on that entry. SEOmatic reads the entry first and merges the change into what is already there, field by field, so anything it did not touch comes back exactly as it was.
What if my content model does not use the default field names?
It still works in the common cases. If your model calls it seoTitle rather than metaTitle, or seoDescription rather than metaDescription, the agent writes to the field your entry actually has, so your template renders the change instead of a stray field nobody reads. Unusual names outside that set are not covered, and the write fails loudly rather than quietly landing somewhere useless.
Can agents rewrite a Rich Text body?
No. Body content is written as HTML, which lands correctly in a long text field but is not the structured format a Contentful Rich Text field expects, so that write is rejected. Titles, slugs and meta are unaffected and work on any model. If your bodies are Rich Text, treat SEOmatic as handling everything around the content rather than the content itself.
Can agents set canonical tags, noindex or schema markup?
No. Contentful stores content, not page-level SEO directives, so those live in your front end rather than in the CMS. When a fix needs one, the agent writes the exact change and hands it to you. On WordPress the same agent writes all three directly.
Does the change show up on my live site straight away?
That depends on your front end, not on us. Contentful is headless, so SEOmatic publishes the entry and your site picks it up on its next build or revalidation. If your site is statically generated, the change is live in Contentful before it is visible to a visitor.
What if someone else is editing the same entry?
Every write carries the version it was based on, so if a colleague changed the entry in the meantime Contentful rejects the write instead of silently overwriting them. You are told to try again, and the agent re-reads before it does.
What if the agent makes a change I do not like?
Every edit stores the previous values before it writes, so a change goes back to what it was in one click. The agent starts in approval mode, so by default you see each change before it is applied, and entries you mark as protected keep waiting for your yes. One honest limit: restoring a field that was previously empty is handed to you rather than applied automatically, because an empty value is treated as leave alone rather than clear.
What happens to the work if I cancel?
It stays yours. Agents write into your own Contentful space, so the entries and edits are simply part of it. Nothing reverts or disappears if you stop paying.
See what agents can do on the other platforms SEOmatic connects to.
Agents write and refresh your posts, and set the canonical tags and schema most platforms will not let them touch. You decide what goes live.
Agents write and improve the entries in your Strapi collections, without disturbing the fields they were not asked to touch. You decide what goes live.
Agents write and improve the documents in your Sanity dataset, patching only the fields they own. You stay in control of what ships.
Agents fix titles, meta, content and schema on your live WordPress site. You stay in control, and every change can be undone.
Agents work through your CMS collections item by item, fixing the SEO nobody has time to maintain. You stay in control.
Agents write your blog, build the collection and landing pages you are missing, and repair the pages that are slipping. You decide what goes live.