SEO
Titles, descriptions and robots directives, through the plugin the site already runs. There is no SiteHelm SEO table: the change shows up on your plugin’s own screens, and switching agents off leaves nothing behind.
Anyone with a metadata backlog, and anyone who has been burned by a tool that stored SEO data in its own table.
Each of these is carried by named operations that exist in the release you can download today. The ids under every answer are the calls involved — nothing here is a plan.
Each description is written into the provider the site actually renders tags with — Yoast, Rank Math, All in One SEO, SEOPress, The SEO Framework, Slim SEO or SureRank.
SiteHelm
content-seo-get needs edit_post content-seo-set needs edit_post The plugin’s own stored score is reported as the plugin’s, and SiteHelm’s derived findings separately. Neither is ever presented as the other.
content-seo-score-get needs edit_post content-seo-audit needs edit_posts Term metadata is read and written through the same provider, on the same precedence rules.
content-term-seo-get needs edit_posts + the taxonomy's edit capability content-term-seo-set needs edit_posts + the taxonomy's edit capability Titles, descriptions and robots directives, read and written through whichever SEO plugin the site already runs.
Needs: One of seven providers: Yoast, Rank Math, All in One SEO, SEOPress, The SEO Framework, Slim SEO, or SureRank. Where it is absent the operation refuses by name, rather than failing obscurely.
4 operations that only report. A read still asks WordPress for a capability against the object.
2 that change something — each one previewed as a diff, snapshotted, verified by reading the site back, and reversible from wp-admin.
Free, permanently. Nothing in this area moves into a paid tier later.
Precedence is fixed and published. On a site running two SEO plugins, SiteHelm reads and writes the one actually rendering the tags rather than picking one at random.
There is no SiteHelm SEO table. Metadata is written where the site’s own plugin keeps it, so the plugin’s own screens show the change and switching agents off leaves nothing behind.
Precedence is fixed and published. On a site running two SEO plugins, SiteHelm reads and writes the one that is actually rendering the tags.
content-seo-score-get reports the plugin’s own stored score, and separately the findings SiteHelm derives. It never presents one as the other.
Get the free plugin How a write is guarded
List by status, approve, hold, spam or trash, and reply beneath a comment. Everything here asks for the same permission the site’s own moderation screen asks for.
3 opsEvery area of the catalogue, by what it lets you do.
indexEvery operation on the site in one list, with capability, risk and rollback.
reference