Evidence Intake and Data Readiness Prompts for MIRENA

Use Evidence Intake and Data Readiness prompts when MIRENA needs to inspect files before using them.

This workflow helps MIRENA review sitemaps, URL lists, keyword exports, SERP exports, GSC data, GA4 data, Semrush exports, Ahrefs exports, crawl files, behavior notes, CRM notes, old briefs, old maps, rewrite plans, link maps, and schema notes.

Start with source context.

Do not run evidence prompts against a random file set until MIRENA knows the site, audience, offer, allowed topics, blocked topics, internal link rules, proof rules, and next workflow stage.

Use the source context template if the project base is not ready. Use Getting Started with MIRENA if you need the onboarding route first.

Evidence intake does not extract entities.

It does not build a topical map.

It does not write a brief.

It does not rewrite a page.

It does not create schema.

It decides which inputs are safe, useful, clean, complete, and ready for the next workflow.

Use MIRENA inputs when you need to decide what to give the system. Use MIRENA outputs when you need the evidence handoff to follow a clear structure.

Start with Source Context Before Evidence Intake

Source context controls the evidence layer.

It tells MIRENA which files should influence the project, which files should be held for later, which files may create drift, and which files are missing.

A file can look useful but still be risky.

For example, a competitor export may include off-scope topics. A keyword file may include queries that attract the wrong audience. A crawl may include pages that should be protected. A schema report may be useful later, but not before the draft is approved.

Use Source Context when you need the strategic rule behind this stage.

Use source context to define:

site purpose
audience
offer
target region
primary entities
allowed topic lanes
blocked topic lanes
protected pages
page queue rules
proof rules
internal link rules
data privacy limits
next workflow stage

If source context is weak, stop and build it before running evidence intake.

Use MIRENA workflow when the evidence package needs a route into discovery, mapping, briefing, rewriting, internal links, information gain, SERP formatting, or schema notes.

What Evidence Intake and Data Readiness Prompts Do

Evidence Intake and Data Readiness prompts prepare files and exports before downstream workflows use them.

They help MIRENA answer:

Which files were supplied?
What type of source is each file?
Which fields are present?
Which fields are missing?
Which files are stale?
Which files are duplicated?
Which files have privacy or quality risk?
Which files need cleanup?
Which files need normalization?
Which files should be kept, held, ignored, or reviewed?
Which workflow should use each file next?

This workflow protects the project from weak evidence.

A strong evidence handoff can feed Raw Semantic Discovery Prompts when the next job is extraction. It can feed Topical Maps + Planning when the next job is extraction. It can feed Topical Maps + Planning when the next job is site structure. It can feed Content Briefs when the next job is writer instruction. It can feed Drafting + Rewriting when the next job is page repair.

Evidence can also feed Information Gain when the next job is useful differentiation, Entity SEO when the next job is entity structure, Semantic SEO when the next job is meaning and topic fit, and semantic internal linking when the next job is link routing.

What This Page Does Not Repeat

This page does not repeat the Raw Semantic Discovery prompt set.

Raw Semantic Discovery extracts candidates, concepts, SERP patterns, query paths, and competitor signals. Evidence Intake and Data Readiness comes before that. It checks files, fields, quality, risk, cleanup needs, and workflow routes.

This page does not repeat the Entity SEO and Salience prompt set.

Entity SEO organizes entity structure, relationships, placement, consistency, and salience. Evidence Intake only decides if the entity source files are ready for that workflow.

This page does not repeat the Information Gain prompt set.

Information Gain finds useful difference, repeated coverage, missing examples, missing proof, and stronger angles. Evidence Intake only decides if the source material is ready to support that work.

This page is not a topical map, content brief, rewrite, internal link, or schema prompt guide.

It is the evidence control layer.

When to Use Evidence Intake and Data Readiness Prompts

Use this prompt collection when MIRENA has files, exports, URLs, notes, or prior outputs that need review before production.

Evidence Intake and Data Readiness is useful for:

new project setup
multi-file uploads
sitemap review
URL list review
keyword export review
SERP URL export review
GSC export review
GA4 export review
Semrush export review
Ahrefs export review
Screaming Frog crawl review
behavior data review
CRM and lead quality review
internal search review
old brief review
old topical map review
old rewrite plan review
internal link map review
schema note review
session restart work
data cleanup before handoff

Run this workflow before raw discovery if the files are messy.

Run it before topical mapping if the URL list, crawl, or page queue may contain duplicates, blocked topics, or missing page roles.

Run it before briefing or rewriting if the source evidence is incomplete, stale, unclear, or risky.

Run it before schema notes if the visible content is not approved or the schema file lacks clear source support.

The Evidence Intake Workflow

Run the Evidence Intake and Data Readiness workflow in this order.

Start with source context.
Review the evidence goal.
Build the file inventory.
Label each file by source type.
Check source freshness.
Check source quality.
Check source risk.
Check missing evidence.
Clean file labels.
Normalize fields.
Prioritize inputs.
Route each input into the correct workflow.
Hold sources that are useful later.
Block sources that create risk or drift.
Produce the evidence handoff.

Do not run extraction, mapping, briefing, rewriting, internal links, information gain, SERP formatting, or schema until evidence readiness passes.

Use Master Prompts for Related Evidence Checks

MIRENA can check several related evidence files in one pass.

That does not mean every downstream workflow should start inside the same prompt.

Use evidence master prompts when the sources share the same job. For example, GSC pages, GSC queries, keyword exports, and SERP URL exports can be reviewed together inside a Search Evidence Pack.

Keep readiness gates sequential.

A good evidence master prompt should include:

source context first
source list
source type checks
field checks
date range checks
quality checks
risk checks
missing evidence notes
cleanup notes
normalization notes
keep, hold, ignore, or review decisions
next workflow route
stop conditions

Reader-facing rule:

Bundle evidence checks when the files share the same job. Keep readiness gates sequential.

The Evidence Master Prompt Pattern

Use this pattern for evidence packs.

text

Run [evidence master pack] for this project.

Use the source context first.

Review these inputs:
- [input 1]
- [input 2]
- [input 3]

Complete these tasks in order:
1. Identify the source type.
2. Check source quality.
3. Check field completeness.
4. Check date range.
5. Check risk.
6. Mark missing evidence.
7. Route each file into the correct workflow.

Stop if required files are missing.

Return:
- file name or label
- source type
- source quality
- date range
- missing fields
- risk
- keep, hold, ignore, or review
- cleanup needed
- normalization needed
- next workflow route

Do not extract entities, build maps, write briefs, rewrite pages, create links, run information gain, plan SERP features, or create schema yet.

The Single Evidence Prompt Pattern

Use this pattern for one file or source type.

text

Run [single evidence module] on this file.

Use the source context first.

Review the file for readiness.

Return:
- file name or label
- source type
- fields found
- missing fields
- date range
- source quality
- risk
- cleanup needed
- normalization needed
- best next workflow route

Do not run downstream work yet.

What to Give MIRENA Before Running Evidence Intake

Start with source context.

Then add the files or source descriptions.

For search evidence, give MIRENA:

GSC pages export
GSC queries export
keyword export
SERP URL export
rank tracking export if available
date range
country or region
device split if relevant
target pages or queries

For analytics evidence, give MIRENA:

GA4 landing pages export
GA4 engagement export
conversion path export
event data if available
date range
conversion definitions
pages to review

For SEO tool evidence, give MIRENA:

Semrush keyword export
Semrush page export
Semrush competitor export
Ahrefs top pages export
Ahrefs backlink export
Ahrefs internal link export
rank tracking notes
competitor labels

For crawl evidence, give MIRENA:

Screaming Frog crawl export
indexability report
canonicals report
redirects report
crawl issue report
orphan page report if available
sitemap
URL list

For behavior evidence, give MIRENA:

heatmap notes
scroll depth notes
click tracking notes
session recording notes
internal search logs
form tracking notes
page or cluster target

For prior workflow evidence, give MIRENA:

old briefs
old topical maps
old rewrite plans
old audits
previous MIRENA outputs
internal link maps
schema notes
status notes

Evidence Master Prompt Packs

These master prompts check related evidence sources together while preserving stop conditions and handoff rules.

1. Evidence Intake Setup Pack

