SEO & GEO/AEO

Verified against ChatGPT · 2026-08-11

Brief an SEO landing page that stays honest to organic intent while still matching a paid campaign's promise

Drafts a landing page content brief for a page that has to satisfy both organic search intent and a specific paid ad's promise, flagging where the two pull in different directions instead of quietly picking one.

ChatGPT (GPT-5.1)4 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

This landing page brief is for a page that needs to do two jobs at once: rank organically for a target keyword, and also serve as the destination for a specific paid ad campaign whose promise the page must honor. These two jobs sometimes want different things from the page, and your job includes surfacing that tension, not just resolving it silently.

TARGET KEYWORD AND ORGANIC INTENT
'best project management software for agencies' — organic searchers are comparing multiple options, not committed to one.

PAID AD PROMISE
Ad headline: 'Cut Agency Reporting Time in Half — Free 14-Day Trial'.

OFFER DETAILS
14-day free trial is real; the 'cut reporting time in half' figure comes from a single customer case study, not a guaranteed average result.

COMPETING PAGES CURRENTLY RANKING
Top 3 results are comparison roundups from review sites, not single-vendor product pages.

First, check whether the ad promise and the organic search intent actually point to the same page structure. If someone searching organically for this keyword wants a comparison or educational answer, but the ad promise is narrowly about one specific offer, name that mismatch explicitly and propose how the page should be structured to serve the organic visitor first (since they arrived with a broader question) while still surfacing the specific offer prominently enough for the paid visitor who already expects it.

Then produce the actual brief: a heading structure (H1 through H2s) that reflects genuine informational value for the organic searcher, not just ad-copy restated as headings; a note on where in the page the specific paid offer should appear so a paid visitor isn't left hunting for what the ad promised; and a list of trust or proof elements (specifics, not generic claims) the page needs to compete with the currently-ranking pages.

Flag anything in the ad promise that oversells relative to the actual offer details given — if the ad promise claims something the offer details don't support, note it as a mismatch to resolve with the person who owns the ad copy, rather than writing a page that repeats an unsupported claim.

OUTPUT: (1) the intent-versus-promise mismatch check, (2) heading structure with a one-line purpose per heading, (3) offer placement note, (4) trust/proof element list, (5) any ad-promise oversell flag.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

A landing page brief that treats organic intent and paid ad promise as automatically aligned produces pages that satisfy neither audience well, because the two traffic sources genuinely can want structurally different things — an organic searcher for a broad comparison keyword arrives expecting to evaluate options, while a paid visitor arrives already primed by a specific claim and expects to find exactly that claim fulfilled immediately; asking GPT-5.1 to check for this mismatch before drafting anything prevents it from defaulting to whichever framing it read first (usually the ad promise, since it's stated more narrowly and is easier to write headings around). Requiring the heading structure to reflect genuine informational value rather than ad copy restated as headings counters a common and checkable failure mode where a model asked to write "SEO headings" for a page whose main brief is an ad promise will just rephrase the ad's claims into H2 format, producing a page that reads as promotional to an organic visitor who arrived wanting a comparison, and that mismatch between apparent intent and actual content is exactly what search engines' intent-matching increasingly penalizes. The instruction to flag ad-promise oversell against the given offer details is the load-bearing accuracy control here: without it, the model will simply carry the ad's claim through into page copy, and if that claim isn't actually supported by the offer details, the page repeats and amplifies an overstatement rather than surfacing it as something the ad-copy owner needs to resolve — the brief's job is to catch this before it compounds across both the ad and the landing page.

What you get back

Mismatch check: organic searchers want a comparison; ad promise is single-offer specific. Recommend leading with a brief honest comparison framework (3-4 evaluation criteria) before narrowing to our offer, so organic visitors don't bounce feeling sold-to immediately. Oversell flag: 'cut reporting time in half' is based on one case study, not an average — recommend the page state it as 'one agency reported cutting reporting time in half' rather than implying a typical guaranteed result.

Verified against

ChatGPT GPT-5.1 · 2026-08-11

Changelog

  • 2026-08-11 — Initial publish, verified against ChatGPT GPT-5.1.

Building this for real?

This is a free starting point. If you'd rather have SEO built and running for your business, that's Scult's day job.

EXPLORE SEO
All SEO & GEO/AEO prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY