Upstream semantic evidence

Collect and qualify semantic evidence before MIRENA turns it into structure.

Use 34 modules to guard scope, inspect source assets, extract candidates, classify query intent, read result patterns, compare competitors, rank opportunities, package accepted findings, and route the output into the correct next workflow.

Choose a starting route Search all 34 prompts

34 modules 5 workflow phases 6 starting routes One final handoff

First gateSource contextSite, audience, offer, scope, protection, and route

Core evidenceCandidates and query pathsEntities, concepts, modifiers, attributes, and intent

Search evidenceConsensus and divergenceExpected patterns, missing angles, and unstable intent

Final outputDiscovery handoffAccepted, rejected, review, blocked, owner, and route

Starting route

Begin with the asset and decision already in front of you.

Each route names the smallest useful starting module, the recommended sequence, and the point where discovery must stop.

The project boundary is unclear

Start with

Source Context Check

Source Context Check, then Discovery Asset Review when files are present.

Stop condition

Stop until audience, offer, allowed topics, blocked topics, protected pages, and the next workflow are clear.

You have many files or exports

Start with

Discovery Asset Review

Discovery Asset Review, Source Candidate Ranking, then the smallest relevant extraction module.

Stop condition

Hold sources with weak quality, stale scope, unclear labels, or noise risk.

You have a page set or content corpus

Start with

Corpus Scan

Corpus Scan, NER Pass, Concept Harvest, Frequency Signal Scan, and Placement Signal Scan.

Stop condition

Do not turn the first scan into final entity structure or a topical map.

You have a keyword or GSC query export

Start with

Query Intent Classification

Query Intent Classification, Query Modifier Scan, Semantic Query Clustering, and Query Treatment Selection.

Stop condition

Do not create pages until page, section, question, merge, anchor, and reject treatments are reviewed.

You have competitor URLs or a result set

Start with

SERP Entity Harvest

SERP Entity Harvest, Competitor Entity Harvest, Competitive Coverage Snapshot, SERP Consensus Scan, and SERP Divergence Scan.

Stop condition

Use competitor evidence to discover patterns. Do not copy wording or structure.

A raw discovery pass already exists

Start with

Discovery Opportunity Matrix

Candidate Weighting, Discovery Opportunity Matrix, Entity Universe Package, then Discovery Handoff.

Stop condition

Do not send blocked, uncertain, or unsupported findings into production.

Five phase workflow

Move from scope control to a routed discovery package.

The sequence prevents loose keyword, competitor, and source evidence from becoming structure before it has been qualified.

Guard the boundary

Confirm source context, inspect assets, and rank sources before extraction.

Modules 1, 2, 3, and 30

Extract and qualify candidates

Collect named entities, concepts, signals, modifiers, attributes, and facets, then classify and weight them.

Modules 4 to 12

Build the query evidence layer

Classify intent, scan modifiers, select treatment, generate and classify queries, cluster meaning, and expand the network.

Modules 13 to 20

Read the result set and competitors

Harvest entities and patterns, compare coverage, separate consensus from divergence, and test adjacent concepts.

Modules 21 to 29

Turn findings into routes

Prioritize opportunities, package the entity universe, identify page type seeds, and create a clean handoff.

Modules 31 to 34

34 discovery modules

Search, inspect, and copy one module at a time.

Every record keeps the purpose, short command, full prompt, return fields, stop rule, and possible routes together.

01 Scope and intake

Source Context Check

Confirm the site purpose, audience, offer, allowed topic lanes, blocked topic lanes, protected pages, target workflow, and discovery boundary.

Copy full prompt

Short command Run Source Context Check on this discovery task.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Source Context Check on this discovery task.

Use the approved source context first.

Confirm the site purpose, audience, offer, allowed topic lanes, blocked topic lanes, protected pages, target workflow, and discovery boundary.

Return:
– site purpose
– audience
– offer
– allowed topic lanes
– blocked topic lanes
– target workflow stage
– discovery boundary
– files that should influence discovery
– files that should not influence discovery
– risk if discovery starts too broad
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Stop when the project boundary, protected pages, or next workflow are unclear.

Route accepted output into one of these destinations:
– Discovery Asset Review
– Corpus Scan

Do not run the routed workflow yet.

Best for

new projects
broad topics
unclear page lists
competitor research

Return fields

site purpose
audience
offer
allowed topic lanes
blocked topic lanes
target workflow stage
discovery boundary
files that should influence discovery
files that should not influence discovery
risk if discovery starts too broad
next workflow route

Stop rule

Stop when the project boundary, protected pages, or next workflow are unclear.

Possible routes

Discovery Asset Review
Corpus Scan

02 Scope and intake

Discovery Asset Review

Review each file, export, URL list, report, sitemap, crawl, search file, analytics file, behavior note, competitor source, or earlier MIRENA output before extraction.

Copy full prompt

Short command Run Discovery Asset Review on these files.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Discovery Asset Review on these files.

Use the approved source context first.

Review each file, export, URL list, report, sitemap, crawl, search file, analytics file, behavior note, competitor source, or earlier MIRENA output before extraction.

Return:
– asset name or label
– asset type
– source quality
– freshness risk
– discovery value
– best use
– noise risk
– missing file or field
– recommended processing order
– keep, hold, ignore, or review
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not extract candidates until every asset has a source type, quality note, and use decision.

Route accepted output into one of these destinations:
– Corpus Scan
– NER Pass
– Query Intent Classification
– SERP Entity Harvest
– Source Candidate Ranking

Do not run the routed workflow yet.

Best for

large uploads
mixed file sets
search exports
crawl data

Return fields

asset name or label
asset type
source quality
freshness risk
discovery value
best use
noise risk
missing file or field
recommended processing order
keep, hold, ignore, or review
next workflow route

Stop rule

Do not extract candidates until every asset has a source type, quality note, and use decision.

Possible routes

Corpus Scan
NER Pass
Query Intent Classification
SERP Entity Harvest
Source Candidate Ranking

03 Scope and intake

Corpus Scan

Scan a page set, draft set, or content export for recurring terms, concepts, phrases, themes, weak signals, overused language, and candidate areas before deeper extraction.

Copy full prompt

Short command Run Corpus Scan on this content set.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Corpus Scan on this content set.

Use the approved source context first.

Scan a page set, draft set, or content export for recurring terms, concepts, phrases, themes, weak signals, overused language, and candidate areas before deeper extraction.