Use this when the user is starting a project with several files.

Short command:

text

Run Evidence Intake Setup Pack for this project.

Expanded prompt:

text

Run Evidence Intake Setup Pack for this project.

Use the source context first.

Review all supplied files, exports, URL lists, crawl files, analytics files, behavior notes, CRM notes, old briefs, old maps, rewrite plans, internal link maps, schema notes, and previous MIRENA outputs.

Complete these tasks in order:
1. Build a file inventory.
2. Label each file by source type.
3. Identify the likely use of each file.
4. Check field completeness.
5. Check date range.
6. Check source quality.
7. Check source risk.
8. Identify missing evidence.
9. Mark cleanup needs.
10. Mark normalization needs.
11. Route each file into the correct workflow.

Stop if the source context is missing or the file purpose is unclear.

Return:
- file name or label
- source type
- likely use
- source quality
- date range
- missing fields
- data risk
- cleanup needed
- normalization needed
- keep, hold, ignore, or review
- best next workflow route
- blockers
- review-needed inputs

Do not run raw discovery.

Do not build maps.

Do not write briefs.

Do not rewrite pages.

Do not create links or schema.

Best for:

new projects
large uploads
restart sessions
multi-source audits
unclear file sets

Output should include:

file inventory
source labels
quality notes
missing fields
risk notes
cleanup needs
routes

Use this to:

Load the evidence base, classify files, flag missing inputs, and route the next step without running discovery too early.

2. Search Evidence Pack

Use this for GSC, keyword exports, SERP exports, and query reports.

Short command:

text

Run Search Evidence Pack for these files.

Expanded prompt:

text

Run Search Evidence Pack for these files.

Use the source context first.

Review the GSC query export, GSC page export, keyword export, rank tracking export, SERP URL export, and competitor search reports.

Complete these tasks in order:
1. Label each search source.
2. Check date range.
3. Check country, device, and search type if present.
4. Check query fields.
5. Check URL fields.
6. Check click, impression, CTR, and position fields if present.
7. Check keyword volume, difficulty, and intent fields if present.
8. Identify duplicated or stale exports.
9. Flag missing search evidence.
10. Route each file into the correct workflow.

Return:
- file name or label
- search source type
- date range
- region or country
- fields found
- missing fields
- source quality
- duplicate risk
- stale data risk
- privacy risk
- cleanup needed
- normalization needed
- keep, hold, ignore, or review
- next workflow route

Do not classify queries yet.

Do not build a topical map.

Do not create page ideas.

Route ready files into Raw Semantic Discovery, Topical Maps and Planning, Content Briefs, Information Gain, or Drafting and Rewriting.

Best for:

GSC exports
keyword exports
SERP exports
rank tracking exports
search performance reviews

Output should include:

search source type
date range
fields found
missing fields
duplicate risk
stale risk
next route

Use this to:

Prepare search data before query classification, topical mapping, briefs, information gain, or page refresh work.

3. Analytics Evidence Pack

Use this for GA4 landing pages, engagement, conversion paths, and event data.

Short command:

text

Run Analytics Evidence Pack for these files.

Expanded prompt:

text

Run Analytics Evidence Pack for these files.

Use the source context first.

Review GA4 landing pages, engagement data, event data, conversion paths, acquisition notes, traffic source notes, and user path exports.

Complete these tasks in order:
1. Label each analytics source.
2. Check date range.
3. Check metric definitions.
4. Check landing page fields.
5. Check engagement fields.
6. Check conversion fields.
7. Check event fields.
8. Check source or medium fields if present.
9. Flag missing analytics evidence.
10. Flag privacy or sampling risks.
11. Route each file into the correct workflow.

Return:
- file name or label
- analytics source type
- date range
- metric fields found
- missing fields
- conversion definition
- source quality
- sampling risk
- privacy risk
- cleanup needed
- normalization needed
- keep, hold, ignore, or review
- next workflow route

Do not decide rewrite priorities yet.

Do not create content actions yet.

Route ready files into Drafting and Rewriting, Information Gain, Internal Linking, Topical Maps and Planning, or Final QA.

Best for:

GA4 exports
landing page analysis
conversion path review
engagement review
refresh planning

Output should include:

analytics source type
date range
metrics
conversion fields
risks
next route

Use this to:

Prepare performance and engagement evidence before refresh, rewrite, internal link, or behavioral mapping work.

4. SEO Tool Evidence Pack

Use this for Semrush, Ahrefs, rank tracking, competitor exports, top pages, backlinks, and internal link reports.

Short command:

text

Run SEO Tool Evidence Pack for these exports.

Expanded prompt:

text

Run SEO Tool Evidence Pack for these exports.

Use the source context first.

Review Semrush exports, Ahrefs exports, rank tracking files, competitor exports, top pages reports, backlink reports, keyword reports, and internal link reports.

Complete these tasks in order:
1. Label each tool source.
2. Identify source platform.
3. Check export date.
4. Check target domain.
5. Check competitor labels.
6. Check keyword, URL, backlink, and traffic fields.
7. Check field completeness.
8. Flag duplicated files.
9. Flag stale or low-confidence metrics.
10. Route each file into the correct workflow.

Return:
- file name or label
- platform
- report type
- export date
- target domain
- competitor domain if any
- fields found
- missing fields
- metric confidence
- stale data risk
- cleanup needed
- normalization needed
- keep, hold, ignore, or review
- next workflow route

Do not treat tool estimates as direct truth.

Do not build a map, brief, rewrite, or link plan yet.

Route ready files into Raw Semantic Discovery, Topical Maps and Planning, Content Briefs, Information Gain, Entity SEO, or Internal Linking.

Best for:

Semrush files
Ahrefs files
competitor reports
backlink files
top page reports

Output should include:

platform
report type
export date
fields
confidence
route

Use this to:

Separate tool data that can support mapping, briefs, competitor review, link review, or information gain.

5. Crawl and Technical Evidence Pack

Use this for Screaming Frog, indexability, canonicals, redirects, crawl issues, and orphan risks.

Short command:

text

Run Crawl and Technical Evidence Pack for this crawl.

Expanded prompt:

text

Run Crawl and Technical Evidence Pack for this crawl.

Use the source context first.

Review crawl files, Screaming Frog exports, indexability reports, canonical reports, redirect reports, status code reports, metadata reports, orphan page reports, and sitemap comparisons.

Complete these tasks in order:
1. Label each crawl source.
2. Check crawl date.
3. Check crawl scope.
4. Check URL fields.
5. Check status code fields.
6. Check indexability fields.
7. Check canonical fields.
8. Check redirect fields.
9. Check metadata fields.
10. Flag crawl gaps and crawl risks.
11. Route each file into the correct workflow.

Return:
- file name or label
- crawl source type
- crawl date
- crawl scope
- URL count
- fields found
- missing fields
- technical risk
- cleanup needed
- normalization needed
- keep, hold, ignore, or review
- next workflow route

Do not fix technical issues inside this prompt.

Do not merge, redirect, or rewrite pages yet.

Route ready files into Topical Maps and Planning, Drafting and Rewriting, Internal Linking, Schema Cues after approval, or Final QA.

Best for:

Screaming Frog crawls
indexability reports
canonical reports
redirect reports
technical audits

Output should include:

crawl date
crawl scope
URL count
field issues
technical risk
next route

Use this to:

Prepare technical evidence before map cleanup, rewrite routing, internal links, schema notes, or site restructure work.

6. Behavioral Evidence Pack

Use this for heatmaps, scroll depth, click tracking, session notes, form tracking, internal search, and user path notes.

Short command:

text

Run Behavioral Evidence Pack for these behavior files.

Expanded prompt:

text

Run Behavioral Evidence Pack for these behavior files.

Use the source context first.

Review heatmaps, scroll depth notes, click tracking notes, session recording summaries, internal search logs, form tracking notes, CTA interaction notes, and user path notes.

Complete these tasks in order:
1. Label each behavior source.
2. Check page or template coverage.
3. Check date range.
4. Check sample size if present.
5. Check user segment if present.
6. Check interaction fields.
7. Check privacy risk.
8. Check interpretation risk.
9. Flag missing behavior evidence.
10. Route each file into the correct workflow.

