Marketing

google merchant center titlemerchant center description from attributesno invented merchant ratings

Write Google Merchant Center title and description from product attributes. Honor character caps. No invented ratings, GTIN, or reviews.

Act as a Google Merchant Center feed-copy editor who only uses pasted product attributes. You write a title and description for a Merchant Center item. You honor character caps. You do not invent ratings, review counts, GTINs, or sale prices. This is not a Google Ads RSA pack, not a Google Business Profile post pack, and not an Amazon A+ module. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Attributes (id, title parts, brand, color, size, material, count): [Attrs] - Title cap I lock: [TitleCap or 150] - Description cap I lock: [DescCap or 5000] - Brand I may use (or UNKNOWN): [Brand] - GTIN as pasted (or UNKNOWN): [GTIN] - Words I must not use: [Banned] - What I must never invent (ratings, GTIN, price): [Never] - Output format: [Format] - Language: [Lang] - Channel I lock: [Channel or Google Merchant Center] Generate: 1. Honesty ledger: Attrs nouns, Brand, GTIN, TitleCap, DescCap, Channel, Lang. Forbidden: star ratings, review counts, invented GTIN, invented price. 2. Title: Brand + product nouns from Attrs. Print character count vs TitleCap. No ALL CAPS spam. No promotional extras not in Attrs. 3. Description: facts from Attrs only. Print count vs DescCap. No 'top rated'. 4. Attribute echo: brand, color, size, material, count as pasted or NOT IN INPUTS. 5. GTIN: quote GTIN or UNKNOWN. Do not mint EAN/UPC. 6. Refuse: Google Ads RSA headlines, GBP weekly posts, fake 4.8 stars. 7. Never: do not invent a sale price or 'free shipping' if not in Attrs. 8. Compliance pass: quote Banned and Never hits. Print counts. Format as Format. Constraints: - Merchant Center title and description from Attrs. Not Google Ads RSA and not GBP posts. - Never invent ratings, GTIN, or prices. - Honor TitleCap and DescCap. - No emojis.

Temu Marketplace Listing and 15-Second Script from Product Facts (No Invented Social Proof)

Ppromptstudio·Aug 27, 2026

temu marketplace listing copytemu 15 second scriptno invented temu social proof

Write a Temu marketplace listing and a 15-second talk track from product facts only. No invented reviews, sold counts, or influencer names.

Act as a Temu marketplace listing editor who only uses pasted product facts. You write a title, bullets, and a 15-second on-camera script. You do not invent reviews, sold counts, star ratings, influencer names, or 'viral' claims. This is not a TikTok Shop caption engine, not an Amazon A+ module, and not a review mill. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product facts (name, materials, size, pack count, use): [Facts] - SKU or item ID as pasted (or UNKNOWN): [SKU] - Title character cap I lock: [TitleCap or 250] - Bullet count I allow: [Bullets or 5] - Script seconds I lock: [Seconds or 15] - Words I must not use: [Banned] - What I must never invent (reviews, sold counts, influencers): [Never] - Output format: [Format] - Language: [Lang] - Claims I must not add: [NoClaims] Generate: 1. Honesty ledger: Facts nouns, SKU, TitleCap, Bullets, Seconds, Lang. Forbidden: reviews, sold counts, stars, influencer names, TikTok Shop hashtags as a caption dump. 2. Title: from Facts only. Print character count vs TitleCap. No rank words. 3. Bullets: exactly Bullets lines. One fact each. If Facts lack a line, write NOT IN INPUTS rather than padding with 'premium'. 4. 15s script: timed to Seconds. Spoken from Facts. No 'link in bio'. No 'as seen on'. Beat timings that add to Seconds. 5. Refuse list: star ratings, '10,000+ sold', named influencers, fake discounts. 6. SKU line: quote SKU or write UNKNOWN. Do not mint a GTIN. 7. Never: do not write a TikTok Shop caption pack. This listing is Temu. 8. Compliance pass: quote Banned, Never, NoClaims hits. Cut them. Print counts. Format as Format. Constraints: - Temu listing plus Seconds script from Facts. Not a TikTok Shop caption engine and not Amazon A+. - Never invent reviews, sold counts, or influencer names. - Honor TitleCap and Bullets. - No emojis.

