SeoVision Publisher

Changelog

0.14.1

• Technical SEO: product fixes for Google Merchant Center. When Google reports that a product lacks its brand, barcode (GTIN) or part number (MPN) and your store already holds it somewhere your Google feed app does not read, SeoVision can fill the field the app sends: Google for WooCommerce’s brand and MPN, Google Product Feed’s brand, GTIN and MPN, or WooCommerce’s own GTIN field. Only empty fields are filled, and only once you confirm the batch in SeoVision. Like every fix, the batch is backed up first and can be undone.
• The technical SEO page list also tells SeoVision a product’s variation IDs and what those feed fields hold, so a Merchant Center issue on a variation is matched with its product. The read changes nothing on the site.

0.14.0

• SeoVision can publish pages as well as posts: the new pages shown in your SeoVision content plan go to your site as WordPress pages, with their SEO title, description and structured data. A post or page SeoVision already published keeps its type, and your own pages are never touched. Pages are not added to your menus.
• IndexNow: when a SeoVision post or page goes live, Bing, Yandex and the other IndexNow search engines are told its address at once. The site’s key is created on your site and served at /.txt. Nothing is sent while the site discourages search engines, and the seovision_indexnow_enabled filter switches it off.
• Uninstalling the plugin also removes its IndexNow key.

0.13.0

• Technical SEO: product selling points and answers. Once you confirm the batch in SeoVision, a product shows up to 6 short selling points and the questions shoppers ask with their answers, under its characteristics. SeoVision writes them only from the product’s own text, never for medicines, and adds the selling points to your product feed. Like every fix, the batch is backed up first and can be undone, and the same checkbox on the plugin’s settings page hides the blocks.
• The catalog read for SeoVision’s product feed can read chosen products only. The read changes nothing on the site.
• Uninstalling the plugin also removes the selling points and answers it stored on your products.

0.12.0

• Technical SEO: product characteristics. SeoVision gathers the characteristics your store already holds for each product (its brand, the strength, volume, weight or count its name states, the attributes shown on the product page or used for its variations, weight, dimensions, barcode and category) and, once you confirm the batch in SeoVision, shows them in a “Product details” block under the product’s description and adds them to the product markup as additional properties, so shoppers, search engines and AI shopping assistants read them in one place. Your own description stays as it is. A product without a description gets its Description tab back to show the block. Like every fix, the batch is backed up first and can be undone, and the block can be hidden with one checkbox on the plugin’s settings page.
• Technical SEO: a read of the published catalog (prices, sale dates, stock, photos, brand, barcode, SKU, attributes, categories and variations) for the product feed SeoVision builds at its own address, which you can add to Google Merchant Center, Perplexity and Microsoft Merchant Center. The read changes nothing on the site. Products hidden from the shop or protected by a password are left out.
• The “Related articles” block now shows in block themes (such as Twenty Twenty-Five) too, including under a product without a description, and still once per page. It never reaches the description an SEO plugin builds from the page’s text, an excerpt or a feed.
• Uninstalling the plugin now also removes the FAQ markup and the characteristics it stored on your pages.

0.11.1

• One breadcrumb trail and one organization on each SeoVision article. When Rank Math or Yoast SEO prints its own breadcrumb markup on the page, the article’s structured data leaves its breadcrumb list out. When the SEO plugin prints the site’s organization (or a business type such as a pharmacy, store or local business), the article leaves its own organization out and names the SEO plugin’s organization as its publisher. Google then reads one trail and one organization per article. Sites without Rank Math or Yoast SEO keep the article’s full structured data. A site that wants both can return false from the seovision_dedupe_article_schema filter.

0.11.0