Return:
– source page or document
– recurring term
– recurring concept
– repeated phrase
– candidate entity
– modifier candidate
– weak signal
– overused signal
– source location
– extraction confidence
– suggested next module
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not turn the scan into a topical map or final entity structure.

Route accepted output into one of these destinations:
– NER Pass
– Concept Harvest
– Frequency Signal Scan
– Placement Signal Scan
– Entity Universe Package

Do not run the routed workflow yet.

Best for

existing site content
old blog libraries
draft folders
documentation sets

Return fields

source page or document
recurring term
recurring concept
repeated phrase
candidate entity
modifier candidate
weak signal
overused signal
source location
extraction confidence
suggested next module
next workflow route

Stop rule

Do not turn the scan into a topical map or final entity structure.

Possible routes

NER Pass
Concept Harvest
Frequency Signal Scan
Placement Signal Scan
Entity Universe Package

04 Candidate extraction

NER Pass

Extract named candidate entities such as people, organizations, products, software, brands, places, known concepts, frameworks, documents, standards, and tools.

Copy full prompt

Short command Run NER Pass on this asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run NER Pass on this asset.

Use the approved source context first.

Extract named candidate entities such as people, organizations, products, software, brands, places, known concepts, frameworks, documents, standards, and tools.

Return:
– candidate entity
– entity type
– source page or passage
– source location
– frequency signal
– placement signal
– confidence level
– source context fit
– keep, reject, or review
– reason
– suggested next module
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not build the finished entity map, score final salience, or create schema.

Route accepted output into one of these destinations:
– Entity Type Classification
– Candidate Weighting
– Entity Universe Package
– Entity SEO and Salience

Do not run the routed workflow yet.

Best for

pages
drafts
SERP exports
competitor pages

Return fields

candidate entity
entity type
source page or passage
source location
frequency signal
placement signal
confidence level
source context fit
keep, reject, or review
reason
suggested next module
next workflow route

Stop rule

Do not build the finished entity map, score final salience, or create schema.

Possible routes

Entity Type Classification
Candidate Weighting
Entity Universe Package
Entity SEO and Salience

05 Candidate extraction

Concept Harvest

Extract important process terms, decision concepts, category terms, user states, intent concepts, technical ideas, and support concepts that may not appear as named entities.

Copy full prompt

Short command Run Concept Harvest on this asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Concept Harvest on this asset.

Use the approved source context first.

Extract important process terms, decision concepts, category terms, user states, intent concepts, technical ideas, and support concepts that may not appear as named entities.

Return:
– concept
– concept type
– source passage
– source location
– related topic
– related candidate entity
– confidence note
– source context fit
– keep, reject, or review
– reason
– suggested next module
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not turn concepts into a map or assign final entity roles.

Route accepted output into one of these destinations:
– Candidate Weighting
– Semantic Neighborhood Expansion
– Discovery Opportunity Matrix
– Entity Universe Package

Do not run the routed workflow yet.

Best for

guides
documentation
workflow content
educational clusters

Return fields

concept
concept type
source passage
source location
related topic
related candidate entity
confidence note
source context fit
keep, reject, or review
reason
suggested next module
next workflow route

Stop rule

Do not turn concepts into a map or assign final entity roles.

Possible routes

Candidate Weighting
Semantic Neighborhood Expansion
Discovery Opportunity Matrix
Entity Universe Package

06 Candidate extraction

Entity Type Classification

Normalize mixed candidates into clear types such as person, organization, brand, software, product, feature, location, process, framework, document, category, metric, modifier, format, support concept, or reject.

Copy full prompt

Short command Run Entity Type Classification on this candidate list.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Type Classification on this candidate list.

Use the approved source context first.

Normalize mixed candidates into clear types such as person, organization, brand, software, product, feature, location, process, framework, document, category, metric, modifier, format, support concept, or reject.

Return:
– candidate
– normalized type
– source context fit
– confidence
– unclear type warning
– reject reason
– preferred label
– duplicate label
– suggested next module
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not decide the final hierarchy, run salience, or create schema cues.

Route accepted output into one of these destinations:
– Candidate Weighting
– Entity Universe Package
– Discovery Opportunity Matrix

Do not run the routed workflow yet.

Best for

NER output
competitor extracts
mixed keyword files
product lists

Return fields

candidate
normalized type
source context fit
confidence
unclear type warning
reject reason
preferred label
duplicate label
suggested next module
next workflow route

Stop rule

Do not decide the final hierarchy, run salience, or create schema cues.

Possible routes

Candidate Weighting
Entity Universe Package
Discovery Opportunity Matrix

07 Candidate extraction

Candidate Weighting

Weight each candidate by frequency, placement, source quality, source count, intent fit, topic fit, buyer fit, workflow fit, and downstream usefulness.

Copy full prompt

Short command Run Candidate Weighting on this discovery list.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Candidate Weighting on this discovery list.

Use the approved source context first.

Weight each candidate by frequency, placement, source quality, source count, intent fit, topic fit, buyer fit, workflow fit, and downstream usefulness.

Return:
– candidate
– candidate type
– frequency score
– placement score
– source quality score
– source count
– intent fit
– topic fit
– buyer fit
– workflow fit
– risk note
– keep, reject, or review
– reason
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Reject repeated candidates that fall outside the approved scope and hold candidates that need stronger evidence.

Route accepted output into one of these destinations:
– Entity Universe Package
– Discovery Opportunity Matrix
– Topical Maps and Planning

Do not run the routed workflow yet.

Best for

large extraction sets
raw entity harvests
competitor scans
SERP exports

Return fields

candidate
candidate type
frequency score
placement score
source quality score
source count
intent fit
topic fit
buyer fit
workflow fit
risk note
keep, reject, or review
reason
next workflow route

Stop rule

Reject repeated candidates that fall outside the approved scope and hold candidates that need stronger evidence.

Possible routes

Entity Universe Package
Discovery Opportunity Matrix
Topical Maps and Planning

08 Candidate extraction

Frequency Signal Scan

Measure repeated terms, concepts, phrases, modifiers, entity candidates, and page themes without treating repetition as proof of importance.

Copy full prompt

Short command Run Frequency Signal Scan on this content set.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Frequency Signal Scan on this content set.

Use the approved source context first.

Measure repeated terms, concepts, phrases, modifiers, entity candidates, and page themes without treating repetition as proof of importance.

