Every name the plugin uses now starts with citedby_seo_fields_. Values stored by earlier versions are moved to the new names once, on the first visit after the update. Do not go back to 0.3.3 afterwards: it reads only the old names.<\/p>","0.3.3":"
Update the CitedBy application before installing this plugin version. Schema contract 3 prevents delayed retries from bringing back a change after Undo. Earlier applied changes remain recoverable.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.4.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[37556,5777,1117,186,1460],"plugin_category":[55],"plugin_contributors":[286253],"plugin_business_model":[],"class_list":["post-384926","plugin","type-plugin","status-publish","hentry","plugin_tags-local-business","plugin_tags-meta-description","plugin_tags-schema","plugin_tags-seo","plugin_tags-title","plugin_category-seo-and-marketing","plugin_contributors-seofields","plugin_committers-seofields"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/citedby-seo-fields.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
Keeps an SEO title and a meta description for each published page and post, and prints them\nin the page head: the title in the title tag, the description in one meta description tag.\nA page with no SEO title keeps the title WordPress gives it. A page with no description gets\nno description tag.<\/p>\n\n
It can also keep one business schema block for a page or post: a schema.org LocalBusiness (or\na more exact kind, such as Plumber) with the business's name, phone, address, area served,\nwebsite and profile links. It prints it as one JSON-LD script in that page's head. Nothing\nelse can go in the block: no reviews or ratings, no other kinds of schema.<\/p>\n\n
It is made for sites with no other SEO plugin. While another SEO plugin is active, or a theme\nwith SEO built in, it prints no title or description. A theme that prints its own title tag\nstops the title and description only.<\/p>\n\n
The business block works with no SEO plugin, printed as its own script, and with Yoast SEO\n(version 20 or later, without Yoast Local SEO), placed inside Yoast's own schema through\nYoast's public filter. When Yoast's schema names the same business, that entry is given the\nbusiness type, phone, address and area, and keeps its own name exactly as written; otherwise the\nblock is added as its own entry. Names count as the same when they differ only in capitals, in\napostrophes, full stops or commas, in \"&\" against \"and\", in spacing, or by one closing Ltd,\nLimited, LLP or PLC. It is left out whenever the page's schema already holds a local business, or\nYoast's entry names a different business, or already has a phone, address or area. With any other SEO\nplugin or an SEO theme, it prints no block and will not store one.<\/p>\n\n
It does not import anything from another SEO plugin.<\/p>\n\n
It never changes a page's content, its own title, a menu or a theme file. It adds no admin\nscreen and contacts no outside server.<\/p>\n\n
Switched off, it prints nothing and keeps what it stored. Deleted, everything it stored is\nremoved. A page or post deleted for good takes its business block with it.<\/p>\n\n
Asked for its fields by page or post id, it reads each one directly, so another plugin's\nquery filter cannot leave one out. The full list, asked without ids, goes through WordPress's\nown query: with a language plugin it may hold one language only.<\/p>\n\n
This plugin is the WordPress side of CitedBy (https:\/\/citedby.co.uk), a paid service for UK\nlocal businesses. CitedBy works out the SEO title, meta description and business block for a\npage, and sends them to this plugin through the WordPress REST API. It uses an application\npassword that an administrator of the site creates and gives to CitedBy.<\/p>\n\n
CitedBy calls the site; the plugin never calls CitedBy or any other outside server. What CitedBy\nsends: a page or post id and the title, description or business block for it. What it reads\nback: what the plugin holds for that page, its version, and whether another SEO plugin stops it\nprinting.<\/p>\n\n
Any tool holding an administrator's application password can use the same calls. CitedBy is the\none it is made for.<\/p>\n\n
CitedBy's terms: https:\/\/citedby.co.uk\/terms\nCitedBy's privacy policy: https:\/\/citedby.co.uk\/privacy<\/p>\n\n\n
Through two REST API calls at A write can say what it expects each field to hold now. The field is then written only while it\nstill holds exactly that, checked by the database in the same step as the write. If anyone has\nchanged it since, nothing is written and the answer says so, with what the fields hold now.\nThe read says Through Published pages and posts with no password. A page WordPress never shows as itself, such as a\nWooCommerce shop page, is refused, since nothing stored for it could print.<\/p><\/dd>\n Not in this version. On a network it registers nothing and prints nothing.<\/p><\/dd>\n\n<\/dl>\n\n\n\/wp-json\/seo-fields\/v1\/seo_fields<\/code>: GET reads the stored\nfields, POST writes them. Both need a user who can manage the site's options; a write also\nneeds that user to be allowed to edit the page or post. They are meant for CitedBy, which the site\nowner connects with an administrator's application password. The plugin adds no screen of its\nown.<\/p><\/dd>\nWhat if a field is changed while a write is on its way?<\/h3><\/dt>\n
conditional_write: true<\/code> when the plugin supports this.<\/p><\/dd>\nHow is the business block filled in?<\/h3><\/dt>\n
\/wp-json\/seo-fields\/v1\/schema<\/code>, with the same rights as the fields. Every write names\nthe revision it read, and is done only while the block still holds exactly that, checked by the\ndatabase in the same step as the write. Each page's block is one row in the options table,\nnamed citedby_seo_fields_schema_<\/code> and the page id, so two writers filling an empty block at the same\nmoment cannot both win. An undo puts back the block that write replaced, or removes the block\nif that write created it, and only while the block still holds exactly what that write stored.<\/p><\/dd>\nWhich pages can hold them?<\/h3><\/dt>\n
Does it work on a multisite network?<\/h3><\/dt>\n
0.4.0<\/h4>\n\n
\n
0.3.3<\/h4>\n\n
\n