Spintax

Spintax is a content-generation toolkit for WordPress that turns one template into unique, non-duplicate copy across your whole site. Author reusable templates in spintax markup (enumerations, permutations, conditionals, plural agreement), then either embed them inline via shortcodes / PHP — automatically picking up the current WooCommerce product on product pages — or bind them to ACF and post-meta fields so every matching post gets its own rendered variant on save, on a cron schedule, or on demand.

A built-in Logs page surfaces what each Bulk Apply / Run-now walk did; a WP-CLI surface covers staging-to-production sync.

Ideal for content managers and SEO specialists producing many similar-but-unique pages: product descriptions, category copy, location / landing pages, listing blurbs, and FAQ snippets.

Key features:

• Enumerations {a|b|c} — randomly pick one option, with nesting support

• Permutations [<config>a|b|c] — pick N elements, shuffle, join with custom separators

• Variables %var% — global, local ( #set re-picks at every use, #def picks once per render), and shortcode-level scopes

• Conditionals {?VAR?then|else} — render a branch based on whether a variable is set (also {?!VAR?then} inverted)

• Plural agreement {plural <count>: form1|form2|form3} — pick grammatically correct noun form by count. RU/UK/BE and SR/HR/BS 3-form (one|few|many), Arabic 6-form (zero|one|two|few|many|other), EN-style 2-form (one|many). Other languages fall back to the 2-form rule, so pl, cs, sk, sl and bg are bucketed by a rule that is not theirs rather than rejected. First spintax engine with first-class plurals.

• Nested templates — embed templates within templates via #include or [spintax]

• ACF / post-meta bindings (NEW in 2.0) — configure once per post type, render Spintax templates into ACF text/textarea/wysiwyg fields or post-meta keys on every matching post. Auto-seed empty fields, preserve manual edits, Bulk Apply via Action Scheduler.

• WooCommerce product context (NEW in 2.2) — on a single-product page, [spintax] / spintax_render() automatically expose the current product as %product_name%, %product_sku%, %product_categories%, %product_attribute_<slug>%, and more. Volatile pricing is intentionally out of scope. WooCommerce is optional — the variables simply appear when a product context is present.

• WooCommerce product-field bindings (NEW in 2.4) — generate a product’s description or short description from a template, per product, using that product’s own SKU, categories and attributes. Only those two fields are writable; price, SKU and stock are commerce data and stay out of reach. Manual edits are preserved by default.

• Object cache — rendered output cached via WP Object Cache API (Redis/Memcached ready)

• Cron regeneration — optional scheduled cache refresh per template, plus per-binding cron walks

• WP-CLI — wp spintax bindings list|apply|test|export|import

• Validation — bracket matching, circular reference detection, syntax checking

• Admin UI — code editor, live preview, shortcode copy, settings page, bindings list

The syntax is an open, documented standard. net. NET, Object Pascal) plus this plugin — are held to one shared test corpus, and a free native Windows editor — Spintax Studio — authors it with live preview and validation.

External services

This plugin does not connect to any external services, APIs, or third-party servers.

All content generation happens locally on your WordPress server. No data is sent externally. No remote requests are made during activation, rendering, or caching.

Privacy Policy

This plugin does not collect, store, or transmit any personal user data. It does not use cookies, tracking pixels, analytics, or any form of telemetry.

Templates and their rendered output are stored entirely within your WordPress database and object cache.

Credits

• Syntax: the open spintax standard documented at spintax.net, rooted in the historical GTW (Generating The Web) application

• Developed by 301st