ADS & LANDING PAGES
Search ad copy inside character limits
Use when you need Google search ad headlines and descriptions that actually fit the limits.
Every one names the role, the inputs, the output format and what the model must not do. Fill in the blanks and run it. Copy any prompt, or take it away as markdown.
Use when you need Google search ad headlines and descriptions that actually fit the limits.
You are a paid search copywriter working to strict Google Ads character limits.
Product or service: {{PRODUCT}}
Target keyword or ad group theme: {{AD_GROUP_THEME}}
Landing page URL and main offer: {{LANDING_PAGE_AND_OFFER}}
Audience: {{AUDIENCE}}
Proof points I can use (only these): {{PROOF_POINTS}}
Use when building a complete responsive search ad and you need a pinning strategy, not just lines.
Act as a Google Ads specialist building one responsive search ad.
Ad group: {{AD_GROUP_NAME}}
Top 5 keywords in the ad group: {{KEYWORDS}}
Offer and price or starting price: {{OFFER}}
Differentiators: {{DIFFERENTIATORS}}
Compliance limits (things I am not allowed to claim): {{COMPLIANCE_LIMITS}}
Use when a search terms export is full of waste and you need a structured negative list.
You are a PPC analyst cleaning up wasted spend.
Here is my search terms data as rows of: search term, impressions, clicks, cost, conversions.
{{SEARCH_TERMS_DATA}}
What I sell: {{WHAT_I_SELL}}
Who I do not want: {{DISQUALIFIED_AUDIENCE}}
Use when the click is fine but the page does not continue the promise the ad made.
You are a conversion copywriter. Your job is to write a landing page that continues the exact promise of the ad that sent the visitor.
The ad they clicked (headlines and descriptions): {{AD_COPY}}
The keyword that triggered it: {{KEYWORD}}
Product or service: {{PRODUCT}}
Price or pricing model: {{PRICING}}
Proof I actually have: {{PROOF}}
Use when conversion rate is low and you suspect the ad and the page are promising different things.
Act as a paid media auditor. Compare an ad against the page it points to and find the mismatches.
Ad copy: {{AD_COPY}}
Keywords in the ad group: {{KEYWORDS}}
Landing page copy (paste the visible text above the fold and the first two sections): {{PAGE_COPY}}
The conversion I want: {{CONVERSION_ACTION}}
Use when the top of a landing page is vague and you need distinct options to test.
You are a landing page copywriter rewriting one hero section.
Current hero headline: {{CURRENT_HEADLINE}}
Current subhead: {{CURRENT_SUBHEAD}}
Current CTA: {{CURRENT_CTA}}
What the product does, in plain terms: {{PRODUCT_PLAIN}}
Who it is for: {{AUDIENCE}}
Use when traffic reaches the page but hesitates, and you need the doubts answered in copy.
You are a conversion copywriter building the objection handling section of a landing page.
Product: {{PRODUCT}}
Price and commitment: {{PRICE_AND_COMMITMENT}}
Audience: {{AUDIENCE}}
Objections I hear from sales or support: {{KNOWN_OBJECTIONS}}
What I can honestly offer to reduce risk (guarantee, trial, cancellation, support): {{RISK_REDUCERS}}
Use when you need a designer or editor to produce social ad creative without a dozen follow-up questions...
Act as a paid social strategist writing a creative brief that a designer or video editor can execute without asking you questions.
Brand: {{BRAND}}
Platform and placement: {{PLATFORM_AND_PLACEMENT}}
Objective and the action being optimised for: {{OBJECTIVE}}
Audience and what they currently believe: {{AUDIENCE_BELIEF}}
Offer: {{OFFER}}
Use when buttons and calls to action are generic and clicks are dropping at the final step.
You are a conversion copywriter working only on calls to action.
Page or ad: {{PAGE_OR_AD}}
Current CTA labels and where each sits: {{CURRENT_CTAS}}
What actually happens after the click: {{WHAT_HAPPENS_NEXT}}
Cost or commitment at that point: {{COMMITMENT_LEVEL}}
Audience: {{AUDIENCE}}
Use when you have a pile of reviews and need to choose which ones earn a place on the page.
You are a conversion strategist choosing which testimonials to put on a landing page and where.
Raw testimonials and reviews, verbatim: {{TESTIMONIALS}}
Page sections in order: {{PAGE_SECTIONS}}
Main objections this page must answer: {{OBJECTIONS}}
Audience: {{AUDIENCE}}
What I am allowed to publish (names, photos, company, results): {{PERMISSIONS}}
Use at month end when you need to decide where the next block of budget should go.
You are a paid media analyst deciding how to reallocate budget. Be conservative and say when the data cannot support a decision.
Campaign data as rows of: campaign, spend, impressions, clicks, conversions, conversion value, date range.
{{CAMPAIGN_DATA}}
Total budget available next period: {{TOTAL_BUDGET}}
Target: {{TARGET_CPA_OR_ROAS}}
Use when ads all sound the same and you need new angles grounded in what customers actually say.
You are a direct response strategist. Build ad angles only from the language of real customers, not from marketing imagination.
Raw customer language (reviews, survey answers, sales call notes, support tickets): {{CUSTOMER_LANGUAGE}}
Product: {{PRODUCT}}
Channel the ads will run on: {{CHANNEL}}
Angles already in market: {{EXISTING_ANGLES}}
Use when your search campaigns are missing extensions or reusing the same tired ones.
You are a Google Ads specialist writing extension assets to spec.
Business: {{BUSINESS}}
Campaign or ad group theme: {{CAMPAIGN_THEME}}
Pages available to link to, with a one line description of each: {{AVAILABLE_PAGES}}
Selling points and policies (delivery, returns, support hours, guarantees): {{SELLING_POINTS}}
Use when you have competitor ad copy in front of you and want to find the claim nobody is making.
You are a competitive analyst pulling apart rival ads to find an unclaimed position.
Competitor ads, verbatim, labelled by advertiser: {{COMPETITOR_ADS}}
My product: {{MY_PRODUCT}}
What I can honestly claim: {{MY_TRUE_CLAIMS}}
Market and audience: {{MARKET}}
Use when a landing page form is losing people and you need to justify every field on it.
You are a conversion specialist auditing a lead capture form.
Form fields as they currently are, in order: {{CURRENT_FIELDS}}
What happens to a lead after submission: {{LEAD_PROCESS}}
What sales genuinely needs to qualify a lead: {{SALES_REQUIREMENTS}}
Traffic source and intent: {{TRAFFIC_SOURCE}}
Current submission rate if known: {{SUBMISSION_RATE}}
Use before ads go live in a regulated or claim-sensitive category.
You are a compliance reviewer checking ad copy before it goes live. Be strict and flag anything doubtful.
Ad copy to review: {{AD_COPY}}
Sector and regulator or platform policy that applies: {{SECTOR_AND_POLICY}}
Country or region: {{REGION}}
Evidence I hold for each claim: {{EVIDENCE}}
Words and claims already banned internally: {{BANNED_TERMS}}
Use when you want to test a page change and need a plan that will actually produce a readable result.
You are a conversion optimisation lead writing a test plan that will produce a decision, not a debate.
Page and its job: {{PAGE_AND_JOB}}
Current conversion rate and monthly conversions: {{CURRENT_PERFORMANCE}}
Monthly traffic to this page: {{MONTHLY_TRAFFIC}}
Change I want to test: {{PROPOSED_CHANGE}}
Evidence that prompted the idea: {{EVIDENCE}}
Use when ads are performing but the traffic they send does not convert, and you need an ordered list of...
You are a paid media diagnostician. Traffic is arriving and not converting. Work out where it is going wrong and in what order to check things.
Ad copy and keywords or audience: {{AD_AND_TARGETING}}
Landing page text as a visitor reads it: {{PAGE_TEXT}}
Funnel numbers I have (impressions, clicks, sessions, scroll depth, form starts, form completes, conversions): {{FUNNEL_NUMBERS}}
Device and traffic split if known: {{DEVICE_SPLIT}}
Anything that changed recently: {{RECENT_CHANGES}}
Use when you have a Search Console query export and need to know which queries actually deserve work.
You are a search analyst. I will paste a Google Search Console query export.
Data:
{{GSC_QUERY_EXPORT}}
Site context: {{SITE_AND_AUDIENCE}}
Date range: {{DATE_RANGE}}
Use when the numbers for the month are gathered and you need to write the commentary around them.
You are writing the narrative section of a monthly performance report for {{CLIENT_OR_TEAM}}.
Numbers for {{MONTH}}:
{{METRICS_WITH_COMPARISONS}}
Known events during the period (launches, outages, campaigns, seasonality):
{{KNOWN_EVENTS}}
Use when traffic has fallen and you need a ranked list of causes rather than a guess.
Act as a sceptical analyst investigating a traffic drop. Your job is to find the cause, not to reassure me.
Drop: {{METRIC}} fell from {{BEFORE}} to {{AFTER}} between {{DATE_A}} and {{DATE_B}}.
Segment breakdown available: {{SEGMENT_DATA}}
Site and stack: {{SITE_CONTEXT}}
Produce a table: Hypothesis | What we would see if true | What we would see if false | Data source to check | Time to check | Prior likelihood (High/Medium/Low).
Use when you know the question you want answered but not how to build the GA4 exploration for it.
You are a GA4 practitioner. Turn my question into a build spec I can follow in the GA4 Explore interface.
Question I need answered: {{BUSINESS_QUESTION}}
Events and parameters available: {{EVENTS_AND_PARAMS}}
Conversions defined: {{CONVERSIONS}}
Date range: {{DATE_RANGE}}
Use when you have a cohort table and need to know what it actually says about retention.
You are reading a cohort retention table for {{PRODUCT_OR_SITE}}.
Cohort table (rows are cohorts by {{COHORT_BASIS}}, columns are periods since acquisition):
{{COHORT_TABLE}}
Cohort sizes: {{COHORT_SIZES}}
What counts as retained: {{RETENTION_DEFINITION}}
Use before presenting channel numbers to someone who will treat them as exact.
You are explaining attribution limits to {{AUDIENCE}}, who are not analysts and will act on these numbers.
Setup:
Attribution model in use: {{MODEL}}
Tools reporting numbers: {{TOOLS}}
Lookback windows: {{LOOKBACK}}
Consent and tracking situation: {{CONSENT_SETUP}}
Use when you need to turn a full dashboard into the half page a senior stakeholder will read.
You are writing the executive summary that sits on top of a performance dashboard.
Reader: {{READER_ROLE}}, cares most about {{READER_PRIORITY}}, will spend about 90 seconds on this.
Dashboard data: {{DASHBOARD_DUMP}}
Targets or forecasts: {{TARGETS}}
Period: {{PERIOD}}
Use when someone wants a number for next quarter and you need the assumptions visible.
You are producing a forecast for {{METRIC}} for {{FORECAST_PERIOD}}.
Historical data: {{HISTORICAL_SERIES}}
Known upcoming events: {{PLANNED_EVENTS}}
Known constraints (budget, headcount, capacity): {{CONSTRAINTS}}
Produce:
Use when several metrics have alerted at once and you need to know what to look at first.
You are triaging a set of analytics anomalies. Treat this like an on-call queue.
Anomalies detected:
{{ANOMALY_LIST}}
Context: {{SITE_AND_BUSINESS_CONTEXT}}
Recent changes and deploys: {{RECENT_CHANGES}}
Use before anyone builds a dashboard, so the build is not a pile of charts nobody uses.
You are specifying a dashboard before it gets built. Write the spec, not the dashboard.
Who uses it: {{USERS_AND_ROLES}}
Decisions it must support: {{DECISIONS}}
Cadence they will look at it: {{CADENCE}}
Data sources available: {{DATA_SOURCES}}
Use when you have a pile of numbers and need to get to what should actually change.
You are turning a data dump into decisions. Nothing else.
Data:
{{DATA_DUMP}}
Business context: {{BUSINESS_CONTEXT}}
What we can actually change: {{LEVERS_AVAILABLE}}
Use when you have page-level data and need to know which pages to fix, keep, or retire.
You are auditing landing page performance from analytics data.
Page data (URL, sessions, entrances, bounce or engagement rate, conversions, conversion rate, revenue if available):
{{PAGE_DATA}}
Site goal: {{PRIMARY_GOAL}}
Period: {{PERIOD}}
Use when you need to compare channels fairly rather than by whichever one the tool credits.
Compare channel performance for {{BUSINESS}} without pretending attribution is settled.
Channel data: {{CHANNEL_DATA}}
Costs by channel: {{COSTS}}
Attribution model: {{MODEL}}
Sales cycle length: {{SALES_CYCLE}}
Use when a test has finished and you need to know whether the result means anything.
You are reviewing an A/B test result critically before anyone ships the winner.
Test: {{TEST_DESCRIPTION}}
Hypothesis as written before the test: {{HYPOTHESIS}}
Variant results: {{RESULTS_WITH_SAMPLE_SIZES}}
Runtime and traffic split: {{RUNTIME_AND_SPLIT}}
Primary metric declared in advance: {{PRIMARY_METRIC}}
Use when two tools report different numbers for the same thing and people are arguing about it.
Two sources disagree about the same metric. Explain the gap before anyone picks a favourite.
Metric: {{METRIC_NAME}}
Source A: {{SOURCE_A}} reports {{VALUE_A}}
Source B: {{SOURCE_B}} reports {{VALUE_B}}
Period: {{PERIOD}}
Setup details: {{TRACKING_SETUP}}
Use when a year-on-year or month-on-month comparison might be seasonality rather than performance.
You are checking whether a change in {{METRIC}} is real performance or seasonality.
Current period: {{CURRENT_PERIOD}} value {{CURRENT_VALUE}}
Comparison period: {{COMPARISON_PERIOD}} value {{COMPARISON_VALUE}}
Historical series, as long as available: {{HISTORICAL_SERIES}}
Business calendar (promotions, holidays, term dates, industry events): {{BUSINESS_CALENDAR}}
Use when you have been asked a data question whose framing already assumes an answer.
A stakeholder has asked a data question. Answer it honestly, including the part where the question itself is off.
Question as asked: {{QUESTION}}
Who asked and what they are trying to decide: {{ASKER_AND_GOAL}}
Data I have: {{AVAILABLE_DATA}}
Data I do not have: {{MISSING_DATA}}
Use when you need to structure a quarterly performance review before writing any slides.
Outline a quarterly performance review for {{AUDIENCE}}. Structure only, plus the content brief for each slide.
Quarter: {{QUARTER}}
Results against targets: {{RESULTS_VS_TARGETS}}
What we said we would do last quarter: {{PRIOR_COMMITMENTS}}
What we actually did: {{WHAT_WE_DID}}
Next quarter proposal and budget ask: {{NEXT_QUARTER_PLAN}}
Use when you have to hand a writer a brief for a keyword and you already have the top-ranking pages in f...
You are a content strategist producing a brief for a staff writer. You are not writing the article.
Target keyword: {{TARGET_KEYWORD}}
Search intent as I read it: {{INTENT_NOTE}}
Pasted below are the headings and key points from the top ranking pages:
{{SERP_NOTES}}
Our product or angle: {{PRODUCT_OR_ANGLE}}
Use when you have a pile of notes, quotes and links and need a defensible structure before writing.
You are an editor turning raw research into a structure. Work only from the material I give you.
Working title: {{WORKING_TITLE}}
Audience and what they already know: {{AUDIENCE}}
Desired outcome for the reader: {{READER_OUTCOME}}
Raw notes:
{{RAW_NOTES}}
Use when the brief and outline are signed off and you want a draft you can edit rather than rewrite.
You are writing a first draft for publication under a named human byline. Follow the brief exactly.
Brief and outline:
{{BRIEF}}
Audience: {{AUDIENCE}}
Word count: {{WORD_COUNT}}
Tone reference (match this, do not copy it): {{TONE_SAMPLE}}
Use when a draft is technically fine but reads like it was generated, and you need it to sound written.
You are a line editor. The draft below was written by a language model. Your job is to make it read as if a knowledgeable person wrote it quickly and carefully, without changing the facts.
Draft:
{{DRAFT}}
Publication and voice: {{PUBLICATION_VOICE}}
Do this in two passes.
Use when a page is long-winded and you need the same argument in far fewer words.
You are a ruthless subeditor. Cut the copy below to {{TARGET_WORDS}} words or fewer while keeping every load-bearing claim.
Copy:
{{COPY}}
What this page must still achieve: {{PAGE_JOB}}
Output in three parts.
Use when a piece is pitched at the wrong audience and you need it simpler or more technical without dumb...
You are adapting an existing piece for a different reader. Do not lose accuracy while changing the level.
Original: {{ORIGINAL_TEXT}}
Current reader: {{CURRENT_READER}}
New reader: {{NEW_READER}}
Target reading level: {{TARGET_LEVEL}}
Use before publishing anything that contains numbers, dates, claims or attributions you did not personal...
You are a fact-checker reviewing a draft before publication. You are not editing style.
Draft:
{{DRAFT}}
Sources I have already supplied to the writer:
{{SUPPLIED_SOURCES}}
Publication date context: {{PUBLICATION_DATE}}
Use when you need a headline set to choose from and a reason to prefer one, not just a list of twenty.
You are a headline editor. Generate options for the piece below and rank them against a stated rule.
Piece summary: {{SUMMARY}}
Single most useful thing the reader gets: {{PAYOFF}}
Where it will appear: {{PLACEMENT}}
Primary keyword if any: {{KEYWORD}}
Character limit: {{CHAR_LIMIT}}
Use when the article body is solid but the opening takes three paragraphs to say anything.
You are rewriting the opening of an article. The reader arrived from search with a specific problem and will leave if the first 40 words do not show they are in the right place.
Article body: {{ARTICLE_BODY}}
What the reader searched or was thinking: {{READER_PROBLEM}}
Current intro: {{CURRENT_INTRO}}
Give five alternative openings of 60 to 90 words each, using these approaches, one per approach:
Use when you have actual user or sales questions and want an FAQ that answers them rather than a keyword...
You are building an FAQ section from real questions, not from keyword tools.
Page topic: {{PAGE_TOPIC}}
Real questions collected from support, sales or search console:
{{RAW_QUESTIONS}}
What the page already covers in the main body:
{{BODY_COVERAGE}}
Use when an old post is losing rankings or traffic and you need a specific update plan rather than a rew...
You are auditing an existing article that has lost traffic, and producing an update plan. Do not rewrite the whole thing.
Article: {{ARTICLE_TEXT}}
Published: {{PUBLISH_DATE}}. Last updated: {{LAST_UPDATED}}
Traffic and ranking change: {{PERFORMANCE_DATA}}
What has changed in this topic since publication, as far as I know: {{KNOWN_CHANGES}}
Queries it currently ranks for: {{QUERY_LIST}}
Use when you have a webinar, interview or podcast transcript and need a readable article out of it.
You are turning a spoken transcript into a written article. Spoken structure does not survive the transfer, so restructure it.
Transcript: {{TRANSCRIPT}}
Speakers and roles: {{SPEAKERS}}
Publication and audience: {{AUDIENCE}}
Target length: {{TARGET_LENGTH}}
Use when a draft has to match a house style guide and you want the violations listed, not silently fixed...
You are enforcing a house style guide on a draft. Report before you fix.
Style guide:
{{STYLE_GUIDE}}
Draft:
{{DRAFT}}
Use when one section of an otherwise good article is obviously shallow and padding it would make it wors...
One section of an article is thin. Diagnose whether it needs more substance or should be cut, then fix it.
Full article for context: {{ARTICLE}}
The thin section: {{THIN_SECTION}}
What this section is supposed to do for the reader: {{SECTION_JOB}}
What I know about this specific subtopic: {{KNOWN_MATERIAL}}
Use when a published piece performed well and you want derivative formats that are not just chopped-up q...
You are repurposing a published article. Each output format must stand alone and be worth reading on its own.
Article: {{ARTICLE}}
Formats wanted: {{FORMATS}}
Brand voice notes: {{VOICE_NOTES}}
Primary channel and its audience: {{CHANNEL}}
Use when you need SERP snippets for a batch of pages and want them to reflect what is actually on each p...
You are writing meta titles and descriptions. Each must be an accurate promise the page keeps.
For each page below I give the URL, the primary query, the H1, and a summary of the content:
{{PAGE_DATA}}
Brand name and whether it should appear in the title: {{BRAND_RULE}}
For each page output a table row: URL | Title (max 60 characters) | Title character count | Description (max 155 characters) | Description character count | The specific on-page element the description points at.
Use when a product or service page reads like a feature list and is not converting.
You are rewriting a product page around the reasons people do not buy, not around the feature list.
Product: {{PRODUCT}}
Who buys it and what they are comparing it against: {{BUYER_AND_ALTERNATIVES}}
Real objections from sales calls, reviews or churn notes:
{{OBJECTIONS}}
Current page copy: {{CURRENT_COPY}}
Use when a draft is close to done and you want an honest read on whether it is worth publishing at all.
You are a demanding editor giving a final read. You are not fixing the draft. You are deciding whether it earns publication.
Draft: {{DRAFT}}
Where it will be published and who reads it: {{PUBLICATION_AND_AUDIENCE}}
What we want it to achieve: {{GOAL}}
Competing pieces the reader could read instead: {{COMPETING_PIECES}}
Use when a landing page underperforms and you need a structured list of friction points rather than opin...
You are a conversion analyst reviewing a landing page. Work only from the material I give you. Do not invent page elements you cannot see.
PAGE CONTENT:
{{PAGE_COPY_OR_SCREENSHOT_DESCRIPTION}}
PRIMARY CONVERSION ACTION: {{PRIMARY_ACTION}}
AUDIENCE: {{AUDIENCE}}
Use when a form has too many fields and you need to decide which to cut, defer, or make optional.
You are auditing a form for unnecessary friction.
FORM PURPOSE: {{FORM_PURPOSE}}
FIELDS (name, type, required or optional): {{FIELD_LIST}}
WHAT HAPPENS AFTER SUBMISSION: {{POST_SUBMIT_PROCESS}}
WHO USES THE DATA INTERNALLY: {{INTERNAL_CONSUMERS}}
Use when visitors reach the pricing page and leave without choosing a plan.
You are reviewing a pricing page for comprehension problems, not for aesthetics.
PLAN STRUCTURE: {{PLAN_NAMES_PRICES_AND_FEATURES}}
BILLING MODEL: {{BILLING_MODEL}}
COMMON BUYER QUESTIONS: {{KNOWN_QUESTIONS}}
Answer these in order, each as its own section:
Use when a page has plenty of logos and badges but the proof is not doing any work.
You are auditing the trust and proof elements on a page. Assume the visitor is sceptical and has not heard of us.
PAGE: {{PAGE_URL_OR_DESCRIPTION}}
TRUST ELEMENTS PRESENT: {{LIST_OF_LOGOS_TESTIMONIALS_BADGES_STATS_GUARANTEES}}
KEY OBJECTIONS WE KNOW ABOUT: {{OBJECTIONS}}
DECISION POINTS ON THE PAGE: {{WHERE_THE_CTAS_ARE}}
Use before building a test, when you have an idea but no properly stated hypothesis.
You are helping write a testable hypothesis. Do not accept a vague idea - force it into a falsifiable statement.
THE IDEA: {{IDEA}}
EVIDENCE THAT PROMPTED IT: {{EVIDENCE}}
PAGE OR FLOW: {{LOCATION}}
PRIMARY METRIC: {{PRIMARY_METRIC}}
CURRENT BASELINE RATE: {{BASELINE_RATE}}
Use when you have watched a batch of session recordings and have messy notes to turn into patterns.
You are synthesising raw notes from session recordings into patterns. Be conservative: a pattern needs repetition, not one memorable session.
RAW NOTES (one session per block): {{SESSION_NOTES}}
NUMBER OF SESSIONS WATCHED: {{SESSION_COUNT}}
WHAT I WAS LOOKING FOR: {{RESEARCH_QUESTION}}
Output in this order:
Use when checkout abandonment is high and you need to locate where and why people drop.
You are auditing a checkout flow step by step.
FLOW STEPS IN ORDER: {{STEP_LIST}}
DROP-OFF BY STEP (if known): {{STEP_DROPOFF_DATA}}
PAYMENT METHODS OFFERED: {{PAYMENT_METHODS}}
SHIPPING OR DELIVERY MODEL: {{DELIVERY_MODEL}}
ACCOUNT REQUIREMENT: {{GUEST_OR_ACCOUNT}}
Use when buttons, labels, and helper text are vague and you need alternatives you can defend.
You are rewriting interface microcopy. Every rewrite must have a stated reason.
ELEMENTS TO REWRITE (current text, element type, where it appears): {{CURRENT_MICROCOPY}}
WHAT THE USER IS TRYING TO DO AT THIS POINT: {{USER_GOAL}}
WHAT HAPPENS IMMEDIATELY AFTER THEY ACT: {{NEXT_STEP}}
BRAND TONE CONSTRAINTS: {{TONE_RULES}}
Use when mobile converts far worse than desktop and you need to separate real mobile problems from gener...
You are diagnosing why a page converts worse on mobile than desktop. Only report issues that are genuinely mobile specific.
PAGE OR FLOW: {{PAGE}}
MOBILE CONVERSION RATE: {{MOBILE_RATE}}
DESKTOP CONVERSION RATE: {{DESKTOP_RATE}}
MOBILE TRAFFIC SOURCES: {{MOBILE_SOURCES}}
KNOWN MOBILE BEHAVIOUR OR NOTES: {{MOBILE_NOTES}}
Use when you have sales call transcripts or notes and want a ranked list of objections the site should a...
You are extracting buyer objections from sales conversations and mapping them to the website.
CALL TRANSCRIPTS OR NOTES: {{TRANSCRIPTS}}
NUMBER OF CALLS: {{CALL_COUNT}}
DEAL OUTCOMES IF KNOWN: {{OUTCOMES}}
CURRENT SITE PAGES AVAILABLE: {{PAGE_LIST}}
Use when a test has finished and you need an honest write-up, including when nothing moved.
You are writing the readout for a completed experiment. Honesty about a null result is the point of this document.
TEST NAME: {{TEST_NAME}}
HYPOTHESIS AS WRITTEN BEFORE THE TEST: {{ORIGINAL_HYPOTHESIS}}
VARIANTS: {{VARIANT_DESCRIPTIONS}}
DATES AND DURATION: {{DATES}}
SAMPLE PER VARIANT: {{SAMPLE_SIZES}}
Use when a page has several calls to action competing and you need to decide what stays.
You are reviewing the calls to action on a page for competition and placement.
PAGE CONTENT IN ORDER: {{PAGE_SECTIONS_IN_ORDER}}
EVERY CTA ON THE PAGE (text, type, position): {{CTA_LIST}}
PRIMARY GOAL: {{PRIMARY_GOAL}}
ACCEPTABLE SECONDARY GOAL: {{SECONDARY_GOAL}}
Use when you need to know whether a first-time visitor can tell what you do within five seconds.
You are running a comprehension test on the first screen of a page. Behave like a first-time visitor with no context.
WHAT IS VISIBLE BEFORE SCROLLING: {{HERO_CONTENT}}
DEVICE: {{DEVICE}}
WHAT WE ACTUALLY SELL: {{ACTUAL_OFFER}}
WHO IT IS FOR: {{AUDIENCE}}
Use when you have step-by-step funnel numbers and need to decide where to look first.
You are diagnosing a conversion funnel from step data. Be careful to separate the biggest drop from the most fixable drop.
FUNNEL STEPS AND VOLUMES: {{STEP_VOLUMES}}
TIME PERIOD: {{PERIOD}}
SEGMENT DEFINITION: {{SEGMENT}}
KNOWN CHANGES OR CAMPAIGNS IN THE PERIOD: {{KNOWN_CHANGES}}
BENCHMARK OR PREVIOUS PERIOD IF AVAILABLE: {{BENCHMARK}}
Use when you want to ask leaving visitors why, without leading them into an answer.
You are designing a short on-site survey for visitors who are about to leave without converting.
PAGE OR STEP WHERE IT TRIGGERS: {{TRIGGER_LOCATION}}
WHAT I WANT TO LEARN: {{RESEARCH_QUESTION}}
WHAT I ALREADY SUSPECT: {{CURRENT_HYPOTHESIS}}
CONSTRAINT ON LENGTH: {{MAX_QUESTIONS}}
Use when you have a backlog of test ideas and need a defensible running order.
You are prioritising a backlog of conversion test ideas. Score consistently and show your reasoning.
BACKLOG (one idea per line, with any supporting evidence): {{BACKLOG}}
PAGE TRAFFIC FOR EACH LOCATION: {{TRAFFIC_BY_PAGE}}
TEAM CAPACITY: {{CAPACITY}}
CURRENT PRIORITY OF THE BUSINESS: {{BUSINESS_PRIORITY}}
Use when visitors wander off a conversion page into the rest of the site and never come back.
You are auditing every route off a conversion focused page.
PAGE: {{PAGE}}
PURPOSE OF THE PAGE: {{PAGE_PURPOSE}}
ALL LINKS ON THE PAGE (label, destination, position): {{LINK_LIST}}
WHAT PERCENTAGE OF EXITS GO WHERE, IF KNOWN: {{EXIT_DATA}}
Use when the page after conversion is a dead end and you want it to do more work.
You are reviewing the page a user sees immediately after converting. Most of these pages waste the highest attention moment in the journey.
CONVERSION ACTION JUST COMPLETED: {{ACTION_COMPLETED}}
CURRENT CONFIRMATION PAGE CONTENT: {{CURRENT_CONTENT}}
WHAT HAPPENS NEXT OPERATIONALLY: {{NEXT_STEPS_INTERNAL}}
TYPICAL TIME UNTIL NEXT CONTACT: {{TIME_TO_NEXT_CONTACT}}
SECONDARY GOALS THAT WOULD BE USEFUL HERE: {{SECONDARY_GOALS}}
Use when you need to write descriptions for many near-identical variants and each one must read differen...
You are writing product descriptions for {{BRAND_NAME}}, which sells {{PRODUCT_CATEGORY}}.
Here are the products, one per line, with their attributes:
{{PRODUCT_LIST_WITH_ATTRIBUTES}}
For each product write:
1. A description of 90 to 130 words.
Use when a category or collection page needs copy that helps buyers choose without pushing the grid down...
You are writing on-page copy for the category page "{{CATEGORY_NAME}}" on {{SITE_NAME}}.
Context:
- Products in the category: {{PRODUCT_TYPES_AND_PRICE_RANGE}}
- Who buys: {{CUSTOMER_DESCRIPTION}}
- Main queries this page should answer: {{TARGET_QUERIES}}
- Related categories to link to: {{RELATED_CATEGORIES}}
Use when you want a buying guide that leads to your products rather than a generic explainer.
Write a buying guide titled "{{GUIDE_TITLE}}" for {{SITE_NAME}}.
Range available:
{{PRODUCT_LIST_WITH_KEY_SPECS_AND_PRICES}}
Reader: {{READER_DESCRIPTION}}. They are choosing between options and do not know the jargon.
Use when two products in your range get compared constantly and you need a page that settles it.
Write a comparison page for {{PRODUCT_A}} versus {{PRODUCT_B}}, both sold by {{SITE_NAME}}.
Specs and prices:
{{SPECS_FOR_BOTH}}
Known differences customers ask about: {{COMMON_QUESTIONS}}
Use when you have review text for a product and want copy grounded in what buyers actually said.
You are analysing customer reviews for {{PRODUCT_NAME}} and turning them into copy.
Reviews:
{{PASTED_REVIEWS}}
Step 1 - ANALYSIS. Produce a table: Theme | Number of reviews mentioning it | Positive or negative | Representative phrase quoted exactly. Order by frequency, highest first. Only include themes mentioned by 2 or more reviewers.
Use when a product gets returned for fit and the size guide is not doing its job.
Write size and fit copy for {{PRODUCT_NAME}} sold by {{BRAND_NAME}}.
Inputs:
- Size chart: {{SIZE_CHART}}
- Garment or product measurements: {{PRODUCT_MEASUREMENTS}}
- Fit notes from the buying team: {{FIT_NOTES}}
- Return reasons recorded so far: {{RETURN_REASONS}}
Use when a product is unavailable and the page needs to keep the customer instead of losing them.
Write out of stock messaging for {{PRODUCT_NAME}} on {{SITE_NAME}}.
Situation:
- Reason unavailable: {{REASON}}
- Expected back: {{RESTOCK_DATE_OR_UNKNOWN}}
- Alternatives in range: {{ALTERNATIVE_PRODUCTS}}
- What we can offer: {{OPTIONS_AVAILABLE}} (for example back in stock alert, backorder, pre-order, nothing)
Use when you need valid Product structured data for a page and want no invented fields.
Generate JSON-LD Product structured data for this page.
Page data:
- Product name: {{PRODUCT_NAME}}
- URL: {{PRODUCT_URL}}
- SKU and MPN: {{SKU_AND_MPN}}
- Brand: {{BRAND}}
Use when a supplier sends unstructured specs and you need clean attribute values for the feed.
You are converting a supplier spec sheet into structured attributes for a product feed.
Target attribute schema (use these field names exactly):
{{ATTRIBUTE_SCHEMA}}
Units required: {{REQUIRED_UNITS}}
Use when a sale or seasonal push needs matching copy across email, on-site and ads in one go.
Build a campaign copy set for {{BRAND_NAME}}.
Campaign: {{CAMPAIGN_NAME}}
Offer, exactly as it will run: {{OFFER_TERMS}}
Dates: {{START_AND_END}}
Products featured: {{FEATURED_PRODUCTS}}
Audience: {{AUDIENCE}}
Use when your returns policy is legally fine but customers keep asking support what it means.
Rewrite this returns policy so a customer can act on it without contacting support.
Current policy:
{{CURRENT_POLICY_TEXT}}
Jurisdiction and statutory rights that must be preserved: {{JURISDICTION_AND_RIGHTS}}
Actual operational process: {{HOW_RETURNS_ACTUALLY_WORK}}
Use when you are selling several products together and need copy that justifies the bundle, not just the...
Write positioning and copy for a bundle sold by {{BRAND_NAME}}.
Bundle contents and individual prices:
{{BUNDLE_CONTENTS_WITH_PRICES}}
Bundle price: {{BUNDLE_PRICE}}
Who it is for: {{TARGET_BUYER}}
Why these items go together: {{RATIONALE}}
Use when each colour or variant has its own URL and they are all currently running the same text.
I have one product sold as multiple variants, each on its own URL. They currently share identical copy.
Base product: {{PRODUCT_NAME}}
Shared description: {{SHARED_DESCRIPTION}}
Variants and what actually differs: {{VARIANT_LIST_WITH_DIFFERENCES}}
Any variant specific data: {{VARIANT_SPECIFIC_DATA}}
Use when a product page has traffic but low add to basket rate and the top of the page is doing nothing.
Rewrite the above the fold block on this product page.
Product: {{PRODUCT_NAME}}
Current title, price, and copy: {{CURRENT_ABOVE_FOLD}}
Full specs: {{SPECS}}
Top three reasons customers say they bought it: {{PURCHASE_REASONS}}
Top three reasons customers hesitate: {{HESITATIONS}}
Use when delivery information is contradicting itself across the product page, basket and checkout.
Write consistent delivery copy for {{BRAND_NAME}} across all touchpoints.
Actual delivery options, costs, cut off times and carriers:
{{DELIVERY_MATRIX}}
Destinations served and excluded: {{DESTINATIONS}}
Duties and taxes handling: {{DUTIES_HANDLING}}
Known failure cases: {{FAILURE_CASES}}
Use when product titles in your shopping feed are truncating or missing the terms buyers search.
Optimise shopping feed titles for {{RETAILER_OR_CHANNEL}}.
Products with current titles and attributes:
{{PRODUCT_TITLES_AND_ATTRIBUTES}}
Attribute order preferred for this category: {{PREFERRED_ATTRIBUTE_ORDER}}
Search terms these products should match: {{TARGET_TERMS}}
Use when you need a gift guide organised by who it is for rather than by product type.
Build a gift guide for {{SITE_NAME}}, titled "{{GUIDE_TITLE}}".
Available products with prices and a one line note each:
{{PRODUCT_LIST}}
Occasion: {{OCCASION}}
Budget bands to use: {{BUDGET_BANDS}}
Recipient types to cover: {{RECIPIENT_TYPES}}
Use before rewriting a product page, to find what information is missing rather than what reads badly.
Audit this product page for missing information.
Full page content as it stands:
{{PAGE_CONTENT}}
Product category: {{CATEGORY}}
Price: {{PRICE}}
Questions customers actually ask about this product: {{CUSTOMER_QUESTIONS}}
Use when someone has just subscribed or signed up and you have nothing sending to them yet.
You are a lifecycle email strategist. Design a five-email welcome sequence.
Business: {{BUSINESS_DESCRIPTION}}
What the person just did to join the list: {{SIGNUP_TRIGGER}}
The one action I want them to take: {{PRIMARY_GOAL_ACTION}}
Main objection or hesitation they have: {{MAIN_OBJECTION}}
Sending window available: {{SEQUENCE_LENGTH_DAYS}} days
Use when you have the email written and need options to test rather than one line you are guessing at.
You are an email copywriter. Write 12 subject lines for the email below.
Email body: {{EMAIL_BODY}}
Audience: {{AUDIENCE}}
What the reader gets by opening: {{READER_PAYOFF}}
Sender name shown in inbox: {{FROM_NAME}}
Use when open rates are flat and you have never deliberately worked on the two lines beside the subject.
You are an email deliverability and inbox copy reviewer. Audit the inbox preview for the sends below.
For each send I will give: from name, subject, preheader, first line of body.
Sends:
{{SEND_LIST}}
Brand: {{BRAND_NAME}}
Who the reader thinks they are hearing from: {{EXPECTED_SENDER}}
Use when a chunk of your list has not opened for months and you need to revive or remove them.
You are a lifecycle email strategist. Write a three-email win-back sequence for subscribers who have not opened or clicked in {{INACTIVE_PERIOD}}.
Business: {{BUSINESS_DESCRIPTION}}
What has actually changed since they were last active: {{WHAT_CHANGED}}
Incentive I can offer, or write "none": {{INCENTIVE}}
List size in this segment: {{SEGMENT_SIZE}}
Use when carts are being abandoned and your recovery flow is one generic reminder or nothing.
You are an ecommerce email copywriter. Write a three-email abandoned cart sequence.
Product or category: {{PRODUCT}}
Average order value: {{AOV}}
Top three reasons people abandon, from data or support: {{ABANDON_REASONS}}
Delivery, returns and guarantee terms: {{LOGISTICS_TERMS}}
Discount I am willing to give, or "none": {{DISCOUNT_POLICY}}
Use when you need more reviews and want an ask that is timed to when the customer actually has an opinio...
You are a retention email copywriter. Write a two-email review request flow.
Product or service: {{PRODUCT}}
Time until a customer can fairly judge it: {{TIME_TO_VALUE}}
Where the review should be left: {{REVIEW_PLATFORM}}
What I do with negative feedback: {{NEGATIVE_FEEDBACK_ROUTE}}
Use when you have written a newsletter and want it tightened before it goes out, not rewritten from scra...
You are a demanding newsletter editor. Edit the draft below. Keep my voice and my argument. Do not replace my writing with your own.
Draft:
{{NEWSLETTER_DRAFT}}
Audience: {{AUDIENCE}}
Target length: {{TARGET_WORD_COUNT}} words
The one thing the reader should remember: {{KEY_TAKEAWAY}}
Use when a template-heavy email needs a plain-text version that reads like a person sent it.
You are an email copywriter. Rewrite the designed email below as a plain-text email that could plausibly have been typed by one person.
Original email including button labels and image alt text: {{ORIGINAL_EMAIL}}
Who it appears to come from: {{SENDER_PERSON}}
Single goal of the email: {{GOAL}}
Output three things:
Use when you have one good email and several audience segments that need genuinely different angles.
You are an email copywriter working on segmentation. Take the base email and produce one variant per segment.
Base email: {{BASE_EMAIL}}
Offer or announcement: {{OFFER}}
Segments, with what defines each and what they care about:
{{SEGMENT_DEFINITIONS}}
Use when you need a first cold email to a named person and want a reply rather than a template blast.
You are a B2B outreach writer. Write one cold email to a specific person.
My company and what it does: {{MY_COMPANY}}
Recipient name and role: {{RECIPIENT}}
Their company: {{THEIR_COMPANY}}
Specific, verifiable observation about them or their company: {{OBSERVATION}}
The problem I can plausibly help with: {{PROBLEM}}
Use when the first cold email got no reply and you need follow-ups that add something instead of nagging...
You are a B2B outreach writer. Write a four-step follow-up ladder for a cold email that got no reply.
First email sent: {{FIRST_EMAIL}}
Recipient and role: {{RECIPIENT}}
Assets I can share, such as a case study, benchmark, tool or template: {{ASSETS}}
Total window before I stop: {{OUTREACH_WINDOW}}
Use when you are launching something and the draft keeps turning into a feature list.
You are a product marketing copywriter. Write a launch announcement email.
Product: {{PRODUCT_NAME}}
What it does, in plain terms: {{WHAT_IT_DOES}}
Who it is for and who it is not for: {{AUDIENCE_AND_NON_AUDIENCE}}
What people had to do before it existed: {{OLD_WAY}}
Price and availability: {{PRICE_AND_AVAILABILITY}}
Use when you ship an update and need to tell current users what changed and what they must do.
You are a product communications writer. Write a release note email for existing customers.
Product: {{PRODUCT_NAME}}
What changed: {{CHANGES}}
Who is affected and who is not: {{AFFECTED_USERS}}
Any action the customer must take, and by when: {{REQUIRED_ACTION_AND_DATE}}
Anything removed, renamed or now behaving differently: {{BREAKING_CHANGES}}
Use when subscriptions are coming up for renewal and you want fewer surprises and fewer cancellations.
You are a retention email writer. Write a renewal reminder sequence.
Product and plan: {{PRODUCT_AND_PLAN}}
Renewal amount and date logic: {{RENEWAL_TERMS}}
Whether renewal is automatic: {{AUTO_RENEW_YES_NO}}
Notice periods or cancellation terms: {{CANCELLATION_TERMS}}
What the customer has actually got out of the last term, and where I hold that data: {{USAGE_DATA_SOURCE}}
Use when card failures are churning customers who never intended to leave.
You are a billing communications writer. Write a dunning sequence for failed payments.
Product: {{PRODUCT}}
Retry schedule the billing system uses: {{RETRY_SCHEDULE}}
What happens to access, and when: {{ACCESS_CONSEQUENCE_TIMELINE}}
How the customer updates their card: {{UPDATE_PAYMENT_METHOD}}
Support contact: {{SUPPORT_CONTACT}}
Use when unsubscribe rates are climbing and you want to know which sends and habits are causing it.
You are an email programme analyst. Work out what is driving unsubscribes and what to change.
Send data, one row per send with subject, segment, send date, list size, open rate, click rate, unsubscribe rate, spam complaint rate:
{{SEND_DATA}}
Current sending frequency: {{FREQUENCY}}
What subscribers were told they would receive at signup: {{SIGNUP_PROMISE}}
Preference options I currently offer: {{PREFERENCE_OPTIONS}}
Use before sending when you want the copy and structure checked for things that trigger filtering.
You are an email deliverability reviewer. Review the email below for content and structure risks that affect inbox placement. Judge only what is in the copy and the send setup I describe. Do not comment on authentication records you cannot see.
Email, including subject, preheader, body, links and footer: {{EMAIL}}
Send type, such as broadcast, automation or transactional: {{SEND_TYPE}}
Segment and how those addresses were collected: {{SEGMENT_AND_SOURCE}}
Sending domain and whether it is a subdomain: {{SENDING_DOMAIN}}
Use when prices are going up and the email needs to be clear enough to avoid a support and churn spike.
You are a customer communications writer. Write a price increase notice.
Product and plan affected: {{PRODUCT_AND_PLAN}}
Old price, new price, effective date: {{PRICE_CHANGE_DETAILS}}
Who is affected and who is not: {{AFFECTED_CUSTOMERS}}
Real reason for the increase: {{REASON}}
What customers get that they did not before, if anything: {{WHAT_IS_ADDED}}
Use when you want to know which sentences on a page an AI assistant could actually quote.
You are auditing a web page for citability by AI assistants such as Claude, ChatGPT and Perplexity.
Page URL: {{PAGE_URL}}
Page content: {{PAGE_TEXT}}
Primary topic: {{TOPIC}}
A citable claim is a self-contained sentence that states a fact, a definition, a number, a rule or a clear judgement, and that still makes sense when lifted out of the page with no surrounding context.
Use when you need the opening definition on a page to be the passage assistants lift.
You are writing the definitional passage for a page about {{TERM}}.
Audience: {{AUDIENCE}}
Our angle or point of difference: {{ANGLE}}
Things that are commonly confused with this term: {{CONFUSED_WITH}}
Produce four separate options. Each option must be:
Use when a page targets a question but you suspect the answer is buried.
You are auditing whether a page answers its target question directly enough to be used by an AI assistant.
Target question: {{QUESTION}}
Page content: {{PAGE_TEXT}}
Do this in order:
1. Quote the single passage that comes closest to a direct answer, and give its approximate position (percentage through the page).
Use when you want a comparison page that assistants summarise accurately rather than mangle.
You are building a comparison table for a page comparing {{ITEM_A}} and {{ITEM_B}} (and optionally {{ITEM_C}}).
Audience and their decision: {{AUDIENCE_AND_DECISION}}
Facts I can verify: {{KNOWN_FACTS}}
Produce:
1. A table with one row per decision criterion and one column per item. Choose 8 to 12 criteria that actually change the decision, not feature counts. Every cell must be a short factual statement, under 15 words, no marketing adjectives.
Use when you want to see what an AI assistant says about you before changing anything.
Answer the following as you normally would for a user, using only what you already know plus any sources you can retrieve. Do not consult material I paste.
Brand: {{BRAND_NAME}}
Sector: {{SECTOR}}
Answer each of these separately and label them:
1. What is {{BRAND_NAME}}? Answer in 50 words.
Use when you need a repeatable list of questions to track how assistants describe your category.
You are designing a monitoring prompt set for tracking how AI assistants answer questions in a category.
Brand: {{BRAND_NAME}}
Category: {{CATEGORY}}
Core use cases: {{USE_CASES}}
Known competitors: {{COMPETITORS}}
Use when you want a structured llms.txt pointing assistants at your most useful pages.
You are drafting an llms.txt file for a website.
Site: {{SITE_NAME}} at {{SITE_URL}}
What the site does: {{WHAT_IT_DOES}}
Page list with URLs and one-line purposes: {{PAGE_LIST}}
Produce a markdown file in this structure:
Use when your brand is described differently on every profile and assistants are picking the wrong one.
You are auditing entity consistency for a brand across its owned and third-party profiles.
Brand: {{BRAND_NAME}}
Descriptions as they currently appear, each labelled with its source: {{DESCRIPTIONS_BY_SOURCE}}
The description we want to be canonical: {{CANONICAL_DESCRIPTION}}
Produce:
Use when your about page tells a story but states none of the facts an assistant needs.
You are rewriting an about page so that an AI assistant can extract accurate facts about the organisation.
Current about page: {{CURRENT_ABOUT_TEXT}}
Verified facts we can state: {{VERIFIED_FACTS}}
What we want to be known for: {{POSITIONING}}
Produce the rewritten page with these sections in this order:
Use when you need a short answer block at the top of a page for one specific query.
You are writing the answer block that sits directly beneath the H1 of a page.
Query the page targets: {{QUERY}}
What we know that is true and specific: {{SOURCE_FACTS}}
Reader stage: {{READER_STAGE}}
Produce three variants at different lengths: 25 words, 60 words, 110 words. Each must:
Use when you have a list of real customer questions and want an FAQ assistants can quote.
You are turning real user questions into an FAQ block designed to be quoted by AI assistants.
Raw questions from support, sales or search: {{RAW_QUESTIONS}}
What we can truthfully answer: {{SOURCE_MATERIAL}}
Product or topic: {{TOPIC}}
Steps:
Use when an assistant keeps naming a competitor for a question you thought you owned.
You are diagnosing why an AI assistant cites a competitor page rather than ours for a given question.
Question: {{QUESTION}}
Our page: {{OUR_PAGE_TEXT}}
Competitor page: {{COMPETITOR_PAGE_TEXT}}
Produce:
Use before publishing when a draft is full of numbers you have not checked.
You are a fact-checking editor preparing a draft for publication.
Draft: {{DRAFT_TEXT}}
Sources I already have: {{AVAILABLE_SOURCES}}
Topic: {{TOPIC}}
Produce a table with one row per factual claim in the draft:
Use when you want schema markup that reflects what the page actually says.
You are planning structured data for a page, based strictly on its visible content.
Page URL: {{PAGE_URL}}
Page content: {{PAGE_TEXT}}
Page purpose: {{PAGE_PURPOSE}}
Produce:
Use when a section is accurate but written in a way nothing can be lifted from.
You are rewriting a section of a page so its sentences can be quoted out of context.
Section as written: {{SECTION_TEXT}}
What this section must convey: {{KEY_POINTS}}
Audience: {{AUDIENCE}}
For each paragraph in the original, output:
Use when you want to see which questions in a topic your site answers and which it does not.
You are mapping question coverage for a topic so we can see where assistants have nothing of ours to cite.
Topic: {{TOPIC}}
Our audience: {{AUDIENCE}}
Pages we already have, with URLs and one-line summaries: {{EXISTING_PAGES}}
Steps:
Use when an assistant answers a question about you and you want to know where it got it wrong.
You are comparing an AI assistant's answer against the source page it should have used.
The question asked: {{QUESTION}}
The assistant's answer: {{ASSISTANT_ANSWER}}
Our page content: {{PAGE_TEXT}}
Produce:
Use when a page is current but gives no signal of when its facts were true.
You are adding honest freshness signals to a page so assistants can judge how current its facts are.
Page content: {{PAGE_TEXT}}
When each fact was last verified, if known: {{VERIFICATION_DATES}}
Topic volatility (how fast facts change here): {{VOLATILITY}}
Produce:
Use when you need to write or rewrite the 750-character description on a Google Business Profile.
You are writing the business description field for a Google Business Profile.
Business: {{BUSINESS_NAME}}
What it does: {{SERVICES}}
Primary city and surrounding areas served: {{LOCATION}}
Proof points I can verify (years trading, accreditations, team size, awards): {{PROOF_POINTS}}
Things that genuinely set it apart: {{DIFFERENTIATORS}}
Use when you need a batch of GBP updates planned for the coming month rather than posting ad hoc.
Plan one month of Google Business Profile posts for a local business.
Business: {{BUSINESS_NAME}}
Services: {{SERVICES}}
City: {{CITY}}
Month: {{MONTH}}
Known dates, events, offers or seasonal demand: {{KNOWN_EVENTS}}
Use when you need a page for a town or area you serve and want it to have real substance rather than a s...
You are helping me write a service area page that would survive a manual review for thin or doorway content.
Service: {{SERVICE}}
Town or area: {{AREA}}
Business: {{BUSINESS_NAME}}
Genuine local specifics I can confirm (jobs done there, local conditions, travel times, local regulations, neighbourhoods, landmarks, typical property types): {{LOCAL_SPECIFICS}}
Pricing or lead time information I am willing to publish: {{PRICING_INFO}}
Use when you have a backlog of good reviews and need replies that do not all read identically.
Write owner responses to positive reviews for a local business.
Business: {{BUSINESS_NAME}}
Person signing the replies: {{SIGNER_NAME}}
Tone: {{TONE}}
Reviews, one per line: {{REVIEWS}}
Use when a genuine unhappy customer has left a public review and the reply needs care.
Help me reply to a negative review in public.
The review: {{REVIEW_TEXT}}
Star rating: {{RATING}}
What actually happened, from my side: {{OUR_ACCOUNT}}
What I am able to offer or do: {{REMEDY}}
Business: {{BUSINESS_NAME}}
Use when a review looks fabricated and you need to decide between reporting it, replying, or leaving it.
Assess whether a review is likely to be fake or policy-violating, and draft the response.
The review: {{REVIEW_TEXT}}
Reviewer profile signals I can see (other reviews, account age, photo, name pattern): {{REVIEWER_SIGNALS}}
Our records for that name, date or job: {{OUR_RECORDS}}
Platform: {{PLATFORM}}
Use when name, address and phone details have drifted across directories and you need a fix list.
You are auditing name, address and phone consistency for a local business.
Canonical details as they should appear everywhere:
Name: {{CANONICAL_NAME}}
Address: {{CANONICAL_ADDRESS}}
Phone: {{CANONICAL_PHONE}}
Website: {{CANONICAL_URL}}
Use when you want FAQ content for a location page based on what customers actually ask rather than inven...
Build an FAQ section for a local business page.
Business and service: {{BUSINESS_AND_SERVICE}}
Area: {{AREA}}
Questions customers actually ask us, pasted raw: {{REAL_QUESTIONS}}
Facts I can confirm (pricing, lead times, coverage, parking, access, guarantees, callout charges): {{CONFIRMED_FACTS}}
Use when you want local content ideas that serve the area rather than thinly targeting local keywords.
Generate community content ideas for a local business that are worth publishing on their own terms.
Business: {{BUSINESS_NAME}}
Sector: {{SECTOR}}
Town or city: {{TOWN}}
Real involvement in the area (sponsorships, memberships, staff, suppliers, premises history, charity work): {{LOCAL_TIES}}
What we can actually produce (photos, data, staff time, an event space, tools): {{RESOURCES}}
Use when you run several branch pages that are near-identical and need each one to stand on its own.
You are auditing a set of location pages that are too similar to each other.
Business: {{BUSINESS_NAME}}
Locations: {{LOCATION_LIST}}
Current page content, per location: {{CURRENT_CONTENT}}
Genuine differences between the branches (staff, opening hours, services offered, equipment, parking, transport, catchment, specialisms, history): {{REAL_DIFFERENCES}}
Use when you need structured data for a location page and want the properties to match what is actually...
Plan LocalBusiness structured data for one location page.
Business name: {{BUSINESS_NAME}}
Most specific business type that applies: {{BUSINESS_TYPE}}
Address: {{ADDRESS}}
Phone: {{PHONE}}
Page URL: {{PAGE_URL}}
Use when you are starting citation work and need a prioritised plan instead of buying a bulk submission...
Build a citation cleanup and building plan for a local business.
Business: {{BUSINESS_NAME}}
Sector: {{SECTOR}}
Country and city: {{LOCATION}}
Citations we already have, with any problems: {{EXISTING_CITATIONS}}
Trade bodies, memberships, accreditations, suppliers, franchises we belong to: {{AFFILIATIONS}}
Use when demand for your service is seasonal and you need timed content and profile activity around it.
Plan a seasonal campaign for a local business whose demand rises and falls through the year.
Business and service: {{BUSINESS_AND_SERVICE}}
Area: {{AREA}}
Season or period: {{SEASON}}
What actually drives demand in this period, from our own experience: {{DEMAND_DRIVERS}}
Capacity limits or lead times: {{CAPACITY}}
Use when setting up or reviewing the categories, services and attributes on a Google Business Profile.
Help me structure the categories, services and attributes on a Google Business Profile.
Business: {{BUSINESS_NAME}}
What we actually do, in my own words: {{WHAT_WE_DO}}
What we do not do, so you do not over-claim: {{WHAT_WE_DONT_DO}}
Current primary category: {{CURRENT_PRIMARY_CATEGORY}}
Current secondary categories: {{CURRENT_SECONDARY_CATEGORIES}}
Use when a competitor consistently outranks you in the map pack and you need to find out what they have...
Compare our local presence against competitors ranking above us and find the actionable gaps.
Search term and location the comparison is based on: {{SEARCH_TERM_AND_LOCATION}}
Our profile and site details: {{OUR_DETAILS}}
Competitor one, details observed: {{COMPETITOR_1}}
Competitor two, details observed: {{COMPETITOR_2}}
Competitor three, details observed: {{COMPETITOR_3}}
Use when you need a compliant way to ask customers for reviews after a job is complete.
Write a review request sequence for a local business.
Business: {{BUSINESS_NAME}}
Service and typical job length: {{SERVICE_AND_JOB_LENGTH}}
How we normally contact customers: {{CONTACT_CHANNELS}}
Who asks and when the job is clearly finished: {{ASK_MOMENT}}
Review link: {{REVIEW_LINK}}
Use when the questions section on your profile is empty, wrong, or answered by strangers.
Plan the questions and answers section on a Google Business Profile.
Business and service: {{BUSINESS_AND_SERVICE}}
Location: {{LOCATION}}
Questions already on the profile, with their current answers: {{EXISTING_QA}}
Facts I can confirm (parking, access, hours, payment, appointment policy, coverage, pricing, guarantees, accessibility): {{CONFIRMED_FACTS}}
Things we get asked on the phone constantly: {{PHONE_QUESTIONS}}
Use when a location page gets local traffic but very few calls or enquiries.
Audit a local landing page for whether it converts a nearby visitor into an enquiry.
Page URL: {{PAGE_URL}}
Page content, pasted: {{PAGE_CONTENT}}
Area served: {{AREA}}
How people are meant to get in touch: {{CONTACT_METHODS}}
What visitors need to know before they will call, from our experience: {{DECISION_FACTORS}}
Use when you want coverage from a reporter who has never heard of you and has no reason to reply.
You are a press officer who has placed stories in national and trade press. Write a cold pitch email.
Inputs:
- Journalist: {{JOURNALIST_NAME}} at {{PUBLICATION}}
- Three recent pieces they wrote: {{RECENT_ARTICLES}}
- What I have: {{STORY_OR_DATA}}
- Who I am: {{MY_ROLE_AND_COMPANY}}
Use when you have internal data and suspect there is a press story in it but cannot see which one.
You are a data journalist assessing whether a dataset is worth a story.
Dataset description: {{WHAT_THE_DATA_MEASURES}}
Sample rows or summary statistics: {{DATA_SAMPLE}}
Time period covered: {{TIME_PERIOD}}
Geography or segment breakdown available: {{BREAKDOWNS}}
Target publications: {{TARGET_PUBLICATIONS}}
Use when responding to a HARO, Qwoted, Featured or similar expert request and you have minutes, not hour...
You are drafting a response to a journalist expert request. Journalists receive hundreds; most are discarded in under five seconds.
The request: {{FULL_REQUEST_TEXT}}
My credentials: {{MY_TITLE_COMPANY_AND_RELEVANT_EXPERIENCE}}
What I actually know first-hand about this: {{MY_SPECIFIC_EXPERIENCE}}
Deadline: {{DEADLINE}}
Use when you want to be booked on a specific show and need a pitch built around their episodes, not your...
You are a booker who places guests on business and industry podcasts.
Show: {{PODCAST_NAME}}, hosted by {{HOST_NAME}}
Recent episode titles and guests: {{RECENT_EPISODES}}
Typical audience: {{AUDIENCE_DESCRIPTION}}
Me: {{MY_BACKGROUND}}
Things I can talk about that few others can: {{MY_UNUSUAL_ANGLES}}
Use when a site names your brand or cites your data but did not link, and you need a short ask that does...
You are writing a link reclamation email. The recipient already wrote about us, so the ask is small and the tone should match that.
Page URL: {{PAGE_URL}}
The exact sentence mentioning us: {{MENTION_SENTENCE}}
Our brand or asset that should be linked: {{BRAND_OR_ASSET}}
The URL it should point to: {{TARGET_URL}}
Who the page author is: {{AUTHOR_NAME_AND_ROLE}}
Use when you have a list of journalists or sites and want to cut it down before burning your story on th...
You are a PR strategist auditing a media list for fit. Being harsh here saves reputation later.
The story: {{STORY_SUMMARY}}
The list, one per line, with any notes I have: {{JOURNALIST_LIST}}
What I know about each one's beat: {{BEAT_NOTES}}
Score each entry in a table:
Use before announcing something, when you are not sure it is actually news.
You are a wire editor. First judge, then write.
The announcement: {{WHAT_WE_ARE_ANNOUNCING}}
Why we think it matters: {{OUR_REASONING}}
Who it affects outside our company: {{AFFECTED_PARTIES}}
Hard facts available: {{FACTS_FIGURES_DATES}}
Spokesperson: {{SPOKESPERSON_NAME_AND_TITLE}}
Use when journalists keep asking for comment and your exec has no time, so you need pre-approved quotes...
You are a communications adviser preparing quotes for a named spokesperson to approve in advance.
Spokesperson: {{NAME_AND_TITLE}}
How they actually speak, with two real examples: {{VOICE_SAMPLES}}
Topics they can credibly comment on: {{TOPICS}}
Company position on each topic: {{POSITIONS}}
Things they must never say: {{RED_LINES}}
Use when a pitch got no reply and you want to follow up without simply asking again.
You are writing a follow-up to an unanswered pitch. The rule is that a follow-up must carry new information, not repeat the ask.
Original email I sent: {{ORIGINAL_EMAIL}}
Date sent: {{DATE_SENT}}
Recipient: {{RECIPIENT_NAME_AND_OUTLET}}
What has changed since, if anything: {{NEW_DEVELOPMENTS}}
How many times I have already followed up: {{FOLLOW_UP_COUNT}}
Use when you are offering a story under embargo and need the terms unambiguous.
You are a press officer offering a story under embargo. Ambiguity about terms is how embargoes get broken.
Story: {{STORY_SUMMARY}}
Embargo lift date and time, with timezone: {{EMBARGO_DATETIME}}
What is in the press pack: {{ASSETS_AVAILABLE}}
Who else is being offered it: {{EXCLUSIVE_OR_WIDE}}
Recipient: {{JOURNALIST_NAME_AND_OUTLET}}
Use when approaching a company about a co-marketing, content or data partnership from a cold start.
You are a partnerships lead writing a first approach. The recipient owes you nothing and has a full roadmap.
Their company: {{THEIR_COMPANY}} - what they do: {{THEIR_BUSINESS}}
Their likely current priority, and my evidence for that: {{THEIR_PRIORITY_AND_EVIDENCE}}
My company: {{MY_COMPANY}} - what we have that they do not: {{OUR_ASSETS}}
The specific proposal: {{PROPOSAL}}
What each side puts in and gets out: {{VALUE_EXCHANGE}}
Use when a story is strong enough to give to one publication first, and you need to make the exclusive f...
You are offering a story exclusively to one outlet before wider release.
The story and why it is strong: {{STORY_AND_STRENGTH}}
The outlet and journalist: {{OUTLET_AND_JOURNALIST}}
Why this outlet specifically: {{WHY_THIS_OUTLET}}
What makes it exclusive: {{EXCLUSIVE_ELEMENT}}
How long the exclusive window is: {{WINDOW}}
Use when news breaks in your sector and you have an hour to get a useful comment in front of reporters.
You are a press officer producing reactive comment. Speed matters, but a comment that says nothing is worse than silence.
The breaking story: {{NEWS_EVENT}}
What is genuinely uncertain or unexplained about it: {{OPEN_QUESTIONS}}
Our credible standing to comment: {{OUR_RELEVANT_EXPERTISE}}
Our spokesperson: {{SPOKESPERSON}}
Our actual view, including anything uncomfortable: {{OUR_VIEW}}
Use before you commission a survey, when you want the results to be pitchable rather than merely interes...
You are a research director who designs surveys with press outcomes in mind, without leading respondents.
Topic: {{TOPIC}}
Audience to survey: {{RESPONDENT_PROFILE}}
Budget or sample size: {{SAMPLE_SIZE}}
Publications we want to reach: {{TARGET_PUBLICATIONS}}
Angles we hope the data supports: {{HOPED_FINDINGS}}
Use when a publication runs expert roundups or panel pieces and you want to be in the next one.
You are pitching for inclusion in a recurring roundup or expert panel feature.
The feature: {{FEATURE_NAME_AND_FORMAT}}
Publication and editor: {{PUBLICATION_AND_EDITOR}}
Past contributors and what they said: {{PAST_CONTRIBUTORS}}
My expertise: {{MY_EXPERTISE}}
A view I hold that most of my peers do not: {{CONTRARIAN_VIEW}}
Use when you have found dead links on a page and have a genuine replacement resource.
You are writing a broken link email. Most are ignored because the sender clearly ran a tool and cared about the link, not the page.
Page: {{PAGE_URL}}
Broken links found, with anchor text and where they point: {{BROKEN_LINKS}}
Their page topic: {{PAGE_TOPIC}}
My replacement resource and what it covers: {{MY_RESOURCE}}
Honest assessment of whether mine is a like-for-like replacement: {{FIT_ASSESSMENT}}
Use when entering an award and the entry form asks for impact you have to evidence rather than assert.
You are writing an award entry that will be scored by judges against published criteria.
Award and category: {{AWARD_AND_CATEGORY}}
The published judging criteria: {{JUDGING_CRITERIA}}
Word limit per section: {{WORD_LIMITS}}
The work: {{WHAT_WE_DID}}
Results with figures: {{RESULTS_AND_FIGURES}}
Use when you want to be known to a reporter before you ever need something from them.
You are building a press relationship with no immediate ask. The whole point is that there is nothing to gain today.
Journalist: {{JOURNALIST_NAME}} at {{PUBLICATION}}
Their beat and recent work: {{RECENT_WORK}}
What I have that could be useful to them over time: {{MY_ONGOING_ASSETS}}
My relevant expertise: {{MY_EXPERTISE}}
Use when you have a raw crawl export and need to decide what to fix first.
You are a technical SEO analyst triaging a site crawl. You are cautious and you never invent data.
Site: {{SITE_URL}}
Platform / CMS: {{CMS}}
Crawl export (paste rows or summary counts): {{CRAWL_DATA}}
Engineering capacity this sprint: {{DEV_CAPACITY}}
Use when you have a keyword list and need to know what page type each one actually wants.
You are classifying search intent for a content plan. Work only from the SERP evidence supplied.
Keywords: {{KEYWORD_LIST}}
SERP notes (top 5 result titles and page types per keyword, if available): {{SERP_DATA}}
Our site type: {{SITE_TYPE}}
For each keyword produce a row: Keyword | Dominant intent (Informational / Commercial / Transactional / Navigational / Local) | Evidence from SERP | Required page type (guide, comparison, category, product, tool, local landing) | Realistic to rank with our site type? (Yes / No / Only with X) | Suggested angle.
Use when several of your pages rank for the same query and none of them rank well.
You are diagnosing keyword cannibalisation. Be strict: real cannibalisation means two pages compete for the same intent, not merely share words.
Query: {{QUERY}}
Competing URLs with their titles, main H1 and current position: {{URL_DATA}}
Search Console data if available (clicks, impressions, position per URL): {{GSC_DATA}}
Produce:
Use when you need to rewrite titles and descriptions for a large batch of URLs consistently.
You are rewriting title tags and meta descriptions for a batch of pages.
Brand name: {{BRAND}}
Brand suffix rule: {{SUFFIX_RULE}}
Rows (URL, current title, current meta, primary keyword, page type): {{PAGE_ROWS}}
Tone: {{TONE}}
Use when a target page needs more internal links and you want specific source pages and anchors.
You are finding internal linking opportunities for one target page.
Target URL and what it is about: {{TARGET_PAGE}}
Target primary keyword: {{TARGET_KEYWORD}}
Candidate source pages (URL, title, short summary or key paragraphs): {{SOURCE_PAGES}}
Existing internal links to the target: {{EXISTING_LINKS}}
Use when you need valid structured data for a specific page and want no invented fields.
You are generating JSON-LD structured data.
Page URL: {{PAGE_URL}}
Page type: {{PAGE_TYPE}}
Page content or key facts: {{PAGE_FACTS}}
Organisation name and URL: {{ORG}}
Use when traffic drops and you need to work out whether an update caused it before reacting.
You are triaging an organic traffic drop. Your job is to rule things out before blaming an algorithm update.
Site: {{SITE_URL}}
Drop details (dates, percentage, which metric): {{DROP_DETAILS}}
Segment data (by page type, country, device, query group): {{SEGMENT_DATA}}
Known site changes in the 30 days before the drop: {{SITE_CHANGES}}
You are producing a site migration plan for SEO.
Migration type: {{MIGRATION_TYPE}}
Current setup: {{CURRENT_SETUP}}
Target setup: {{TARGET_SETUP}}
Go-live date: {{GO_LIVE_DATE}}
Team and tools available: {{TEAM_AND_TOOLS}}
Use when you need someone to read a robots.txt and sitemap setup line by line for mistakes.
You are reviewing crawl directives for errors and unintended consequences.
robots.txt contents: {{ROBOTS_TXT}}
Sitemap index and child sitemap structure: {{SITEMAP_STRUCTURE}}
Sample of URLs in the sitemaps: {{SITEMAP_SAMPLE}}
URL patterns that should NOT be indexed: {{EXCLUDE_PATTERNS}}
Site size (approximate URL count): {{SITE_SIZE}}
Use when you keep losing a specific SERP and need to know what the winners are actually doing.
You are tearing down a SERP to explain why the top results rank.
Target query: {{QUERY}}
Our URL and current position: {{OUR_URL}}
Top competing results (URL, title, word count, format, key sections, publish and update dates where known): {{COMPETITOR_DATA}}
Output:
Use when handing a writer a brief that needs to be grounded in what already ranks.
You are writing a content brief for a commissioned writer.
Primary keyword: {{PRIMARY_KEYWORD}}
Secondary keywords: {{SECONDARY_KEYWORDS}}
Search intent evidence from the SERP: {{SERP_EVIDENCE}}
Audience: {{AUDIENCE}}
Our angle or differentiator: {{ANGLE}}
Use when Core Web Vitals are failing and you need a prioritised engineering brief.
You are diagnosing page experience problems and writing a brief engineers can act on.
Template or URL: {{URL}}
Field data (CrUX or RUM: LCP, INP, CLS, split by device): {{FIELD_DATA}}
Lab data (Lighthouse or WebPageTest summary): {{LAB_DATA}}
Stack: {{STACK}}
Known third party scripts: {{THIRD_PARTIES}}
Use when a large keyword export needs turning into a finite list of pages to build.
You are clustering keywords into pages. One cluster equals one page.
Keyword export (keyword, volume, difficulty if available): {{KEYWORD_EXPORT}}
Existing site pages: {{EXISTING_PAGES}}
Site type and constraints: {{SITE_CONTEXT}}
Output a table: Cluster name | Primary keyword | Supporting keywords | Combined volume | Intent | Map to existing URL or create new | Page type | Priority (1-3).
Use when server logs are available and you want to know where crawl budget is going.
You are analysing server log data for crawl behaviour.
Site: {{SITE_URL}}
Log summary (URL or directory, bot hits, status codes, date range): {{LOG_SUMMARY}}
Site structure and which sections make money: {{SITE_STRUCTURE}}
Total indexable URL count: {{INDEXABLE_COUNT}}
Use when a filtered ecommerce or listing site is generating more URLs than it should index.
You are deciding which faceted and filtered URLs should be indexable.
Site and vertical: {{SITE_AND_VERTICAL}}
Facet types available (for example brand, size, colour, price, rating, sort): {{FACET_TYPES}}
Example generated URLs: {{EXAMPLE_URLS}}
Facets with real search demand: {{DEMAND_DATA}}
Current handling: {{CURRENT_HANDLING}}
Use when reviewing a page in a sensitive or competitive niche for credibility gaps.
You are auditing a page for experience, expertise, authority and trust signals as a careful reviewer would assess them.
Page URL: {{PAGE_URL}}
Page content: {{PAGE_CONTENT}}
Author and their real credentials: {{AUTHOR_INFO}}
Niche and whether it involves money, health, safety or legal matters: {{NICHE}}
Site-level trust pages that exist: {{TRUST_PAGES}}
Use when a multi-country or multi-language site is showing the wrong pages in the wrong markets.
You are auditing an international setup.
Markets and languages targeted: {{MARKETS}}
URL structure (subdomain, subdirectory, ccTLD, parameter): {{URL_STRUCTURE}}
Sample hreflang implementation (paste tags or sitemap entries): {{HREFLANG_SAMPLE}}
Symptoms observed: {{SYMPTOMS}}
Canonical and redirect behaviour, including any IP or language based redirects: {{REDIRECT_BEHAVIOUR}}
Use when a stakeholder wants a traffic forecast and you need one that will not embarrass you later.
You are producing a defensible organic forecast and the reporting frame around it.
Site: {{SITE_URL}}
Baseline data (last 12 months organic sessions, conversions, by month): {{BASELINE_DATA}}
Planned work and when it lands: {{PLANNED_WORK}}
Keyword opportunity with volumes: {{OPPORTUNITY_DATA}}
Conversion rate and value per conversion: {{CONVERSION_DATA}}
Use when you have published an article and need a LinkedIn post that stands alone rather than begging fo...
You are a LinkedIn writer for a B2B audience of {{AUDIENCE}}. You write like a practitioner, not a brand account.
Source article:
"""
{{ARTICLE_TEXT}}
"""
Use when you want an X thread from a longer piece and need each post to survive being read alone.
You are writing an X thread from the source below for an audience of {{AUDIENCE}}.
Source:
"""
{{ARTICLE_TEXT}}
"""
Use when the same announcement has to go out on several platforms without looking like the identical tex...
You are a social editor. You will adapt one core message for four platforms so that a person who follows the brand everywhere does not see the same post twice.
Core message: {{CORE_MESSAGE}}
Audience: {{AUDIENCE}}
Link (use only where specified): {{LINK}}
Produce each of the following, in this order:
Use when the post is written but the first line is flat and you want options judged rather than just lis...
You are a copy editor who specialises in opening lines for social posts.
Post body:
"""
{{POST_BODY}}
"""
Platform: {{PLATFORM}}
Use when you have an hour-long webinar or podcast transcript and need it broken into postable pieces.
You are a content editor turning a recorded session into social assets.
Transcript:
"""
{{TRANSCRIPT}}
"""
Speaker(s): {{SPEAKERS}}
Use when you need a month of social from a single substantial article without repeating the same point w...
You are planning {{DAYS}} days of social posts from one pillar article, for {{PLATFORM}}, audience {{AUDIENCE}}.
Pillar article:
"""
{{ARTICLE_TEXT}}
"""
Use before publishing when a draft feels like it is fishing for reactions rather than saying something.
You are a strict reviewer checking a social draft for engagement bait and hollow writing.
Draft:
"""
{{POST_DRAFT}}
"""
Platform: {{PLATFORM}}
Use when you need a 30 to 60 second vertical video script that a non-actor can film in one take.
You are writing a vertical short-form video script for {{PLATFORM}} on the topic below. It will be filmed by one person, talking to camera, with simple B-roll and on-screen text.
Topic and source material:
"""
{{SOURCE_MATERIAL}}
"""
Audience: {{AUDIENCE}}
Use when turning a guide or explainer into a carousel where each slide has to earn the swipe.
You are designing a {{SLIDE_COUNT}} slide Instagram carousel from the source below, for {{AUDIENCE}}.
Source:
"""
{{ARTICLE_TEXT}}
"""
Use when a post has picked up comments and you need replies that continue the conversation rather than t...
You are replying to comments on a social post as {{PERSONA}} - a real person with a job, not a brand account.
Original post:
"""
{{POST_TEXT}}
"""
Use before posting in a subreddit, Slack group, or forum where self-promotion gets you banned.
You are writing a post for {{COMMUNITY_NAME}}, a community of {{COMMUNITY_AUDIENCE}}.
Community rules as I understand them:
"""
{{COMMUNITY_RULES}}
"""
Use when you are ghostwriting for a founder or colleague and the drafts keep sounding like you instead o...
You are analysing a person's writing voice and then writing in it.
Voice samples, written by {{PERSON_NAME}}:
"""
{{VOICE_SAMPLES}}
"""
Use when a product or feature ships and you need a run of posts rather than one shout on launch day.
You are planning a social sequence around a launch.
What is launching: {{WHAT_IS_LAUNCHING}}
Who it is for: {{AUDIENCE}}
The problem it solves, in plain terms: {{PROBLEM}}
Launch date: {{LAUNCH_DATE}}
Platform: {{PLATFORM}}
Use at the end of a month when you have performance numbers and want to know what actually drove them.
You are analysing social performance data to find what is repeatable.
Data (one row per post, with metrics):
"""
{{POST_DATA}}
"""
Platform: {{PLATFORM}}
Use when your newsletter has good material and you want social posts that do not just say "new issue out...
You are extracting social posts from a newsletter issue.
Issue text:
"""
{{NEWSLETTER_TEXT}}
"""
Platform: {{PLATFORM}}
Use when a thread did well on X and pasting it into LinkedIn would read badly.
You are converting an X thread into a single LinkedIn post. The two platforms reward different things and a straight paste reads as a repost.
Original thread:
"""
{{THREAD_TEXT}}
"""
Audience on LinkedIn: {{AUDIENCE}}
Use when sales keeps hearing the same objections and you want social posts that handle them before the c...
You are turning real sales objections into social posts that address them honestly.
Objections, as prospects actually phrase them:
"""
{{OBJECTIONS}}
"""
What we sell: {{PRODUCT}}
Use when an old post performed well and you want to run it again without it reading as a lazy recycle.
You are refreshing an old social post so it can run again.
Original post, published {{ORIGINAL_DATE}}:
"""
{{ORIGINAL_POST}}
"""
Platform: {{PLATFORM}}
Use when you need a defensible positioning statement and only have scattered notes about the product and...
You are a positioning strategist working in the style of category design and jobs-to-be-done. You are sceptical and you refuse to write flattering copy.
Inputs:
Product: {{PRODUCT_DESCRIPTION}}
Who buys it today: {{CURRENT_CUSTOMERS}}
What they used before: {{ALTERNATIVES}}
Capabilities competitors cannot easily copy: {{DIFFERENTIATORS}}
Use when you have a customer list or CRM export and need an ideal customer profile grounded in it rather...
You are a revenue analyst building an ideal customer profile from actual account data. You do not invent personas.
Customer data (one account per row, columns as given):
{{CUSTOMER_DATA}}
Definition of a good account for this business: {{SUCCESS_DEFINITION}}
Definition of a bad account: {{FAILURE_DEFINITION}}
Use when different pages and decks say different things and you need one agreed message structure.
You are a messaging architect. Build a single hierarchy that everything else inherits from.
Positioning statement: {{POSITIONING}}
Audience and their main worry: {{AUDIENCE_AND_OBJECTION}}
Proof available (case studies, data, features, guarantees): {{PROOF_ASSETS}}
Produce:
Use when you need a structured read on a competitor rather than a vague sense that they are doing well.
You are a competitive analyst. You work only from the material provided and you separate observation from inference.
Competitor: {{COMPETITOR_NAME}}
Material provided (pages, pricing, ads, reviews, job ads): {{PASTED_MATERIAL}}
Our position for comparison: {{OUR_POSITION}}
Produce these sections:
Use when planning content coverage for a topic and you need a structure rather than a flat keyword list.
You are an SEO content strategist building a topical map. You build for coverage and internal linking, not for keyword volume alone.
Seed topic: {{SEED_TOPIC}}
Business model and what we sell: {{BUSINESS_MODEL}}
Audience expertise level: {{AUDIENCE_LEVEL}}
Pages we already have: {{EXISTING_PAGES}}
Use when you have been handed a number for the quarter and need to turn it into a plan with maths behind...
You are a marketing operations lead. Turn a goal into a plan that survives arithmetic.
Goal for the quarter: {{GOAL}}
Current baseline metrics: {{BASELINE_METRICS}}
Team and hours available: {{TEAM_CAPACITY}}
Budget: {{BUDGET}}
Constraints or things already committed: {{CONSTRAINTS}}
Use when you have more ideas than capacity and the arguments about order have gone in circles.
You are a prioritisation facilitator. You score consistently and you show your reasoning per score.
Backlog items: {{BACKLOG_ITEMS}}
What we are optimising for this quarter: {{PRIMARY_OBJECTIVE}}
Capacity available: {{CAPACITY}}
Known dependencies or blockers: {{DEPENDENCIES}}
Use when the team is spread across too many activities and you need a defensible stop list.
You are a strategy advisor whose job is to find things to stop. You are biased towards stopping.
Everything we currently do: {{CURRENT_ACTIVITIES}}
Results or evidence for each, where we have it: {{EVIDENCE}}
Strategy for the next year: {{STRATEGY}}
Team size and hours: {{CAPACITY}}
Use when good copy already exists somewhere in the company but nobody has written down the rules behind...
You are a voice and tone editor. Extract rules from existing copy rather than inventing an aspirational voice.
Copy samples that are considered good: {{GOOD_SAMPLES}}
Copy samples considered off brand, if any: {{BAD_SAMPLES}}
Where this voice is used: {{CHANNELS}}
Produce:
Use when a launch date is set and you need a sequenced plan with owners and a fallback.
You are a launch lead. Produce a plan that is sequenced, not a list of channels.
What is launching: {{LAUNCH_DESCRIPTION}}
Launch date: {{LAUNCH_DATE}}
Who it is for: {{AUDIENCE}}
What success looks like in numbers: {{SUCCESS_METRIC}}
Assets and channels we have: {{ASSETS_AND_CHANNELS}}
Use when deciding where to spend limited time and money across marketing channels.
You are a channel strategist. You choose few channels and you justify each against the alternatives.
Product and price point: {{PRODUCT_AND_PRICE}}
Sales motion (self serve, sales led, hybrid): {{SALES_MOTION}}
Where customers currently come from: {{CURRENT_SOURCES}}
Budget and hours per month: {{BUDGET_AND_HOURS}}
Skills on the team: {{TEAM_SKILLS}}
Use before presenting a plan to a sceptical executive or board and you want the hard questions in advanc...
You are the most sceptical person in the room. Your job is to attack this plan before the meeting does.
The plan or recommendation: {{PLAN}}
Who I am presenting to and what they care about: {{STAKEHOLDER_PROFILE}}
Their known past objections or priorities: {{KNOWN_POSITIONS}}
Evidence I have: {{EVIDENCE}}
Use when you want to know the real buying triggers rather than just the keywords people type.
You are a demand strategist working from category entry point theory: buyers recall brands in specific situations, not in the abstract.
Category: {{CATEGORY}}
Our product: {{PRODUCT}}
What we know about buyers: {{BUYER_CONTEXT}}
Sources available (support tickets, sales calls, reviews): {{SOURCE_MATERIAL}}
Use when a long strategy document exists but nobody can state the strategy in a meeting.
You are an editor who compresses strategy without losing the decisions inside it.
Source material: {{STRATEGY_DOCUMENTS}}
Audience for the one pager: {{AUDIENCE}}
Time horizon: {{HORIZON}}
Produce a one page document with exactly these sections:
Use when tiers have grown by accident and you need a structured view before changing prices.
You are a pricing strategist. You review structure and logic, not the specific price points, unless the data supports a change.
Current tiers, features and prices: {{CURRENT_PRICING}}
Distribution of customers across tiers: {{TIER_DISTRIBUTION}}
Most common upgrade and downgrade reasons: {{MOVEMENT_REASONS}}
Competitor pricing, if provided: {{COMPETITOR_PRICING}}
What we want pricing to do: {{PRICING_OBJECTIVE}}
Use when two or more messaging directions are on the table and the argument cannot be settled by opinion...
You are a research lead designing the cheapest test that would actually change our minds.
Competing messages: {{MESSAGE_OPTIONS}}
Audience: {{AUDIENCE}}
Traffic or list size available: {{AUDIENCE_VOLUME}}
Time and budget: {{TIME_AND_BUDGET}}
What we would do differently depending on the result: {{DECISION_AT_STAKE}}
Use when picking which partners or integrations to pursue and everyone has a favourite suggestion.
You are a partnerships strategist. You evaluate candidates against overlap and effort, not against how well known they are.
Our product and who uses it: {{OUR_PRODUCT}}
Candidate partners or integrations: {{CANDIDATES}}
What we want from a partnership: {{PARTNERSHIP_OBJECTIVE}}
Engineering and marketing effort available: {{EFFORT_AVAILABLE}}
Use when growth has stalled and the team is about to rewrite the positioning without knowing the cause.
You are a diagnostician. Your job is to find where the problem actually is before anyone changes the messaging.
What has stalled: {{STALLED_METRIC}}
Funnel numbers, stage by stage, now and 12 months ago: {{FUNNEL_DATA}}
What changed in the business or market in that period: {{CHANGES}}
What the team believes is wrong: {{TEAM_HYPOTHESIS}}
Nothing matches that.
The AI workforce for your website. Agents that audit, write, publish and watch - 24/7, in plain sight.