SEOPress 10.1: the AI metadata feature leads, but robots.txt revisions are the one that saves sites
The new release auto-generates meta titles and descriptions the moment you publish, adds ProductGroup schema for WooCommerce variable products, and gives robots.txt a version history. One of those prevents a category of disaster; one deserves more caution than the announcement suggests.
Table of contents
SEOPress 10.1 is out — the plugin sits at 300,000+ active installations on WordPress.org with a 4.8-star rating from over 1,240 reviews, so a point release here touches a lot of sites. This one is unusually feature-dense for a minor version, and the feature getting the least attention is the one most likely to matter.
The headline: AI metadata, generated on publish
The marquee change is automation. Enable the option and SEOPress generates the meta title and description with your chosen AI provider the moment a post is published — no extra click, no half-filled fields, no posts going live with an empty snippet for Google to improvise around.
It extends further than posts. AI generation now also covers taxonomy terms — categories, tags and custom taxonomies — in one click, at scale. Anyone who has ever looked at a site with four hundred tag archives all sharing one templated description will recognise why that is useful.
Two sensible guardrails ship alongside it: generation can be restricted to specific user roles, and your AI credits balance is visible from the SEOPress dashboard. The latest DeepSeek V4 models are supported as a provider.
The part worth thinking about
Automation on publish is convenient precisely because it removes the review step — which is also the argument against it.
A meta description is one of the few pieces of text on your site written for the click rather than for the page. It is short, high-leverage, and the thing an editor is best placed to get right. Handing it to a model that has read the post but not your positioning gets you something serviceable, and serviceable is a real improvement on empty. It is not an improvement on considered.
The reasonable configuration for most sites is a middle one: let it fill gaps, not set defaults. Use it to eliminate empty fields across an archive of old posts and to cover taxonomy terms nobody was ever going to write by hand. On the pages that actually earn traffic, write them yourself and let the automation skip what already exists. The role restriction exists to let you enforce exactly that split across a team.
The quiet hero: robots.txt revision history
This is the feature that will save somebody's site this year.
A single wrong line in robots.txt can wall off a whole site from search engines, and the failure is silent — nothing breaks, nothing errors, traffic simply decays over the following weeks until someone investigates. It is one of the few SEO mistakes that is both trivially easy to make and genuinely expensive.
SEOPress 10.1 adds revisions for robots.txt: every change is saved, versions can be compared side by side, and any previous version restored in one click. That is a plain undo button on the highest-consequence text file in WordPress.
If you run client sites or share admin access with anyone, this alone is worth the update.
For stores: ProductGroup schema for variable products
The WooCommerce work is substantial and specific. SEOPress 10.1 adds ProductGroup structured data for variable products, so Google reads your sizes and colours as variants of one product rather than as a single flat listing.
Product schemas now also carry sale prices and your merchant return policy — both signals Google uses to render richer results. Underneath, the release fixes shipping details and price validity dates, and strips empty review data that was previously being emitted.
Two more for schema users: dynamic variables now resolve inside custom schema fields, and a new Manual tab on the Schemas screen lists every piece of content where a schema was assigned by hand. That second one is unglamorous and genuinely useful — manually assigned schemas are exactly the thing that gets forgotten and then contradicts your automated rules a year later.
Site Audit gets a technical tab
The Site Audit adds a Technical tab running site-wide checks against your homepage — the configuration fundamentals an SEO consultant would verify before anything else, surfaced without leaving WordPress.
Practically more important: stalled audits and broken-link scans now recover automatically, so long crawls finish. Crawls that quietly die partway through are a familiar WordPress problem with a familiar cause — the same scheduled-task fragility we went through in why WordPress sites randomly slow down. A scan that reports partial results as if they were complete is worse than one that fails loudly.
For agencies: set a site up once, reuse it forever
If you build sites for a living, this is the release's best value. You can now export a reusable configuration file that excludes site-specific data, then import it directly from the installation wizard on the next project. Define your standard SEOPress setup once and stop rebuilding it by hand.
Migration also improved on three fronts: the Yoast importer now brings social profiles and feed settings, the SureRank importer picks up settings it previously missed, and a new importer pulls redirections from Slim SEO. If you were weighing SureRank as an alternative — we covered it in this SureRank write-up — the migration path between the two now runs in both directions, which lowers the cost of being wrong.
Everything else
The release also brings a redesigned License page with update troubleshooting built in, quick actions in the WordPress command palette, clearer on/off states for every feature in settings, WPML compatibility for llms.txt and target keywords, more reliable content analysis with page builders, new translations (Arabic, German, Norwegian, Canadian French), security improvements and a long list of fixes.
The llms.txt detail is small but pointed: it is the file that tells AI crawlers what your site is and what they may use, and multilingual support means each language version can now state its own. That matters more each quarter, for reasons we set out in why AI crawlers skip most WordPress sites.
Content analysis working properly with page builders is also overdue — if your pages are built in Divi or Elementor, on-page analysis that reads the raw post content has always been half-blind. Relevant to anyone running the setups in our page builder comparison.
Should you update?
Yes, and reasonably promptly — the release includes security fixes, which is reason enough on its own.
Do it in the usual order: back up, update on staging if you have it, then check that your existing schema output is unchanged before and after. The WooCommerce schema changes are the most likely place for a store to see different markup than it had, and validating a couple of product URLs afterwards takes two minutes.
Then leave the AI-on-publish option off until you have decided the policy. Turning it on later costs nothing; turning it off after four hundred posts have shipped with generated descriptions is a cleanup job.
Sources
