Description
ROAS Master is a service by Boost Media that prepares SEO titles and meta descriptions for the pages of a site. The site owner reviews every change on an approval page, and only the approved changes are written to the site, through the WordPress REST API.
WordPress lets an outside service write a page’s content through its REST API, but not the SEO title and the meta description: Yoast SEO keeps them in two protected fields (_yoast_wpseo_title, _yoast_wpseo_metadesc) that its own REST API only reads. This plugin registers exactly those two fields for the REST API, for pages and posts, and nothing else.
- With Yoast SEO: the plugin opens the two fields. Yoast SEO keeps printing them, as always.
- Without an SEO plugin: the plugin also prints them: the page’s title (the browser tab and search results) and the
<meta name="description">tag. - With Rank Math, All in One SEO, SEOPress or The SEO Framework: the plugin prints nothing; that plugin owns the page’s head.
Google Tag Manager (optional). When the site owner approves it in ROAS Master, the plugin prints the site’s Google Tag Manager container: Google’s own snippet at the top of <head> and its <noscript> part right after <body>. Only the container id (GTM-XXXX) is stored, in one option; no other code can be set. Until an id is set, nothing is printed and nothing is loaded.
Site keys (optional, 1.3.0). Two small values a search engine asks a site owner to put on the site, written through GET|POST|DELETE /wp-json/roas-seo-fields/v1/site-keys by a user who may edit other users’ pages (an Editor or an Administrator): the IndexNow key — the plugin answers /<key>.txt at the site root with the key, as the IndexNow protocol asks (https://www.indexnow.org/documentation), only when WordPress answers the root of its host — and Bing’s site verification — the plugin prints <meta name="msvalidate.01" content="<code>" /> on the front page. Each value is checked against its pattern before it is stored; DELETE ?key=indexnow or ?key=bing takes exactly that one off. Until a value is written, nothing is served or printed.
Form submissions (optional, 1.4.0, off by default). When the site owner turns it on in ROAS Master, a submission of a form made with Elementor Pro, Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Ninja Forms or Jetpack Forms is also sent to the site owner’s ROAS Master lead desk, so a lead from the site is handled with the leads from the ads. See «Form submissions (external service)» below. Until it is turned on, the plugin adds no form hook, sends nothing and sets no cookie.
What it does not do:
- It sends no request to any other server unless the site owner turned on the form submissions. A visitor’s browser loads Google Tag Manager only when a container id was set.
- It adds no database table and no admin screen. Its options are the Google Tag Manager container id, the two site keys and an approved robots.txt, each only when one was set; deleting the plugin removes them.
- A write is stored only when the logged-in WordPress user may edit that page or post (
edit_post). An empty value brings back the default title. - Deactivate or delete it and the fields are closed again. Nothing is deleted: the titles and descriptions stay in the page’s fields, and Yoast SEO reads them if it is installed later.
The plugin answers a read-only REST route, GET /wp-json/roas-seo-fields/v1/status (users who can edit posts), with its version and mode, so a connected service can see that it is active. The container id is read and set at /wp-json/roas-seo-fields/v1/tracking, only by a user who may add scripts to the site (unfiltered_html).
The plugin works on its own: any REST client with a WordPress user that may edit the page can read and write the two fields. It does not require a ROAS Master account.
About ROAS Master
ROAS Master (https://roas-master.boostmedia.co.il/) is the service this plugin was written for. The plugin itself never contacts it. When a site owner connects a site to ROAS Master, the service calls the site’s REST API with the WordPress user and application password the owner gave it. Its terms: https://roas-master.boostmedia.co.il/terms . Its privacy policy: https://roas-master.boostmedia.co.il/privacy .
Google Tag Manager (external service)
Only when a container id was set, every page tells the visitor’s browser to load that container from Google Tag Manager (https://www.googletagmanager.com/), as with any Google Tag Manager installation; what the container then loads is configured by the site owner in Google Tag Manager. Without an id nothing is loaded. Google’s terms: https://marketingplatform.google.com/about/analytics/tag-manager/use-policy/ . Google’s privacy policy: https://policies.google.com/privacy .
Form submissions (external service)
Off by default. It is turned on only by an administrator (manage_options) through POST /wp-json/roas-seo-fields/v1/leads with the address of the site owner’s ROAS Master lead desk (https://roas-master.boostmedia.co.il/) and a key, and turned off with DELETE on the same route; GET /wp-json/roas-seo-fields/v1/status says leads: on or off (never the key).
- What is sent: for each form submission, the form’s name and id, each field’s label, type (phone, e-mail, text, message) and the value the visitor typed, the address of the page the form is on, the page the visitor came from, and the advertising click ids and campaign tags of the visitor’s landing page (
gclid,gbraid,wbraid,utm_*). No IP address and no browser identification are sent. - To whom: only to the address the administrator set (ROAS Master, operated by Boost Media).
- When: once per submission, after the form has already answered the visitor. If the lead desk cannot be reached, the form works exactly as before.
- Cookie: while it is on, a visitor who arrives from an ad link gets the first-party cookie
roas_msf_click(90 days) holding those click ids and campaign tags, so that a form sent later in the visit carries them. - How to turn it off:
DELETE /wp-json/roas-seo-fields/v1/leads, or deactivate the plugin. Deleting the plugin removes the setting.
ROAS Master’s terms: https://roas-master.boostmedia.co.il/terms . Its privacy policy: https://roas-master.boostmedia.co.il/privacy .
The plugin’s source is the plugin itself: one readable PHP file, with no build step.
robots.txt (1.3.0): WordPress serves /robots.txt itself when the site root holds no robots.txt file. The route /wp-json/roas-seo-fields/v1/robots (administrators only, manage_options) reads what WordPress serves, and stores a new robots.txt only when the request names exactly what is served now (so a change prepared earlier never overwrites a newer one), no robots.txt file wins over WordPress, and the site is public. The stored text is printed through the documented robots_txt filter. Sending null removes it, and WordPress serves its own file again. Deactivating the plugin also brings back WordPress’s own file.
Privacy
Unless the form submissions are turned on, the plugin collects no data, sets no cookie, stores no personal data and sends nothing to any server. When they are turned on, each form submission is sent to the site owner’s ROAS Master lead desk and the roas_msf_click cookie is set, as described in «Form submissions (external service)» above. It stores only the SEO title and meta description that an authorised user writes to a page or post, in that page’s own fields, the Google Tag Manager container id when one was set, the two site keys (public values a search engine reads on the site) when they were set, and an approved robots.txt when one was written. Once a container id is set, the visitors’ browsers load that Google Tag Manager container, and what it collects is governed by the container’s own configuration and Google’s privacy policy (see «Google Tag Manager (external service)» above).
Installation
- In the WordPress admin: Plugins > Add New Plugin, search for “ROAS Master SEO Fields”, Install, Activate.
- That is all. There are no settings.
A connection whose WordPress user may install plugins can also install it through the WordPress REST API (POST /wp-json/wp/v2/plugins with the slug roas-master-seo-fields). ROAS Master does that only after the site owner approves that step.
FAQ
Do I need Yoast SEO?
No. With Yoast SEO the plugin opens Yoast’s two fields; without any SEO plugin it prints the title and the description itself.
Does it load anything from Google?
Only when a Google Tag Manager container id was set (by you, or by ROAS Master after you approved it). Then the visitor’s browser loads that container from Google, as with any Google Tag Manager installation. Without an id nothing is loaded.
Who can write the fields?
Only a logged-in WordPress user (for example through an application password) who may edit that page or post. Values are stored as plain text (sanitize_text_field).
Does it change anything when it is activated?
No. Until a value is written to a page, the page prints exactly what it printed before.
What happens when I remove the plugin?
The REST API stops accepting the two fields. The values that were written stay where they are; nothing is deleted.
Is this plugin made by Yoast?
No. It is made by Boost Media and is not affiliated with Yoast. It uses the same two field names so that Yoast SEO, when it is active, prints what was written.
Changelog
1.4.0
- Optional, off by default: form submissions of Elementor Pro, Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Ninja Forms and Jetpack Forms are sent to the site owner’s ROAS Master lead desk, after the form answered the visitor; turned on and off by an administrator through
roas-seo-fields/v1/leads. - The status route says whether form submissions are on.
1.3.0
- Optional site keys: the IndexNow key file at the site root and Bing’s site-verification tag, through
roas-seo-fields/v1/site-keys. - robots.txt: an administrators-only REST route reads what WordPress serves at /robots.txt and stores an approved new one, printed through the robots_txt filter; null brings back WordPress’s own file. Deleting the plugin removes that option too.
1.2.0
- Optional: prints the site’s Google Tag Manager container (Google’s two snippets) once its id is set through
roas-seo-fields/v1/tracking. - The status route lists the features and the container id.
1.1.0
- First release in the WordPress.org plugin directory: readme, text domain, plugin URI, license notice.
- Prints the title and the meta description on a site without an SEO plugin.
- A read-only status route (
roas-seo-fields/v1/status).
1.0.0
- Opens Yoast SEO’s title and meta description to the WordPress REST API.