SEO Content Brief Prompts from Verified Inputs

This reviewed prompt collection is for SEO strategists, editors, and content teams. It does not ask a model to pretend it has current search results; the user must supply dated SERP observations and trusted business facts.

When to use these prompts#

Use this page when you need prompts that turn verified keyword and SERP inputs into a brief with intent, audience, required coverage, evidence gaps, internal links, and differentiation notes. Replace every bracketed variable with verified, non-sensitive information before using a template in your own AI product.

Inputs to prepare#

• primary query and secondary query set
• country, language, device, and observation date
• current SERP notes and result types
• target audience and search intent hypothesis
• verified product, service, or subject facts
• existing site pages and internal-link candidates
• available expert sources and evidence gaps
• business goal, exclusions, and editorial standards

Draft prompt templates#

1. Full editorial brief#

Purpose: Convert current supplied research into a writer-ready brief.

Create an SEO content brief for [PRIMARY QUERY] in [LOCALE]. Use only these dated SERP observations: [SERP NOTES], these audience notes: [AUDIENCE], and these verified subject facts: [FACTS]. Include intent, reader questions, working angle, required coverage, evidence needed, terms to define, internal links from [URL INVENTORY], risks, and a suggested heading structure. Label assumptions and do not invent rankings, search volume, competitors, or live SERP features.

Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.

2. Evidence and differentiation plan#

Purpose: Identify what the page must contribute beyond generic coverage.

Using [SERP SUMMARY] and [AVAILABLE SOURCES], identify repeated coverage, unanswered questions, weak evidence patterns, and opportunities for original information gain. Return a table with opportunity, reader value, evidence required, owner, and whether the idea is supported or hypothetical. Then propose three defensible angles for [SITE OR BRAND] without making claims beyond [VERIFIED CAPABILITIES].

Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.

3. Brief quality audit#

Purpose: Review an existing content brief for unsupported SEO assumptions.

Audit this content brief: [BRIEF]. Check alignment between query, supplied SERP evidence, audience, intent, proposed headings, source plan, internal links, and conversion goal. Flag invented metrics, stale observations, keyword stuffing, duplicated sections, and recommendations that need manual validation. Return prioritized fixes and a revised brief outline.

Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.

Why the structure matters#

A model can organize research but cannot be treated as a current search-results database. These prompts require dated evidence, separate facts from hypotheses, and turn the brief into an editorial contract rather than a keyword list.

Weak prompt and what it misses#

Create a complete SEO content brief for the keyword best project management software.

The prompt does not provide locale, date, live SERP evidence, product facts, audience, or existing site context. The model may fabricate competitors, volume, rankings, or user needs from stale memory.

Human review checklist#

• Verify SERP observations manually and record date, locale, and device.
• Remove any search volume, ranking, or competitor claim not supplied by a trusted source.
• Confirm that every required section serves the stated intent.
• Assign evidence owners for claims that need expert or first-party support.
• Validate every proposed internal URL against the actual site inventory.

Testing and maintenance#

1. Use original, non-sensitive sample values when testing a prompt.
2. Retest examples after material changes to the prompt, page, or AI product.
3. Check factual preservation, requested format, missing-data behavior, and task-specific risks.
4. Update the visible test date when a material retest is completed.
5. Keep the site operator responsible for the final human review.

A dated operator attestation is sufficient for the site's internal publication check; full chat transcripts are not retained or published.