Return:
– term or concept
– frequency
– source count
– dominant source
– repeated context
– topic fit
– possible overuse
– possible importance
– risk note
– suggested next module
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Flag frequent candidates that fall outside scope, repeat weak copy, or indicate topic drift.

Route accepted output into one of these destinations:
– Candidate Weighting
– Placement Signal Scan
– Discovery Opportunity Matrix

Do not run the routed workflow yet.

Best for

content libraries
competitor result sets
query exports
draft collections

Return fields

term or concept
frequency
source count
dominant source
repeated context
topic fit
possible overuse
possible importance
risk note
suggested next module
next workflow route

Stop rule

Flag frequent candidates that fall outside scope, repeat weak copy, or indicate topic drift.

Possible routes

Candidate Weighting
Placement Signal Scan
Discovery Opportunity Matrix

09 Candidate extraction

Placement Signal Scan

Check where candidates appear across titles, headings, openings, body sections, tables, questions, captions, anchors, schema notes, and action sections.

Copy full prompt

Short command Run Placement Signal Scan on this asset.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Placement Signal Scan on this asset.

Use the approved source context first.

Check where candidates appear across titles, headings, openings, body sections, tables, questions, captions, anchors, schema notes, and action sections.

Return:
– candidate
– source page
– placement location
– placement strength
– repeated placement pattern
– source context fit
– importance note
– extraction confidence
– suggested next module
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Use placement only as a discovery signal. Do not score final salience or rewrite the asset.

Route accepted output into one of these destinations:
– Candidate Weighting
– SERP Pattern Intake
– Content Briefs
– Drafting and Rewriting

Do not run the routed workflow yet.

Best for

competitor page analysis
draft analysis
content refresh work
result structure review

Return fields

candidate
source page
placement location
placement strength
repeated placement pattern
source context fit
importance note
extraction confidence
suggested next module
next workflow route

Stop rule

Use placement only as a discovery signal. Do not score final salience or rewrite the asset.

Possible routes

Candidate Weighting
SERP Pattern Intake
Content Briefs
Drafting and Rewriting

10 Candidate extraction

Modifier Harvest

Extract modifiers that change audience, product fit, feature angle, location, comparison need, process stage, price sensitivity, problem state, buyer stage, format, or page type.

Copy full prompt

Short command Run Modifier Harvest on this keyword set.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Modifier Harvest on this keyword set.

Use the approved source context first.

Extract modifiers that change audience, product fit, feature angle, location, comparison need, process stage, price sensitivity, problem state, buyer stage, format, or page type.

Return:
– modifier
– modifier type
– example query
– related candidate
– intent signal
– page type signal
– source context fit
– keep, reject, or review
– reason
– suggested next module
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Reject modifiers that create topic drift and group accepted modifiers by function.

Route accepted output into one of these destinations:
– Facet Intent Extraction
– Query Modifier Scan
– Query Treatment Selection
– Topical Maps and Planning

Do not run the routed workflow yet.

Best for

keyword exports
GSC query exports
local projects
comparison clusters

Return fields

modifier
modifier type
example query
related candidate
intent signal
page type signal
source context fit
keep, reject, or review
reason
suggested next module
next workflow route

Stop rule

Reject modifiers that create topic drift and group accepted modifiers by function.

Possible routes

Facet Intent Extraction
Query Modifier Scan
Query Treatment Selection
Topical Maps and Planning

11 Candidate extraction

Attribute Candidate Harvest

Collect candidate features, qualities, constraints, use cases, benefits, limitations, categories, criteria, specifications, proof points, and descriptive phrases.

Copy full prompt

Short command Run Attribute Candidate Harvest on this corpus.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Attribute Candidate Harvest on this corpus.

Use the approved source context first.

Collect candidate features, qualities, constraints, use cases, benefits, limitations, categories, criteria, specifications, proof points, and descriptive phrases.

Return:
– candidate attribute
– related candidate
– source passage
– source location
– modifier link
– confidence level
– source context fit
– keep, reject, or review
– reason
– suggested downstream workflow
– handoff note

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not assign final attribute priority or repeat the later Entity Attributes workflow.

Route accepted output into one of these destinations:
– Entity Universe Package
– Content Briefs
– Information Gain
– Entity SEO and Salience

Do not run the routed workflow yet.

Best for

product content
comparison content
documentation
competitor pages

Return fields

candidate attribute
related candidate
source passage
source location
modifier link
confidence level
source context fit
keep, reject, or review
reason
suggested downstream workflow
handoff note

Stop rule

Do not assign final attribute priority or repeat the later Entity Attributes workflow.

Possible routes

Entity Universe Package
Content Briefs
Information Gain
Entity SEO and Salience

12 Candidate extraction

Facet Intent Extraction

Identify feature, audience, location, comparison, price, problem, process, trust, format, and urgency facets that change user need or page treatment.

Copy full prompt

Short command Run Facet Intent Extraction on this query set.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Facet Intent Extraction on this query set.

Use the approved source context first.

Identify feature, audience, location, comparison, price, problem, process, trust, format, and urgency facets that change user need or page treatment.

Return:
– facet
– facet type
– related query
– primary intent
– secondary intent
– confidence score
– page treatment suggestion
– source context fit
– keep, reject, or review
– reason
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not build the page map. Use facets only to prepare query treatment and page planning.

Route accepted output into one of these destinations:
– Query Intent Classification
– Query Treatment Selection
– Topical Maps and Planning

Do not run the routed workflow yet.

Best for

long tail queries
product attributes
local modifiers
comparison modifiers

Return fields

facet
facet type
related query
primary intent
secondary intent
confidence score
page treatment suggestion
source context fit
keep, reject, or review
reason
next workflow route

Stop rule

Do not build the page map. Use facets only to prepare query treatment and page planning.

Possible routes

Query Intent Classification
Query Treatment Selection
Topical Maps and Planning

13 Query discovery

Query Intent Classification

Classify each query by primary intent, secondary intent, user stage, likely page type, answer treatment, result format, and source context fit.

Copy full prompt

Short command Run Query Intent Classification on this query set.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Query Intent Classification on this query set.

Use the approved source context first.

Classify each query by primary intent, secondary intent, user stage, likely page type, answer treatment, result format, and source context fit.

