by Franky 0 (0 reviews)

Spintax

Name: Spintax
Author: Franky

Generate unique content at scale with spintax — bind templates to ACF & post-meta fields, pull WooCommerce product data, Bulk Apply, cron, WP-CLI.

Spintax ranks #61,936 among WordPress.org plugins with 0+ active installations, is #7,665 of 8,590 in the Customization category, and was last updated Sep 6, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.2

v3.1.0 Current Version v3.1.0

Updated 2 weeks ago Last Update on 06 Sep, 2026

Refreshed 6 hours ago Last Refreshed on

#7,665 of 8,590 in Customization Actively maintained

View on WordPress.org

Rank

#61,936

— No change

Active Installs

-100%

KW Avg Position

— No change

Downloads

802

+5 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 10%

0+ 10+

42,196

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 9 more installs to reach 10+

Rank Changes

Current #61,936

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 3.1.0
Last Updated: Sep 06, 2026
Requires WP: 6.2+
Tested Up To: 7.1.2
PHP Version: 8.0 or higher
Author: Franky

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

acf content generation seo spintax woocommerce

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,760

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,009

Elementor Website Builder – more than just a page builder

10M+ installs

LiteSpeed Cache

7M+ installs

Ultimate Addons for Elementor – Widgets, Templates, WooCommerce & Header Footer Builder

2M+ installs

#26

Essential Addons for Elementor – Popular Elementor Templates & Widgets

1M+ installs

#29

Starter Templates: AI-Powered Website Templates for Elementor & Gutenberg

One Click Demo Import

1M+ installs

#62

Translate Wordpress with GTranslate

900K+ installs

#71

View all Customization plugins

Frequently Asked Questions

Common questions about Spintax

Go to Spintax > Add New in the WordPress admin. Enter a title and your spintax markup in the editor.

{a|b|c} — randomly picks one option [a|b|c] — permutation: picks N elements, shuffles, joins with space [<minsize=2;maxsize=3;sep=", ";lastsep=" and "> a|b|c|d] — configured permutation %variable% — variable reference #set %var% = value — local variable, a macro: re-picked at every use #def %var% = value — local variable, picked once per render and held at every use {?VAR?then|else} — conditional: render a branch by truthiness of %VAR% (also {?!VAR?then} inverted) {plural %Count%: form1|form2|form3} — plural agreement: picks the correct grammatical form by count (RU/UK/BE and SR/HR/BS 3-form, EN-style 2-form) /#comment#/ — block comment (stripped from output) #include "slug" — embed another template Full syntax reference with examples and a live playground: https://spintax.net/docs/syntax

Compact syntax reference: https://spintax.net/docs/syntax — all primitives in one page (13 languages) Plural agreement guide: https://spintax.net/docs/plural-spintax/ — {plural N: form1|form2|form3} in depth (EN/RU) Conditional spintax guide: https://spintax.net/docs/conditional-spintax/ — {?VAR?then|else} value-driven branching (EN/RU) Authoring mindset: https://spintax.net/docs/authoring-mindset/ — write the final text first, add markup last (EN/RU) Live playground: https://spintax.net/play/ — write a template, set variables, render N variants in your browser (EN/RU) Editors & tooling: https://spintax.net/spintax-editor/ — Spintax Studio for Windows, VS Code and Sublime Text extensions, and the archived GTW application that started the syntax Engine family: https://spintax.net/spintax-engines/ — the five standalone libraries (PHP, JavaScript/TypeScript, Python, .NET, Object Pascal) and how one shared corpus keeps them identical Spintax in PHP: https://spintax.net/spintax-for-php/ — the standalone spintax/core package this plugin's engine is kept in step with

Yes — Spintax Studio, a free native Windows editor built for exactly this syntax: two-pane live preview rendered by a real engine, inline validation with per-error documentation, variable panels, variant counting and export, and built-in help in 14 languages. Install it from the Microsoft Store; an overview of all the editor tooling (including VS Code and Sublime Text extensions) lives at https://spintax.net/spintax-editor/ Studio embeds spintax-win v0.8.1 — the Object Pascal engine from the same corpus-locked family as this plugin's — so a template that validates and previews there behaves the same way when this plugin renders it.

The plugin uses the WordPress Object Cache API. With a persistent backend (Redis, Memcached), cached output persists across requests. Without one, templates are re-rendered on each page load.

Yes: [spintax slug="greeting" name="Alice" city="Moscow"] makes %name% and %city% available inside the template.

Yes, since 2.2. On a single-product page the plugin auto-detects the current product and exposes it to [spintax] and spintax_render() as %product_*% variables — for example %product_name%, %product_slug%, %product_sku%, %product_type%, %product_stock_status%, %product_categories%, %product_tags%, %product_short_description%, and one %product_attribute_<slug>% per product attribute. So a template embedded as [spintax slug="product-seo-block"] on a product renders that product's data, and the same template on two products gets two separate cached variants. Pricing (%product_price% and friends) is intentionally not exposed: it is volatile commerce data, not generated copy, and folding it into templates would churn the render cache on every price change. To target a specific product regardless of the current page, pass [spintax slug="…" product_id="123"]; any explicit variable you pass always overrides the auto-detected one. WooCommerce is optional: with it inactive, or on non-product pages, behavior is unchanged. Since 2.4 the plugin can also write generated copy into a product — see the next question. Product loops and cards are still deferred.

Yes, since 2.4. Create a binding with the target kind WooCommerce product field, on the Product post type, and pick Description or Short description. Every matching product then gets its own rendered copy — seeded when the field is empty, or regenerated on save if you ask for that — through the same machinery as ACF and post-meta bindings: cron schedules, Bulk Apply, WP-CLI, and the Logs page. Turn on Expose WooCommerce product data in the binding's Variables tab and the template can use that product's own facts — %product_name%, %product_sku%, %product_type%, %product_categories%, %product_tags%, %product_attribute_<slug>% — so each product gets copy that is actually about it, not just a differently-worded version of the same sentence. Three deliberate limits: Only those two fields are writable. Price, SKU, stock and sale dates are commerce data, not copy. A template cannot reach them — the whitelist is enforced when you save the binding and again before every write. Manual edits win. With "Preserve manual edits" on (the default), a description a human has changed is never overwritten; the binding skips it and says so in the Logs. Writes go through WooCommerce. Not straight into the database — so WooCommerce's own caches, lookup tables and save hooks stay consistent, and other plugins that listen for product saves still hear them. With WooCommerce deactivated, product bindings simply stop writing. Copy that was already generated stays where it is: by then it is the product's real description, and reverting it would destroy content.

A binding pairs a Spintax template (or a per-post inline source) with one target field on one post type — for example "Posts → ACF: hero_subtitle". Configure it once under Spintax → Bindings and the plugin populates the field on every matching post on save, on a cron schedule, or on demand via Bulk Apply. Manual edits are preserved by default (hash-tracked); flags control whether the binding auto-seeds empty fields, regenerates on every save, or clears the field when the template renders to empty.

Yes. Bindings support both ACF (text / textarea / wysiwyg, top-level fields) and plain post-meta keys. ACF Free and Pro are both supported; nested fields (repeater / flexible_content rows) are not supported in 2.0 — that lands in a later release. The form-side field picker auto-fills the stable ACF field key so writes work on the first save without ACF's reference-meta handshake.