How to Test Gutenberg 24.0’s DataForm Editor
Gutenberg 24.0 lets WordPress users try a redesigned settings panel for posts and pages. The redesign uses DataForm, a form-based way to…
Gregius Optimizer is a WordPress plugin for managing search, social-sharing, and AI-related metadata in WordPress’s block editor, the editor you use to build pages from content blocks. Metadata is information added to a page so search engines and social platforms can understand or display it. The plugin also controls sitemap and crawler settings.
Despite its name, the plugin’s documented features focus on discoverability, not page speed. The listing does not describe caching, code minification, or other general speed-tuning tools. Before installing it, check the requirements: the WordPress.org listing identifies version 1.3.0 and requires WordPress 6.9 or later and PHP 8.2 or later.
For most WordPress sites, the dashboard is the simplest installation route. In the admin area, open Plugins → Add New, search for Gregius Optimizer, confirm the result is by Gregius, then select Install Now and Activate. WordPress.org’s plugin management instructions also cover uploading a ZIP file and transferring plugin files to the server.
After activation, edit a post or page in the block editor. The plugin’s panels appear in the right sidebar, in this order: Sitemap, Robots, Schema, Social Cards, and LLMs. Activation does not configure these features for your content; review the relevant panels on the posts and pages where you want to use them.
The plugin directory reports few active installations and no reviews. That limited public feedback leaves little user history to assess and does not establish whether the plugin is safe or effective. Test it on a staging site, or make a backup before using it on a live site.
The Sitemap panel controls which post types and taxonomies appear in the XML sitemap, a file that lists URLs for search engines. You can also choose whether author archives appear. The panel lets you exclude individual posts from search and choose which URLs serve as the sitemap. Include content types you want search engines to discover. Exclude archives or posts that should not be promoted. After saving, check the sitemap itself to confirm the URLs match your choices.
The Robots panel edits robots.txt, a text file that tells crawlers which parts of a site they should request. The plugin describes rules for search crawlers, AI crawlers, and model-training crawlers, and provides a way to reset the file to WordPress defaults.
Use crawler rules and search-indexing controls for different purposes. A robots.txt rule can stop a crawler from fetching a page, but it does not reliably remove that page from search results. To prevent indexing, Google recommends a noindex directive, which tells a search engine not to show the page in results. The crawler must be able to access the page to read that directive, so blocking the page in robots.txt can prevent Google from seeing it. Google explains the distinction in its guidance on crawling and search visibility and blocking indexing with noindex.
The Schema panel lets you choose structured data by post type or override the choice for an individual post. Structured data formats page information so software can read it. The plugin uses JSON-LD, a format for embedding that information in a page, and the listing describes 174 subtypes across nine categories, including Article, Event, Organization, Product, and Review.
Choose a type that accurately describes what readers can see on the page, then preview the JSON-LD and validate the result. Adding structured data does not guarantee a special search result. Google says markup must follow its policies and match visible page content; even valid markup only makes a page eligible for certain search features. Its structured-data guidelines explain those conditions.
The Social Cards panel lets you set different titles, descriptions, and images for Google search snippets, Open Graph platforms such as Facebook and LinkedIn, and Twitter/X Cards. Use wording and an image that accurately represent the page, then check how the details appear in the relevant platform previews.
The plugin registers a cropped 1200 × 630 image size for Open Graph. That size does not guarantee every platform will display the image in the same way. The plugin’s character counters are interface aids, not guaranteed platform limits or ranking guidance.
The LLMs panel generates a /llms.txt file from site content and provides controls for global context and individual posts, including whether to include a post and what description to use. The plugin presents this feature as a way to help AI agents discover site content.
You can publish the file as an optional way to help AI agents find site content. The listing describes the underlying llms.txt material as a proposal, and publishing a file does not establish that AI tools will cite the site, improve its rankings, or send more traffic. Review the generated preview and include only content you want represented.
Gregius Optimizer covers features that also appear in full SEO plugins. If you already use another SEO plugin, check which one controls each page’s search description, canonical tag, social metadata, and structured data. A canonical tag tells search engines which URL to treat as the preferred version of a page. Duplicate or conflicting output can make it harder to tell which settings search engines receive.
Inspect the rendered page source after configuring the plugins. Look for repeated descriptions, canonical tags, social tags, or JSON-LD, and disable overlapping output where necessary. The Gregius listing says the plugin can complement or replace other SEO plugins depending on the workflow, but this does not show that it has all the same features or works with every other SEO plugin.
The plugin also says it creates a custom settings table when activated and removes it when uninstalled. Save any settings you need before uninstalling; deactivation and uninstallation are separate actions. On a multisite installation, each site manages its own configuration. The listing also states that the plugin does not send data to an external service. This is the developer’s disclosure, not an independent privacy or security audit.
Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.
Take a look at vroni.com