Return:
– query
– primary intent
– secondary intent
– user stage
– page type recommendation
– content treatment
– SERP format note
– source context fit
– page, section, question, comparison, anchor, merge, or reject
– reason
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not convert the query list into a topical map.

Route accepted output into one of these destinations:
– Topical Maps and Planning
– Content Briefs
– Information Gain

Do not run the routed workflow yet.

Best for

keyword exports
GSC queries
generated query lists
content brief intake

Return fields

query
primary intent
secondary intent
user stage
page type recommendation
content treatment
SERP format note
source context fit
page, section, question, comparison, anchor, merge, or reject
reason
next workflow route

Stop rule

Do not convert the query list into a topical map.

Possible routes

Topical Maps and Planning
Content Briefs
Information Gain

14 Query discovery

Query Modifier Scan

Scan query wording for modifiers that change page type, intent, format, audience, product stage, local need, comparison need, trust need, or next step.

Copy full prompt

Short command Run Query Modifier Scan on this query set.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Query Modifier Scan on this query set.

Use the approved source context first.

Scan query wording for modifiers that change page type, intent, format, audience, product stage, local need, comparison need, trust need, or next step.

Return:
– modifier
– modifier class
– example query
– repeated pattern
– intent shift
– page type signal
– source context fit
– keep, reject, or review
– reason
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Flag modifiers that should become sections, questions, comparisons, anchors, templates, or examples instead of new pages.

Route accepted output into one of these destinations:
– Query Treatment Selection
– Semantic Query Clustering
– Topical Maps and Planning

Do not run the routed workflow yet.

Best for

keyword exports
Search Console data
topic expansion
page type decisions

Return fields

modifier
modifier class
example query
repeated pattern
intent shift
page type signal
source context fit
keep, reject, or review
reason
next workflow route

Stop rule

Flag modifiers that should become sections, questions, comparisons, anchors, templates, or examples instead of new pages.

Possible routes

Query Treatment Selection
Semantic Query Clustering
Topical Maps and Planning

15 Query discovery

Query Treatment Selection

Decide whether each query needs a dedicated page, section, question, list, comparison, table, anchor target, link target, template, example, merge, or rejection.

Copy full prompt

Short command Run Query Treatment Selection on this query list.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Query Treatment Selection on this query list.

Use the approved source context first.

Decide whether each query needs a dedicated page, section, question, list, comparison, table, anchor target, link target, template, example, merge, or rejection.

Return:
– query
– recommended treatment
– target page if known
– page type if new
– reason
– source context fit
– overlap risk
– internal link note
– keep, merge, section, question, anchor, or reject
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Reject queries outside scope and flag duplicate intent before a new page is proposed.

Route accepted output into one of these destinations:
– Topical Maps and Planning
– Content Briefs
– Internal Linking
– Information Gain

Do not run the routed workflow yet.

Best for

raw keyword lists
generated queries
question planning
page and section decisions

Return fields

query
recommended treatment
target page if known
page type if new
reason
source context fit
overlap risk
internal link note
keep, merge, section, question, anchor, or reject
next workflow route

Stop rule

Reject queries outside scope and flag duplicate intent before a new page is proposed.

Possible routes

Topical Maps and Planning
Content Briefs
Internal Linking
Information Gain

16 Query discovery

Synthetic Query Generation

Generate possible future queries from accepted candidates, modifiers, user stages, page types, product angles, audience needs, location signals, feature signals, and comparison paths.

Copy full prompt

Short command Run Synthetic Query Generation on this candidate and modifier set.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Synthetic Query Generation on this candidate and modifier set.

Use the approved source context first.

Generate possible future queries from accepted candidates, modifiers, user stages, page types, product angles, audience needs, location signals, feature signals, and comparison paths.

Return:
– synthetic query
– source candidate
– source modifier
– inferred intent
– likely user stage
– content treatment
– source context fit
– confidence
– risk note
– keep, reject, or review
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not treat generated queries as proven demand. Mark speculative queries and reject drift.

Route accepted output into one of these destinations:
– Synthetic Query Classification
– Query Treatment Selection
– Semantic Query Clustering

Do not run the routed workflow yet.

Best for

emerging topics
long tail planning
new product attributes
audience variants

Return fields

synthetic query
source candidate
source modifier
inferred intent
likely user stage
content treatment
source context fit
confidence
risk note
keep, reject, or review
next workflow route

Stop rule

Do not treat generated queries as proven demand. Mark speculative queries and reject drift.

Possible routes

Synthetic Query Classification
Query Treatment Selection
Semantic Query Clustering

17 Query discovery

Synthetic Query Classification

Review generated queries for intent, confidence, source context fit, usefulness, risk, and downstream value.

Copy full prompt

Short command Run Synthetic Query Classification on this generated query list.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Synthetic Query Classification on this generated query list.

Use the approved source context first.

Review generated queries for intent, confidence, source context fit, usefulness, risk, and downstream value.

Return:
– generated query
– source candidate
– source modifier
– primary intent
– secondary intent
– confidence
– usefulness
– risk
– keep, revise, reject, or review
– reason
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Reject generated queries that create topic drift and flag queries that need result set validation.

Route accepted output into one of these destinations:
– Query Treatment Selection
– Semantic Query Clustering
– SERP Pattern Intake
– Topical Maps and Planning

Do not run the routed workflow yet.

Best for

generated query sets
future demand planning
speculative planning
feature expansions

Return fields

generated query
source candidate
source modifier
primary intent
secondary intent
confidence
usefulness
risk
keep, revise, reject, or review
reason
next workflow route

Stop rule

Reject generated queries that create topic drift and flag queries that need result set validation.

Possible routes

Query Treatment Selection
Semantic Query Clustering
SERP Pattern Intake
Topical Maps and Planning

18 Query discovery

Semantic Query Clustering

Group queries by meaning, intent layer, user job, page type, modifier pattern, and shared concept rather than repeated words alone.

Copy full prompt

Short command Run Semantic Query Clustering on this query set.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Semantic Query Clustering on this query set.

Use the approved source context first.

Group queries by meaning, intent layer, user job, page type, modifier pattern, and shared concept rather than repeated words alone.

Return:
– cluster name
– included queries
– shared concept
– dominant intent
– secondary intent
– likely page type
– page or section risk
– overlap risk
– source context fit
– suggested next module
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Flag clusters that mix incompatible intent or may need separate pages.