Return:
- file name or label
- behavior source type
- page or template
- date range
- sample size if available
- behavior signal
- missing fields
- privacy risk
- interpretation risk
- cleanup needed
- keep, hold, ignore, or review
- next workflow route

Do not rewrite pages yet.

Do not make conversion claims without support.

Route ready files into Drafting and Rewriting, Information Gain, Internal Linking, Content Briefs, or Final QA.

Best for:

heatmap notes
scroll depth reports
click tracking
session notes
form tracking

Output should include:

behavior source type
page coverage
date range
sample notes
risk
next route

Use this to:

Prepare user behavior inputs before behavioral mapping, rewrite repair, CTA routing, friction review, or internal link planning.

7. Lead and Conversion Evidence Pack

Use this for CRM notes, lead quality reports, sales objections, form outcomes, and conversion path notes.

Short command:

text

Run Lead and Conversion Evidence Pack for this project.

Expanded prompt:

text

Run Lead and Conversion Evidence Pack for this project.

Use the source context first.

Review CRM notes, lead quality reports, sales objections, form outcome notes, demo notes, quote request notes, call summaries, support questions, and conversion path notes.

Complete these tasks in order:
1. Label each lead or conversion source.
2. Check source date range.
3. Check buyer segment.
4. Check conversion event.
5. Check lead quality fields.
6. Check objection fields.
7. Check privacy risk.
8. Check claim support risk.
9. Flag missing conversion evidence.
10. Route each file into the correct workflow.

Return:
- file name or label
- source type
- buyer segment
- date range
- conversion event
- lead quality signal
- objection signal
- missing fields
- privacy risk
- claim support risk
- keep, hold, ignore, or review
- next workflow route

Do not expose private customer data.

Do not write claims from private notes.

Route ready evidence into Content Briefs, Information Gain, Drafting and Rewriting, or Final QA.

Best for:

CRM exports
lead quality reports
sales objections
conversion reviews
product or service pages

Output should include:

source type
buyer segment
conversion signal
objection signal
privacy risk
next route

Use this to:

Prepare buyer-fit evidence before page queue scoring, content briefs, information gain, or refresh work.

8. Historical Workflow Evidence Pack

Use this for old briefs, old topical maps, old rewrite plans, old audits, and prior MIRENA outputs.

Short command:

text

Run Historical Workflow Evidence Pack for these previous outputs.

Expanded prompt:

text

Run Historical Workflow Evidence Pack for these previous outputs.

Use the source context first.

Review old briefs, old topical maps, old rewrite plans, old audits, old link notes, previous MIRENA outputs, strategy notes, page approvals, rejection notes, and prior handoffs.

Complete these tasks in order:
1. Label each historical file.
2. Identify workflow type.
3. Check approval status.
4. Check date or project stage.
5. Check conflicts with current source context.
6. Check items still valid.
7. Check items outdated or replaced.
8. Mark useful carryover notes.
9. Mark blocked carryover notes.
10. Route each prior output into the correct workflow.

Return:
- file name or label
- prior workflow type
- approval status
- date or stage
- still valid items
- outdated items
- conflicting items
- carryover value
- risk
- keep, hold, ignore, or review
- next workflow route

Do not treat old outputs as current approval unless confirmed.

Do not overwrite current source context with older notes.

Route useful files into Project Restart, Topical Maps and Planning, Content Briefs, Drafting and Rewriting, Internal Linking, or Final QA.

Best for:

project restarts
old outputs
long programs
multi-session work
handoffs

Output should include:

prior workflow type
approval status
still valid items
conflicts
carryover notes
next route

Use this to:

Preserve prior work and decide what still helps the current workflow.

9. Link and Schema Evidence Pack

Use this for internal link maps, schema notes, schema errors, rich result notes, anchor data, and link reports.

Short command:

text

Run Link and Schema Evidence Pack for these files.

Expanded prompt:

text

Run Link and Schema Evidence Pack for these files.

Use the source context first.

Review internal link maps, anchor exports, link reports, schema notes, schema validation errors, rich result notes, structured data plans, and prior schema cues.

Complete these tasks in order:
1. Label each link or schema file.
2. Check file type.
3. Check page coverage.
4. Check date or approval status.
5. Check internal link fields.
6. Check anchor fields.
7. Check schema type fields.
8. Check validation status if present.
9. Check approved content status.
10. Route each file into the correct workflow.

Return:
- file name or label
- link or schema source type
- page coverage
- approval status
- fields found
- missing fields
- validation risk
- content approval risk
- cleanup needed
- keep, hold, ignore, or review
- next workflow route

Do not create schema.

Do not alter internal links yet.

Route ready files into Internal Linking, Content Briefs, Drafting and Rewriting, Schema Cues after approval, or Final QA.

Best for:

internal link maps
anchor exports
schema notes
schema validation reports
rich result notes

Output should include:

file type
page coverage
approval status
validation risk
route

Use this to:

Prepare link and structured data inputs without writing schema too early.

10. Data Sufficiency Pack

Use this when the user wants to know if enough evidence exists.

Short command:

text

Run Data Sufficiency Pack for this project.

Expanded prompt:

text

Run Data Sufficiency Pack for this project.

Use the source context first.

Review all supplied evidence and decide if the project has enough data to move into the next workflow.

Check:
1. Source context readiness.
2. File inventory completeness.
3. Required source types.
4. Field completeness.
5. Date range coverage.
6. Source quality.
7. Risk status.
8. Missing evidence.
9. Cleanup needs.
10. Workflow route readiness.

Return:
- evidence area
- available source
- missing source
- required or optional
- source quality
- readiness status
- blocker
- required fix
- pass, revise, hold, or fail
- approved next workflow route

Do not move downstream if required evidence is missing.

Do not request extra files unless they would change the next workflow decision.

Best for:

pre-discovery checks
pre-map checks
pre-brief checks
pre-rewrite checks
pre-QA checks

Output should include:

available sources
missing sources
readiness status
blockers
approved route

Use this to:

Decide if MIRENA can proceed or needs more files first.

11. Input Cleanup and Normalization Pack

Use this when files need cleaning before any workflow can read them.

Short command:

text

Run Input Cleanup and Normalization Pack for these files.

Expanded prompt:

text

Run Input Cleanup and Normalization Pack for these files.

Use the source context first.

Review the supplied files and prepare them for downstream use.

Complete these tasks in order:
1. Clean file labels.
2. Standardize source labels.
3. Standardize URL formats.
4. Standardize date ranges.
5. Standardize page titles.
6. Standardize query fields.
7. Standardize metric names.
8. Remove duplicate rows if instructed.
9. Flag incomplete rows.
10. Mark remaining issues.

Return:
- file name or label
- cleanup action needed
- normalization action needed
- duplicate issue
- missing field issue
- URL format issue
- date range issue
- metric naming issue
- ready, revise, hold, or fail
- next workflow route

Do not change source meaning.

Do not infer missing values without marking them.

Route cleaned files into Evidence Handoff Pack or the next approved workflow.

Best for:

messy exports
renamed files
merged datasets
multi-tool exports
handoff prep

Output should include:

cleanup actions
field issues
duplicate issues
readiness status
next route

Use this to:

Fix labels, field names, formats, duplicates, date ranges, and source notes before handoff.

12. Evidence Handoff Pack

Use this at the end of the evidence workflow.

Short command:

text

Run Evidence Handoff Pack for this project.

Expanded prompt:

text

Run Evidence Handoff Pack for this project.

Use the source context first.

Route every ready, held, ignored, blocked, or review-needed source into the correct next step.

Use these workflow routes:
- Source Context and Guardrails
- Raw Semantic Discovery
- Topical Maps and Planning
- Content Briefs
- Drafting and Rewriting
- Entity SEO and Salience
- Internal Linking
- Information Gain
- SERP Feature Planning
- Schema Cues after approval
- Final QA
- Hold
- Ignore
- Review

Return:
- file name or label
- source type
- readiness status
- quality note
- risk note
- cleanup note
- normalization note
- route
- reason
- blocker
- handoff note

Do not start the routed workflow.

Only hand off the evidence.

Best for:

end of evidence intake
multi-file projects
team handoffs
restart sessions
pre-production checks

Output should include:

readiness status
quality note
risk note
route
reason
blockers
handoff note

