Schema Pro Changelog

• Saving now says what was saved. Every screen answered with the same word — “Saved.” — which tells you the one thing you already knew, that you pressed the button. Each screen names what it kept.
• The confirmation message has no close button and more room at both ends: it leaves on its own after four seconds, and clicking anywhere on it dismisses it.

• Confirmation and error messages are easier to see: rounder, and coloured by what they are saying — green for saved, red for something rejected, amber for something to look at — each with a mark of its own.
• A licence message now looks like one. Activating a key answered in an unmarked grey box, whatever it said; it carries the right colour and a mark like every other message on the screen.
• A licence key that could not be a key is refused on the spot, without a request to the licence server and without reloading the screen. An empty box used to mean a wait, and on an offline site it meant being told the licence server could not be reached.
• A key pasted out of an email in lower case, or with the dashes lost, is put right rather than reported as wrong.

• Confirmation messages line up properly and sit on rounder corners: they were top-aligned with the text nudged down two pixels to meet the icon, which on a one-line message read as a misalignment because it was one.

• Confirmations are easier to see. The message after a save is bordered in the colour of what it is telling you, sized to the words rather than stretched to a fixed card, and it now says what was saved rather than just "Saved".
• It stays for four seconds instead of three — long enough to read a sentence — and hovering it holds it open.

• Tab changes are instant. The plugin's other screens are fetched quietly in the background while you read the first one, so by the time you click a tab there is nothing left to wait for — tens of milliseconds instead of a second and a half.
• One at a time, never in parallel, started only once the screen you are on is ready and the browser says it is idle, stopped the moment you navigate, and skipped entirely on a metered connection.

• An admin that never reloads. Every screen arrives without a page load and every save happens where you are standing — and the screen you are heading for is usually already fetched, because moving a pointer to a menu item takes long enough to fetch it.
• Saved, and told so where you are looking. A save answers in a small message in the top-right corner that clears itself after a few seconds, instead of reloading the page and putting a notice above the header.
• It is an enhancement, not a dependency: if a fetch fails or scripting is off, links navigate and forms submit exactly as they always did, and the server side is unchanged.

• Notices redesigned: a quiet bordered card at 14px with the tone carried by a tinted icon, rather than a block of colour in coloured type.

• Every notice this plugin prints now looks the same: a white box with a coloured rule down its edge — orange for something to do, red for something wrong, green for something that worked. WordPress tinted a warning cream and an error pink and gave each one its own border colour, so a few notices in a row read as a few different kinds of box.
• The message on the licence screen after activating or deactivating a key now stays where it is printed, rather than jumping down the page a second after the screen has loaded.

• Fixed: a notice from this plugin no longer jumps after the page has loaded. WordPress lifts any notice out of the page once it is ready and drops it under the page heading, so the screen settled and then everything below moved by the height of a notice — and painted once in WordPress's colours before ours arrived. Ours stay where they are put, styled from the first paint. The setup prompt also gets its own colour back on the rule down its edge, rather than WordPress blue.

• Tooltips are ours rather than the browser's. They appear the moment you hover or focus instead of after a second, they are styled like the rest of the screen, and somebody using a keyboard gets them too. On this plugin that is the marker beside a property Google requires.

• Every dropdown now draws its own arrow. A native select is nearly invisible against our surface on macOS and sometimes has no arrow at all elsewhere, so a dropdown could read as a text box — and a text box invites typing rather than clicking.

• WordPress's own plugin details window now says what the plugin is, not only what changed in the last version.
• Settings screens have the two-column layout the shared stylesheet was missing.
• Three releases that were published but never written up — 1.0.1, 1.2.0 and 1.6.7 — are in the changelog.

• The plugin mark in the section bar is versioned by file time, so a redrawn icon actually reaches you instead of the browser serving the one it cached first.

• The plugin icon has lost the decorative braces that used to sit either side of the mark. They crowded it at every size, and the mark is drawn larger in their place.

• Website catch-up: this page, the documentation and the feature list now describe 1.7.0 and 1.8.0. No change to the plugin itself.