Route accepted output into one of these destinations:
– Query Treatment Selection
– Topical Maps and Planning
– Content Briefs
– SERP Pattern Intake

Do not run the routed workflow yet.

Best for

keyword exports
GSC exports
generated query lists
topical map intake

Return fields

cluster name
included queries
shared concept
dominant intent
secondary intent
likely page type
page or section risk
overlap risk
source context fit
suggested next module
next workflow route

Stop rule

Flag clusters that mix incompatible intent or may need separate pages.

Possible routes

Query Treatment Selection
Topical Maps and Planning
Content Briefs
SERP Pattern Intake

19 Query discovery

Latent Intent Discovery

Find hidden user needs implied by the topic, query set, result set, competitors, modifiers, product context, or user stage.

Copy full prompt

Short command Run Latent Intent Discovery on this topic.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Latent Intent Discovery on this topic.

Use the approved source context first.

Find hidden user needs implied by the topic, query set, result set, competitors, modifiers, product context, or user stage.

Return:
– latent intent
– source signal
– related query pattern
– user need
– likely page type
– content treatment
– source context fit
– confidence
– risk note
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not create pages from latent intent alone. Require query, result set, or source context validation.

Route accepted output into one of these destinations:
– Query Network Expansion
– SERP Pattern Intake
– Topical Maps and Planning
– Content Briefs

Do not run the routed workflow yet.

Best for

emerging topics
low volume topics
ambiguous topics
competitor gaps

Return fields

latent intent
source signal
related query pattern
user need
likely page type
content treatment
source context fit
confidence
risk note
next workflow route

Stop rule

Do not create pages from latent intent alone. Require query, result set, or source context validation.

Possible routes

Query Network Expansion
SERP Pattern Intake
Topical Maps and Planning
Content Briefs

20 Query discovery

Query Network Expansion

Expand a seed topic into query paths, intent branches, user stages, support questions, comparison paths, feature paths, process paths, and adjacent topics.

Copy full prompt

Short command Run Query Network Expansion on this seed topic.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Query Network Expansion on this seed topic.

Use the approved source context first.

Expand a seed topic into query paths, intent branches, user stages, support questions, comparison paths, feature paths, process paths, and adjacent topics.

Return:
– query path
– branch type
– related concept
– primary intent
– secondary intent
– likely page treatment
– source context fit
– keep, reject, or review
– reason
– suggested next workflow

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Reject branches outside scope and flag branches that belong as sections instead of pages.

Route accepted output into one of these destinations:
– Semantic Query Clustering
– Query Treatment Selection
– Topical Maps and Planning
– Content Briefs

Do not run the routed workflow yet.

Best for

early topic exploration
topical map intake
content brief planning
search journey mapping

Return fields

query path
branch type
related concept
primary intent
secondary intent
likely page treatment
source context fit
keep, reject, or review
reason
suggested next workflow

Stop rule

Reject branches outside scope and flag branches that belong as sections instead of pages.

Possible routes

Semantic Query Clustering
Query Treatment Selection
Topical Maps and Planning
Content Briefs

21 SERP and competitor

SERP Entity Harvest

Extract repeated candidate entities, dominant terms, attributes, concepts, headings, table topics, question topics, comparison angles, and visible entity signals from top ranking sources.

Copy full prompt

Short command Run SERP Entity Harvest on these result set competitors.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run SERP Entity Harvest on these result set competitors.

Use the approved source context first.

Extract repeated candidate entities, dominant terms, attributes, concepts, headings, table topics, question topics, comparison angles, and visible entity signals from top ranking sources.

Return:
– candidate
– candidate type
– SERP occurrence count
– source URL count
– source placement
– related modifier
– candidate attribute
– consensus note
– source context fit
– keep, reject, or review
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not copy competitor structure or treat repeated competitor coverage as mandatory.

Route accepted output into one of these destinations:
– Competitive Coverage Snapshot
– SERP Consensus Scan
– Discovery Opportunity Matrix
– Information Gain

Do not run the routed workflow yet.

Best for

competitor pages
SERP exports
content gap work
brief intake

Return fields

candidate
candidate type
SERP occurrence count
source URL count
source placement
related modifier
candidate attribute
consensus note
source context fit
keep, reject, or review
next workflow route

Stop rule

Do not copy competitor structure or treat repeated competitor coverage as mandatory.

Possible routes

Competitive Coverage Snapshot
SERP Consensus Scan
Discovery Opportunity Matrix
Information Gain

22 SERP and competitor

SERP Pattern Intake

Review the result set for dominant page types, content formats, repeated sections, result features, answer formats, tables, questions, comparisons, local results, product blocks, and missing angles.

Copy full prompt

Short command Run SERP Pattern Intake on this query.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run SERP Pattern Intake on this query.

Use the approved source context first.

Review the result set for dominant page types, content formats, repeated sections, result features, answer formats, tables, questions, comparisons, local results, product blocks, and missing angles.

Return:
– query
– dominant page type
– repeated format
– visible SERP feature
– repeated section
– repeated answer pattern
– missing angle
– source context fit
– content treatment note
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not write the brief or finalize result feature strategy during intake.

Route accepted output into one of these destinations:
– Query Treatment Selection
– Content Briefs
– SERP Feature Planning
– Information Gain

Do not run the routed workflow yet.

Best for

high value queries
comparison topics
commercial investigation
result feature targets

Return fields

query
dominant page type
repeated format
visible SERP feature
repeated section
repeated answer pattern
missing angle
source context fit
content treatment note
next workflow route

Stop rule

Do not write the brief or finalize result feature strategy during intake.

Possible routes

Query Treatment Selection
Content Briefs
SERP Feature Planning
Information Gain

23 SERP and competitor

Competitor Entity Harvest

Extract candidate entities, attributes, concepts, page formats, proof points, comparison angles, product references, question themes, and support topics from competitor sources.

Copy full prompt

Short command Run Competitor Entity Harvest on these competitor URLs.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Competitor Entity Harvest on these competitor URLs.

Use the approved source context first.

Extract candidate entities, attributes, concepts, page formats, proof points, comparison angles, product references, question themes, and support topics from competitor sources.

Return:
– extracted candidate
– candidate type
– source competitor
– source passage
– source placement
– repeated attribute
– coverage note
– confidence
– source context fit
– keep, reject, or review
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Use competitor sources as evidence only. Do not copy wording or structure.

