| 开发者 | haasder |
|---|---|
| 更新时间 | 2026年11月2日 17:05 |
| PHP版本: | 7.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/seoptimate/v1/post-types (the public post types with a REST route) and /seoptimate/v1/acf-structure?post_type=... (the ACF field groups and fields of one post type: field type, required flag, choices, repeater sub fields and flexible content layouts). They return structure only, never content or field values.No. It only makes existing SEO fields writable through the standard WordPress API, for users who could already edit them. Changes only happen when you approve a proposal in SEOptimate.
Then the plugin registers nothing. A separate SEO title and description require an SEO plugin; SEOptimate will tell you so honestly.
No. Yoast SEO stores the SEO data of categories and brands in a single site option instead of on the term itself, and that option cannot be written through the REST API. SEOptimate then links you directly to the edit screen of that category or brand.
Only the structure of your site, and only when you have connected it with an application password. The post-types endpoint returns your public post types with their name, label, REST route, taxonomies and whether the connected user may edit and publish them. The acf-structure endpoint returns, for one post type, the ACF field groups and their fields: name, label, field type, whether it is required, the available choices, repeater sub fields and flexible content layouts. No post content, no field values, no users, no settings and no visitor data are read. Both endpoints answer only to a logged-in user who may edit that post type; without ACF the acf-structure endpoint returns an empty list with a notice.