Prompt Library
Search Intent Prompts Based on Current SERP Evidence
Classify dominant and mixed search intent from supplied queries and dated SERP observations without treating model memory as live search data.
This reviewed prompt collection is for SEOs, content strategists, and marketers. It requires the user to collect current search-result evidence and keeps uncertainty visible.
When to use these prompts#
Use this page when you need prompts that classify intent from supplied query and current SERP evidence, record mixed intent, and avoid treating model memory as live search data. Replace every bracketed variable with verified, non-sensitive information before using a template in your own AI product.
Inputs to prepare#
- query and close variants
- country, language, device, and search date
- top-result page types and titles
- SERP features and repeated result patterns
- business context and target audience
- existing page purpose if evaluating a URL
- ambiguous modifiers or multiple meanings
- confidence scale and decision threshold
Draft prompt templates#
1. Intent classification from evidence#
Purpose: Explain dominant and secondary intent using supplied observations.
Analyze search intent for [QUERY] in [LOCALE] using only these dated SERP observations: [EVIDENCE]. Classify dominant intent, secondary or mixed intent, likely reader task, expected page type, and confidence. Cite the supplied observations supporting each conclusion. Do not claim access to live search results or use model memory as evidence.Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.
2. Mixed-intent matrix#
Purpose: Separate different jobs hidden inside one keyword set.
For [QUERY SET] and [SERP NOTES], create an intent matrix with query, interpretation, audience, desired outcome, dominant result type, ambiguity, and recommended manual check. Keep distinct intents separate even when the words are similar. Identify terms that should not share one page without further evidence.Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.
3. Intent change comparison#
Purpose: Compare two dated observation sets without overclaiming trend.
Compare the search-result observations from [DATE A] and [DATE B] for [QUERY]. Identify changes in result types, repeated themes, SERP features, and apparent reader task. Label each finding as observed, plausible interpretation, or insufficient evidence. Do not call a change a long-term trend from only two snapshots.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#
Intent is inferred from language, context, and current results; it is not a permanent label stored in a model. These prompts require date and locale, distinguish observation from interpretation, and support mixed intent rather than forcing one category.
Weak prompt and what it misses#
Tell me the exact search intent for this keyword and what Google wants.The prompt treats intent as exact and asks the model to speak for a search engine without current evidence. It omits locale, date, result types, ambiguity, and confidence.
Human review checklist#
- Collect current results manually for the correct locale and device.
- Distinguish observed result patterns from your interpretation.
- Record mixed intent where multiple page types persist.
- Check ambiguous terms with industry or language context.
- Revalidate high-value queries before major content decisions.
Testing and maintenance#
- Use original, non-sensitive sample values when testing a prompt.
- Retest examples after material changes to the prompt, page, or AI product.
- Check factual preservation, requested format, missing-data behavior, and task-specific risks.
- Update the visible test date when a material retest is completed.
- 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.