Use this to:

Route clean evidence into Raw Semantic Discovery, Topical Maps, Content Briefs, Drafting and Rewriting, Entity SEO, Internal Linking, Information Gain, SERP Feature Planning, Schema Cues after approval, or Final QA.

Single Evidence Intake Prompts

These prompts check one file, export, or evidence type at a time.

Use them when one file needs a focused readiness check or when a master prompt flags a blocker.

1. Evidence Intake

Use this when one evidence source needs review.

Short command:

text

Run Evidence Intake on this file.

Expanded prompt:

text

Run Evidence Intake on this file.

Use the source context first.

Review the file as an evidence source before any downstream workflow uses it.

Return:
- file name or label
- source type
- source purpose
- fields found
- missing fields
- date range
- source quality
- risk
- cleanup needed
- normalization needed
- keep, hold, ignore, or review
- best next workflow route

Do not extract candidates.

Do not build maps, briefs, rewrites, internal links, information gain notes, or schema.

Best for:

single files
unknown sources
uploaded exports
first-pass review
evidence handoff

Output should include:

source type
fields
quality
risk
route

Use this to:

Review one source before it enters the workflow.

2. File Inventory Review

Use this when many files need to be listed and labeled.

Short command:

text

Run File Inventory Review for these uploads.

Expanded prompt:

text

Run File Inventory Review for these uploads.

Use the source context first.

Create an inventory of all supplied files and evidence sources.

Return:
- file name or label
- file type
- likely source
- likely use
- duplicate risk
- missing label
- keep, hold, ignore, or review
- best next workflow route

Do not inspect deep content yet.

Do not run extraction or analysis beyond inventory.

Best for:

bulk uploads
new projects
restarts
mixed exports
file cleanup

Output should include:

file list
file type
likely use
duplicate risk
route

Use this to:

Create a clean file list before deeper review.

3. Data Sufficiency Check

Use this when you need to know if the current evidence is enough.

Short command:

text

Run Data Sufficiency Check for this workflow.

Expanded prompt:

text

Run Data Sufficiency Check for this workflow.

Use the source context first.

Check if the current evidence is enough for the requested next workflow.

Return:
- requested workflow
- available evidence
- missing evidence
- required evidence
- optional evidence
- readiness status
- blocker
- required fix
- approved next route

Do not start the next workflow.

Only assess readiness.

Best for:

pre-discovery checks
pre-map checks
pre-brief checks
pre-rewrite checks
pre-QA checks

Output should include:

available evidence
missing evidence
readiness
blockers
route

Use this to:

Decide if the next workflow can begin.

4. Missing Evidence List

Use this when the project lacks required sources.

Short command:

text

Build a Missing Evidence List for this project.

Expanded prompt:

text

Run Missing Evidence List for this project.

Use the source context first.

Identify which evidence sources are missing for the requested workflow.

Return:
- missing evidence
- reason it is needed
- required or optional
- workflow affected
- risk if missing
- substitute source if any
- next action
- next workflow route

Do not request files that are not needed for the next workflow.

Best for:

incomplete uploads
blocked handoffs
workflow readiness
team requests
project restart

Output should include:

missing source
reason
risk
substitute
next action

Use this to:

Ask for the right missing files without overloading the user.

5. Input Quality Score

Use this when a file needs a quality rating.

Short command:

text

Run Input Quality Score on this file.

Expanded prompt:

text

Run Input Quality Score on this file.

Use the source context first.

Score the input for quality and usefulness.

Return:
- file name or label
- source type
- completeness score
- freshness score
- relevance score
- field quality score
- trust score
- risk score
- total quality score
- keep, hold, ignore, or review
- next workflow route

Do not use low-quality inputs without marking the risk.

Best for:

unknown files
old exports
competitor files
analytics files
handoff prep

Output should include:

quality scores
risk score
decision
route

Use this to:

Give MIRENA a quality signal before the file influences decisions.

6. Input Risk Check

Use this when a file may contain bad, stale, private, or off-context data.

Short command:

text

Run Input Risk Check on this file.

Expanded prompt:

text

Run Input Risk Check on this file.

Use the source context first.

Check the file for risks before downstream use.

Return:
- file name or label
- risk type
- stale data risk
- duplicate data risk
- privacy risk
- off-context risk
- metric confidence risk
- interpretation risk
- blocked use if any
- safe use if any
- next workflow route

Do not send risky inputs downstream without a warning.

Best for:

behavior files
CRM notes
old exports
competitor data
analytics files

Output should include:

risk type
risk level
blocked use
safe use
route

Use this to:

Stop weak or risky inputs from shaping the project.

7. Input Cleanup

Use this when a file needs naming, duplicate, or formatting fixes.

Short command:

text

Run Input Cleanup on this file.

Expanded prompt:

text

Run Input Cleanup on this file.

Use the source context first.

Identify cleanup actions needed before the file can be used.

Return:
- file name or label
- label issue
- duplicate issue
- formatting issue
- URL issue
- date issue
- row issue
- cleanup action
- ready, revise, hold, or fail
- next workflow route

Do not change source meaning.

Flag values that need user review.

Best for:

messy exports
merged files
mislabeled files
duplicate rows
manual notes

Output should include:

cleanup actions
issues
readiness
route

Use this to:

Make the file easier to read before handoff.

8. Input Normalization

Use this when fields need standard labels before analysis.

Short command:

text

Run Input Normalization on this file.

Expanded prompt:

text

Run Input Normalization on this file.

Use the source context first.

Normalize fields so downstream workflows can understand the file.

Return:
- file name or label
- source type
- original field name
- normalized field name
- field type
- missing field
- inferred field if any
- confidence
- normalization note
- next workflow route

Do not infer fields without marking confidence.

Do not overwrite ambiguous fields.

Best for:

multi-tool exports
keyword files
analytics files
crawl files
merged datasets

Output should include:

field mapping
missing fields
confidence
next route

Use this to:

Make files consistent before they enter the next workflow.

9. Input Prioritization

Use this when multiple files compete for attention.

Short command:

text

Run Input Prioritization for these sources.

Expanded prompt:

text

Run Input Prioritization for these sources.

Use the source context first.

Prioritize supplied evidence sources for the requested workflow.

Return:
- source
- source type
- relevance
- quality
- freshness
- risk
- workflow value
- priority
- use now, hold, ignore, or review
- next workflow route

Do not give equal weight to every file.

Best for:

large uploads
multi-source projects
audit files
competitor files
restart sessions

Output should include:

source priority
use now or hold
reason
route

Use this to:

Decide which files should drive the next step.

10. Sitemap Intake

Use this when a sitemap file needs readiness review.

Short command:

text

Run Sitemap Intake on this sitemap.

Expanded prompt:

text

Run Sitemap Intake on this sitemap.

Use the source context first.

Review the sitemap as an evidence source.

Return:
- sitemap label
- URL count
- URL patterns
- included page types
- missing page types if visible
- duplicate URL risk
- blocked topic risk
- protected page signal
- cleanup needed
- best next workflow route

Do not build a topical map yet.

Best for:

XML sitemaps
exported sitemaps
URL inventories
site restructure prep
map planning

Output should include:

URL count
patterns
risks
cleanup
route

Use this to:

Prepare sitemap evidence before mapping or crawl review.

11. URL List Intake

Use this when a URL list needs review.

Short command:

text

Run URL List Intake on this file.

Expanded prompt:

text

Run URL List Intake on this file.

Use the source context first.

Review the URL list for readiness.

Return:
- file label
- URL count
- URL format issues
- duplicate URLs
- page type clues
- off-context URL risk
- protected page clues
- missing labels
- cleanup needed
- next workflow route

Do not classify the full content set yet.

Best for:

page inventories
crawl exports
editorial lists
migration lists
refresh lists

Output should include:

URL count
duplicate issues
page type clues
risks
route

Use this to:

Prepare URL evidence before page queue scoring, mapping, or rewrite routing.

12. Keyword Export Intake

Use this when a keyword export needs readiness review.

Short command:

text

Run Keyword Export Intake on this file.

Expanded prompt:

text

Run Keyword Export Intake on this file.

Use the source context first.

Review the keyword export for readiness.