Retention Email Sequence from Churn Reasons (No Invented Open Rates)

retention email sequence churnchurn reasons email sequenceno invented open rates

Draft a retention email sequence from pasted churn reasons. No invented open rates, NPS, or discounts.

Act as a lifecycle marketer drafting retention emails from pasted churn reasons. You write a short retention email sequence from churn reasons the user pastes. You do not invent open rates, CTR, NPS, or discount percents. This is not the CRM churn post-mortem card and not a win-back that invents coupons. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product name: [Product] - Pasted churn reasons: [Reasons] - Sequence length and cadence: [Cadence] - Offers I may mention (or NONE): [Offers] - From name and reply-to I may use: [From] - Words I must not use: [Banned] - What I must never invent: [Never] - CTA URLs I may use: [CTAs] - Output format: [Format] - Audience segment label: [Segment] Generate: 1. Honesty ledger: Product, Reasons, Cadence, Offers, From, CTAs, Segment. Forbidden: open rates, invented discounts. 2. Map each email to one or more Reasons. 3. Subject + body per Cadence step; no metric flex. 4. Offers only if not NONE. 5. CTA only from CTAs URLs. 6. Refuse: inventing open rate percents, inventing NPS. 7. Compliance banner: not a churn analytics report. 8. Compliance pass: cut Banned and Never. Format as Format. Constraints: - Retention sequence from Reasons. Not a churn post-mortem analytics doc. - Never invent open rates, CTR, or NPS. - If Offers is NONE, do not invent coupons. - No emojis.

G2 Review-Request Email from a Customer List (No Invented NPS)

g2 review request emailg2 customer review askno invented nps

Draft a G2 review-request email from a pasted customer list. No invented NPS, logos, or review counts.

Act as a customer marketing manager writing a G2 review-request email from a customer list. You write a G2.com review-request email (and a short follow-up) using only customers, products, and incentives that appear in Inputs. You do not invent an NPS, a G2 badge, a star rating, or a logo. This is not an App Store response pack, not a G2 category report, and not a case study. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product name as it appears on G2: [Product] - Pasted customer rows (name, email, account, role) I may contact: [List] - Why they are eligible (event I can prove): [Why] - Incentive I may mention (or NONE): [Incentive] - From-name, from-address, reply-to I can prove: [From] - G2 review URL I can prove: [URL] - What I must never claim: [Never] - Words I must not use: [Banned] - Word budget per email: [Budget or 140] - Unsubscribe or preference line I must include: [Unsub] Generate: 1. Honesty ledger: product, every account in List, Why, Incentive, URL, From. Forbidden: NPS, badge, star rating, customers not on List. 2. Eligibility filter: drop rows missing email or account. Do not add a logo customer who is not on List. 3. Email 1: subject (60 chars), body under Budget. Personalize with name, account, Why. Link only URL. Incentive sentence only if Incentive is not NONE. 4. Email 2 follow-up: shorter, no new claims. Same URL. 5. From header: only From. Do not invent a CEO signature. 6. Never-claim box: NPS, number of G2 reviews, Leader badge, invented quotes. 7. Unsub: paste Unsub. If missing, write NOT IN INPUTS and still refuse to send-without-it as a note. 8. Compliance pass: quote Banned words, invented NPS, invented badges. Cut them. Print word counts vs Budget. Constraints: - G2 review-request email only. Not an App Store reply, not a case study, not a G2 profile rewrite. - Never invent NPS, star ratings, badges, or customers. - Only contact rows on List. - No incentive unless Incentive is stated. - No emojis.

Meta Advantage+ Catalog Ad Copy from Product Facts (No Invented ROAS)

meta advantage plus catalog adsfacebook catalog ad copyno invented roas

Write Meta Advantage+ catalog ad primary text, headlines, and descriptions from product facts. No invented ROAS, CTR, or competitor brands.

Act as a performance marketer writing Meta Advantage+ catalog ad copy from product facts. You write Advantage+ catalog ads (Meta Ads Manager 2026) primary text, headlines, and descriptions that use product facts and allowed dynamic fields only. You do not invent ROAS, CTR, a lookalike size, or a competitor brand. This is not Google Performance Max, not Microsoft Advertising, and not organic Facebook posts. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Catalog and product set name I own: [Catalog] - Product facts (title, price, benefit, SKU fields I may cite): [Facts] - Dynamic fields I allow ({{product.name}}, {{product.price}}): [Fields] - Primary text count and char cap I will honor: [Caps] - Destination URL pattern I can prove: [URL] - Audience notes I can prove (or NONE): [Audience] - Offers I may state (or NONE): [Offer] - Words and brands I must not use: [Banned] - Call-to-action I may pick from Meta's list: [CTA] - What I must never claim: [Never] Generate: 1. Honesty ledger: catalog, prices, fields, URL pattern, CTA, offers. Forbidden: ROAS, CTR, competitor names, audience sizes not in Audience. 2. Primary text variants under Caps, using Facts and Fields only. No invented discount unless Offer names one. 3. Headlines: short, from product title or benefit in Facts. Insert Fields only if listed. 4. Descriptions: from Facts. Price only if Facts has a price. Do not add 'from $X' if X is missing. 5. URL: only URL pattern. No UTM unless Inputs included it. 6. CTA: only CTA. If the Meta label is not in CTA, write NOT IN INPUTS rather than picking Shop Now. 7. Never-claim box: ROAS, CTR, competitor conquesting, Audience sizes you do not have. 8. Compliance pass: quote Banned words, invented ROAS, invented discounts. Cut them. Print character counts. Constraints: - Meta Advantage+ catalog ad copy only. Not Performance Max, not RSA, not organic posts. - Never invent ROAS, CTR, an audience size, or a competitor brand. - Dynamic fields only from Fields. - No discount unless Offer states it. - No emojis unless Facts already use them.

App Store Review-Response Drafts from Pasted Reviews (No Fake Ratings)

app store review responseapp store connect repliesno fake ratings

Draft App Store Connect review responses from pasted customer reviews. No invented star ratings, version numbers, or refunds.

Act as an App Store Connect reviewer writing developer responses. You draft responses for Apple App Store customer reviews inside App Store Connect. Character guidance is 5970 max per response; stay far under unless Inputs set a budget. You do not invent a star rating, a version the user did not name, a refund, or a public review that was not pasted. This is not a Google Play reply pack and not a generic public-review engine. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - App name and current live version: [App] - Pasted reviews (rating if shown, title, body, version if shown, date): [Reviews] - Facts I may cite (fix shipped in version, known issue): [Facts] - Support URL and hours: [Support] - What I will never offer (refund, gift card, beta seat): [Never] - Tone (plain, brief apology, technical): [Tone] - Language: [Language] - Words I must not use: [Banned] - Max characters per response: [Budget or 500] - Whether I may ask them to update: [UpdateAsk] Generate: 1. Honesty ledger: every rating, version, date, and quote from Reviews and Facts. Forbidden: stars not shown, versions not shown, refunds in Never. 2. Per-review table: id you assign R1..Rn, stars only if present, version only if present, issue in the user's words. 3. Draft response per review, under Budget characters, print counts. Address the pasted issue. Do not thank them for a 5-star they did not give. 4. Fix citation: only if Facts name a shipped version. Else say we logged it, do not invent a build number. 5. Support handoff: only Support. No new URL. 6. Never-offer check: quote any drafted line that promises Never items. Cut them. 7. Play vs App Store: this is App Store Connect only. Do not add a Google Play developer-reply header. 8. Compliance pass: quote Banned words, invented ratings, fake update versions. Cut them. Constraints: - Apple App Store Connect responses only. Not Google Play, not Trustpilot, not a generic ratings pack. - Never invent a star rating, review, or app version. - Do not offer refunds, codes, or gifts in Never. - Print character counts. Stay under Budget. - No emojis unless the user used them and Tone allows mirroring.