• Technical SEO: restore points. Before any fix, SeoVision asks this site to save a copy of every field it can change here: the title, description, canonical address and noindex of every published page, post, product and category, the FAQ and “Related articles” fields, the alt text of every image, and the site-wide settings and redirects. The copy is saved on this site, in steps so a large store never hits a time limit, and can be downloaded from the plugin’s settings page. Fixes are applied only while a restore point of the last 12 hours exists. The seven newest restore points are kept.
• The Technical SEO read of the site now says whether Rank Math adds the missing image alt text itself (General Settings, Images, “Add missing ALT attributes”). SeoVision then proposes no alt text that the pages already show.

0.10.3

• Technical SEO: three new fixes for structured data. WebSite markup on the front page and breadcrumb markup on posts, pages, products, categories and the shop page, printed only where neither an SEO plugin nor a SeoVision article’s own markup prints them. The product markup WooCommerce, Rank Math or Yoast prints gets the brand, barcode (GTIN) and photo the store holds, the delivery and return terms the site owner entered in SeoVision, and the rating of the store’s own reviews, each only where the markup has none. What the markup already says stays as it is. Like every fix, each waits for the administrator’s approval of its batch, is backed up first and can be undone.
• Technical SEO: a fourth new fix marks up as FAQ the questions a page already holds, word for word (a heading that asks, or a details block, with the text under it), only where no FAQ block of Yoast or Rank Math marks them up.
• The page text the Technical SEO read sends keeps a space between paragraphs, list items and lines, so a description built from it no longer runs two sentences together.
• The Technical SEO read of a page now includes the links of this site its text and its “Related articles” block hold, and the questions on it; of a product, its brand, barcode and review count; of the site, the links in its menus and the redirects SeoVision set. The scan uses them to find pages nothing links to and redirect chains, and to know what can be added.

0.10.2

• Technical SEO with Rank Math or Yoast SEO: a new fix adds the business type, postal address, phone and license number the site owner entered in SeoVision to the organization markup Rank Math or Yoast prints. A property the SEO plugin already prints stays as it is, and the type changes only from a plain “Organization”. Like every fix, it waits for the administrator’s approval of its batch, is backed up first and can be undone.

0.10.1

• Technical SEO with Rank Math: the title and meta description the scan reads for a page are now the ones Rank Math prints on it, built from its title and description templates in the same order Rank Math uses. Before, a page whose fields were left to Rank Math’s templates read as having no title and no description, because Rank Math fills its template variables only on a page view.
• The business markup is printed the same way as the articles’ structured data, and the code follows WordPress’s Plugin Check (escaped output, comments on the LiteSpeed Cache and sitemap hooks this plugin calls).

0.10.0

• Technical SEO fixes, off until an administrator allows them under Technical SEO fixes on the plugin’s settings page. Two new authenticated reads, GET /wp-json/seovision/v1/technical-seo/site and GET /wp-json/seovision/v1/technical-seo/pages, and two writes, POST /wp-json/seovision/v1/technical-seo/apply (only once allowed) and POST /wp-json/seovision/v1/technical-seo/rollback.
• Every batch is backed up on the site before anything changes, and nothing changes when the backup cannot be saved. A field changes only while it still holds the value SeoVision saw. Backups can be downloaded and restored from the settings page.
• What a fix can change: the SEO title, meta description, canonical address and noindex of a post, page, product or category (in Yoast SEO or Rank Math, or printed by this plugin), the alt text of an image, the “Discourage search engines” setting, crawler groups in the virtual robots.txt, /llms.txt, a business markup on every page, WordPress’s own sitemap, noindex on addresses with chosen query parameters, redirects of broken addresses to a page of the same site, and a “Related articles” block under a page.
• GET /wp-json/seovision/v1/verify also reports whether technical SEO fixes are allowed and which SEO plugin is active.

0.9.2

• One Article per page: on a SeoVision article whose structured data this plugin prints, the Article or BlogPosting that Yoast SEO or Rank Math adds is left out, so Google reads one article with one author and one date. Their other structured data (WebPage, breadcrumbs, organization) stays. A site that wants theirs back can return false from the seovision_dedupe_seo_plugin_schema filter.

0.9.1