Route accepted output into one of these destinations:
– Competitive Coverage Snapshot
– SERP Consensus Scan
– Discovery Opportunity Matrix
– Information Gain

Do not run the routed workflow yet.

Best for

top result pages
competitor blogs
comparison pages
product and docs content

Return fields

extracted candidate
candidate type
source competitor
source passage
source placement
repeated attribute
coverage note
confidence
source context fit
keep, reject, or review
next workflow route

Stop rule

Use competitor sources as evidence only. Do not copy wording or structure.

Possible routes

Competitive Coverage Snapshot
SERP Consensus Scan
Discovery Opportunity Matrix
Information Gain

24 SERP and competitor

Competitive Coverage Snapshot

Summarize common coverage, overused coverage, missing coverage, repeated formats, proof patterns, and seeds for useful differentiation.

Copy full prompt

Short command Run Competitive Coverage Snapshot on this result set.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Competitive Coverage Snapshot on this result set.

Use the approved source context first.

Summarize common coverage, overused coverage, missing coverage, repeated formats, proof patterns, and seeds for useful differentiation.

Return:
– common coverage
– overused coverage
– missing coverage
– repeated format
– proof pattern
– differentiation seed
– source context fit
– risk note
– recommended next module
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not create the page outline or copy competitor sections.

Route accepted output into one of these destinations:
– Information Gain
– Content Briefs
– SERP Pattern Intake
– Discovery Opportunity Matrix

Do not run the routed workflow yet.

Best for

result gap preparation
information gain preparation
brief intake
rewrite planning

Return fields

common coverage
overused coverage
missing coverage
repeated format
proof pattern
differentiation seed
source context fit
risk note
recommended next module
next workflow route

Stop rule

Do not create the page outline or copy competitor sections.

Possible routes

Information Gain
Content Briefs
SERP Pattern Intake
Discovery Opportunity Matrix

25 SERP and competitor

SERP Consensus Scan

Identify repeated concepts, claims, expected sections, page formats, examples, definitions, question topics, comparison angles, and answer patterns across the result set.

Copy full prompt

Short command Run SERP Consensus Scan on this query group.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run SERP Consensus Scan on this query group.

Use the approved source context first.

Identify repeated concepts, claims, expected sections, page formats, examples, definitions, question topics, comparison angles, and answer patterns across the result set.

Return:
– consensus concept
– repeated format
– expected section
– common claim
– common example type
– repeated question topic
– gap
– differentiation note
– source context fit
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Separate expected coverage from repeated coverage and mark areas that need a stronger angle.

Route accepted output into one of these destinations:
– Information Gain
– Content Briefs
– SERP Feature Planning
– Discovery Opportunity Matrix

Do not run the routed workflow yet.

Best for

brief preparation
information gain intake
competitor review
format selection

Return fields

consensus concept
repeated format
expected section
common claim
common example type
repeated question topic
gap
differentiation note
source context fit
next workflow route

Stop rule

Separate expected coverage from repeated coverage and mark areas that need a stronger angle.

Possible routes

Information Gain
Content Briefs
SERP Feature Planning
Discovery Opportunity Matrix

26 SERP and competitor

SERP Divergence Scan

Find where top pages differ in intent, format, audience, page type, depth, angle, action path, proof, result feature focus, and topic scope.

Copy full prompt

Short command Run SERP Divergence Scan on this query group.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run SERP Divergence Scan on this query group.

Use the approved source context first.

Find where top pages differ in intent, format, audience, page type, depth, angle, action path, proof, result feature focus, and topic scope.

Return:
– divergence type
– source page
– different page type
– unique angle
– intent signal
– audience signal
– format signal
– risk note
– source context fit
– recommended next module
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Flag mixed result sets and hold page decisions until the intent is clear enough.

Route accepted output into one of these destinations:
– Query Treatment Selection
– SERP Pattern Intake
– Content Briefs
– Information Gain

Do not run the routed workflow yet.

Best for

uncertain intent
mixed result sets
commercial investigation
comparison pages

Return fields

divergence type
source page
different page type
unique angle
intent signal
audience signal
format signal
risk note
source context fit
recommended next module
next workflow route

Stop rule

Flag mixed result sets and hold page decisions until the intent is clear enough.

Possible routes

Query Treatment Selection
SERP Pattern Intake
Content Briefs
Information Gain

27 SERP and competitor

Topical Authority Baseline

Review current site coverage, competitor depth, related support areas, repeated entities, query branches, and missing support areas before page planning.

Copy full prompt

Short command Run Topical Authority Baseline on this topic.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Topical Authority Baseline on this topic.

Use the approved source context first.

Review current site coverage, competitor depth, related support areas, repeated entities, query branches, and missing support areas before page planning.

Return:
– topic
– current site coverage signal
– competitor depth signal
– expected support area
– repeated support area
– missing support area
– authority risk
– source context fit
– priority note
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Use the result as a baseline. Do not build the full topical map.

Route accepted output into one of these destinations:
– Topical Maps and Planning
– Content Briefs
– Discovery Opportunity Matrix

Do not run the routed workflow yet.

Best for

new clusters
hub planning
site expansion
authority gap reviews

Return fields

topic
current site coverage signal
competitor depth signal
expected support area
repeated support area
missing support area
authority risk
source context fit
priority note
next workflow route

Stop rule

Use the result as a baseline. Do not build the full topical map.

Possible routes

Topical Maps and Planning
Content Briefs
Discovery Opportunity Matrix

28 SERP and competitor

Competitive Schema Scan

Collect visible structured data types, entity fields, attribute patterns, breadcrumb patterns, sameAs cues, and repeated data fields from competitor sources.

Copy full prompt

Short command Run Competitive Schema Scan on these competitor pages.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Competitive Schema Scan on these competitor pages.

Use the approved source context first.

Collect visible structured data types, entity fields, attribute patterns, breadcrumb patterns, sameAs cues, and repeated data fields from competitor sources.

Return:
– competitor source
– visible schema type
– entity field
– attribute pattern
– repeated structured data field
– schema gap note
– source context fit
– relevance to our content
– later schema cue
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not create final schema or add markup before visible content approval.

Route accepted output into one of these destinations:
– Schema Cues after approval
– Content Briefs

Do not run the routed workflow yet.

Best for

product pages
software pages
question heavy pages
process pages

Return fields

competitor source
visible schema type
entity field
attribute pattern
repeated structured data field
schema gap note
source context fit
relevance to our content
later schema cue
next workflow route