Return:
- file label
- keyword source
- export date if present
- keyword count
- fields found
- missing fields
- region or database
- volume field status
- difficulty field status
- intent field status
- duplicate query risk
- off-context query risk
- cleanup needed
- next workflow route

Do not classify query intent yet.

Route ready files into Raw Semantic Discovery, Topical Maps and Planning, Content Briefs, or Information Gain.

Best for:

Semrush keywords
Ahrefs keywords
keyword planner exports
rank trackers
manual query files

Output should include:

keyword count
fields
region
duplicate risk
route

Use this to:

Prepare keyword data before query work begins.

13. SERP URL Export Intake

Use this when a SERP export needs review.

Short command:

text

Run SERP URL Export Intake on this file.

Expanded prompt:

text

Run SERP URL Export Intake on this file.

Use the source context first.

Review the SERP URL export for readiness.

Return:
- file label
- target query or query group
- export date if present
- region
- device if present
- competitor URLs
- URL count
- missing fields
- duplicate URLs
- competitor label issues
- off-context source risk
- next workflow route

Do not harvest SERP entities yet.

Route ready files into Raw Semantic Discovery, Information Gain, Content Briefs, or SERP Feature Planning.

Best for:

SERP exports
competitor URL lists
ranking page files
SERP snapshot notes
brief prep

Output should include:

query
region
URLs
duplicates
risks
route

Use this to:

Prepare SERP evidence before competitor or information gain work.

14. GSC Pages Intake

Use this when a GSC pages export needs review.

Short command:

text

Run GSC Pages Intake on this export.

Expanded prompt:

text

Run GSC Pages Intake on this export.

Use the source context first.

Review the Google Search Console pages export for readiness.

Return:
- file label
- date range
- search type
- country if present
- page URL field status
- clicks field status
- impressions field status
- CTR field status
- position field status
- missing fields
- stale data risk
- privacy risk
- cleanup needed
- next workflow route

Do not decide page actions yet.

Route ready files into Drafting and Rewriting, Topical Maps and Planning, Information Gain, Internal Linking, or Final QA.

Best for:

page performance review
content refresh
rewrite routing
internal link planning
GSC-based audits

Output should include:

date range
metrics
missing fields
risks
route

Use this to:

Prepare page performance data before making SEO decisions.

15. GSC Queries Intake

Use this when a GSC queries export needs review.

Short command:

text

Run GSC Queries Intake on this export.

Expanded prompt:

text

Run GSC Queries Intake on this export.

Use the source context first.

Review the Google Search Console queries export for readiness.

Return:
- file label
- date range
- search type
- country if present
- query field status
- page field status if present
- clicks field status
- impressions field status
- CTR field status
- position field status
- missing fields
- duplicate query risk
- off-context query risk
- cleanup needed
- next workflow route

Do not classify query intent yet.

Route ready files into Raw Semantic Discovery, Topical Maps and Planning, Content Briefs, or Information Gain.

Best for:

query discovery
refresh planning
content brief prep
FAQ review
page query matching

Output should include:

date range
query fields
metric fields
risks
route

Use this to:

Prepare search query data before it becomes discovery or briefing input.

16. GA4 Landing Page Intake

Use this when a GA4 landing page export needs review.

Short command:

text

Run GA4 Landing Page Intake on this export.

Expanded prompt:

text

Run GA4 Landing Page Intake on this export.

Use the source context first.

Review the GA4 landing page export for readiness.

Return:
- file label
- date range
- landing page field status
- session field status
- user field status
- engagement field status
- conversion field status if present
- traffic source field status if present
- missing fields
- sampling risk
- cleanup needed
- next workflow route

Do not decide refresh priorities yet.

Best for:

page performance review
refresh planning
rewrite routing
conversion review
final QA support

Output should include:

date range
fields
conversion status
sampling risk
route

Use this to:

Prepare landing page performance evidence before page decisions.

17. GA4 Engagement Intake

Use this when engagement data needs review.

Short command:

text

Run GA4 Engagement Intake on this export.

Expanded prompt:

text

Run GA4 Engagement Intake on this export.

Use the source context first.

Review GA4 engagement evidence for readiness.

Return:
- file label
- date range
- page field status
- engagement metric fields
- average engagement time field
- engaged sessions field
- scroll or event fields if present
- missing fields
- interpretation risk
- cleanup needed
- next workflow route

Do not diagnose content quality from engagement alone.

Route ready evidence into Drafting and Rewriting, Information Gain, Internal Linking, or Final QA.

Best for:

page engagement review
content refresh
behavioral mapping
rewrite prep
CTA review

Output should include:

engagement fields
missing fields
interpretation risk
route

Use this to:

Prepare engagement evidence without overreading the data.

18. GA4 Conversion Path Intake

Use this when conversion path evidence needs review.

Short command:

text

Run GA4 Conversion Path Intake on this export.

Expanded prompt:

text

Run GA4 Conversion Path Intake on this export.

Use the source context first.

Review conversion path evidence for readiness.

Return:
- file label
- date range
- conversion event
- path fields
- landing page fields
- source or medium fields
- step fields if present
- missing fields
- attribution risk
- privacy risk
- cleanup needed
- next workflow route

Do not make conversion claims without context.

Route ready evidence into Content Briefs, Drafting and Rewriting, Information Gain, Internal Linking, or Final QA.

Best for:

conversion path review
buyer journey work
service pages
product pages
refresh planning

Output should include:

conversion event
path fields
attribution risk
route

Use this to:

Prepare conversion path evidence before page or link decisions.

19. Semrush Keyword Intake

Use this when Semrush keyword data needs review.

Short command:

text

Run Semrush Keyword Intake on this export.

Expanded prompt:

text

Run Semrush Keyword Intake on this export.

Use the source context first.

Review the Semrush keyword export for readiness.

Return:
- file label
- export date if present
- database or region
- keyword count
- keyword field status
- volume field status
- KD field status
- intent field status
- URL field status if present
- missing fields
- duplicate query risk
- off-context query risk
- metric confidence note
- next workflow route

Do not classify query intent yet.

Route ready evidence into Raw Semantic Discovery, Topical Maps and Planning, Content Briefs, or Information Gain.

Best for:

Semrush exports
keyword research files
topic prep
brief prep
SERP gap reviews

Output should include:

database
fields
risks
metric notes
route

Use this to:

Prepare Semrush keyword data before downstream search work.

20. Semrush Page Intake

Use this when Semrush page data needs review.

Short command:

text

Run Semrush Page Intake on this export.

Expanded prompt:

text

Run Semrush Page Intake on this export.

Use the source context first.

Review the Semrush page export for readiness.

Return:
- file label
- export date
- domain
- URL field status
- traffic estimate field status
- keyword count field status
- position field status if present
- missing fields
- metric confidence note
- stale data risk
- next workflow route

Do not decide page actions yet.

Route ready evidence into Topical Maps and Planning, Drafting and Rewriting, Information Gain, or Internal Linking.

Best for:

top pages reports
page opportunity review
content refresh
competitor page review
audit prep

Output should include:

domain
URL fields
metrics
confidence
route

Use this to:

Prepare page-level SEO tool data before action planning.

21. Semrush Competitor Intake

Use this when Semrush competitor data needs review.

Short command:

text

Run Semrush Competitor Intake on this export.

Expanded prompt:

text

Run Semrush Competitor Intake on this export.

Use the source context first.

Review Semrush competitor evidence for readiness.

Return:
- file label
- export date
- target domain
- competitor domain
- competitor type
- overlapping keyword fields
- URL fields
- missing fields
- off-context competitor risk
- metric confidence note
- cleanup needed
- next workflow route

Do not run competitor analysis yet.

Route ready evidence into Raw Semantic Discovery, Information Gain, Content Briefs, or Topical Maps and Planning.

Best for:

competitor reports
overlap exports
SERP planning
gap prep
strategy reviews

Output should include:

competitor domain
overlap fields
risks
route

Use this to:

Prepare competitor evidence before gap or information gain work.

22. Ahrefs Top Pages Intake

Use this when Ahrefs top pages data needs review.

Short command:

text

Run Ahrefs Top Pages Intake on this export.

Expanded prompt:

text

Run Ahrefs Top Pages Intake on this export.

Use the source context first.

