AI Website Management: GPT-5.2 Cookbook

What this cookbook is

This is not a strategy guide. It’s a set of repeatable “recipes” you can run anytime your homepage needs an update.

Each recipe includes:

• When to use it
• What you need (inputs)
• A copy-paste prompt
• What “good output” looks like
• What to watch out for
• How to measure results

If you want changes executed (not just suggested), you can pair these with Cursor Agents or ChatGPT Codex.

Cookbook setup: the one-time prep

Ingredients you should keep handy

Save these somewhere (Notion, Google Doc, README):

• Your brand one-liner (what you do + who for + outcome)
• Your top 3 customer types
• Your top 3 differentiators
• Your primary CTA (and what happens after click)
• Your pricing model (even if not public)
• 3 competitor homepages you respect
• Your analytics baseline (traffic, conversion rate, bounce rate)
• Your current homepage copy (pasteable)

Default “house rules” for GPT-5.2

Use this at the top of any prompt:

• Write for business owners and everyday buyers.
• Avoid jargon and hype.
• Be specific and scannable.
• Prioritize clarity over cleverness.
• If you make assumptions, list them.

Recipe 1: Homepage “Clarity Refresh” (Copy that converts)

When to use: Your homepage feels vague, wordy, or “nice but not clear.”
Inputs: Current hero section + who it’s for + primary CTA.
Output: 3 hero variants + supporting bullets + CTA microcopy.

Prompt (copy/paste):

You are my homepage conversion editor.
Audience: [who buys]. Offer: [what you sell]. Outcome: [result].
Here is my current hero copy:
[paste hero]
Create 3 improved hero variations. Each must include:

1. headline (8–12 words) that states outcome
2. subheadline (1–2 sentences) that clarifies who it’s for and why it’s better
3. 3 bullets (benefits, not features)
4. primary CTA button text + 1 line of microcopy under it

Keep it simple, no buzzwords. Make each version meaningfully different.

What good looks like:

• You instantly understand: who it’s for, what it does, why it matters
• The CTA feels “low friction”
• The bullets are outcomes (save time, book more calls), not internal features

Watch outs:

• Generic headlines (“Unlock your potential”)
• Too many claims without proof
• Unclear CTA (“Learn more” with no context)

Measure:

• Hero CTA click-through rate
• Scroll depth to next section
• Time-to-first-action on homepage

Recipe 2: “Proof Upgrade” (Testimonials and credibility that feel real)

When to use: You have traffic, but people hesitate.
Inputs: Testimonials, logos, metrics, case study bullets.
Output: A proof section layout + rewritten testimonials + suggested trust signals.

Prompt:

Rewrite my proof section to increase trust without sounding salesy.
Here are my current testimonials/logos/metrics:
[paste]
Output:

1. a recommended proof section structure (headline + 3 blocks)
2. rewrite each testimonial to be more specific (problem → outcome)
3. add 5 suggested trust signals I can include (no fake numbers)

Keep everything believable. If something is missing, tell me what to collect.

Measure: conversion rate, contact form completion, demo requests.

Recipe 3: SEO “Homepage Essentials” (Title, description, headings, internal linking)

When to use: Your homepage is not ranking for your core term, or snippets look weak.
Inputs: Primary keyword, secondary keywords, current meta/title/H1.
Output: Meta title, meta description, H1/H2 structure, internal link plan.

Prompt:

Act as an SEO editor for a homepage.
Primary keyword: [keyword]. Secondary keywords: [list].
Current meta title/description/H1: [paste].
Create:

1. 5 meta titles (max ~60 chars)
2. 5 meta descriptions (max ~155 chars)
3. a suggested H1 + 4 H2s that match search intent
4. 6 internal links I should add from the homepage (anchor text + target page)

Write for humans first, SEO second.

Watch outs:

• Keyword stuffing
• Titles that are clever but not descriptive
• H1 that doesn’t match what people search

Measure: impressions, CTR, branded vs non-branded traffic, rankings for primary keyword.

Recipe 4: AEO “Answer Blocks” (Get cited by AI and show up in AI search)

When to use: You want your site to be quotable by AI tools and answer engines.
Inputs: Top 5 buyer questions.
Output: 5 answer blocks that can be added to homepage or FAQ.

Prompt:

Create 5 “answer blocks” for my homepage that are easy for AI to quote.
Business: [describe].
Audience: [who].
Questions buyers ask:

1. …
2. …

Format each answer block as:

• Question (natural language)
• Direct answer (2–3 sentences, no fluff)
• 3 supporting bullets (specific, practical)

Keep each block self-contained and factual.

Measure: referral traffic from AI sources (where visible), improved time-on-page, better lead quality.

Recipe 5: Performance “Lighthouse Translator” (Turn reports into a punch list)

When to use: Your site feels slow or mobile scores are bad.
Inputs: Lighthouse/PageSpeed summary + top opportunities list.
Output: prioritized fix list in plain English + what to do first.

Prompt:

Here is my PageSpeed/Lighthouse summary:
[paste metrics + opportunities]
Translate this into a prioritized action plan for a business owner.
Output:

1. Top 5 fixes in priority order
2. What impact each fix likely has (high/medium/low)
3. What is safe to do quickly vs what needs engineering
4. A simple “done checklist” I can use after changes

Measure: LCP, INP, CLS, mobile score, conversion rate.

Recipe 6: UX “Homepage Friction Audit” (Find why visitors bounce)

When to use: High bounce rate, low CTA clicks, vague messaging.
Inputs: Homepage URL + a screenshot (optional) + analytics symptoms.
Output: top friction points + fixes + test ideas.

Prompt:

Audit my homepage UX for conversion.
Symptoms: [bounce rate, low clicks, etc].
Homepage copy/structure: [paste or describe].
Identify:

1. the top 7 friction points
2. the simplest fix for each
3. 3 A/B tests worth running first

Keep recommendations practical and low-effort.

Measure: bounce rate, CTA clicks, form starts, form completion.

Execution layer: using Cursor Agents or ChatGPT Codex

Use GPT-5.2 for the plan, then an agent to implement:

Agent prompt template:

Apply these homepage edits exactly as written.

• Keep layout consistent
• Do not change navigation
• Do not remove tracking scripts
• Make changes in small commits

Here are the edits:
[paste output]

Best practice: Ask the agent to produce a “diff summary” before merging so you can approve quickly.