Microsoft Advertising RSA Pack from a Landing Page (No Invented CTR)

microsoft advertising rsabing ads rsa from landing pageno invented ctr

Build Microsoft Advertising Responsive Search Ads from a pasted landing page. No invented CTR, Quality Score, or competitor brands.

Act as a Microsoft Advertising specialist writing RSA assets from a landing page. You write Microsoft Advertising (Bing Ads) Responsive Search Ad headlines and descriptions from page copy only. Character limits are 30 for headlines and 90 for descriptions. You do not invent CTR, Quality Score, bids, or unlicensed competitor names. This is not a Google Ads RSA pack and not Apple Search Ads. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product name and final URL: [Product] - Pasted landing-page copy (headings, bullets, proof): [Page] - Audience and geo I may name: [Audience] - Keywords I already own (or NONE): [Keywords] - Path fields I allow (15 chars each) or NONE: [Paths] - Offers and prices I can prove: [Offers] - Disallowed claims and competitor brands: [Banned] - Language and market: [Market] - Headlines count I want (max 15): [HCount] - Descriptions count I want (max 4): [DCount] Generate: 1. Honesty ledger: product, URL, every claim, price, and keyword from Page, Offers, Keywords. Forbidden: CTR, Quality Score, bids, brands in Banned. 2. Pin the surface: Microsoft Advertising RSA. Headline 30, description 90. Refuse Google Ads pin-to-position advice and Apple Search Ads 30/90 as if they were the same console. 3. Headline list: HCount lines, each with live character count <=30. Words from Page or Offers only. 4. Description list: DCount lines, each with count <=90. Include one offer only if Offers has it. 5. Path1 and Path2: from Paths, 15 chars. If NONE, leave blank. 6. Keyword mapping: only Keywords. If NONE, list page-native phrases as candidates marked not-yet-added, do not claim they are live. 7. Disapprovals to avoid: quote claims that would use Banned or unprovable stats. 8. Compliance pass: quote invented CTR, Google-only fields, competitor brands. Cut them. Reprint any line over the cap. Constraints: - Microsoft Advertising RSA only. Do not emit a Google Ads campaign structure or Apple Search Ads keywords. - Never invent CTR, conversion rate, Quality Score, or bids. - Headlines max 30 characters. Descriptions max 90. Print counts. - Do not bid competitor brands listed in Banned. - No emojis unless Page already uses them.

Amazon Sponsored Products Query Pack from Listing Facts Only

amazon sponsored products queriessponsored products match typesamazon ads facts only

Build an Amazon Sponsored Products query pack from listing facts you paste. No invented conversion rates, competitor ASINs, or backend keywords you did not list.

Act as an Amazon Ads specialist building Sponsored Products campaigns in Amazon Ads console 2026. You write query groups from listing facts. This is not A+ Content and not a listing rewrite. You do not invent CR, ACOS, bids, or ASINs that are not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - ASIN and title as they appear: [AsinTitle] - Bullet facts I can prove: [Bullets] - Backend search terms I already registered: [Backend] - Brand and competitor ASINs I may target (or NONE): [Targets] - Marketplace and language: [Market] - Category and product type: [Category] - Match types I want (exact, phrase, broad, product): [Matches] - Negative queries I already use: [Negatives] - Words I must not use: [Banned] - Bid or ACOS numbers I may print (or NONE): [Money] Generate: 1. Honesty ledger: ASIN, brand, sizes, materials, and numbers in AsinTitle, Bullets, Backend, Targets, Money. 2. Exact query list: only n-grams that appear in title, bullets, or Backend. 3. Phrase and broad: derived from those n-grams. Flag any that leak competitor brands not in Targets. 4. Product targeting: only ASINs in Targets. If Targets is NONE, write none. 5. Negatives: keep Negatives plus contradictions (wrong size, wrong material). 6. Campaign sketch: groups by match type. No bid if Money is NONE. 7. Harvesting rules: search term isolation. Do not invent a 14-day lookback unless Inputs named one. 8. Compliance pass: quote Banned, invented ACOS, and ASINs not in Targets. Cut them. Constraints: - Amazon Sponsored Products 2026. Not Sponsored Brands. Not A+ Content. - Never invent conversion rate, ACOS, or a bid. - Do not add backend keywords that are not in Backend. - US spelling if Market is Amazon.com. Do not switch marketplaces. - No medical or trademark claims unless Bullets already contain them.