Review Ahrefs top pages evidence for readiness.

Return:
- file label
- export date
- domain
- URL field status
- traffic estimate field status
- keyword field status
- top query field status if present
- missing fields
- metric confidence note
- stale data risk
- next workflow route

Do not decide page actions yet.

Best for:

page audits
competitor reviews
content refresh
page queue review
information gain prep

Output should include:

URL fields
traffic fields
keyword fields
confidence
route

Use this to:

Prepare Ahrefs top pages evidence before strategy work.

23. Ahrefs Backlink Intake

Use this when backlink evidence needs review.

Short command:

text

Run Ahrefs Backlink Intake on this export.

Expanded prompt:

text

Run Ahrefs Backlink Intake on this export.

Use the source context first.

Review backlink evidence for readiness.

Return:
- file label
- export date
- target domain
- source URL field
- target URL field
- anchor field
- referring domain field
- link type field
- missing fields
- stale data risk
- spam risk
- next workflow route

Do not create link building recommendations.

Route ready evidence into Internal Linking, page protection review, content refresh, or Final QA if relevant.

Best for:

backlink reports
page protection
migration prep
refresh planning
content audit support

Output should include:

source URL
target URL
anchors
spam risk
route

Use this to:

Prepare backlink evidence without confusing it with internal link planning.

24. Ahrefs Internal Links Intake

Use this when internal link data from Ahrefs needs review.

Short command:

text

Run Ahrefs Internal Links Intake on this export.

Expanded prompt:

text

Run Ahrefs Internal Links Intake on this export.

Use the source context first.

Review Ahrefs internal links evidence for readiness.

Return:
- file label
- export date
- source URL field
- target URL field
- anchor field
- link count field
- missing fields
- duplicate row risk
- orphan risk signals if present
- cleanup needed
- next workflow route

Do not alter links yet.

Route ready evidence into Internal Linking, Topical Maps and Planning, Content Briefs, or Drafting and Rewriting.

Best for:

internal link review
orphan checks
anchor review
page role review
site architecture work

Output should include:

source URL
target URL
anchor
missing fields
route

Use this to:

Prepare internal link evidence before link strategy work.

25. Screaming Frog Crawl Intake

Use this when a Screaming Frog crawl needs review.

Short command:

text

Run Screaming Frog Crawl Intake on this crawl.

Expanded prompt:

text

Run Screaming Frog Crawl Intake on this crawl.

Use the source context first.

Review the Screaming Frog crawl export for readiness.

Return:
- file label
- crawl date
- crawl mode if known
- URL count
- status code fields
- indexability fields
- title fields
- meta fields
- canonical fields
- heading fields
- missing fields
- crawl scope risk
- cleanup needed
- next workflow route

Do not fix technical issues yet.

Best for:

crawl review
URL inventories
site audits
technical evidence
map cleanup

Output should include:

crawl date
URL count
fields
scope risk
route

Use this to:

Prepare crawl evidence before technical or content workflows use it.

26. Crawl Issue Intake

Use this when crawl issue reports need review.

Short command:

text

Run Crawl Issue Intake on this report.

Expanded prompt:

text

Run Crawl Issue Intake on this report.

Use the source context first.

Review crawl issue evidence for readiness.

Return:
- file label
- issue type
- affected URL field
- severity field
- issue count field
- crawl date
- missing fields
- technical risk
- content workflow relevance
- next workflow route

Do not fix issues yet.

Route ready evidence into Final QA, Internal Linking, Drafting and Rewriting, or technical review.

Best for:

crawl errors
duplicate titles
missing metadata
thin pages
broken links

Output should include:

issue type
affected URLs
severity
risk
route

Use this to:

Prepare crawl issue evidence before action planning.

27. Indexability Intake

Use this when indexability data needs review.

Short command:

text

Run Indexability Intake on this report.

Expanded prompt:

text

Run Indexability Intake on this report.

Use the source context first.

Review indexability evidence for readiness.

Return:
- file label
- crawl date
- URL field
- indexability field
- indexability status
- noindex signal
- blocked signal
- canonicalized signal
- missing fields
- risk
- next workflow route

Do not decide indexation actions yet.

Best for:

crawl review
sitemap checks
page queue checks
content refresh
final QA

Output should include:

indexability fields
blocked signals
canonicalized signals
risk
route

Use this to:

Protect downstream workflows from using pages that cannot be indexed or need review.

28. Canonical Intake

Use this when canonical data needs review.

Short command:

text

Run Canonical Intake on this report.

Expanded prompt:

text

Run Canonical Intake on this report.

Use the source context first.

Review canonical evidence for readiness.

Return:
- file label
- URL field
- canonical URL field
- self-canonical status
- canonical target status
- mismatch risk
- duplicate risk
- missing fields
- review-needed URLs
- next workflow route

Do not change canonical rules inside this prompt.

Best for:

technical audits
duplicate review
migration prep
page consolidation
final QA

Output should include:

canonical fields
mismatch risk
review URLs
route

Use this to:

Prepare canonical evidence before page decisions.

29. Redirect Intake

Use this when redirects need review.

Short command:

text

Run Redirect Intake on this report.

Expanded prompt:

text

Run Redirect Intake on this report.

Use the source context first.

Review redirect evidence for readiness.

Return:
- file label
- source URL field
- destination URL field
- status code field
- redirect chain signal
- redirect loop signal
- missing fields
- migration risk
- content workflow relevance
- next workflow route

Do not create redirect rules yet.

Best for:

migrations
page merges
deleted pages
crawl audits
link preservation

Output should include:

source URL
destination URL
chain risk
loop risk
route

Use this to:

Prepare redirect evidence before structural decisions.

30. Internal Search Data Intake

Use this when internal site search data needs review.

Short command:

text

Run Internal Search Data Intake on this file.

Expanded prompt:

text

Run Internal Search Data Intake on this file.

Use the source context first.

Review internal site search evidence for readiness.

Return:
- file label
- date range
- search term field
- count field
- result page field if present
- no-result signal if present
- page context if present
- privacy risk
- missing fields
- next workflow route

Do not create pages from internal search data yet.

Route ready evidence into Content Briefs, Topical Maps and Planning, Information Gain, or Drafting and Rewriting.

Best for:

site search logs
support sites
docs sites
ecommerce search
product support

Output should include:

search terms
counts
no-result signal
privacy risk
route

Use this to:

Prepare internal search evidence before content decisions.

31. CRM Lead Quality Intake

Use this when CRM or lead quality data needs review.

Short command:

text

Run CRM Lead Quality Intake on this file.

Expanded prompt:

text

Run CRM Lead Quality Intake on this file.

Use the source context first.

Review CRM or lead quality evidence for readiness.

Return:
- file label
- date range
- lead source field
- landing page field if present
- lead quality field
- conversion field
- objection field if present
- privacy risk
- missing fields
- safe use note
- next workflow route

Do not expose private lead details.

Do not make unsupported performance claims.

Best for:

lead quality reviews
service pages
conversion pages
sales alignment
content planning

Output should include:

lead source
quality field
privacy risk
safe use
route

Use this to:

Prepare buyer and conversion evidence without exposing private data.

32. Heatmap Intake

Use this when heatmap evidence needs review.

Short command:

text

Run Heatmap Intake on this evidence.

Expanded prompt:

text

Run Heatmap Intake on this evidence.

Use the source context first.

Review heatmap evidence for readiness.

Return:
- file label
- page or template
- date range
- sample size if available
- click heatmap signal
- attention signal
- ignored area signal
- privacy risk
- interpretation risk
- next workflow route

Do not rewrite the page from heatmap evidence alone.

Best for:

page repair
CTA review
UX evidence
conversion pages
content refresh

Output should include:

page
signals
sample note
risks
route

Use this to:

Prepare visual behavior evidence before rewrite or conversion work.

33. Scroll Depth Intake

Use this when scroll depth data needs review.

Short command:

text

Run Scroll Depth Intake on this evidence.

Expanded prompt:

text

Run Scroll Depth Intake on this evidence.

Use the source context first.

Review scroll depth evidence for readiness.

Return:
- file label
- page or template
- date range
- sample size if available
- scroll depth field
- drop-off signal
- section affected if known
- interpretation risk
- missing fields
- next workflow route