• The setup wizard is its own focused screen: no notices from other plugins stacked above it, no section nav to wander off into, a centred column and a progress rail that fills as you go.
• The section bar's text and icons now match the other Traslatability plugins exactly — they had been rendering a size smaller here.
• The toolbar shortcut finally has a control. It was read on every admin page load with nothing anywhere to turn it off.

• Site identity shows only the fields for the identity you picked. Choosing "A person" no longer leaves organisation fields on screen, and the setup wizard no longer offers a logo, which a Person never outputs.
• The identity preview says when it is out of date. It is built from saved settings, so it used to sit there quietly contradicting the form above it.
• A targeting rule shows its ID box only for the two target types that use one, and each rule answers to its own row. The box is labelled required rather than optional — leaving it empty silently dropped the rule.

• Checkbox options now sit several to a row instead of one per line, so settings screens use the space properly.

• Clearer section bar: larger, darker labels and icons, and it now stays in place instead of following the page as you scroll.
• Summary tables read as two columns again rather than stacking each value under its label.

• Bigger, clearer admin type throughout, and larger controls to match — easier on the eyes on a long settings page.

• Easier on the eyes: slightly larger text, clearer colours and bigger buttons throughout the admin. Shorter plugin name in the menu and plugin list.

• The licence reminder now sits at the top of the screen instead of halfway down some WooCommerce pages.

• The floating Save button is larger and easier to hit.

• Clicking a link no longer leaves a stray blue focus box; keyboard focus now shows the brand ring.

• The floating Save button in the schema editor is now a clean single pill, matching the other Traslatability plugins.

• Settings: the product-source choice cards now sit side by side rather than stacked.

• Admin: cleaner colour pickers and a nicer focus state on the section tabs.

• Updates: unlicensed sites now see when a new version is available (installing still needs an active licence). The version check is anonymous — no licence key or site details are sent.

• Admin: toggle switches now render correctly.
• Admin: the plugin's header icon now matches the brand.

• Full WordPress Multisite support: schema tables and defaults are set up per site on network activation, and on new sites automatically.
• Refreshed plugin icon.

• The licence check now rides along with the six-hourly update check — one request instead of two, and none until a licence key has been entered.
• Dashboard links are no longer underlined; the licence reminder keeps one colour and gives its links room.

• Spanish and French translations cover every string again, including the dashboard status messages, validation notices, top bar and Tools tabs added since 1.5.7.
• The shipped plugin no longer contains authoring material.

• Changing a schema's target to a list page (blog index, search, archives) now removes every custom-field, ACF and WooCommerce source from the field pickers, not only the WooCommerce ones. No post renders on a list page, so none of its fields can be read there.

• Vehicle listings are emitted as Car with an Offer, the shape Google's vehicle listing guidance uses.
• Video, podcast and audio durations typed in minutes become ISO 8601; an ISO value is kept as typed.
• Podcast audio is emitted as associatedMedia and forum upvotes as an interaction statistic, both properties schema.org defines.
• Q&A pages carry answerCount; recipes gain totalTime; online events use a VirtualLocation.
• Select fields only accept offered choices, Custom JSON-LD is parsed at save, and per-post overrides apply the same number limits as the schema form.
• The type picker's search hides cards that do not match.

• The top bar sits a little below the WordPress admin bar instead of touching it.

• Validation now checks each schema against a real post it applies to, the way the live preview does. A correct Article setup on a fresh site reported five missing fields because nothing could auto-fill against no post at all.
• A required field that fills itself from each post, and is simply absent on the post checked (no featured image, say), is reported as a warning about that post rather than an error in the schema.

• The empty state on the Schemas list is centred; its text and buttons had drifted to the left.

• Fixed the plugin offering the update you had just installed. On hosts where PHP caches compiled files for a while, the old version number could be compared against the new release for up to a minute after updating. The version is now read from the plugin file itself, which is never cached that way.

• The licence page now loads the plugin's stylesheet. It is registered under the product slug rather than the menu slug, so it had been the one screen with no styling at all.
• The welcome notice's buttons are branded on every admin screen, not only on the plugin's own pages.