• The settings page mentions WooCommerce orders only on a site where WooCommerce is active, where the orders section shows below the token.

0.9.0

• WooCommerce orders for SeoVision’s Orders page, off until an administrator allows them under WooCommerce orders on the plugin’s settings page. Two new authenticated reads, GET /wp-json/seovision/v1/orders (orders changed since a time, orders placed up to a time, or orders by id) and GET /wp-json/seovision/v1/orders/changes (orders deleted, restored or erased since SeoVision last asked). Both answer seovision_orders_not_allowed until the store allows them.
• What an order carries: its number, dates, status, totals and refunds, products, the source WooCommerce’s order attribution recorded (the referring host, campaign tags and the entry page’s path without its query string), and the buyer’s name, email address, phone number and shipping address. Orders awaiting payment, failed, cancelled or drafts carry their id and status only.
• GET /wp-json/seovision/v1/verify also reports whether WooCommerce is active and whether orders are shared.
• Privacy: a suggested paragraph for your privacy policy, and SeoVision’s copies of orders in Tools → Export Personal Data and Erase Personal Data.
• Declares compatibility with WooCommerce’s order tables (HPOS).

0.8.5

• A new post goes live only once it is complete. It is written as a draft, and switched to published or scheduled after its images, featured image and SEO fields are in place. Plugins that act the moment a post is published, such as Blog2Social, Jetpack Social and email notifiers, now see the finished post instead of one without its featured image and SEO description.
• Category: SeoVision can file a new post under a category you choose in SeoVision. A post that already exists keeps its categories. A chosen category that no longer exists is skipped and the post goes to your default category.
• New authenticated read, GET /wp-json/seovision/v1/categories. It lists your post categories with their post counts, how many of those posts you published yourself, your default category and the category SeoVision suggests. It is authorized by the same integration token as publishing.

0.8.4

• SeoVision now updates only a post it published itself, recognized by the SeoVision article id stored with the post. Until now, when no post carried that id, the plugin took any post at the same address (slug), so one of your own posts that happened to share the address of a new SeoVision article was overwritten by it. Such an article is now published as a new post, and WordPress gives it a unique address (for example -2 at the end). Your own post is not touched.
• The JSON-LD of a post whose address WordPress suffixed that way points at the post’s real permalink, like every other SeoVision post.

0.8.3

• New authenticated read, GET /wp-json/seovision/v1/articles/<article id>/modified. It answers the ID, status and last-modified date (GMT) of the post SeoVision published for that article, found by the SeoVision article id stored with the post, and nothing about any other post. SeoVision asks it before it updates the text of a live article for a search query, so it can leave a post you changed in WordPress alone, even on a site that blocks the public REST API. The FAQ says exactly when. It is authorized by the same integration token as publishing, and its answer is never cached.

0.8.2

• A picture whose address is a web page (a link the writer formatted as an image) no longer fails the whole publish. The plugin refuses it before download, skips any image it cannot add to the Media Library, keeps the post as written, and reports the skipped addresses under warnings in the response.
• The article’s SeoVision id is stored the moment the post is created, before its images are processed, so a publish that fails in the media step is found by its id on the next attempt instead of being rewritten by slug every hour.

0.8.1

• SEO tags: the article’s SEO title replaces the post title in <title>, and the meta description, Open Graph and Twitter card tags are printed on SeoVision articles when no SEO plugin is active. Jetpack’s own Open Graph output is respected.
• Yoast SEO and Rank Math: the SEO title, meta description and focus keyword are written into their fields on every publish, so they print the tags.
• Stores the article’s focus keyword (_seovision_focus_keyword).
• The JSON-LD now uses the post’s real permalink instead of the address SeoVision assumed before publishing (/blog/<slug>), and the “Blog” breadcrumb points at the site’s posts page, or is left out when posts are shown on the front page. An address set on purpose in SeoVision is kept.

0.8.0