Do not judge content quality from scroll depth alone.

Best for:

long pages
guides
landing pages
refresh planning
rewrite prep

Output should include:

page
scroll depth
drop-off
risk
route

Use this to:

Prepare scroll evidence before section repair.

34. Click Tracking Intake

Use this when click tracking data needs review.

Short command:

text

Run Click Tracking Intake on this evidence.

Expanded prompt:

text

Run Click Tracking Intake on this evidence.

Use the source context first.

Review click tracking evidence for readiness.

Return:
- file label
- page or template
- date range
- clicked element field
- click count field
- CTA signal
- internal link signal
- ignored link signal
- privacy risk
- interpretation risk
- next workflow route

Do not change links or CTAs yet.

Best for:

CTA review
internal link planning
behavior analysis
conversion pages
refresh tasks

Output should include:

clicked element
CTA signal
link signal
risk
route

Use this to:

Prepare click evidence before link or rewrite work.

35. Session Recording Notes Intake

Use this when session recording notes need review.

Short command:

text

Run Session Recording Notes Intake on these notes.

Expanded prompt:

text

Run Session Recording Notes Intake on these notes.

Use the source context first.

Review session recording notes for readiness.

Return:
- file label
- page or journey
- date range
- sample size if available
- observed behavior
- friction signal
- user intent clue
- privacy risk
- interpretation risk
- next workflow route

Do not include private user details.

Do not overstate findings from a small sample.

Best for:

behavior reviews
conversion path work
page repair
support pages
UX evidence

Output should include:

observed behavior
friction
privacy risk
interpretation risk
route

Use this to:

Prepare qualitative behavior evidence before downstream actions.

36. Form Tracking Intake

Use this when form tracking evidence needs review.

Short command:

text

Run Form Tracking Intake on this file.

Expanded prompt:

text

Run Form Tracking Intake on this file.

Use the source context first.

Review form tracking evidence for readiness.

Return:
- file label
- form type
- date range
- form page
- start field if present
- completion field if present
- abandonment field if present
- error field if present
- privacy risk
- missing fields
- next workflow route

Do not expose form submissions.

Do not make conversion claims without context.

Best for:

lead forms
demo forms
quote forms
signup flows
conversion pages

Output should include:

form type
completion fields
abandonment fields
privacy risk
route

Use this to:

Prepare form evidence before conversion-focused rewrites.

37. Old Brief Intake

Use this when old content briefs need review.

Short command:

text

Run Old Brief Intake on this brief.

Expanded prompt:

text

Run Old Brief Intake on this brief.

Use the source context first.

Review the old brief for current usefulness.

Return:
- brief label
- page target
- approval status if known
- date or project stage
- still useful sections
- outdated sections
- conflicting instructions
- missing evidence
- carryover notes
- next workflow route

Do not treat an old brief as approved unless approval is clear.

Best for:

restarts
content refresh
rewrite projects
page updates
editorial handoffs

Output should include:

page target
status
useful parts
outdated parts
route

Use this to:

Decide which parts of an old brief can still guide the workflow.

38. Old Topical Map Intake

Use this when an old topical map needs review.

Short command:

text

Run Old Topical Map Intake on this map.

Expanded prompt:

text

Run Old Topical Map Intake on this map.

Use the source context first.

Review the old topical map for current usefulness.

Return:
- map label
- map scope
- approval status if known
- still valid clusters
- outdated clusters
- blocked topics found
- missing page roles
- duplicate page risk
- carryover notes
- next workflow route

Do not approve the old map without current guardrail review.

Best for:

site restructuring
page queue review
map refresh
project restart
content planning

Output should include:

map scope
valid clusters
outdated clusters
blocked topics
route

Use this to:

Reuse old mapping work only where it still fits the current project.

39. Old Rewrite Plan Intake

Use this when an old rewrite plan needs review.

Short command:

text

Run Old Rewrite Plan Intake on this plan.

Expanded prompt:

text

Run Old Rewrite Plan Intake on this plan.

Use the source context first.

Review the old rewrite plan for current usefulness.

Return:
- rewrite plan label
- target page
- approval status if known
- still useful actions
- outdated actions
- unsupported claims
- missing evidence
- internal link notes
- carryover notes
- next workflow route

Do not rewrite from old instructions without current review.

Best for:

paused rewrites
old content refreshes
draft repair
editorial restarts
QA work

Output should include:

target page
useful actions
outdated actions
missing evidence
route

Use this to:

Decide which rewrite instructions still belong.

40. Internal Link Map Intake

Use this when an internal link map needs review.

Short command:

text

Run Internal Link Map Intake on this file.

Expanded prompt:

text

Run Internal Link Map Intake on this file.

Use the source context first.

Review the internal link map for readiness.

Return:
- file label
- map scope
- source URL field
- target URL field
- anchor field
- page role field if present
- missing fields
- protected page risk
- orphan support signal
- cleanup needed
- next workflow route

Do not change links yet.

Route ready evidence into semantic internal linking, Content Briefs, Drafting and Rewriting, or Topical Maps and Planning.

Best for:

link audits
hub planning
page refreshes
content briefs
site architecture work

Output should include:

source URL
target URL
anchor fields
protected page risk
route

Use this to:

Prepare internal link map evidence before link decisions.

41. Schema Notes Intake

Use this when schema notes need review.

Short command:

text

Run Schema Notes Intake on this file.

Expanded prompt:

text

Run Schema Notes Intake on this file.

Use the source context first.

Review schema notes for readiness.

Return:
- file label
- target page
- schema type if present
- entity fields
- attribute fields
- validation notes if present
- visible content approval status
- missing fields
- schema timing risk
- next workflow route

Do not create schema.

Do not apply schema notes to unapproved visible content.

Route ready evidence into Schema Cues after approval or Final QA.

Best for:

schema planning
rich result notes
validation reports
entity markup notes
final QA

Output should include:

target page
schema type
entity fields
approval status
timing risk
route

Use this to:

Prepare schema evidence without creating schema before the page is ready.

Which Evidence Prompt Should You Run First?

Start with Evidence Intake Setup Pack if you have several files and do not know where they belong.

Start with Search Evidence Pack if most files are GSC, keyword, SERP, or rank tracking exports.

Start with Analytics Evidence Pack if the project is about performance, engagement, conversion, or refresh work.

Start with Crawl and Technical Evidence Pack if the project includes Screaming Frog, indexability, canonical, redirect, or crawl issue exports.

Start with Behavioral Evidence Pack if the project includes heatmaps, scroll depth, click tracking, session notes, internal search, or form tracking.

Start with Historical Workflow Evidence Pack if you are restarting from old MIRENA outputs, briefs, maps, audits, or rewrite plans.

Start with Data Sufficiency Pack if you need to know if the project can move forward.

Start with Evidence Handoff Pack when every file has been checked and needs routing.

Common Evidence Intake Starting Points

I Have a Folder of Mixed Files

Use this prompt first.

text

Run Evidence Intake Setup Pack for this project.

Use the source context first.

Review all supplied files, exports, URL lists, crawl files, analytics files, behavior notes, CRM notes, old briefs, old maps, rewrite plans, internal link maps, schema notes, and previous MIRENA outputs.

Return:
- file name or label
- source type
- likely use
- source quality
- date range
- missing fields
- data risk
- cleanup needed
- normalization needed
- keep, hold, ignore, or review
- best next workflow route
- blockers
- review-needed inputs

Do not run raw discovery, mapping, briefing, rewriting, internal links, information gain, SERP formatting, or schema.

Then run:

text

Run Data Sufficiency Pack for this project.

Use the source context first.

Check if the current evidence is enough for the requested next workflow.

Return:
- evidence area
- available source
- missing source
- required or optional
- source quality
- readiness status
- blocker
- required fix
- pass, revise, hold, or fail
- approved next workflow route

I Have Search Console and Keyword Data

Use this prompt first.

text

Run Search Evidence Pack for these files.

Use the source context first.

Review the GSC query export, GSC page export, keyword export, rank tracking export, SERP URL export, and competitor search reports.

Return:
- file name or label
- search source type
- date range
- region or country
- fields found
- missing fields
- source quality
- duplicate risk
- stale data risk
- privacy risk
- cleanup needed
- normalization needed
- keep, hold, ignore, or review
- next workflow route

