Most WooCommerce catalogues have the same problem: descriptions imported from a supplier, category text nobody read since 2019, and no FAQ where the same three questions repeatedly cost you an order. LLMs are useful for exactly this class of work — volume, structured output, boring but high-margin. Four prompts I actually use for stores.
1. Rewrite supplier product descriptions without losing the SKU
You are a WooCommerce copywriter. I will give you a product with a supplier-supplied description, its attributes and its category. Product name: [NAME] SKU: [SKU] Category: [CATEGORY] Attributes: [color, size, weight, material, etc.] Current description (paste as-is): [PASTE] Rewrite it as: 1. A one-line "for who and why" (25 words max) that a shopper reads first. 2. A short paragraph (3–4 sentences) that describes it in the language a real buyer uses, not the manufacturer's. 3. A bullet list of exactly 5 concrete features — no marketing fluff, only facts a buyer can verify. 4. A one-line "not for you if" that filters out the wrong shopper (fewer returns is worth more than a marginal sale). Keep the SKU and the exact attribute values intact. Do NOT invent specifications. If a specification is missing from what I gave you, leave a bracketed placeholder like [WEIGHT?] so I can fill it in.
Why it works: the SKU + attributes lock the LLM to the actual product, and the “not for you if” line is doing double duty — it reduces returns AND it makes the description sound like a human wrote it, because manufacturers never say who not to sell to. This is the single highest-leverage change on most catalogues.
2. Generate a FAQ schema block from real support questions
You are a WooCommerce SEO copywriter. I run a store selling [CATEGORY / PRODUCT TYPE]. Below are 15 real support tickets I received in the past 3 months. Extract the 5 questions that appear most often (paraphrase, do not quote), then write a FAQPage schema section that: - Answers each in 2–3 sentences, warmly, from the brand's perspective. - Uses the actual language shoppers used, not our internal jargon. - Is honest about limitations (return windows, shipping delays, etc.). - Ends each answer with a link to the relevant page on the store: [BASE URL]. Output as two blocks: 1. Clean markdown for me to paste on a product or category page. 2. A JSON-LD FAQPage block ready to drop into the header. [PASTE 15 TICKETS HERE]
Why it works: FAQ schema helps Google, but the real win is on the page itself — the same three questions block half your buyers, and a store owner rarely knows what they are because they are answering them in tickets one at a time. Aggregating actual tickets is the trick that makes this useful.
3. Upsell copy that does not feel like a used car pitch
Write me 4 versions of an upsell block that appears on a WooCommerce single-product page. Main product: [NAME + ONE-LINE DESCRIPTION] Suggested upsell: [NAME + ONE-LINE DESCRIPTION] Real reason they go together: [ONE HONEST SENTENCE — e.g. "the case protects the screen from the exact drop scenarios that void the warranty"] Constraints on all 4 versions: - Under 40 words each. - No exclamation marks. No "Don't miss out!" No "Only 3 left in stock!" if the stock is not actually 3. - Each version leads with a different frame: 1) practical, 2) financial (bundle math), 3) social (what other buyers did), 4) preventive (avoids a bad outcome). - Include a one-line CTA at the end. Do not use "Add to cart" — write something specific to this product. Then tell me which of the 4 is most likely to convert for THIS product, and why.
Why it works: default WooCommerce upsells are noise (“You may also like…”). Framing the upsell around the actual reason the two products belong together makes it feel like advice, not a pitch. The “no false urgency” constraint keeps you out of dark-pattern territory that also happens to hurt long-term trust.
4. Category text that ranks and reads
You are a WooCommerce SEO writer. Write a category description for this page:
Category name: [NAME]
Category slug: /category/[SLUG]
Number of products: [X]
Main use-cases (from browsing my catalogue): [LIST 2-3]
Main audiences: [LIST 2-3]
Structure:
1. First 40 words: what this category is FOR, in shopper language. This is the meta description.
2. Next 60 words: how to choose from within the category — what factors matter (price, size, use case).
3. Final block: a 3-question FAQ that pre-empts the friction points that come up in support (paraphrase, do not fabricate).
Rules:
- Do not stuff the exact category name into every sentence.
- Do not use "Welcome to our collection of...". Ever.
- Include one honest signal about the store's expertise ("we hand-pick", "we test in-house", whatever is TRUE — I will confirm).
- Include internal links to at most 3 related categories (I will provide slugs on request).
Why it works: most category text is either empty or scraped. A structure that leads with utility (“what this category is for”) and follows with decision help (“how to choose”) reads like a knowledgeable shop assistant. That translates to lower bounce, more time on site, and gradually better rankings for the category page itself.
A note on scale
If you have 500+ products, you are not going to run these prompts one at a time. Wrap them in a script that iterates your CSV export, or use a workflow tool like n8n or Make with the OpenAI/Anthropic node. The prompt is the recipe — the pipeline is up to you. But for a store with 50 products, one focused afternoon with these four prompts and a coffee is enough to lift conversion measurably.