42flows SEO Meta

42flows SEO Meta enables REST API write access to SEO meta fields for posts and pages. It auto-detects your active SEO plugin (Yoast SEO, Rank Math, or All in One SEO) and registers only the relevant meta fields with show_in_rest.

This plugin is required if you use 42flows to publish SEO-optimized content to your WordPress site. Without it, SEO titles, meta descriptions, and focus keyphrases cannot be set via the REST API.

Supported SEO plugins

• Yoast SEO — _yoast_wpseo_title, _yoast_wpseo_metadesc, _yoast_wpseo_focuskw
• Rank Math — rank_math_title, rank_math_description, rank_math_focus_keyword
• All in One SEO — _aioseo_title, _aioseo_description, _aioseo_keywords

What it does

• Detects which SEO plugin is active on your site
• Registers that plugin’s meta fields with show_in_rest => true for posts and pages
• Adds sanitize_callback (sanitize_text_field) and auth_callback (requires edit_posts capability)
• Does nothing if no supported SEO plugin is detected

What it does NOT do

• Does not modify your existing SEO data
• Does not add any admin pages, settings, or UI
• Does not load any JavaScript or CSS
• Does not store any data

Companion plugin installation and upgrades

When your site is connected to 42flows, 42flows may request that this plugin install, activate, or upgrade a companion plugin (42flows-content) that enables render-time features for posts delivered by the 42flows pipeline (schema markup, attribution footer, page-optimizer REST surface). The companion plugin is downloaded from https://42flows.com/plugins/42flows-content-latest.zip via the /wp-json/42flows/v1/install-companion REST route.

The route requires the requesting user to hold:

• install_plugins and activate_plugins for fresh installs (typically Administrator role)
• delete_plugins additionally when a min_version parameter is supplied that exceeds the currently-installed companion version, because the upgrade path deletes the existing companion folder before reinstalling

The companion zip URL is hard-coded in the plugin source — it is never user-supplied — so the route presents no SSRF surface. No installation, upgrade, or deletion occurs unless your site is connected to 42flows and the request is authenticated by an administrator-capability user.