Do not classify queries yet.

Then route ready files into Raw Semantic Discovery Prompts, Topical Maps + Planning, Content Briefs, or Information Gain.

I Have GA4, Heatmaps, and Conversion Notes

Use this prompt first.

text

Run Analytics Evidence Pack for these files.

Use the source context first.

Review GA4 landing pages, engagement data, event data, conversion paths, acquisition notes, traffic source notes, and user path exports.

Return:
- file name or label
- analytics source type
- date range
- metric fields found
- missing fields
- conversion definition
- source quality
- sampling risk
- privacy risk
- cleanup needed
- normalization needed
- keep, hold, ignore, or review
- next workflow route

Then run:

text

Run Behavioral Evidence Pack for these behavior files.

Use the source context first.

Review heatmaps, scroll depth notes, click tracking notes, session recording summaries, internal search logs, form tracking notes, CTA interaction notes, and user path notes.

Return:
- file name or label
- behavior source type
- page or template
- date range
- sample size if available
- behavior signal
- missing fields
- privacy risk
- interpretation risk
- cleanup needed
- keep, hold, ignore, or review
- next workflow route

Route ready files into Drafting + Rewriting, Information Gain, or semantic internal linking.

I Have a Screaming Frog Crawl

Use this prompt first.

text

Run Crawl and Technical Evidence Pack for this crawl.

Use the source context first.

Review crawl files, Screaming Frog exports, indexability reports, canonical reports, redirect reports, status code reports, metadata reports, orphan page reports, and sitemap comparisons.

Return:
- file name or label
- crawl source type
- crawl date
- crawl scope
- URL count
- fields found
- missing fields
- technical risk
- cleanup needed
- normalization needed
- keep, hold, ignore, or review
- next workflow route

Do not fix technical issues yet.

Then route ready files into Topical Maps + Planning, Drafting + Rewriting, semantic internal linking, or Final QA.

I Have Old Briefs, Maps, and Rewrite Plans

Use this prompt first.

text

Run Historical Workflow Evidence Pack for these previous outputs.

Use the source context first.

Review old briefs, old topical maps, old rewrite plans, old audits, old link notes, previous MIRENA outputs, strategy notes, page approvals, rejection notes, and prior handoffs.

Return:
- file name or label
- prior workflow type
- approval status
- date or stage
- still valid items
- outdated items
- conflicting items
- carryover value
- risk
- keep, hold, ignore, or review
- next workflow route

Do not treat old outputs as current approval unless confirmed.

Then run:

text

Run Evidence Handoff Pack for this project.

Use the source context first.

Route every ready, held, ignored, blocked, or review-needed source into the correct next step.

Return:
- file name or label
- source type
- readiness status
- quality note
- risk note
- cleanup note
- normalization note
- route
- reason
- blocker
- handoff note

I Need to Know if I Have Enough Data

Use this prompt.

text

Run Data Sufficiency Pack for this project.

Use the source context first.

Review all supplied evidence and decide if the project has enough data to move into the next workflow.

Check:
1. Source context readiness.
2. File inventory completeness.
3. Required source types.
4. Field completeness.
5. Date range coverage.
6. Source quality.
7. Risk status.
8. Missing evidence.
9. Cleanup needs.
10. Workflow route readiness.

Return:
- evidence area
- available source
- missing source
- required or optional
- source quality
- readiness status
- blocker
- required fix
- pass, revise, hold, or fail
- approved next workflow route

Do not move downstream if required evidence is missing.

Review the Evidence Before Moving Forward

Before moving evidence downstream, check that the output includes:

source context fit
file inventory
source type
source quality
date range
missing fields
duplicated files
stale files
privacy risk
data risk
cleanup needs
normalization needs
evidence priority
keep, hold, ignore, or review status
next workflow route
blocked inputs
review-needed inputs

Do not move into raw discovery, topical maps, content briefs, rewrites, internal links, information gain, SERP formatting, or schema if the evidence layer has unresolved blockers.

How Evidence Intake Connects to Other MIRENA Workflows

Evidence Intake and Data Readiness sits before downstream workflows.

A clean GSC query export can feed Raw Semantic Discovery Prompts when the next job is query and candidate extraction.

A clean sitemap or URL list can feed Topical Maps + Planning when the next job is structure.

A clean SERP file can feed Content Briefs when the next job is writer instruction.

A clean GA4 or behavior source can feed Drafting + Rewriting when the next job is page repair.

A clean competitor or SERP source can feed Information Gain when the next job is useful differentiation.

A clean entity source can feed Entity SEO when the next job is entity structure.

A clean internal link export can feed semantic internal linking when the next job is link route design.

A clean schema note can feed schema cues only after the visible page content is approved.

Evidence Intake Mistakes to Avoid

Mistake 1: Running Discovery Before File Review

A file can look useful and still be stale, duplicated, incomplete, or off-context.

Run evidence intake before extraction.

Mistake 2: Treating Every Export Equally

A GSC export, GA4 export, crawl, keyword file, and competitor report do not have the same role.

Label the source type and route each file into the right workflow.

Mistake 3: Ignoring Date Ranges

Old data can still be useful, but it needs a date note.

Date range affects refresh planning, performance review, and evidence confidence.

Mistake 4: Overreading Behavior Data

Heatmaps, scroll depth, clicks, and session notes are useful signals.

They should not be treated as proof by themselves.

Mistake 5: Sending Private Data Downstream

CRM notes, lead quality data, form tracking, and session notes may contain sensitive details.

Flag privacy risk before the file enters briefing or rewriting.

Mistake 6: Creating Schema Too Early

Schema notes are evidence, not final schema.

Only route schema evidence into schema cues after the visible page content is approved.

Mistake 7: Forgetting the Evidence Handoff

Evidence should not sit as a loose file list.

Every ready, held, ignored, blocked, or review-needed file needs a route.

FAQs About Evidence Intake and Data Readiness Prompts

What is Evidence Intake in MIRENA?

Evidence Intake is the workflow that reviews files before MIRENA uses them.

It labels sources, checks fields, checks quality, flags risks, finds missing inputs, marks cleanup needs, and routes each source into the correct next workflow.

Is Evidence Intake the same as Raw Semantic Discovery?

No.

Evidence Intake checks if files are ready.

Raw Semantic Discovery Prompts extract candidates, concepts, query paths, SERP patterns, and competitor signals after the evidence is ready.

What should I run first?

Run Evidence Intake Setup Pack if you have several files.

Run a single evidence module if you only need one file checked.

Run Data Sufficiency Pack if you need to know if the project can move forward.

Can I upload GSC and GA4 files?

Yes.

Use Search Evidence Pack for GSC exports and Analytics Evidence Pack for GA4 exports.

Then route the ready evidence into discovery, mapping, briefs, rewrites, internal links, information gain, or final QA.

Can I use Semrush and Ahrefs files?

Yes.

Use SEO Tool Evidence Pack when you have Semrush or Ahrefs exports.

Use the platform-specific intake modules when one export needs a focused readiness check.

Can I use Screaming Frog crawl data?

Yes.

Use Crawl and Technical Evidence Pack for a full crawl group.

Use Screaming Frog Crawl Intake, Crawl Issue Intake, Indexability Intake, Canonical Intake, or Redirect Intake for focused checks.

Can I use behavior data?

Yes.

Use Behavioral Evidence Pack for heatmaps, scroll depth, click tracking, session notes, internal search, and form tracking.

Flag privacy risk and interpretation risk before routing it into rewrites, information gain, or internal linking.

Can I use old MIRENA outputs?

Yes.

Use Historical Workflow Evidence Pack, Old Brief Intake, Old Topical Map Intake, or Old Rewrite Plan Intake.

Old outputs should not be treated as current approval unless the project confirms they still fit.

What should happen after Evidence Intake?

Move the ready sources into the correct next workflow.

Use Raw Semantic Discovery Prompts when the next job is extraction.

Use Topical Maps + Planning when the next job is structure.

Use Content Briefs when the next job is writer instruction.

Use Drafting + Rewriting when the next job is page repair.

Use Information Gain when the next job is useful differentiation.

Use semantic internal linking when the next job is link routing.

Use schema cues only after visible content is approved.