SmartyPress AI Engine Documentation Article

Classic Editor and WooCommerce

AI Writer button, TinyMCE Magic Wand, and WooCommerce product description support.

Classic Editor And Woocommerce is the focus of this documentation page. AI Writer button, TinyMCE Magic Wand, and WooCommerce product description support. Follow the sections below to configure the feature and use it in your WordPress workflow.

SmartyPress AI Engine also works with the Classic Editor (TinyMCE) and WooCommerce product descriptions. Use the SmartyPress AI Writer button and Magic Wand in the toolbar.

Classic Editor Integration

When the Classic Editor is active, SmartyPress adds:

  • SmartyPress AI Writer button (smartypress-ai-writer-btn) — above the editor, next to Add Media
  • Magic Wand button — in the TinyMCE toolbar

AI Writer Button

Click it to reveal a dropdown with three actions:

Action What It Does
Generate Title Creates an SEO title from your topic
Generate Content Generates full article content
Generate Excerpt Creates a short summary
SmartyPress AI Writer button above the Classic Editor toolbar with its dropdown menu open
In the Classic Editor the button sits next to Add Media and offers three actions instead of four.

TinyMCE Magic Wand

Select text in the editor, then open the Magic Wand menu. The TinyMCE wand offers these actions:

  • Rewrite
  • Expand
  • Fix Grammar & Spelling
  • Summarize
  • Simplify Tone
  • Translate

Unlike the Gutenberg Magic Wand modal, the Classic Editor wand menu does not include Generate FAQs. You must select text before opening a wand action.

WooCommerce Integration

WooCommerce product screens are always treated as Classic Editor for SmartyPress. When product is an enabled post type, SmartyPress enables:

  • AI Writer button on the main product description editor (content)
  • Magic Wand in the main description editor and in the short description editor (excerpt)
  • Title, content, and excerpt generation for products via AI Writer
Note: Make sure “product” is included in your Enabled Post Types (Settings → Post Types) for WooCommerce integration to work.

Enabling Post Types

By default, SmartyPress AI works with Posts, Pages, and Products (if WooCommerce is active). To add custom post types:

  1. Go to SmartyPress AI → Settings.
  2. In the Post Types section, check the types you want to enable.
  3. Save settings.

Classic Editor And Woocommerce Workflow Checklist

The classic editor and woocommerce workflow should be treated as a repeatable process, not a one-time setting. Start by confirming that the SmartyPress AI Engine module related to this page is enabled, then check the default provider, model, language, and post type settings before you run the feature on production content. This keeps generated output predictable and makes it easier to compare results between OpenAI, DeepSeek, OpenRouter, Yandex GPT, and GigaChat.

Use this checklist whenever you document, test, or train another editor on Classic Editor and WooCommerce. It helps keep the setup aligned with WordPress permissions, Rank Math SEO fields, and the editorial workflow used by your site. If a result looks different from what you expected, repeat the same checklist with a smaller prompt and a lower temperature before changing global settings.

  1. Confirm that the required SmartyPress AI module is enabled in the Components screen.
  2. Open Settings and verify that the selected provider has a valid API key and a tested connection.
  3. Choose the model that fits the task: fast models for drafts, premium models for final marketing copy, and web-search models for research.
  4. Review the output language, temperature, max tokens, and prompt variables before generating content.
  5. Save the result as a draft first, then review headings, links, facts, and SEO fields before publishing.

Recommended Settings

For most classic editor and woocommerce tasks, start with a balanced model such as GPT-4o Mini, GPT-4o, DeepSeek Chat, or a carefully selected OpenRouter model. Keep temperature around 0.5 to 0.8 for documentation and tutorials, because these pages need clarity more than experimentation. Increase temperature only when you need more creative headlines, introductions, or alternative wording.

Use a clear default language and keep prompt variables consistent across articles. For documentation pages, a neutral or professional writing tone usually works best. If the generated result is too short, increase the number of sections or paragraphs per section rather than asking the model to “write more” after the fact. Structured settings create more stable output and make Classic Editor and WooCommerce easier to reproduce later.

Scroll to Top