• "Check again" on the WordPress Updates screen now asks our server directly instead of reusing an answer cached up to six hours earlier, so a release published minutes ago shows up straight away.
• After the plugin updates, the cached update answer is discarded, so the old version can never be offered again.

• Redesigned every admin screen as one system: a shared top bar with the plugin's sections, licence state and docs on every page, the licence page included.
• Form controls restyled as a set — inputs, selects, checkboxes, radios and buttons share one height, radius and brand focus ring, so the licence form no longer looks like a stock Settings page.
• Tools is now three tabs (Validation, Integrations, Maintenance) instead of one long column; the Validation tab shows its issue count.
• Settings checkboxes became full-width check rows with their explanation attached.
• The plugin icon now appears on the WordPress Updates screen and in the plugin details modal.
• Nothing resizes after first paint: inputs and the top bar are sized inline, as the buttons already were.

• The licence screen now looks like the rest of the plugin — same header, panel and status pill — instead of a bare WordPress page with its own box.
• Fixed buttons briefly painting square before their corners rounded.
• One corner radius for surfaces and one for controls across every screen, where five different values had crept in; body text likewise settles on two sizes rather than four.
• The setup wizard uses the shared page header.

• Admin notices now appear above the page header instead of wedged between the title and its subtitle.
• The schemas list is easier to scan: an icon per schema type, the type shown under its name, and status and health side by side.
• Buttons are one consistent size and style across every screen.

• Number fields now refuse impossible values. A rating cannot be negative or above 5, a price or duration cannot be negative, and anything rejected is explained rather than silently dropped.
• The priority control opens as a small panel instead of stretching the row it sits in.

• Field mapping now finds every custom field that genuinely applies to the post type a schema targets: ACF fields scoped by their own location rules, including those nested inside repeaters and groups; fields declared by other plugins even when no post has a value yet; and ordinary custom fields. Private keys beginning with an underscore are hidden.
• Discovery is bounded, so it stays fast on a site with millions of posts, and results are cached until an ACF group or a custom field actually changes.
• Save now sits at the end of the schema name row, and the redundant "Output" label above the switch is gone.

• WooCommerce fields no longer appear for targets that can never be a product — the blog index, front page, search results and archives are lists, not products.
• The Google preview now shows stars for Review schemas, which use a different rating property from everything else.
• The preview panels sit beside the fields again instead of dropping to the bottom of the page, and the image field's Choose button sits on the same line as its input.

• The schema editor's settings now sit in one row at the top: the name, an on/off switch, and priority folded away at its default since it rarely needs changing.
• "Internal title" is now "Schema name", with an example of what to write.

• Fixed activating a licence ending on "you are not allowed to access this page". Successes and errors now show on the licence screen itself.
• The field picker only offers fields that exist on the post types a schema targets, and updates the moment you change a targeting rule — no saving first. WooCommerce sources appear only where they can actually resolve.
• A newly added custom field is offered straight away instead of after an hour.
• A save button now follows you down the editor, so a long schema can be saved without scrolling back up.
• Clearer validation messages, and stat cards with a little more depth.

See what you are building, as you build it.

• A Google preview. The editor shows how a result could look — stars, price, cook time, FAQ rows — so you can see what your markup buys you without reading JSON.
• Both previews are now live. They rebuild as you type, from the values in the form, rather than from the last save. Validation updates with them.
• Previews now appear while creating a schema, not only when editing a saved one.

A clearer admin.

• The dashboard now tells you where you stand. One banner states the situation — nothing set up, nothing published, something missing, or all clear — and offers the single next action, instead of leaving you to work it out from counts.
• Icons throughout, carrying state as well as decoration: a problem card is red with a warning glyph, a healthy one green with a tick.
• "Pages covered" replaces a meaningless type count, saying in plain English where your markup actually appears.
• Fixed the primary button appearing blue for a moment before turning orange.
• Fixed a miscount that said "15 schemas are missing something" when only three existed, and a green all-clear that appeared before anything had been checked.

