MIRENA docs · Input preparation
Give MIRENA the inputs that match the job.
Start with approved source context, then add the files, URLs, drafts, evidence, and page information needed by the selected workflow.
A larger input pack is not automatically better. The useful pack is relevant, current, approved, and clear about the result it should support.
- Source context comes first
- Input type follows the workflow
- Evidence needs dates and limits
- Sensitive data needs review
MIRENA Input Pack Builder
Choose the job and current project state.
Selected input packChoose the workflow
Readiness: blocked0/0
MIRENA INPUT MANIFEST
Loading the input pack builder…
First input
Build source context before the project pack.
Source context controls what belongs, what stays out, which pages are protected, how the offer connects to the work, and which output should come next.
Open the source-context template- site and domain
- product or service
- audience and region
- offer and conversion goal
- allowed and blocked topics
- existing pages and sitemap
- tone, claims, and compliance limits
- requested output and next workflow
Input packs by job
Each workflow needs a different starting pack.
Use the minimum pack to start a controlled task. Add supporting files only when they help answer a real planning, writing, linking, or QA question.
Choose the workflow
Minimum pack
- approved source context
- clear task or problem
- desired output
- current project state
Useful additions
- available files or URLs
- known blockers
- protected-page status
- previous MIRENA outputs
Topical maps and site planning
Minimum pack
- approved source context
- seed topic or niche
- site goal
- audience
- region when relevant
Useful additions
- keyword export
- sitemap or URL inventory
- current rankings
- competitor examples
- existing page roles
- internal-link targets
Content briefing
Minimum pack
- approved source context
- approved page target
- page role
- main query or user job
- audience
Useful additions
- approved topical-map row
- supporting queries
- proof sources
- SERP examples
- internal-link targets
- brand and tone rules
Draft approved copy
Minimum pack
- approved source context
- approved content brief
- approved outline
- proof sources
- page role and user job
Useful additions
- brand voice rules
- preferred terminology
- blocked claims
- internal-link targets
- answer-format instructions
Rewrite an existing page
Minimum pack
- approved source context
- live URL or current draft
- named repair goal
- page role
- main query or user job
Useful additions
- current performance data
- approved proof sources
- related page targets
- protected-page status
- known structural issues
- old brief or outline
Entity SEO and salience
Minimum pack
- approved source context
- target page or cluster
- primary entity
- entity goal
Useful additions
- aliases and disambiguation notes
- entity attributes
- supporting entities
- current headings and copy
- existing structured data
- internal-link targets
Information gain
Minimum pack
- approved source context
- target query or page
- current page or brief
- comparison set or SERP evidence
Useful additions
- competitor pages
- proprietary evidence
- first-hand examples
- customer questions
- current performance data
- existing cluster map
Internal-link planning
Minimum pack
- approved source context
- sitemap or URL list
- target pages to strengthen
- page roles
Useful additions
- crawl export
- current internal links
- anchor constraints
- cluster map
- proof, support, and recovery paths
- page importance notes
SERP feature planning
Minimum pack
- approved source context
- target query
- approved page role
- current or planned page structure
Useful additions
- current SERP captures
- PAA questions
- answer-block candidates
- table or list data
- FAQ candidates
- competitor result formats
Schema cues
Minimum pack
- approved visible draft
- canonical URL
- verified entity facts
- page type
Useful additions
- existing JSON-LD
- organization and author IDs
- visible FAQ or list blocks
- product or offer facts
- breadcrumb path
- plugin-generated markup
Final QA
Minimum pack
- approved visible draft
- approved brief or outline
- proof sources
- internal-link plan
Useful additions
- schema candidate
- desktop and mobile render
- deployment context
- legal or compliance notes
- known risks
- measurement plan
Input quality
A strong input pack answers five questions.
What is the job?
Name the output, page, cluster, or decision the material should support.
Where does it fit?
Connect the input to the site, offer, audience, region, and page role.
How current is it?
Record dates, filters, fields, source quality, and known gaps.
What can it prove?
Explain what the file, URL, screenshot, or export should help decide.
Is it safe to use?
Check permission, confidentiality, personal data, licensing, and protected-page rules.
Common material
Match the input to the question it can answer.
| Input | Best for | Add this context | Common misuse |
|---|---|---|---|
| Seed topic | New maps, clusters, briefs, and page ideas | Audience, offer, region, and site goal | Using a broad phrase as the whole brief |
| Keyword export | Query grouping, demand, page decisions, FAQ and result-format targets | Source, date, metrics, filters, and intent notes | Treating every keyword as a separate URL |
| Sitemap | Structure, overlap, weak hubs, orphan risk, and internal links | Expansion, cleanup, consolidation, or audit goal | Assuming every indexed URL should remain |
| URL list | One cluster, one hub, competing pages, or a narrow link task | Page roles and why this page set was selected | Sending the full site for a narrow question |
| Draft or live URL | Rewrite, entity, information-gain, result-format, and QA work | Page goal, query, proof, related pages, and repair boundary | Asking for a rewrite without the page job |
| Search and analytics export | Demand, performance, decay, route use, and priority | Date range, metric definitions, filters, and tracking gaps | Making causal claims from one metric |
| Screenshot or image | Layout, page comparison, visual blocks, and SERP captures | What the image should prove or help decide | Uploading an image without a task |
| Previous MIRENA output | Restart, revision, handoff, and project continuity | Approval state, open issues, and newer evidence | Treating an old output as current truth |
Data and platform limits
Check permission, privacy, and current upload limits.
Use approved material
Remove or redact personal, confidential, regulated, licensed, or commercially sensitive material unless you have permission and the service is appropriate for the data.
Describe the evidence
For every export or capture, record the source, date range, fields, filters, and limitations. A file without context can create a confident but weak decision.
Check current platform limits
ChatGPT limits can vary by plan, workspace, and file type. Review the official file-upload FAQ before preparing large packs.
Common questions
MIRENA input FAQ
What should I give MIRENA first?
Start with approved source context. It should describe the site, offer, audience, region, allowed topics, blocked topics, existing pages, trust limits, and the result you need.
Can I start with only a topic or keyword?
Yes, but treat it as a light starting point. Add source context, the site goal, the audience, and any existing page or market evidence before accepting a page plan.
Can I use a keyword export?
Yes. A keyword export can support query grouping, page decisions, briefing, and priority. It should not be treated as a page plan without intent, entities, roles, links, and site context.
When should I upload a sitemap?
Use a sitemap for site structure, topical-map audits, overlap checks, weak hubs, orphan risk, page roles, consolidation, and internal-link planning.
What should I provide for a rewrite?
Provide source context, the live URL or current draft, the page goal, the main query or user job, approved proof, related page targets, and the named issue you want repaired.
Can I give MIRENA analytics and search data?
Yes. Search Console, analytics, crawl, ranking, link, heatmap, click, and lead-quality data can support decisions when the date range, fields, source, and limitations are clear.
Can I upload screenshots and images?
Yes. Screenshots are useful for page structure, layout, competitor comparisons, visual blocks, and SERP captures. Add a note that explains what the image should prove or help decide.
What should I avoid uploading?
Do not upload personal, confidential, regulated, licensed, or commercially sensitive material unless you have permission and the service is appropriate for that data.
Do ChatGPT file limits stay the same?
No. Limits can vary by plan, workspace, file type, and product updates. Check the current official OpenAI file-upload documentation before preparing large input packs.
What happens after the input pack is ready?
Use workflow routing to confirm readiness, then move the pack into topical mapping, briefing, drafting, rewriting, entity SEO, information gain, internal links, result-format planning, schema cues, or final QA.
Route the prepared pack into the next workflow.
Use workflow routing to confirm readiness, blockers, and the handoff before MIRENA starts planning, briefing, drafting, rewriting, linking, or QA.