How do I let my AI agent create WooCommerce products?
On a WooCommerce store, your AI agent or bot can create products, not just edit them. It can create simple products, or variable products with options such as sizes and colours (each with its own price, stock and SKU), add categories, tags and images from a link, and have SEOBetter write the copy: the description, a specs table, an FAQ, the short description, missing image alt text, and the SEO title, meta description and focus keyword.
What you need
- WooCommerce active on the site
- SEOBetter Pro 2.0.13 or newer (2.0.15 or newer for the separate product limit), active on a paid plan
- The SEOBetter Agent add-on 0.5.0 or newer (0.5.1 or newer for the separate product limit, 0.5.12 to be told to save facts first, 0.5.13 for Drafts-mode previews of published products), and the free WordPress MCP Adapter
- A bot key (see "How do I connect a Grok bot (or any 24/7 bot) to SEOBetter?") or an assistant connected over MCP
Step by step
- Update both plugins. In Dashboard, then Updates, update SEOBetter Pro and SEOBetter Agent together. The product creation tools only appear when both are new enough and WooCommerce is active.
- Tick Products on the bot key. Open SEOBetter, then AI bot access. In the key's row, tick Products under the site-wide tools and click Save. It is off for a new key.
- Set Product writes per day. In the same row, set how many products SEOBetter may write for the bot each day: 50 by default, up to 2,000. Product writes have their own limit and never use up Articles per day. Each write still counts against your plan's monthly SEOBetter Cloud allowance, or runs on your own AI key.
- Choose Drafts only or Publish. Start with Drafts only: new products are saved as drafts, and the bot cannot change, write or publish a product that is already live. Switch the key to Publish only when you are happy with its drafts. Even in Publish mode, the bot only has publishing rights for the call that publishes, and it can never delete a product.
- Make one test product first. Ask the agent to create a single draft product with SEOBetter writing its copy, for example: "Find out whether a product with SKU PH already exists. If not, create a draft variable product Padded Dog Harness in sizes S, M and L, write its copy with SEOBetter, and give me the edit link." Open the draft in WooCommerce and check the description, the specs, the FAQ and the SEO fields in your SEO plugin.
- Then work in batches of 50.
bulk-create-productstakes up to 50 rows at a time. Ask the agent to run each batch withdry_runfirst: that checks every row (missing fields, duplicates) without creating anything or using any allowance. Then run it for real and follow progress withget-bulk-job. A batch that would pass the key's product writes left for today is refused whole, so nothing is half done. - Publish when ready. In Publish mode,
publish-productputs a draft live. A variable product can only go live with at least one option for sale.
Supplier notes
Give the agent your supplier's product notes. SEOBetter uses them as facts for the copy, and lines in "Label: value" form (such as Material: nylon webbing) become rows in the specs table. Lines about cost, wholesale price, stock, margin or supplier contacts are removed before writing, so they never appear on your product page.
Honest facts only
The writer only sees the product's own details and your notes, never its price, sale price or stock. Every sentence is checked afterwards: a number, a certification, an award, a guarantee, an origin, safety or health claim, a performance claim such as waterproof, or a first-hand claim that is not in your details is removed, and the agent is told what was removed and why. If fewer than 3 FAQ questions survive, the FAQ is left out.
Health claims
With Health claims on (Settings, General; on by default from Pro 2.0.18), the copy never says a product supports, boosts, improves, promotes, treats, prevents or cures anything about health (immunity, digestion, joints, bones, skin, coat, teeth and the like), even when the brand's own description does, unless that exact claim is in the product's verified claims. Give the agent the claims you have confirmed as verified_claims (one per line); they are kept on the product for later writes. Claims credited to someone else ("the brand says", "according to the manufacturer", "is known to", "may help") are always removed: a verified claim is stated plainly. Ingredients, analysis figures such as "contains 0.8% calcium" and other nutrition facts stay, and a pet food description never gets a feeding amount the product data does not give.
Health claims written as nouns count too (from Pro 2.0.24): "glucosamine for joint health support", "for bone health", "joint care" and "joint health benefits" are removed like "supports joint health". "Contains glucosamine" and "glucosamine 200 mg/kg" stay. A product or range name such as "Churu Bites Joint Support" is not a claim. From Pro 2.0.26 only the name itself is excused: "Joint Support rolls" or the full product name is kept, while "dogs needing joint care support" or "joint support nutrition" is removed unless it is your saved verified claim.
A claim you saved as a verified claim is kept when the copy says it word for word or nearly so (from Pro 2.0.25): "Glucosamine helps support your dog's joint health" is kept for a saved "Contains glucosamine to help support your dog's joint health", and a claim saved with "may help", as it is on the pack, may say "may help". Different health words, or credit added that the saved claim does not have ("according to the manufacturer"), are still removed. Verified claims sent with a write are added to the ones already saved.
From Pro 2.0.28 nutrition claims follow the same rule: "complete feed", "complete daily feed", "complete diet", "complete and balanced", "nutritionally complete" and "all the nutrients" are kept only when you saved that claim word for word as a verified claim, otherwise they are removed as nutrition_claim and needs_facts asks for verified_claims.
Pack sizes and cartons
A sentence that relates packs to units, such as "6 packs of 3 rolls", "18 rolls in total (6 packs of 3)", "3 rolls per pack" or "6 x 3 rolls", is kept only when a saved pack-size fact fixes the carton, and only when it matches that fact exactly (from Pro 2.0.24). Save it exactly as it is on the carton, for example Pack size: 18 rolls in total, 6 packs of 3, in Add facts (or other_facts with add-product-facts), in your supplier notes, or as a product attribute named Pack size, Quantity or Contents. "18 rolls, 6 packs" is not enough, because it does not say how many rolls are in each pack. Without the fact the sentence is removed and the result asks for pack_size in needs_facts. The SEO title includes a pack size only when your product name or that saved fact gives it, never one worked out from other numbers.
From Pro 2.0.25 the saved fact may also be a line in your own words, such as Six packs / 18 rolls in total; three 12 g sticks per pack (with or without a label, or as the Size attribute): number words count, and copy that follows its arithmetic ("6 x 3 = 18") is kept. With a saved pack size, a question in the FAQ such as "How many rolls are in a carton?" is always answered in full from it, for example "18 rolls in total: 6 packs of 3 rolls, 12 g each." An answer that gives only a weight is replaced, and the result lists it with the reason faq_ignores_pack_size.
From Pro 2.0.26 the carton may be saved over two lines, such as Pack size: Carton of 6 packs, 18 rolls in total and Per pack: 3 sticks x 12g (36g net): they are read together, "3 sticks x 12g" is three sticks of 12 g each, and rolls, sticks and tubes count as the same unit. The quantity answer then adds the net weight per pack: "18 rolls in total: 6 packs of 3 rolls, 12 g each (36 g net per pack)." The WooCommerce weight and dimensions are shipping data, never the net contents: a sentence that gives the shipping weight as the carton or net weight is removed with the reason shipping_weight_not_contents. The SKU is never a source of numbers.
From Pro 2.0.28 save the pack size as numbers instead, in the Pack size fields of Add facts or as pack with add-product-facts. For the carton above:
{ "product_id": 14640, "pack": { "pack_count": 6, "units_per_pack": 3, "unit_name": "roll", "unit_weight": { "value": 12, "unit": "g" }, "net_weight_per_pack": { "value": 36, "unit": "g" }, "container_name": "carton" } }
pack_count, units_per_pack and unit_name (singular: roll, tube, stick, sachet, pouch, can, piece, bar) are required; add unit_weight, net_weight_per_pack, total_net_weight (each { "value", "unit" } in g, kg, ml, l, oz or lb), total_units and container_name when the carton states them. SEOBetter checks the sums before it saves anything: total_units must be pack_count x units_per_pack, and the net weight per pack and in total must match the unit weight within 2%. A mismatch is refused with the code invalid_pack and a message that names it. What follows is filled in and returned (here 18 rolls in total and 216 g net in total). Your WooCommerce weight and dimensions are never changed.
With a pack saved this way the writer uses only its numbers: "6 packs of 3 sticks, 18 rolls in total" and "216 g net in the carton" are kept, while "336 rolls" or "40 g per pack" is removed with the reason quantity_not_in_pack_facts. The "How many?" answer is built from it ("18 rolls in total: 6 packs of 3 rolls, 12 g each (36 g net per pack)."), and so is the pack part of a fallback SEO title. A product with only the older text facts is still read the 2.0.26 way. With no pack facts at all, a sentence that states packs, a carton or a total is removed and needs_facts asks for pack.
From Pro 2.1.0: facts are written by SEOBetter, not the AI
From Pro 2.1.0 SEOBetter builds one record per product (brand, product line, variant, type, a clean display name, the quantity, attributes, how to use it, who it suits, your verified claims) and writes every fact itself from it: the SEO title, the start of the meta description, a Pack size line, the "How many?" FAQ, the specs table, your verified claims word for word and template alt text. The AI writes only descriptive prose, and a prose sentence with a digit is removed as number_in_prose (the fact is still on the page). For the carton above the page says "Pack size: 18 rolls in total: 6 packs of 3 rolls, 12 g each (36 g net per pack)." and the title is built like "Inaba Dog Churu Rolls Joint Support Chicken Recipe, 18 Rolls".
The quantity comes from your saved pack. The product name is read as well: "Carton Of 6 24 X 14g Tubes" fills in the 14 g a saved pack of 6 x 4 tubes leaves out. When the name and the saved pack disagree, the saved pack is used, the answer lists the difference in conflicts, and the preview cannot be applied until you fix one of them. With no saved pack, a clear quantity in the name (a count of units of one size, packs of units, or one size such as 500 g) is shown and needs_facts lists confirm_quantity: save it with pack to confirm it.
Every preview has can_apply. Tell your agent to apply the preview (send its preview_token as apply_preview) whenever can_apply is true: can_apply true means apply. blocking names the hard errors (record_conflict, title_not_built, meta_not_built); facts_to_save is optional improvement for you and never a reason to hold the copy back. From Pro 2.1.5 needs_facts appears only when SEOBetter refuses to write because there are too few facts; on every written answer it is empty and its advice (for example confirm_quantity) is in facts_to_save.
From Pro 2.1.2: save facts first, and every sentence is checked
Tell your agent to save the product's facts before it writes: add-product-facts with the ingredients or materials, who it is for, how to use it, the pack as numbers, and any verified claims. Copy written from the name and attributes alone is thinner, and more of it is removed. Every answer says facts_saved (false when the product has no saved facts) and facts_to_save, the facts that would help most for that kind of product, most valuable first, with hints. Neither ever blocks: can_apply still decides.
After the AI writes, a second, cheap check reads every sentence against the product record in its own language and removes what your facts do not back, for example "suitable for rabbits, guinea pigs and insects" on a hay for rabbits and guinea pigs, or "it also suits hamsters" when your facts say rats and mice. The reasons are factcheck:audience, factcheck:use, factcheck:claim, factcheck:fact, factcheck:contradiction and factcheck:other; factcheck_report counts what was checked. If the check cannot run, the answer says factcheck: unavailable, the English checks still remove animals or people and usage your facts do not give, and the preview can still be applied. A sentence repeated in the copy is removed as duplicate.
The product type in the title is the most specific category the product is in ("Cat Treats", "Dog Treats", "Small Animal Food"), never a general one such as Products, Supplies or Small Animal, and never one that disagrees with the name (Cat Food on kitten treats); with no such category it is the name's own word ("Peckish Timothy Hay" is hay). Packaging words such as tubes or rolls are never the product type. From Pro 2.1.4 a category that joins two kinds or runs past three words ("Dog Treats & Chews", "Online Dog Food Australia") is never the product type, and a category is added to the title whole, only when none of its words is already in the name ("Hikari Cichlid Gold Sinking Medium" in Fish Food becomes "Hikari Cichlid Gold Sinking Medium Fish Food, 100 g"; "Dog Churu Rolls" in Dog Treats gets nothing added). Names and categories are read as your shop shows them (no HTML entities such as &), and the brand appears once whatever quotes or dashes it is written with. The title keeps the quantity whenever it fits. When the type comes from a category nothing in the name confirms (kitten tubes filed in Cat Food), or there is none, facts_to_save lists product_type first: have the agent save what the product is with add-product-facts product_type (for example "Cat treats", at most 40 characters), or fill in What the product is in Add facts. It then becomes the product type in the copy, ahead of the name and the categories, and the title adds the words of it the name does not already have, unless they are only a general word such as Food (from Pro 2.1.4). record.quantity.sources says where each quantity value came from (pack, name or attribute), and confirm_quantity lists any value read from the name that your saved pack lacks, with the arithmetic it agrees with (for example 10 g each, 6 x 3 = 18 tubes): save it with pack to confirm it.
From Pro 2.1.3: what the check keeps, lower scores, and Drafts-mode previews
The fact check keeps ordinary shop copy: how the product tastes, smells, feels or looks, that pets enjoy it or find it irresistible, convenience that follows from its form, shopper reasons, and the audience your facts give in any wording ("golden years" on a senior product). It still removes health and need claims, uses your how-to-use does not state (a topper, mixing into meals, training rewards), other audiences, invented details and filler such as "refer to the package". If the check cannot run, factcheck_error says why: timeout, model_error (with provider_status), parse_error, no_sentences or disabled.
A preview that scores lower than the current copy is can_apply false with blocking lower_score, and apply_preview refuses it unless your agent sends allow_lower_score. An equal score can still be applied. would_save always matches can_apply (it is what applying would do); score_gain says whether the copy scores higher, and direct_save_rule says what a new optimise run would do instead.
A bot key in Drafts mode may preview a published product (write-product or optimise-product with preview true, nothing saved), so your agent can show you the copy first. Applying it needs a key in Publish mode.
Who it suits
Wording about who a product suits, such as "dogs of all sizes", "for all breeds", "puppies and adults", "for small dogs" or "suitable for ...", is a claim (from Pro 2.0.25). It is kept only when one saved fact says it: the Suitable for attribute (who_for with add-product-facts), a line in your notes, the product name or a category ("suitable for dogs" on a product in Dog Treats). Otherwise the sentence is removed with the reason audience_not_in_facts and needs_facts asks for who_for.
Your supplier's original description
From Pro 2.1.4 and Agent 0.5.14, leave facts_from_current_copy out. The writer then reads the product's original copy: the current description when SEOBetter never wrote the product, or, for a product SEOBetter already rewrote, the earliest description it did not write (SEOBetter keeps it from the first write). SEOBetter's own earlier rewrites are never read as facts. Each sentence, bullet and "Label: value" line of the original copy is a fact with the source original_copy: it counts towards the 3 facts SEOBetter needs, the writer may restate it, and the fact check accepts a close restatement of it, because your shop already publishes it. A health, nutrition or efficacy claim is kept only when the original copy or your verified claims state it, never beyond. Every result has original_copy (where it was read and how many facts it gave) and facts_found.
The English checks accept the same restatements: a health, nutrition, safety, eco, audience or usage sentence is kept when every word that carries its claim is in your original copy, your verified claims or your other saved facts (never only in the product name).
A number in the prose is kept when it equals a value your record states (the name, an attribute, the pack, your saved notes or the original copy) and counts the same thing ("aged ten years and older" for a "10+ Years" product); any other number is removed as number_in_prose.
From Pro 2.1.5: the fact check reads your supplier's description word for word
When the product has its original supplier description, the English checks no longer remove a health, nutrition, audience, use or number sentence on their own. They flag it, and the fact check decides: it now gets the original description word for word next to your saved facts, and keeps a sentence the description states or directly implies, in other words. "Supports skin, coat, eye and digestive health" is kept when the description lists "Skin & coat health ... Eye health ... Digestive health", "without excess calories" when it says low calorie, and "contains beneficial fibre to support digestive health" when it lists the fibre and the prebiotics for healthy gut bacteria. A claim beyond the description is still removed, such as "a complete food", "nutritionally balanced", "a complete nutritional profile", "provides all the essential nutrients", "helps it thrive", "removes the guesswork" or "goes beyond what other treats offer". Ratings, awards, certification, testing and guarantees are still checked by the English rules alone. Without an original description, or when the check cannot run, the English checks remove the sentence as before.
Number words count as the digits in your description: "between fourteen and twenty-eight days" is kept when it says "between 14 and 28 days".
A pack of one bag, tub or container with a weight is shown as its size: "Vetafarm South American Mix, 350 g" and "Net contents: 350 g.", not "1 x 350 g Bag" or "1 bag in each pack".
From Pro 2.1.6: questions shoppers ask, and a clean focus keyword
The description now ends with a "Questions shoppers ask" section after the FAQ: 4 to 6 long, specific questions phrased the way shoppers and AI shopping assistants actually search ("which food suits South American birds such as conures and quakers and includes fresh Australian grown almonds", "how do I switch my rabbit from a muesli mix to nuggets without upsetting its stomach"). Each is 12 to 25 words and answered in 1 to 3 sentences from the product record only (the original description, your saved facts, the pack and your store policies), with the same checks as the rest of the copy. A question of another length, one that repeats an FAQ question, or one whose answer is removed is dropped with its answer, and the result lists the section as search_questions. It uses the same markup as the FAQ (no extra structured data) and comes in the same write, at no extra cost. The FAQ questions themselves are now specific to the product (8 to 15 words) instead of generic ones such as "What are the main ingredients?"; the quantity question is still answered from your saved pack.
The focus keyword is now the clean search phrase from the product record: the brand and the product line, plus the product type when it stays short ("Vetafarm South American Mix", "Burgess Excel Indoor Guinea Pig Nuggets", "Inaba Churu Sprinkles cat treats"). It never carries the supplier's dashes, a weight or a pack count. A keyword you send, or one already saved in your SEO plugin, is kept when it is a clean phrase like that.
A number restated in another unit counts as the description's own: "between two and four weeks" is kept when it says "between 14 and 28 days", and "1500 g" when it says "1.5 kg". A sentence that sums up benefits your description lists is kept too ("supports multiple aspects of your rabbit's wellbeing, from skin and coat condition to eye health and digestive function" when it lists skin and coat, eye and digestive health); the summary on its own is still removed.
Key details (next Pro release)
Google Merchant Center asks shops to "update product descriptions to include details customers are looking for": for pet food that is the Type, Flavour, Size and Health Benefit. Every description SEOBetter writes now has a "Key details" list right after the opening paragraph, one "Label: value" line per detail, built by SEOBetter from the product record with no AI call. Only details with a value are shown, and each comes from somewhere you can check: the product name, an attribute, the saved pack, the category or your supplier's original description.
The details depend on what the product is:
- Food and treats: Type ("Dry dog food", "Wet cat food", "Dog treats"), Flavour ("Kangaroo", "Chicken & Brown Rice"), Size ("2.5 kg", "12 x 400 g"), Life stage ("Puppy", "Adult 7+"), Breed size ("Large breed"), Special diet ("Grain free", "Hypoallergenic", only words the name or the description uses) and Health benefit.
- Clothing: Type, Colour, Size, Material. Electronics: Type, Model, Compatibility, Power. Beds: Type, Size, Material, Washable. Aquarium: Type, Volume, Suitable for. Anything else: Type, Size, Material, Colour.
A Health benefit is only shown when your verified claims or your supplier's description state one, quoted from it ("Promotes gut health and nutrient absorption"). It shows at most 2 benefits, each a short phrase of up to 80 characters, joined with "; ". A phrase is left out when it has a number or a timeframe ("in as little as 30 days", "within weeks"), names a disease or a cure (cure, treat, prevent, heal, illness, arthritis, diabetes, kidney disease) or uses a superlative ("best", "#1"). Navigation and cross-sell lines in a description ("Shop more ...", "Browse ...", "View our range") are never read for any key detail, so "Shop more wet dog food" does not make a dry food wet. A product line in the name such as "Healthy Mobility" is a name, not a benefit, and nothing is ever made up: with no stated benefit there is no Health benefit line. On the owner's 414 pet foods Merchant Center flagged, 413 get three or more key details from the name alone.
The list is written once: a re-optimise replaces it, never adds a second one. The specs table stays below (Google reads both); a specs row with exactly the same text as a key detail is not repeated. The same details are sent in the SEOBetter product feed as product_detail rows in the section "Key details", with the attribute names Type, Flavour, Size, Life stage, Breed size, Special diet and Health benefit (group A in test mode, every product when test mode is off; a Health benefit only when your description or verified claims state it).
The product score shows an informational check, "Key details for shoppers" (no points): it passes when the description shows 3 or more key details, and the writer adds the list when it fails.
Saved facts only
Send facts_from_current_copy: false with write-product or optimise-product (Pro 2.0.24 and Agent 0.5.9) to use your saved facts only: attributes, saved notes and facts, verified claims and the product name. A number or claim only a description states is then left out, and no description counts towards the 3 facts SEOBetter needs. true also reads the current description, as before Pro 2.1.4 (it can reuse SEOBetter's own earlier copy as facts).
What the result tells you
Every preview and write result lists (from Pro 2.0.24):
fact_sources: each number and claim kept in the copy, per field, with where it came from (saved_fact,attribute,product_name,original_copyfrom Pro 2.1.4,current_copyorstore_policies).image_alts: one row per product image (the main image, the gallery and, from Pro 2.0.25, each variation's image), with its current alt text, the proposed alt text, and whether it was kept (it already had alt text), written or skipped, and why, even when nothing changes.checks_beforeandchecks_after: every score check with its points and maximum, so you can confirm, for example, that Delivery and returns scored 8 of 8.needs_facts: what each removed sentence was missing, such aspack_size,verified_claimsorwho_for, with a hint on how to add it;field_fallbacksnames each field that lost a sentence. From Pro 2.0.25 it never asks for a fact you have already saved. From Pro 2.1.5 this list is infacts_to_save(withfacts_to_save_hints), andneeds_factsis only on a refusal for too few facts.own_key_calls: how many requests went to your own AI key (0 on SEOBetter Cloud).
Never worse, every field
Optimising a product saves new copy only when the product score goes up; otherwise everything is put back and the agent is told why (kept_original). The agent can ask for a preview first, or change only some fields (description, short_description, seo_title, meta_description, focus_keyword, image_alt). To set an SEO title or meta description by hand, the agent uses set-seo-meta.
SEO fields
The SEO title (up to 60 characters), meta description (up to 160) and focus keyword go into Yoast, Rank Math, AIOSEO or SEOPress, whichever you use. A focus keyword you give the agent is used when it is a clean search phrase (from Pro 2.1.6; otherwise the record's own phrase is). SEOBetter never adds article schema to a product: your SEO plugin and WooCommerce keep their own Product structured data.
From Pro 2.0.27, when the SEO title falls back to your product name (field_fallbacks.seo_title: "product_name"), it is built from the name's own parts rather than cut mid-word: whole parts are dropped from the end to fit 60 characters, a title never ends or starts on a stray dash, pipe, colon, comma or slash, and a saved pack size is added when the name does not already state it.
No duplicates
The same SKU is never created twice, and the agent can look a product up first with find-product. A retry with the same client_ref returns the first result instead of creating or writing again.
Limits
- 50 rows per bulk batch, 10 images per product (https links, up to 10 MB each), 20 attributes and 100 variations per product
- Product writes per day per bot key: 50 by default, up to 2,000
- Product creates and product writes: 500 an hour each per user
- Your plan's monthly SEOBetter Cloud allowance: one product write is one article