• The licence screen now lives inside the Schema Pro menu rather than under Settings, and an unlicensed site is told so on every admin screen instead of only on the licence page itself.
• Fixed the health check overlapping its own text when a finding was longer than a few words.
• The invoice sign-off is a setting now, so it can be edited or removed.

Easier field mapping.

• "Where it applies" now comes first in the schema editor, because what a schema targets determines what its fields can read from.
• Fields are chosen from a list, not typed. The picker shows the custom fields and ACF fields that actually exist on the post types the schema targets — so a schema aimed at Products offers product fields, not every key on the site. A free-text option remains for a field that exists but has no value stored yet.
• Removed a duplicated validation message in the editor.

Field mapping, WooCommerce, and translations.

• Point a field at your data. Any field can now read from a custom field, an ACF field, the author's profile or a term field instead of holding a fixed value. One schema can finally produce different values per post — a price, a rating, a cook time — without a schema per post.
• WooCommerce. Product fields read price, currency, SKU, stock, ratings, brand, GTIN and sale end date straight from each product, with no meta keys to type. Woo's own product markup is switched off so there is only one.
• Spanish and French included, with English as the default. The plugin is fully translation-ready, so any language can be added.

Guidance throughout, for people who have never touched structured data.

• Two-minute setup. A new install is offered a short wizard: who publishes the site, what its posts are, done. It creates a working schema and confirms the markup is live, without needing to know a single schema.org type name.
• Every type explains itself. All 30 now say what you actually gain — "Cook time, rating and a photo can appear in the recipe carousel" — and link to Google's own guidance for that type.
• Field help. 71 fields carry concrete guidance: what format, what units, and a worked example.
• A useful empty screen. With no schemas configured, the list explains what a schema is and offers the setup, rather than saying "no schemas match".
• Test from the toolbar. A Schema menu appears on the front end with one-click links to Google's Rich Results Test and the Schema Markup Validator for the page you are looking at. Hidden on local and private sites, which Google cannot reach anyway.
• Named validation. The editor now says which properties are missing rather than only that something is.

• A guided setup wizard.
• Each schema type explains what it earns you in search, with a link to Google's own documentation for it.
• Help text on 71 fields.

Per-post control, conflict handling and six more schema types.

• Per-post overrides. A Schema Pro panel in the post editor lets you change any field for one post without touching the schema every other post shares. Empty boxes show the value that will be used, so nothing is guesswork.
• Works alongside your SEO plugin. Yoast, Rank Math, SEOPress, All in One SEO and The SEO Framework are detected automatically, and site identity, breadcrumbs and the sitelinks box stand down rather than emitting a second copy. Article and Web Page markup can be handed over too, from Tools.
• Six new types: Profile Page, Forum Post, Item List, Movie, Audio and Vehicle Listing — the last two of which are current Google rich results.
• Article subtypes: Technical, Scholarly, Report, Opinion, Review, Background, Satirical and Sponsored.
• 75 Local Business subtypes, up from 10 — restaurants, trades, clinics, shops and professional services each get their precise type.

• Documentation, knowledge base and feature pages published on traslatability.com.

Initial release.

• 24 schema types: Article, Blog Posting, News Article, FAQ, Q&A Page, How-to, Recipe, Course, Book, Video, Podcast Episode, Image Licence, Product, Service, Software Application, Review, Local Business, Organization, Person, Job Posting, Event, Dataset, Web Page and Custom JSON-LD.
• Targeting rules by post type, taxonomy, specific post or term, archive, front page, search and 404, with exclusions taking precedence over inclusions.
• Automatic field values pulled from the post being rendered — title, excerpt, featured image, author, dates and permalink.
• A single JSON-LD @graph per page, which is what Google recommends.
• Site identity as Organization or Person, with logo, contact details and sameAs social profiles.
• Breadcrumb markup and the sitelinks search box, each independently switchable.
• Validation report listing schemas missing properties Google requires.
• Four purpose-built database tables, so nothing is written to postmeta.
• Per-URL caching of rendered markup, cleared automatically when content or configuration changes.