Stop rule

Do not create final schema or add markup before visible content approval.

Possible routes

Schema Cues after approval
Content Briefs

29 SERP and competitor

Semantic Neighborhood Expansion

Expand a seed topic into nearby concepts, adjacent categories, related query paths, support concepts, comparisons, processes, features, and explicit rejection candidates.

Copy full prompt

Short command Run Semantic Neighborhood Expansion on this seed topic.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Semantic Neighborhood Expansion on this seed topic.

Use the approved source context first.

Expand a seed topic into nearby concepts, adjacent categories, related query paths, support concepts, comparisons, processes, features, and explicit rejection candidates.

Return:
– adjacent concept
– relationship type
– related query path
– nearby category
– source context fit
– keep, reject, or review
– reject note
– risk note
– suggested next module
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Semantic proximity alone is not enough. Reject adjacent concepts that do not support the approved scope.

Route accepted output into one of these destinations:
– Query Network Expansion
– Semantic Query Clustering
– Topical Maps and Planning
– Discovery Opportunity Matrix

Do not run the routed workflow yet.

Best for

early topical discovery
weak seed topics
query expansion
cluster discovery

Return fields

adjacent concept
relationship type
related query path
nearby category
source context fit
keep, reject, or review
reject note
risk note
suggested next module
next workflow route

Stop rule

Semantic proximity alone is not enough. Reject adjacent concepts that do not support the approved scope.

Possible routes

Query Network Expansion
Semantic Query Clustering
Topical Maps and Planning
Discovery Opportunity Matrix

30 Scope and intake

Source Candidate Ranking

Rank sources by quality, relevance, freshness risk, evidence strength, extraction value, topic fit, intent fit, and risk of adding noise.

Copy full prompt

Short command Run Source Candidate Ranking on this discovery set.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Source Candidate Ranking on this discovery set.

Use the approved source context first.

Rank sources by quality, relevance, freshness risk, evidence strength, extraction value, topic fit, intent fit, and risk of adding noise.

Return:
– source
– source type
– source quality score
– relevance score
– evidence strength
– extraction value
– freshness risk
– noise risk
– keep, hold, ignore, or review
– reason
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not treat every source equally. Reduce the weight of sources that create drift or weak evidence.

Route accepted output into one of these destinations:
– Candidate Weighting
– SERP Entity Harvest
– Competitor Entity Harvest
– Discovery Opportunity Matrix

Do not run the routed workflow yet.

Best for

competitor URLs
SERP exports
large file sets
crawl extracts

Return fields

source
source type
source quality score
relevance score
evidence strength
extraction value
freshness risk
noise risk
keep, hold, ignore, or review
reason
next workflow route

Stop rule

Do not treat every source equally. Reduce the weight of sources that create drift or weak evidence.

Possible routes

Candidate Weighting
SERP Entity Harvest
Competitor Entity Harvest
Discovery Opportunity Matrix

31 Packaging and handoff

Discovery Opportunity Matrix

Turn accepted candidates, rejected candidates, query paths, modifier groups, result patterns, competitor findings, source notes, and risks into prioritized opportunities.

Copy full prompt

Short command Run Discovery Opportunity Matrix on this raw discovery output.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Discovery Opportunity Matrix on this raw discovery output.

Use the approved source context first.

Turn accepted candidates, rejected candidates, query paths, modifier groups, result patterns, competitor findings, source notes, and risks into prioritized opportunities.

Return:
– opportunity
– opportunity type
– evidence source
– source context fit
– impact
– risk
– confidence
– effort
– recommended next workflow
– reason
– blocked items
– review items

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not create final maps, briefs, rewrites, links, or schema.

Route accepted output into one of these destinations:
– Topical Maps and Planning
– Content Briefs
– Drafting and Rewriting
– Entity SEO and Salience
– Internal Linking
– Information Gain
– SERP Feature Planning
– Schema Cues after approval
– Reject or hold

Do not run the routed workflow yet.

Best for

final discovery output
content strategy
mapping handoff
brief handoff

Return fields

opportunity
opportunity type
evidence source
source context fit
impact
risk
confidence
effort
recommended next workflow
reason
blocked items
review items

Stop rule

Do not create final maps, briefs, rewrites, links, or schema.

Possible routes

Topical Maps and Planning
Content Briefs
Drafting and Rewriting
Entity SEO and Salience
Internal Linking
Information Gain
SERP Feature Planning
Schema Cues after approval
Reject or hold

32 Packaging and handoff

Entity Universe Package

Package accepted candidates, rejected candidates, review candidates, query paths, modifier groups, candidate attributes, source notes, result signals, competitor signals, and handoff notes.

Copy full prompt

Short command Run Entity Universe Package on this discovery output.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Entity Universe Package on this discovery output.

Use the approved source context first.

Package accepted candidates, rejected candidates, review candidates, query paths, modifier groups, candidate attributes, source notes, result signals, competitor signals, and handoff notes.

Return:
– accepted candidate
– candidate type
– source evidence
– supporting query path
– related modifier group
– candidate attribute
– SERP signal
– competitor signal
– rejection list
– review list
– source context fit
– handoff note
– next workflow route

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not create the finished entity map, run final salience, or create schema.

Route accepted output into one of these destinations:
– Topical Maps and Planning
– Content Briefs
– Entity SEO and Salience
– Drafting and Rewriting
– Information Gain

Do not run the routed workflow yet.

Best for

raw discovery completion
map intake
brief intake
entity review intake

Return fields

accepted candidate
candidate type
source evidence
supporting query path
related modifier group
candidate attribute
SERP signal
competitor signal
rejection list
review list
source context fit
handoff note
next workflow route

Stop rule

Do not create the finished entity map, run final salience, or create schema.

Possible routes

Topical Maps and Planning
Content Briefs
Entity SEO and Salience
Drafting and Rewriting
Information Gain

33 Packaging and handoff

Page Archetype Seed Discovery

Identify signals for likely page archetypes, user jobs, page roles, and downstream routes from intent, modifiers, result patterns, competitor formats, existing pages, user stages, and commercial goals.

Copy full prompt

Short command Run Page Archetype Seed Discovery on this discovery set.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Page Archetype Seed Discovery on this discovery set.

Use the approved source context first.

