Your SEO plugin, SureRank or SEOPress, owns the page head: the search title, the meta description, canonical, robots, share tags, sitemap and schema. Delta never prints them itself. What Delta adds is timing: the agent fills them in the same request that writes the page.
Who owns what
SureRank and SEOPress each have their own screens, templates and checks, and they keep working as before. Delta works through the plugin’s own save, so what you set in its screens stays, and the plugin’s own checks apply to what the agent writes.
The agent sees which plugin runs and how many published pages have no description of their own. Run two SEO plugins and the agent warns and asks you to keep one.
Set with the page
When the agent creates or updates a page, it can set the search title, the meta description, a canonical address, noindex and nofollow, and the title, description and image used when the page is shared, all in the same request as the content. A new landing page arrives with its SEO done.
“Create the Pricing page from the brief, with the search title Delta pricing and a description that names the one-licence model.”
A value you remove goes back to the plugin’s template. The search title replaces the plugin’s whole title template, so if you want the site name in it, say so.
Designed pages
A page designed by Delta keeps its HTML outside the block editor, where SEO plugins cannot see it. Delta hands the plugin the page’s own text instead: the excerpt when there is one, otherwise the words of the page. Automatic descriptions and the plugin’s content checks then work on designed pages as they do on posts.
The start of a page rarely makes a good description. Write a real one for the home page, landing pages and every page someone would search for. Do not change the plugin’s site-wide description template to work around a missing one, because native posts depend on it.
“Which published pages have no meta description? Write one for each.”
The plugin’s own tools
Beyond one page’s values, the agent uses the plugin’s own abilities: site-wide title and description templates, robots.txt, the sitemap, term SEO, schema. Each plugin lists those only while you turn on a setting of its own. The agent asks; it never works around the switch.
| Plugin | Setting | Pro edition adds |
|---|---|---|
| SureRank | SureRank → Tools → MCP → Enable MCP | Per-type templates, redirects and more schema types. Its redirects live in SureRank’s own screen |
| SEOPress | SEO → Advanced settings → Advanced → Abilities API → Expose abilities to AI agents and external tools | Redirections, schemas, AI generation and the technical audit |
Delta can install SureRank and SEOPress. The Pro editions you install yourself. Needs SureRank 1.10 or SEOPress 10 or newer.
The SEO plugin’s own data stays with the plugin. The agent reads a page’s SEO values through Delta, not from the plugin’s raw fields, and a request that tries to write those fields directly is refused.
Coming Soon
While the Coming Soon gate is on, the SEO plugin’s robots tag says noindex, nofollow, as Delta’s own tag does. Nothing is indexed before launch.
For developers
seo on delta/create-page, delta/create-entry and delta/update-page takes title, description, canonical, noindex, nofollow, socialTitle, socialDescription and socialImage (an attachment id or a URL). Send only the keys that change; null or an empty string removes the entry’s own value. noindex: false is a value of its own on SureRank (the page is indexed whatever the per-type setting says); SEOPress has no per-post index value, so there it equals null.
delta/get-page returns seo with the entry’s own values, effective (what the head prints) and descriptionSource: set, derived or template. delta/list-pages rows carry seoDescriptionMissing. get-design-context.seo names the provider, counts entriesWithoutDescription, and lists under detected any SEO plugin that runs without a Delta integration.
Warnings: seo_no_provider (no supported SEO plugin runs; the rest of the write was saved), seo_not_saved (the plugin refused the values), seo_two_plugins. The plugin’s own post meta (surerank_*, _seopress_*) stays out of meta in answers; meta input naming those keys is refused before anything is written; includePrivateMeta returns them when you need the raw rows.
SureRank’s abilities are surerank/*; the two *-seo-checks abilities store results, so they count as writes. SEOPress’s are seopress/*; analyze-post-content stores its result, so it counts as a write, and PRO’s generate-* abilities spend the owner’s AI credits.