• Removed WordPress user creation. Posts are now attributed to an existing user selected in SeoVision; the plugin never calls wp_insert_user.
• Authorization is now the integration token only. The previous fallback that also accepted any logged-in user with edit_posts is gone — it let a Contributor publish immediately and set an arbitrary post author, bypassing their normal capabilities.
• Article CSS is delivered through wp_enqueue_style() + wp_add_inline_style() instead of a <style> tag echoed into wp_head.
• Hosts that move the Authorization header to REDIRECT_HTTP_AUTHORIZATION (Apache with PHP as CGI/FastCGI) now work without an .htaccess change. Where the header is still missing, the plugin answers with a distinct error so SeoVision can name the real cause instead of blaming the token.
• The settings page no longer prints the saved token into the input. It shows the last characters instead, and an empty field on save keeps the existing token — pasting a new token on top of the old one used to concatenate them, after which no request could ever authenticate.

0.7.7

• Removed the Plugin URI header. It pointed at seovision.io, the same address as Author URI, which the WordPress.org submission form rejects; seovision.io describes the author, not this specific plugin.

0.7.6

• Fixes the Plugin Check findings from the 0.7.5 review run: prefixed the two global variables in uninstall.php, and annotated the intentional single-row meta lookup that makes publishing idempotent (it never runs on page views).
• Brand name consistently written “SeoVision” across the plugin UI, readme, and headers. All technical identifiers (text domain, option names, REST namespace, meta prefix) are unchanged, so updates and stored data are unaffected.

0.7.5

• WordPress.org submission readiness. Tested up to WordPress 7.1.
• Hardened the /users endpoint: it now lists only users who can edit posts and no longer returns login names (usernames), closing a username-enumeration aid. The SeoVision dashboard only needs display names for its “Post author” dropdown.
• Replaced @unlink() with wp_delete_file() in the image sideloader and sanitized the raw Authorization header reads.
• error_log() diagnostics now only run when WP_DEBUG is enabled; the same warning still reaches SeoVision in the REST response.
• readme: added an “External services” disclosure section (data in/out, terms, privacy policy) and documented exactly when the plugin creates an Author-role WordPress user.

0.7.4

• Adds uninstall cleanup: deleting the plugin now removes the stored integration token (seovision_integration_token) and the activation-redirect flag. Previously these options survived a delete, so reinstalling on the same site showed “A token is configured” with the old token pre-filled. Deactivating (without deleting) still keeps the token.

0.6.1

• Security/correctness: the JSON-LD printed into the page head now escapes <, >, and & (JSON_HEX_TAG | JSON_HEX_AMP). Previously a value containing the literal </script> could close the schema script tag early and break the page or inject markup. Slashes stay unescaped so embedded URLs remain readable.

0.6.0

• Draft, scheduled, and immediate publish modes with media sideloading and JSON-LD head injection (see prior internal releases for details).

0.5.2

• Keeps already-published posts published when repeated schedule requests are sent.
• Prevents accidental unpublishing of indexed WordPress posts during bulk schedule operations.
• Restores the safer default after 0.5.1: schedule requests never unpublish existing live posts.

0.5.1

• Allows a published post to be moved back to scheduled status when the requested schedule date is still in the future.
• Keeps already-published posts live when repeated schedule requests refer to dates that have already passed.

0.5.0

• Added support for draft, scheduled, and immediate publish modes.
• Scheduled posts use post.status future with the supplied WordPress local post.date.
• Idempotent lookup now includes published posts to avoid duplicate articles on repeat requests.

0.4.0

• Moved article image sideloading into the plugin endpoint.
• Added media URL rewriting for article HTML and JSON-LD before draft meta is stored.
• The plugin endpoint now returns the generated media map and featured media ID.

0.3.1

• Centralized plugin contract naming constants for pre-release rename readiness.
• Added WordPress.org-ready license metadata and readme scaffold.

0.3.0

• Added authenticated plugin REST endpoint for idempotent article draft create/update.
• Added media map meta storage.