Identify signals for likely page archetypes, user jobs, page roles, and downstream routes from intent, modifiers, result patterns, competitor formats, existing pages, user stages, and commercial goals.

Return:
– likely page archetype
– user job
– intent signal
– source evidence
– possible page role
– source context fit
– overlap risk
– keep, reject, or review
– recommended downstream workflow
– reason

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Use the result as a page type seed only. Do not build the processed map.

Route accepted output into one of these destinations:
– Topical Maps and Planning
– Content Briefs
– Docs planning
– Use Case planning
– Comparison planning
– Templates and Examples planning

Do not run the routed workflow yet.

Best for

topical map preparation
use case planning
comparison planning
documentation planning

Return fields

likely page archetype
user job
intent signal
source evidence
possible page role
source context fit
overlap risk
keep, reject, or review
recommended downstream workflow
reason

Stop rule

Use the result as a page type seed only. Do not build the processed map.

Possible routes

Topical Maps and Planning
Content Briefs
Docs planning
Use Case planning
Comparison planning
Templates and Examples planning

34 Packaging and handoff

Discovery Handoff

Route accepted findings, rejected findings, review items, query clusters, modifier groups, result findings, competitor findings, source notes, opportunities, and blocked items into the correct next workflow.

Copy full prompt

Short command Run Discovery Handoff on this raw discovery output.

Open full prompt, fields, stop rule, and routes

Full prompt text

Run Discovery Handoff on this raw discovery output.

Use the approved source context first.

Route accepted findings, rejected findings, review items, query clusters, modifier groups, result findings, competitor findings, source notes, opportunities, and blocked items into the correct next workflow.

Return:
– finding
– finding type
– evidence source
– source context fit
– route to Topical Maps and Planning
– route to Content Briefs
– route to Drafting and Rewriting
– route to Entity SEO and Salience
– route to Internal Linking
– route to Information Gain
– route to SERP Feature Planning
– route to Schema Cues after approval
– blocked item
– reason
– owner or next action
– handoff note

Rules:
– Reject findings that do not support the approved site, audience, offer, or workflow goal.
– Mark uncertainty, weak evidence, and review requirements clearly.
– Do not leave a useful finding without a route and do not send rejected or uncertain findings downstream.

Route accepted output into one of these destinations:
– Topical Maps and Planning
– Content Briefs
– Drafting and Rewriting
– Entity SEO and Salience
– Internal Linking
– Information Gain
– SERP Feature Planning
– Schema Cues after approval
– Hold, review, or reject

Do not run the routed workflow yet.

Best for

end of discovery
large discovery outputs
team handoffs
workflow routing

Return fields

finding
finding type
evidence source
source context fit
route to Topical Maps and Planning
route to Content Briefs
route to Drafting and Rewriting
route to Entity SEO and Salience
route to Internal Linking
route to Information Gain
route to SERP Feature Planning
route to Schema Cues after approval
blocked item
reason
owner or next action
handoff note

Stop rule

Do not leave a useful finding without a route and do not send rejected or uncertain findings downstream.

Possible routes

Topical Maps and Planning
Content Briefs
Drafting and Rewriting
Entity SEO and Salience
Internal Linking
Information Gain
SERP Feature Planning
Schema Cues after approval
Hold, review, or reject

Discovery handoff

The final package separates accepted evidence from noise, uncertainty, and blocked work.

A useful discovery output names the source, confidence, fit, risk, owner, and next route for every finding.

Accepted

Candidate evidence

Accepted entities, concepts, attributes, modifiers, query paths, and result signals with their source evidence.

Rejected

Noise and drift

Repeated terms, adjacent concepts, query branches, sources, and competitor patterns that do not support the approved scope.

Review

Uncertain findings

Items that need stronger evidence, result validation, source context clarification, or human review.

Opportunity

Prioritized next work

Impact, effort, confidence, risk, reason, and the recommended workflow for each accepted opportunity.

Protection

Blocked items

Protected pages, privacy risks, unsupported claims, schema timing issues, and topics that must not move downstream.

Route

Named owner and destination

Mapping, briefs, rewriting, entity review, links, information gain, result features, schema cues, hold, review, or reject.

Continue to Topical Maps Continue to Content Briefs Continue to Information Gain

Questions

Raw Semantic Discovery questions.

What is Raw Semantic Discovery in MIRENA?

Raw Semantic Discovery is the upstream workflow that collects and qualifies candidate entities, concepts, modifiers, query paths, intent signals, result patterns, competitor signals, source signals, and opportunity notes before later workflows decide structure or production.

What should I run first?

Start with Source Context Check when the project boundary is not fully approved. Use Discovery Asset Review for many files, Corpus Scan for a page set, Query Intent Classification for keyword evidence, or SERP Entity Harvest for competitor evidence.

Is Raw Semantic Discovery the same as Entity SEO?

No. Raw Semantic Discovery collects and qualifies candidates. Entity SEO and Salience later organize identity, attributes, relationships, placement, support, and salience.

Is Raw Semantic Discovery the same as topical mapping?

No. Discovery gathers signals and rejects noise. Topical mapping turns approved signals into page ownership, hierarchy, roles, routes, overlap controls, and build order.

Can keyword exports and GSC queries be used?

Yes. Use Query Intent Classification, Query Modifier Scan, Semantic Query Clustering, and Query Treatment Selection before any query becomes a page decision.

Can competitor pages be used?

Yes. Use competitor and result set modules to collect expected concepts, repeated coverage, missing angles, proof patterns, consensus, and divergence. Competitor evidence should guide discovery rather than dictate wording or structure.

Can analytics or behavior evidence be used?

Yes, after Evidence Intake confirms quality, privacy, date range, and interpretation limits. Analytics and behavior evidence can support source ranking, opportunity review, rewrite intake, and route decisions.

What happens after discovery?

Run Discovery Opportunity Matrix, Entity Universe Package, and Discovery Handoff. Route accepted findings into mapping, briefs, rewriting, entity review, internal links, information gain, result feature planning, schema cues after approval, or a hold state.

Next route

Start with source context, run the smallest useful discovery module, then hand off only the accepted findings.

Use the Docs library for evidence intake, workflow routing, topical mapping, briefs, rewrites, entity review, information gain, internal links, result formats, and schema cues.

Founder access is €20 per 30 days excluding VAT for one seat and one active MIRENA instance. OpenAI account rules and usage limits remain separate.

Open MIRENA Browse Docs