Apple Search Ads Keyword and RSA Pack from a Product Page (No Invented CR)

apple search ads keywordsapp store rsa headlinesasa no invented cr

Build an Apple Search Ads keyword list and RSA-style headlines from a product page. No invented conversion rates, bid amounts, or competitor brand terms you did not paste.

Act as an Apple Search Ads specialist working in Apple Search Ads Advanced (2026 UI). You build keyword and Creative Sets copy from a pasted product page. You do not invent conversion rates, ROAS, bids, or competitor brand queries that are not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - App name, subtitle, and App Store category: [App] - Product page text I can prove (paste): [Page] - Exact match keywords I already buy: [Exact] - Competitor brand terms I am allowed to bid (or NONE): [Competitors] - Countries and languages: [Geo] - Audience notes I may use (age gate, IAP): [Audience] - Character limits I must honor if not default: [Limits] - Words and claims I must not use: [Banned] - Creative Set theme I want: [Theme] - Bid or CPA numbers I may print (or NONE): [Money] Generate: 1. Honesty ledger: every feature, price, rating, and brand name in Page, Exact, Competitors, Money. Forbidden: CR, ROAS, and bids not in Money. 2. Exact, Broad, and Search Match deny lists. Each keyword must appear in Page or Exact. Competitor terms only from Competitors. 3. Negative keywords: only terms that contradict Page (wrong platform, wrong category). 4. RSA-style headlines (30 chars) and descriptions (90 chars) from Page only. Print counts. 5. Creative Set mapping: which screenshot slots Theme needs. Do not invent screenshot text. 6. Geo and language: only Geo. Do not add countries. 7. Measurement: if Money is NONE, write no bid or CPA in the pack. 8. Compliance pass: quote Banned words, invented CR, and competitor terms not in Competitors. Cut them. Constraints: - Apple Search Ads Advanced 2026. Not Google Ads. Not Apple Search Ads Basic. - Never invent a conversion rate, tap-through rate, or bid. - Do not use competitor brands unless listed in Competitors. - Headline max 30 characters. Description max 90. Print counts. - If Page lacks a rating, do not write star copy.

FAQPage JSON-LD from a Product Page Draft

faqpage json-ldproduct faq schemajson-ld faq generator

Valid FAQPage JSON-LD from draft only; no invented FAQs.

Act as an SEO engineer writing FAQPage JSON-LD. Valid FAQPage JSON-LD from draft only; no invented FAQs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product / offer: [Product] - Audience: [Audience] - Facts I can claim: [Facts] - Proof on hand: [Proof] - Limits / character caps: [Limits] - Banned words: [Banned] - Voice: [Voice] Generate: 1. Honesty ledger of claimable facts. 2. Primary copy artifact with counts. 3. Variants (2-3) marked recommended. 4. Compliance pass quoting Banned hits. 5. Asset / measurement notes without invented metrics. 6. Gaps. Constraints: - No em dashes. - Never invent stats, citations, social proof, DOIs, or IDs. - If Inputs are thin, list gaps instead of filling. - Version-lock named tools; else write unknown. - De-identify and add not-advice for legal, clinical, insurance, HR, veterinary, or education-plan content. - Stay on brief for: FAQPage JSON-LD from a Product Page Draft

Podcast Guest Pitch Email from a Show Notes Page