Every MIRENA project starts with source context.
Source context tells MIRENA what the site is, who it serves, what it sells, which topics belong, which topics should be blocked, what data is available, and what output the project needs.
Do not start with a prompt, keyword list, sitemap, draft, or workflow choice.
Start by defining the source context.
Once that is clear, MIRENA can help you plan the site, brief the page, draft or rewrite the page, place internal links, prepare schema notes, and run final QA.
The fast path is:
- Build source context.
- Add the strongest files and data you have.
- Choose the workflow.
- Ask for one clear output.
- Review the output.
- Move it into the next stage.
Use the source context template if you want a copyable setup file. Use the MIRENA input documentation if you need the full list of files, exports, and project notes you can give the system.
Source Context Comes First
Source context is the control layer for MIRENA.
It gives the workflow its boundaries. It tells MIRENA the site, offer, audience, topic scope, exclusions, internal link targets, source files, and requested output.
A strong source context should explain:
- site name
- domain
- product or service
- audience
- target region
- main offer
- core workflows
- existing sitemap
- allowed topics
- blocked topics
- target pages
- internal link rules
- tone rules
- data sources used
- desired output
- next workflow stage
Without source context, MIRENA has to infer too much. The output may look organized, but it can drift away from the site, audience, product, or commercial path.
With source context, the output can stay tied to the project. That makes the topical map cleaner, the brief clearer, the rewrite more useful, and the internal links easier to place.
The source context template is the best starting point when you need a structured input file. It defines the site, audience, offer, entities, exclusions, existing pages, internal links, and requested output before MIRENA creates maps, briefs, rewrites, audits, or recommendations.
The Source Context page explains the planning rule behind this. Source context protects the site’s topical focus before new pages enter the map.
What MIRENA Does
MIRENA is an AI SEO operating system for structured content work.
It helps teams turn source context, topics, sitemaps, URL lists, drafts, keyword exports, analytics exports, search data, link data, and behavior signals into usable SEO outputs.
The core workflow is:
- Define the source context.
- Add project evidence.
- Plan the site.
- Brief the page.
- Draft or rewrite the page.
- Review internal links.
- Add schema notes after approval.
- Run final QA.
That sequence keeps SEO work from jumping straight from research into writing. It gives the site structure before content is produced.
MIRENA can help create:
- topical maps
- page inventories
- entity maps
- content briefs
- rewrite plans
- draft audits
- internal link plans
- SERP feature notes
- schema notes
- publishing order
- consolidation notes
- behavior based page path notes
- source context files
MIRENA is not only a writing tool. It helps plan, brief, shape, connect, and review SEO content before it goes live.
Weak pages often come from weak planning. A page can contain plenty of copy and still have unclear intent, weak entity coverage, poor internal links, or no clear next step.
MIRENA is built to solve those problems earlier in the workflow.
The MIRENA Workflow at a Glance
The easiest way to use MIRENA is to move through the workflow in order.
Start with source context. Then add evidence. Then choose the workflow. Then request the right output. Then review the result before moving to the next stage.
The full path is:
- Source context
- Evidence and files
- Workflow choice
- Input preparation
- Output request
- Output review
- Next stage handoff
- Internal link review
- Schema notes
- Final QA
Each output should have a job.
A topical map helps you decide which pages should exist. A content brief helps a writer build the right page. A rewrite improves an existing page around structure, entity placement, search intent, internal links, and user flow.
For the full sequence, use the MIRENA workflow page. It shows how source context moves into intake, topical mapping, content briefs, drafts, rewrites, internal links, and the publish pack.
Add the Strongest Evidence You Have
Source context comes first. After that, add the strongest evidence you have for the project.
Useful evidence can include:
- Google Search Console page exports
- Google Search Console query exports
- Google Analytics landing page reports
- Google Analytics engagement reports
- Semrush keyword exports
- Semrush page exports
- Ahrefs top page exports
- Ahrefs backlink exports
- Ahrefs internal link exports
- Screaming Frog crawls
- heatmap exports
- scroll depth notes
- click tracking notes
- session recording notes
- form data
- internal site search logs
- CRM lead quality notes
- previous MIRENA outputs
- old briefs
- old topical maps
- old rewrite plans
- internal link maps
- schema notes
This evidence helps MIRENA understand what the site already has, what users already do, which pages have search demand, where links need support, which pages need rewriting, and which topics should not become new pages.
Source context is the base.
Evidence makes the output sharper.
Build a Local Source Context File
A local source context file lets you restart MIRENA work in a future session without losing the project state.
Create a plain .txt file on your computer.
Name it:
text
MIRENA_SEMANTEC_MASTER_SOURCE_CONTEXT.txtUse it to store:
- site context
- product context
- audience context
- allowed topics
- excluded topics
- existing page inventory
- internal link targets
- search and analytics files used
- completed MIRENA outputs
- page queue
- drafting rules
- link rules
- schema rules
- open tasks
When you begin a new session, upload that file first. Then upload any newer sitemap, GSC, GA4, Semrush, Ahrefs, crawl, or user behavior exports.
This makes MIRENA work portable across sessions.
Choose the Workflow After Source Context
Once source context is clear, choose the result you need.
MIRENA works best when the task has one main output.
The three main workflows are:
- Topical Mapping + Planning
- Content Briefing
- Drafting + Rewriting
Each workflow uses different inputs and returns a different type of output.
Do not choose the workflow before source context is defined. The context sets the boundary of the task.
Use the MIRENA use cases page when you need to pick the workflow that matches the problem.
Use Topical Mapping + Planning When You Need Structure
Choose topical mapping when your source context shows that the site needs a clearer structure.
This workflow fits projects that need:
- a new site plan
- a cluster plan
- a page inventory
- a sitemap review
- a publishing sequence
- page role decisions
- page vs section decisions
- internal link direction
- overlap cleanup
The topical mapping workflow turns raw inputs into a processed structure. It can help define page roles, cluster hierarchy, search intent, publishing order, and internal link routes.
Use the Topical Maps + Planning workflow when the next job is turning source context, a sitemap, keyword data, or a topic list into a governed page plan.
Use Content Briefing When You Need Writer Instructions
Choose content briefing when the source context and page target are clear, but the writer needs structured instructions.
A MIRENA content brief should define:
- primary entity
- supporting entities
- search intent
- page purpose
- heading flow
- section requirements
- snippet blocks
- FAQ targets
- internal link targets
- anchor text guidance
This helps close the gap between strategy and writing. The writer should not have to guess the page purpose, entity set, link path, or SERP format.
Use the Content Briefs workflow when the next step is assigning a page to a writer, editor, or drafting process.
Use Drafting + Rewriting When You Need a Cleaner Page
Choose drafting and rewriting when the source context is defined and you have an approved brief, existing draft, or live page content.
This workflow can help improve:
- opening answers
- page purpose
- entity placement
- section order
- internal links
- FAQ quality
- table structure
- transitions
- SERP formatting
- rewrite notes
This workflow is useful when a page exists but does not hold together.
Use the Drafting + Rewriting workflow when you need to improve a draft, refresh an old page, or reshape a live URL.
Prepare Inputs After Source Context
MIRENA can start from simple inputs, but stronger inputs produce stronger outputs.
A thin request may still produce something useful, but it will rely on assumptions. A stronger request gives MIRENA more context about the site, audience, offer, page type, and goal.
The detailed checklist belongs in the MIRENA input documentation. This page gives you the starting path.
Input 1: Source Context
Source context is always first.
It tells MIRENA what the site is, who it serves, what it sells, and which topics are allowed.
A good source context can include:
- site name
- product or service
- audience
- region
- core outcomes
- offer
- exclusions
- current sitemap
- target workflow
- tone rules
- link rules
- trust notes
- compliance notes
Use source context for every MIRENA workflow.
That includes topical maps, content briefs, rewrites, internal link plans, schema notes, and output reviews.
Input 2: Seed Topic
A seed topic is the starting concept.
Good seed topics are specific enough to give the project direction.
Useful seed topics might include:
- topical map generator
- SEO content brief
- semantic internal linking
- entity salience
- content refresh workflow
- SaaS comparison page structure
- local service page structure
Use a seed topic when you want MIRENA to build a new map, cluster, brief, or outline from scratch.
A seed topic works best when paired with source context.
“Content brief” is broad. “Content brief workflow for an SEO agency serving SaaS clients” gives MIRENA a clearer direction.
Input 3: Keyword Export
A keyword export helps MIRENA see demand and query variation.
Use keyword exports when you need:
- topical map planning
- query grouping
- page vs section decisions
- content brief targets
- FAQ targets
- SERP feature targets
- publishing priority
A keyword export should not be treated as a page plan by itself.
MIRENA can use keyword data as one input, then apply intent, entities, page roles, and internal link structure.
This is useful when moving from keyword research into the topical mapping workflow.
Input 4: Sitemap
A sitemap helps MIRENA understand the current site structure.
Use a sitemap when you need to find:
- missing pages
- overlapping pages
- weak hubs
- orphan risks
- unclear page roles
- poor internal route logic
- content clusters that need cleanup
A sitemap works well for content refresh, site restructure, topical map audits, and internal link planning.
For a sitemap task, tell MIRENA if you want expansion, cleanup, consolidation, or a fresh processed map.
Input 5: URL List
A URL list helps when you want MIRENA to review a smaller set of pages.
Use this input when you want to analyze:
- one cluster
- one hub and its spokes
- a set of comparison pages
- a group of weak blog posts
- pages that compete with each other
- pages that need internal links
A URL list is often better than a full sitemap when the task is narrow.
If you only want to audit the content brief cluster, send that page set rather than the full site.
Input 6: Existing Draft
An existing draft is useful for the drafting and rewriting workflow.
Give MIRENA the draft when you need help with:
- clearer introduction
- stronger answer block
- improved section order
- entity reinforcement
- better table structure
- stronger FAQ blocks
- internal link placement
- rewrite notes
For rewrite work, include the source context, target page purpose, main query, and internal link targets. Without those, the rewrite may improve the prose but miss the page job.
Use the Drafting + Rewriting workflow when your input is a draft, live page, or approved brief.
Input 7: Audience Notes
Audience notes help MIRENA choose the right framing.
Useful audience labels include:
- SEO consultant
- agency lead
- in-house SEO manager
- founder
- editor
- writer
- publisher
- SaaS marketer
- local service operator
This affects framing, CTAs, link routing, and level of explanation.
A page for an SEO consultant may need audit language. A page for a writer may need clearer handoff instructions. A page for a founder may need more product and workflow framing.
Input 8: Region
Use region when the workflow includes local SEO, market terms, legal constraints, or regional language.
Useful region inputs include:
- Ireland
- United Kingdom
- United States
- Dublin
- multi location service area
MIRENA can use regional context for page structure, local modifiers, and internal link planning.
Regional context is important for local service pages, multi location sites, and market specific product pages.
Input 9: Product or Service Notes
Product or service notes help connect the map or brief to the commercial route.
Include details such as:
- what the product does
- who it helps
- main use cases
- pricing model
- proof points
- limitations
- competitors
- conversion goal
This helps MIRENA keep the output tied to the offer.
A topical map for a SaaS product should not look like a generic blog map. It should support product pages, use cases, comparison pages, docs, proof pages, and pricing.
Input 10: Search and Analytics Data
Search and analytics files give MIRENA evidence from the live site.
Add these files when you have them:
- Google Search Console pages export
- Google Search Console queries export
- Google Analytics landing page report
- Google Analytics engagement report
- Semrush organic keyword export
- Semrush organic page export
- Ahrefs top pages
- Ahrefs backlink export
- Ahrefs internal link export
- Screaming Frog crawl
- heatmap data
- scroll tracking data
- click tracking data
- internal site search data
- CRM or lead quality notes
- previous MIRENA outputs
This data helps MIRENA identify which pages already have demand, which pages need support, where users stop, which links deserve more weight, and which topics should be refreshed before new pages are created.
Source context still comes first. Search and analytics data comes after it.
Input 11: Internal Link Targets
Internal links should not be added at the end as a cleanup step.
Give MIRENA the pages you want to strengthen. These may include hubs, product pages, pricing pages, use case pages, docs, templates, examples, or proof pages.
For Semantec SEO, many pages should route readers toward outcome hubs such as Topical Maps + Planning, Content Briefs, and Drafting + Rewriting.
When you send internal link targets, MIRENA can suggest contextual anchor text instead of placing links in disconnected blocks.
MIRENA Modules You Can Run by Name
Many Semantec SEO page titles also work as MIRENA module names.
You do not need to type the full page title every time. Use the shortest clear action.
For example:
text
Run Content Brief for this page.text
Run Entity Map for this cluster.text
Run Behavioral Topical Map on this sitemap.text
Run Query Granularity on this keyword list.text
Run Rewrite for Internal Links on this draft.text
Run Anchor Text by Intent on this link plan.Use the module name, add the source context, and state the output you want.
A good activation pattern is:
text
Run [module or action] on [asset].
Use the source context first.
Return [output].
Route it into [next workflow stage].The module name can be short as long as the task is clear.
Source Context and Setup Modules
Use these modules before maps, briefs, rewrites, and link plans.
Source Context
Prompt:
text
Build a Source Context file for this project.Use this when the project needs a stable base before any map, brief, rewrite, or link plan.
Input Check
Prompt:
text
Run Input Check for this project.Use this to identify which files, notes, URLs, and exports should be added before the workflow starts.
Workflow Route
Prompt:
text
Run Workflow Route for this project.Use this when you need MIRENA to choose the best path from source context to plan, brief, draft, links, schema notes, and QA.
Output Review
Prompt:
text
Run Output Review on this result.Use this when you need to understand what an output means, how to review it, and what stage comes next.
Source Context Guard
Prompt:
text
Run Source Context Guard on these page ideas.Use this to score page ideas for entity fit, buyer fit, workflow fit, differentiation fit, and link fit.
Local Context File
Prompt:
text
Build a Local Context File from this session.Use this to preserve completed pages, page queue, rules, internal links, and open tasks.
Topical Mapping and Planning Modules
Use these modules when the site needs structure, page roles, publishing order, or cluster cleanup.
Topical Map
Prompt:
text
Run Topical Map on this source context.Use this to define the main map structure for a project.
Processed Topical Map
Prompt:
text
Run Processed Topical Map on this topic list.Use this to turn raw topics into a page structure with roles, intent, and internal links.
Processed Map Build
Prompt:
text
Build a Processed Map from this sitemap and keyword export.Use this when the project has both current site data and query data.
Query Granularity
Prompt:
text
Run Query Granularity on these topics.Use this to decide which topics need standalone URLs and which belong as sections.
Topical Authority
Prompt:
text
Run Topical Authority on this cluster.Use this to plan authority without creating extra pages.
Topical Map Template
Prompt:
text
Format this as a Topical Map Template.Use this when the output needs a repeatable structure.
Topical Map Example
Prompt:
text
Create a Topical Map Example from this raw cluster.Use this when the user needs to see the raw input and processed output.
Source Context for Topical Maps
Prompt:
text
Run Source Context on this topical map.Use this to keep the map aligned with the site scope.
Cluster Roles
Prompt:
text
Run Cluster Roles on this page inventory.Use this to label pages as hub, spoke, bridge, support, comparison, conversion, docs, or proof.
Cannibalization Prevention
Prompt:
text
Run Cannibalization Check on this cluster.Use this to flag pages that compete with each other.
Content Architecture
Prompt:
text
Build Content Architecture from this source context.Use this to create a clean structure across hubs, spokes, support pages, and conversion pages.
Topic Governance
Prompt:
text
Run Topic Governance on this page queue.Use this to create rules for adding, blocking, merging, and refreshing pages.
Map Approval
Prompt:
text
Run Map Approval on this topical map.Use this to create a review checklist before briefs begin.
Page vs Section
Prompt:
text
Run Page vs Section on this cluster.Use this to decide which topics need URLs and which belong inside existing pages.
Query Buckets
Prompt:
text
Run Query Buckets on this keyword export.Use this to group query data into better page plans.
SERP URL Clustering
Prompt:
text
Run SERP URL Clustering on this query set.Use this to use ranking patterns for page grouping.
Keyword to Topic Map
Prompt:
text
Turn this keyword export into a Topic Map.Use this to create a processed page inventory from keyword data.
Multi Audience Map
Prompt:
text
Run Multi Audience Map on this site.Use this to keep a site from drifting across audience segments.
Multi Product Map
Prompt:
text
Run Multi Product Map on this site.Use this to structure pages across several products without overlap.
Site Merger Map
Prompt:
text
Run Site Merger Map on these inventories.Use this to combine page inventories without topic collisions.
Legacy Site Map
Prompt:
text
Turn this legacy site into a Processed Map.Use this to rebuild an old structure into a cleaner topical map.
Site Growth Model
Prompt:
text
Run Site Growth Model on this cluster.Use this to plan expansion without losing structure.
Templates and Examples Plan
Prompt:
text
Run Templates and Examples Plan on this cluster.Use this to identify reusable assets the cluster needs.
Docs Cluster Plan
Prompt:
text
Run Docs Cluster Plan for this product.Use this to build documentation that fits the product workflow.
Compare Cluster Plan
Prompt:
text
Run Compare Cluster Plan for this product.Use this to structure comparison pages so they support the product route.
Use Case Architecture
Prompt:
text
Run Use Case Architecture on this site.Use this to build the structure around jobs users need done.
Navigation Cluster Plan
Prompt:
text
Run Navigation Cluster Plan on this site.Use this to build clear paths through the site.
Authority Hub Plan
Prompt:
text
Run Authority Hub Plan on this topic.Use this to define the hub pages that support a topic.
Support Cluster Design
Prompt:
text
Run Support Cluster Design on this hub.Use this to identify support pages that strengthen the hub.
Commercial Spine
Prompt:
text
Run Commercial Spine on this map.Use this to connect topical authority to conversion pages.
Semantic Site Architecture
Prompt:
text
Run Semantic Site Architecture on this sitemap.Use this to build clusters that keep their shape.
Topic Coverage Score
Prompt:
text
Run Topic Coverage Score on this cluster.Use this to grade a cluster for strength, gaps, and overreach.
Intent to Page Mapping
Prompt:
text
Run Intent to Page Mapping on this query set.Use this to match search intent to the correct page type.
Cluster Health Check
Prompt:
text
Run Cluster Health Check on this page set.Use this to find weak points before the cluster breaks.
Topic Dependency Mapping
Prompt:
text
Run Topic Dependencies on this map.Use this to set publishing order.
Map Refresh
Prompt:
text
Run Map Refresh on this topical map.Use this to update a topical map without breaking the site.
Topical Map Audit
Prompt:
text
Run Topical Map Audit on this sitemap.Use this to find gaps, overlap, drift, missing routes, and cleanup actions.
Behavioral Topical Map Modules
Use these modules when the page needs user movement, friction, trust, satisfaction, or next step routing.
Behavioral Topical Map
Prompt:
text
Run Behavioral Topical Map on this page inventory.Use this to add user state, friction, trust needs, next paths, and fallback routes.
User Journey Map
Prompt:
text
Run User Journey Map on this cluster.Use this to map pages around how users move through the site.
Use this to build link paths around user progress.
User Gain
Prompt:
text
Run User Gain on this page.Use this to improve usefulness before adding more coverage.
Satisfaction Signals
Prompt:
text
Run Satisfaction Signals on this topical map.Use this to define behavior signals that should trigger refresh work.
Trust Paths
Prompt:
text
Run Trust Paths on this map.Use this to add proof routes, comparison support, and confidence paths.
Passage Order
Prompt:
text
Run Passage Order on this draft.Use this to reorder a page around the reader’s path.
Feedback Loops
Prompt:
text
Run Feedback Loops on this map.Use this to define how behavior data should update the map.
Semantic Completeness vs User Usefulness
Prompt:
text
Run Usefulness Check on this page.Use this to balance coverage with reader value.
Content Brief Modules
Use these modules when the output should become writer instructions.
Content Brief
Prompt:
text
Run Content Brief for this page.Use this to define the brief requirements for a page.
Entity Brief
Prompt:
text
Run Entity Brief for this page.Use this to create a brief around the primary entity, supporting entities, attributes, and links.
Intent Brief
Prompt:
text
Run Intent Brief for this page.Use this to build the brief around search intent and page purpose.
SERP Brief
Prompt:
text
Run SERP Brief for this page.Use this to add snippet, PAA, table, FAQ, and answer block instructions.
Internal Link Brief
Prompt:
text
Run Internal Link Brief for this page.Use this to add source pages, target pages, anchor direction, and link purpose to the brief.
Brief Template
Prompt:
text
Format this as a Brief Template.Use this to prepare a writer handoff.
Agency Brief
Prompt:
text
Run Agency Brief for this page.Use this to standardize a brief for client delivery.
In House Brief
Prompt:
text
Run In House Brief for this page.Use this to align a brief with product, docs, and internal review.
Writer Brief
Prompt:
text
Run Writer Brief for this page.Use this to make the brief easier to draft from.
Editor Handoff
Prompt:
text
Run Editor Handoff for this brief.Use this to create an editor review path.
Writer Handoff
Prompt:
text
Run Writer Handoff for this brief.Use this to prepare the brief for writing.
FAQ Brief
Prompt:
text
Run FAQ Brief for this page.Use this to add useful question targets with answer intent.
Table Brief
Prompt:
text
Run Table Brief for this page.Use this to plan tables that support the page.
Intro Brief
Prompt:
text
Run Intro Brief for this page.Use this to define what the opening answer must do.
Section Order Brief
Prompt:
text
Run Section Order on this brief.Use this to arrange the brief in the strongest reading order.
Brief Depth
Prompt:
text
Run Brief Depth on this page.Use this to decide how detailed the brief should be.
Information Gain Brief
Prompt:
text
Run Information Gain Brief for this page.Use this to plan a page around differentiation.
Entity Page Brief
Prompt:
text
Run Entity Page Brief for this page.Use this to create instructions for an entity focused page.
SERP Feature Brief
Prompt:
text
Run SERP Feature Brief for this page.Use this to plan snippet, PAA, FAQ, and table coverage.
Comparison Brief
Prompt:
text
Run Comparison Brief for this page.Use this to scope proof, tables, differences, and CTAs.
Category Brief
Prompt:
text
Run Category Brief for this page.Use this to define scope, links, and page role.
Refresh Brief
Prompt:
text
Run Refresh Brief for this page.Use this to create a content refresh brief that fixes the page.
Brief Revision
Prompt:
text
Run Brief Revision on this brief.Use this to repair weak brief instructions before writing.
Brief Approval
Prompt:
text
Run Brief Approval on this brief.Use this to create an approval checklist before drafting.
Brief Scoring
Prompt:
text
Run Brief Score on this brief.Use this to grade the brief before writing starts.
Drafting and Rewriting Modules
Use these modules when a page already exists or a draft needs repair.
Pre Publish Check
Prompt:
text
Run Pre Publish Check on this draft.Use this to inspect a draft before publishing.
Support Entity Placement
Prompt:
text
Fix Support Entity Placement in this draft.Use this to improve where supporting entities appear.
Section Order
Prompt:
text
Fix Section Order in this draft.Use this to reorder the draft for stronger flow.
Page Purpose
Prompt:
text
Fix Page Purpose in this draft.Use this to clarify what the page is meant to do.
Proof Sections
Prompt:
text
Add Proof Sections to this draft.Use this to add trust, proof, and support blocks.
Weak FAQs
Prompt:
text
Fix Weak FAQs on this page.Use this to improve the questions, answers, and page flow.
Weak Tables
Prompt:
text
Fix Weak Tables on this page.Use this to repair tables, comparisons, and summaries.
No Next Step
Prompt:
text
Fix No Next Step on this page.Use this to add the right next action for the reader.
Buried Answers
Prompt:
text
Fix Buried Answers in this draft.Use this to move the main answer where the reader needs it.
Weak Transitions
Prompt:
text
Fix Weak Transitions in this draft.Use this to improve the connections between sections.
Repetition
Prompt:
text
Fix Repetition in this draft.Use this to reduce repeated ideas, phrases, and structures.
Overlapping Pages
Prompt:
text
Fix Overlapping Pages in this cluster.Use this to decide what to merge, split, rewrite, or protect.
Thin Support Sections
Prompt:
text
Fix Thin Support Sections in this draft.Use this to strengthen weak support content.
Mixed Intent
Prompt:
text
Fix Mixed Intent in this page.Use this to separate conflicting search intents.
Weak Intros
Prompt:
text
Fix Weak Intro on this page.Use this to rewrite the opening for page purpose and answer clarity.
Use Case Rewrite
Prompt:
text
Run Use Case Rewrite on this page.Use this to improve intent, product fit, and conversion path.
Comparison Rewrite
Prompt:
text
Run Comparison Rewrite on this page.Use this to repair proof, tables, CTAs, and intent fit.
Category Rewrite
Prompt:
text
Run Category Rewrite on this page.Use this to improve structure, links, and conversion route.
Old Post Refresh
Prompt:
text
Run Old Post Refresh on this page.Use this to update aging content with stronger structure.
Conversion Path Rewrite
Prompt:
text
Run Conversion Path Rewrite on this page.Use this to make the next step clearer.
PAA Rewrite
Prompt:
text
Run PAA Rewrite on this page.Use this to reshape the page for People Also Ask coverage.
Snippet Rewrite
Prompt:
text
Run Snippet Rewrite on this section.Use this to fix answers, lists, tables, and FAQs.
Internal Link Rewrite
Prompt:
text
Run Internal Link Rewrite on this page.Use this to repair weak SEO paths in the content.
Structure Rewrite
Prompt:
text
Run Structure Rewrite on this draft.Use this to turn weak content into a clear page.
Supporting Entity Rewrite
Prompt:
text
Run Supporting Entity Rewrite on this page.Use this to strengthen the page’s semantic support.
Topic Fit Rewrite
Prompt:
text
Run Topic Fit Rewrite on this page.Use this to keep the page on the right topic.
Clarity Rewrite
Prompt:
text
Run Clarity Rewrite on this page.Use this to make the page easier to understand.
Rewrite Brief
Prompt:
text
Run Rewrite Brief for this page.Use this to plan the rewrite before editing the page.
Rewrite Score
Prompt:
text
Run Rewrite Score on this page.Use this to grade a page before rewriting.
Rewrite Priority
Prompt:
text
Run Rewrite Priority on this page set.Use this to pick the right pages to fix first.
Definition Rewrite
Prompt:
text
Run Definition Rewrite on this page.Use this to fix a weak definition page.
Process Rewrite
Prompt:
text
Run Process Rewrite on this page.Use this to improve a step based page.
FAQ Rewrite
Prompt:
text
Run FAQ Rewrite on this page.Use this to improve weak questions, answers, and page flow.
Table Rewrite
Prompt:
text
Run Table Rewrite on this page.Use this to repair tables, comparisons, and summaries.
Heading Rewrite
Prompt:
text
Run Heading Rewrite on this page.Use this to improve page structure and section flow.
Section Rewrite
Prompt:
text
Run Section Rewrite on this draft.Use this to fix weak page blocks.
Intro Rewrite
Prompt:
text
Run Intro Rewrite on this page.Use this to clarify the page opening.
Entity SEO Modules
Use these modules when the page needs stronger entity structure, salience, or semantic relationships.
Entity Definition
Prompt:
text
Run Entity Definition on this page.Use this to define the main entity set.
Entity Map
Prompt:
text
Run Entity Map for this cluster.Use this to create the entity structure for a page or cluster.
Entity Attributes
Prompt:
text
Run Entity Attributes for this entity.Use this to list attributes each important entity needs.
Entity Salience
Prompt:
text
Run Entity Salience on this draft.Use this to improve the prominence of key entities.
Entity Support Pages
Prompt:
text
Run Entity Support Pages for this cluster.Use this to identify support pages the cluster needs.
Entity Consistency
Prompt:
text
Run Entity Consistency across this page set.Use this to check that entities stay aligned across pages.
Entity Conflict Resolution
Prompt:
text
Run Entity Conflict Resolution on this cluster.Use this to fix mixed signals, attributes, and support pages.
Entity Gap Audit
Prompt:
text
Run Entity Gap Audit on this page set.Use this to find missing entities in a cluster.
Entity Cluster Design
Prompt:
text
Run Entity Cluster Design for this topic.Use this to build a cleaner structure around entities.
Entity Led Internal Links
Prompt:
text
Run Entity Links on this cluster.Use this to place links around clear concepts.
Entity Led Sections
Prompt:
text
Run Entity Sections on this page.Use this to structure page sections around core concepts.
Entity Rich Intro
Prompt:
text
Run Entity Intro on this page.Use this to rewrite the opening with clearer meaning and stronger signals.
Entity Context Windows
Prompt:
text
Run Context Windows for these entity mentions.Use this to improve the local text around entity mentions.
Entity Disambiguation
Prompt:
text
Run Entity Disambiguation on this page.Use this to clarify meaning, context, and page intent.
Support Entity Selection
Prompt:
text
Run Support Entity Selection for this page.Use this to choose the right supporting concepts.
Main Entity Selection
Prompt:
text
Run Main Entity Selection for this page.Use this to choose the right primary entity.
Entity Density vs Clarity
Prompt:
text
Run Entity Clarity on this draft.Use this to add support without crowding the page.
Entity Proximity
Prompt:
text
Run Entity Proximity on this section.Use this to move supporting terms closer to key entities.
Entity Distance
Prompt:
text
Run Entity Distance on this page.Use this to review how placement shapes relevance and clarity.
Entity Hierarchy
Prompt:
text
Run Entity Hierarchy for this page.Use this to structure primary, secondary, and supporting entities.
Entity Co Occurrence
Prompt:
text
Run Entity Co Occurrence on this draft.Use this to improve how related concepts appear together.
Entity Relationships
Prompt:
text
Run Entity Relationships for this cluster.Use this to map connections between concepts.
Contextual Entity Integration
Prompt:
text
Run Entity Integration on this draft.Use this to place entities where they strengthen the page.
Entity Markup
Prompt:
text
Run Entity Markup cues for this approved draft.Use this to define structured data support for important entities.
Semantic SEO Modules
Use these modules when a page needs stronger topical fit, meaning, coverage, or search intent alignment.
Semantic SEO
Prompt:
text
Run Semantic SEO on this page.Use this to define the semantic frame.
Semantic Coverage
Prompt:
text
Run Semantic Coverage on this page.Use this to find missing supporting concepts.
Passage Retrieval
Prompt:
text
Run Passage Retrieval on this page.Use this to make each section easier for search systems to understand.
Semantic Relevance
Prompt:
text
Run Semantic Relevance on this page.Use this to test if a page fits its topic.
Semantic Clustering
Prompt:
text
Run Semantic Clustering on this keyword set.Use this to build cleaner topic groups.
Intent Coverage
Prompt:
text
Run Intent Coverage on this brief.Use this to check if the page fits the query.
Topic Completion
Prompt:
text
Run Topic Completion on this page.Use this to find missing coverage that belongs on the page.
Query Rewrite Patterns
Prompt:
text
Run Query Rewrite Patterns on this query set.Use this to identify query variations a page should support.
Section Relevance
Prompt:
text
Run Section Relevance on this draft.Use this to check if each page block stays on track.
Search Journey
Prompt:
text
Run Search Journey on this cluster.Use this to build the page around the reader path.
Context vs Coverage
Prompt:
text
Run Context vs Coverage on this page.Use this to remove content that adds length without fit.
Entity First SEO
Prompt:
text
Run Entity First SEO on this page.Use this to structure content around entities before keywords.
Topic vs Query
Prompt:
text
Run Topic vs Query on this page.Use this to decide how a page should own the topic.
Search Intent Layers
Prompt:
text
Run Intent Layers on this query.Use this to map primary and secondary intent.
Semantic Search
Prompt:
text
Run Semantic Search Check on this page.Use this to update the page for meaning based retrieval.
Meaning First Structure
Prompt:
text
Run Meaning First Structure on this cluster.Use this to build the cluster around clear relationships.
Supporting Concepts
Prompt:
text
Run Supporting Concepts on this page.Use this to add concepts that improve topic coverage.
Content Depth vs Topic Fit
Prompt:
text
Run Depth vs Fit on this draft.Use this to remove depth that does not support the page job.
Internal Linking Modules
Use these modules when the project needs link routes, anchor text, crawl paths, or page support.
Semantic Internal Linking
Prompt:
text
Run Semantic Internal Linking on this cluster.Use this to build links that reinforce meaning.
Internal Link Audit
Prompt:
text
Run Internal Link Audit on this cluster.Use this to find structural weaknesses before they hurt the cluster.
Anchor Text by Intent
Prompt:
text
Run Anchor Text by Intent on this link plan.Use this to choose anchors that match what the reader needs next.
Broken Topic Paths
Prompt:
text
Fix Broken Topic Paths in this cluster.Use this to repair weak internal routes.
Internal Link Prioritization
Prompt:
text
Run Link Prioritization on this page set.Use this to choose the right links first.
Refresh Links
Prompt:
text
Run Refresh Links on this page.Use this to fix link drift during content updates.
Anchor Variation
Prompt:
text
Run Anchor Variation on this link plan.Use this to create smarter internal link anchors.
Sitewide vs Contextual Links
Prompt:
text
Run Sitewide vs Contextual Links on this plan.Use this to decide which links belong in copy.
Link Depth
Prompt:
text
Run Link Depth on this site section.Use this to review internal link structure.
Deep Link Distribution
Prompt:
text
Run Deep Link Distribution on this cluster.Use this to build stronger internal link paths.
Link Routing by Cluster Role
Prompt:
text
Run Link Routing by Role on this map.Use this to connect hubs, spokes, supports, and conversion pages.
Adjacency Matrix
Prompt:
text
Build an Adjacency Matrix for this cluster.Use this to map page relationships.
Link Governance
Prompt:
text
Run Link Governance on this site section.Use this to create rules, roles, and review cycles.
Orphan Page Recovery
Prompt:
text
Run Orphan Recovery on these pages.Use this to find contextual links into unsupported pages.
Hub and Spoke Linking
Prompt:
text
Run Hub and Spoke Linking on this cluster.Use this to build clearer topic clusters.
Behavioral Internal Linking
Prompt:
text
Run Behavioral Internal Linking on this page path.Use this to build link paths around user progress.
Information Gain Modules
Use these modules when the page needs stronger differentiation, missing relationships, proof, or better source material.
Information Gain
Prompt:
text
Run Information Gain on this page.Use this to define the differentiation target.
SERP Redundancy
Prompt:
text
Run SERP Redundancy on these competitors.Use this to identify repeated ideas before briefing.
Entity Attribute Gaps
Prompt:
text
Run Attribute Gaps on this entity set.Use this to find missing entity relationships.
Competitor Overlap
Prompt:
text
Run Competitor Overlap on this SERP set.Use this to spot repeated coverage before briefing.
Answer Gap
Prompt:
text
Run Answer Gap on this query group.Use this to find missing answers before drafting.
Query Expansion Gaps
Prompt:
text
Run Query Expansion Gaps on this topic.Use this to find missing search paths.
Novel Subtopics
Prompt:
text
Run Novel Subtopics on this cluster.Use this to find coverage gaps that improve information gain.
SERP Consensus
Prompt:
text
Run SERP Consensus on this query.Use this to separate common SERP coverage from unique angles.
Information Gain Score
Prompt:
text
Run Information Gain Score on this page.Use this to grade a page for useful differentiation.
Novelty vs Redundancy
Prompt:
text
Run Novelty vs Redundancy on this draft.Use this to remove repeated SERP patterns.
Query Gap
Prompt:
text
Run Query Gap on this cluster.Use this to find missing query paths.
Content Gap
Prompt:
text
Run Content Gap on this page set.Use this to identify missing coverage across a page or cluster.
Topical Coverage Gaps
Prompt:
text
Run Topical Coverage Gaps on this cluster.Use this to find what the content still misses.
Use this to improve both usefulness and differentiation.
SERP Feature and Formatting Modules
Use these modules when the page needs answer blocks, snippets, tables, PAA, or format repair.
Featured Snippets
Prompt:
text
Run Featured Snippet Formatting on this section.Use this to format the page for fast answers.
People Also Ask
Prompt:
text
Run PAA Mapping on this topic.Use this to build better question paths.
Comparison Tables
Prompt:
text
Run Comparison Table on this page.Use this to structure side by side content.
FAQ Blocks
Prompt:
text
Run FAQ Blocks for this page.Use this to build Q&A sections that support the page.
Intent Based Formatting
Prompt:
text
Run Intent Formatting on this page.Use this to match content format to search intent.
Feature Ready Brief
Prompt:
text
Run Feature Ready Brief for this page.Use this to build a brief for search features.
Summary Box
Prompt:
text
Write a Summary Box for this page.Use this to create clear search ready summary blocks.
Rich Result Eligibility
Prompt:
text
Run Rich Result Check on this page.Use this to check which result types the page can support.
How To Intro
Prompt:
text
Write a How To Intro for this page.Use this to write openings that answer fast and support search.
Knowledge Panel Support
Prompt:
text
Run Knowledge Panel Support on this entity.Use this to build clearer entity signals.
Best Format
Prompt:
text
Run Best Format for this query.Use this to choose the right page format.
Table Design
Prompt:
text
Run Table Design for this section.Use this to build tables that search systems and users can read.
SERP Feature Priority
Prompt:
text
Run SERP Feature Priority on this page.Use this to choose which search features to target first.
Snippet Loss
Prompt:
text
Run Snippet Loss on this page.Use this to find why a page lost snippet visibility.
FAQ vs PAA
Prompt:
text
Run FAQ vs PAA for this query group.Use this to decide when to use FAQ blocks or PAA coverage.
PAA Question Map
Prompt:
text
Build a PAA Question Map for this topic.Use this to build better follow up question paths.
Section Snippet Targeting
Prompt:
text
Run Section Snippet Targeting on this draft.Use this to make sections snippet ready.
Answer Blocks
Prompt:
text
Run Answer Blocks on this page.Use this to write clear opening answers.
Process Formatting
Prompt:
text
Run Process Formatting on this page.Use this to build clear step based pages.
Comparison Formatting
Prompt:
text
Run Comparison Formatting on this page.Use this to structure side by side content.
Definition Formatting
Prompt:
text
Run Definition Formatting on this page.Use this to write clear answers search can pull.
Table Snippets
Prompt:
text
Run Table Snippets on this page.Use this to format comparison answers.
Paragraph Snippets
Prompt:
text
Run Paragraph Snippets on this section.Use this to format direct answers.
List Snippets
Prompt:
text
Run List Snippets on this page.Use this to format pages for search.
How To Formatting
Prompt:
text
Run How To Formatting on this page.Use this to structure process content for search.
Knowledge Panels
Prompt:
text
Run Knowledge Panel Support for this entity.Use this to build entity summary support.
Schema Modules
Use these modules when a final approved draft needs structured data notes.
Schema notes should follow approval. Do not finalize schema before the page structure and visible content are locked.
Schema Cues
Prompt:
text
Run Schema Cues for this approved draft.Use this to list schema cues for a page.
JSON LD
Prompt:
text
Prepare JSON LD notes for this approved draft.Use this to create a clean structured data plan.
FAQ Schema
Prompt:
text
Run FAQ Schema Check on this page.Use this to check if visible FAQs qualify for markup.
HowTo Schema
Prompt:
text
Run HowTo Schema Check on this page.Use this to check if process content qualifies.
Product Schema
Prompt:
text
Run Product Schema Check for this product page.Use this to review product page structured data.
Entity Markup
Prompt:
text
Run Entity Markup cues for this page.Use this to support important entities with structured data.
Article Schema
Prompt:
text
Run Article Schema cues for this page.Use this to plan structured data for editorial pages.
sameAs and Entity Identity
Prompt:
text
Run Entity Identity on this schema plan.Use this to align entity references.
Organization Schema
Prompt:
text
Run Organization Schema cues for this site.Use this to support brand identity.
Entity Identity Across Pages
Prompt:
text
Run Entity Identity across this page set.Use this to keep schema and SEO signals aligned.
Use Case Page Schema
Prompt:
text
Run Use Case Schema cues for this page.Use this to plan schema for a use case page.
Comparison Page Schema
Prompt:
text
Run Comparison Schema cues for this page.Use this to plan markup for a comparison page.
Category Page Schema
Prompt:
text
Run Category Schema cues for this page.Use this to fit structured data to the page role.
Schema Priority
Prompt:
text
Run Schema Priority for this page.Use this to decide which schema to plan first.
Rich Results Test
Review Snippet Rules
Prompt:
text
Run Review Snippet Rules for this page.Use this to check if review markup is appropriate.
SoftwareApplication Schema
Prompt:
text
Run SoftwareApplication Schema cues for this product.Use this to plan product software markup.
Service Schema
Prompt:
text
Run Service Schema cues for this page.Use this to plan service page markup.
Person Schema
Prompt:
text
Run Person Schema cues for this profile.Use this to support profile page identity.
WebPage Schema
Prompt:
text
Run WebPage Schema cues for this page.Use this to define the page identity.
Website Schema
Prompt:
text
Run Website Schema cues for this site.Use this to support site identity.
Breadcrumb Schema
Prompt:
text
Run Breadcrumb Schema for this page.Use this to support site structure.
Use Case Modules
Use these modules when the project belongs to a user type, business model, or project type.
Agency Workflow
Prompt:
text
Run Agency Workflow for this project.Use this to shape the workflow for client delivery.
In House Workflow
Prompt:
text
Run In House Workflow for this project.Use this to adapt the workflow for internal control.
Editorial Lead Workflow
Prompt:
text
Run Editorial Lead Workflow for this brief.Use this to improve briefs, review, and page flow.
Content Design Workflow
Prompt:
text
Run Content Design Workflow for this project.Use this to turn the work into a stronger content system.
Multi Location Workflow
Prompt:
text
Run Multi Location Workflow on this site.Use this to structure local pages across every location.
Local Service Workflow
Prompt:
text
Run Local Service Workflow on this site.Use this to improve service page structure.
Online Store Workflow
Prompt:
text
Run Online Store Workflow on this site.Use this to improve category pages, briefs, and refreshes.
SaaS Workflow
Prompt:
text
Run SaaS Workflow on this site.Use this to connect product, docs, comparison, and content pages.
Publisher Workflow
Prompt:
text
Run Publisher Workflow on this site.Use this to build stronger topic hubs and content workflows.
Consultant Workflow
Prompt:
text
Run Consultant Workflow for this client project.Use this to create briefs, audits, and site plans.
Startup Workflow
Prompt:
text
Run Startup Workflow for this site.Use this to plan, brief, and publish stronger search pages.
Site Restructure Workflow
Prompt:
text
Run Site Restructure on this sitemap.Use this to rebuild a site structure with clarity.
Content Refresh Workflow
Prompt:
text
Run Content Refresh on this page set.Use this to refresh pages with better structure.
Category SEO Workflow
Prompt:
text
Run Category SEO Workflow on this page set.Use this to improve category page structure.
B2B Services Workflow
Prompt:
text
Run B2B Services Workflow on this site.Use this to structure service pages around proof and conversion.
B2B Software Workflow
Prompt:
text
Run B2B Software Workflow on this site.Use this to connect product, comparison, docs, and use cases.
How to Ask for the Right Output
A strong MIRENA request should name the source context, workflow, input type, goal, audience, and output format.
A weak request sounds like this:
text
Make content for my site.A stronger request sounds like this:
text
Use this source context and sitemap to create an internal link plan for the topical mapping cluster. Include source pages, target pages, anchor text, link purpose, and next stage routes into the content brief workflow.The second request gives MIRENA a clear job.
Use this request pattern:
text
Use [source context] and [input] to create [output] for [audience, page, or cluster].
Include [required fields].
Keep the result aligned with [business goal].
Route the output into [next workflow stage].That structure works for topical maps, briefs, rewrites, internal links, and output reviews.
Request Pattern for a Topical Map
Use this request when you need a processed map:
text
Use this source context and keyword list to create a processed topical map. Include clusters, page roles, search intent, page vs section decisions, publishing order, overlap warnings, and internal link targets.This request connects naturally to the Topical Maps + Planning workflow.
It is a good first request when you have source context plus topics, keywords, or a sitemap, but no clear page architecture.
Request Pattern for a Content Brief
Use this request when you need writer instructions:
text
Use this source context and approved page target to create an SEO content brief. Include the primary entity, supporting entities, search intent, page purpose, heading plan, section requirements, snippet block, FAQ targets, internal links, and anchor text guidance.This request should point into the entity led content brief process when entity clarity is the main need.
It should point into the intent led brief process when the main challenge is matching the page to the query.
Request Pattern for a Rewrite
Use this request when you need to improve an existing page:
text
Use this source context and draft to rewrite the page for clearer structure, stronger entity placement, better section order, snippet formatting, FAQ quality, and contextual internal links. Include rewrite notes explaining what changed.This request fits the Drafting + Rewriting workflow.
It works best when you include the source context, draft, main query, page goal, audience, and internal link targets.
Request Pattern for Internal Links
Use this request when you need a link plan:
text
Use this source context and page list to create an internal link plan. Include source URL, target URL, optimized anchor text, link purpose, cluster role, and next stage route.This works well when paired with the semantic internal linking process and the anchor text by intent framework.
MIRENA should place links where the surrounding paragraph supports the target page. Strong links do not sit in a random list. They sit inside the user journey.
Request Pattern for Behavior Data
Use this request when you have heatmaps, scroll data, click data, or session notes:
text
Use this source context and behavior data to find where users stall, which links they miss, which CTAs need repositioning, and which pages need a clearer next step.This request fits behavioral topical mapping, user journey mapping, and internal link repair.
Request Pattern for GSC Data
Use this request when you have Google Search Console exports:
text
Use this source context, GSC pages export, and GSC queries export to find high impression pages, weak click pages, missing snippet opportunities, query mismatch, and internal link support needs.This request is useful when pages have visibility but need stronger page purpose, snippets, or links.
Request Pattern for GA4 Data
Use this request when you have Google Analytics reports:
text
Use this source context and GA4 landing page export to find weak engagement, poor next step behavior, and conversion path gaps. Return a rewrite and internal link priority list.This request is useful when pages attract users but fail to move them forward.
Understand MIRENA Outputs
MIRENA outputs should be treated as work artifacts.
Each output should have a job and a next step.
The main output types include:
- topical map
- content brief
- rewrite plan
- rewritten draft
- internal link plan
- schema notes
- QA checklist
- publishing order
- consolidation notes
- page inventory
- behavior map
- local source context file
A topical map should move into briefs.
A brief should move into drafting or rewriting.
A rewritten draft should move into internal link review and schema notes.
A link plan should move into implementation.
If an output does not tell you what to do next, the request was probably too vague.
You can review the full output layer through the MIRENA output documentation.
Review the Output Before You Use It
Do not publish or hand off a MIRENA output without review.
Review is part of the workflow.
Use this checklist:
- Does the output match the source context?
- Does it support one of the main MIRENA outcomes?
- Does every page or section have a clear role?
- Are the main entities visible early?
- Are supporting entities placed near the right topic?
- Does the output avoid duplicate intent?
- Are internal links placed with useful anchor text?
- Is the next workflow stage clear?
- Is the CTA route aligned with the page purpose?
- Are schema notes held until the page is approved?
- Is the output ready for the next handoff?
This review step helps prevent a common mistake: treating an AI output as finished just because it is structured.
MIRENA should produce work that is easier to review, not work that bypasses review.
Move From Source Context to Plan to Brief to Draft or Rewrite
The strongest MIRENA workflow keeps every output moving.
Source context feeds the plan. The plan feeds the brief. The brief feeds the draft or rewrite. The draft or rewrite feeds link review and schema notes.
That sequence keeps strategy, writing, and publishing connected.
Step 1: Define the Source Context
Start by defining the site, offer, audience, allowed topics, blocked topics, workflow goal, and next step.
Do this before asking for any output.
The source context gives MIRENA the boundary for the project.
Step 2: Add the Best Evidence You Have
After source context, add the best project evidence you have.
That may be a seed topic, sitemap, keyword list, URL list, page inventory, analytics export, search data export, crawl file, behavior notes, or previous MIRENA output.
Give MIRENA the files that reflect the job.
If the task is a topical map, give source context, sitemap, keyword data, and page inventory.
If the task is a rewrite, give source context, the draft, target page goal, query data, internal link targets, and behavior signals.
If the task is internal linking, give source context, page inventory, hub pages, commercial pages, and pages needing support.
Step 3: Turn Inputs Into a Plan
After source context and evidence, ask MIRENA to create a processed map, audit, or page inventory.
The output should tell you which pages are needed, how they connect, and what each page should do.
If this is your first planning workflow, start with the Topical Maps + Planning use case.
Step 4: Turn the Plan Into Briefs
Once the page inventory is clear, create briefs for the highest priority pages.
A strong brief should include the page purpose, entity set, section order, SERP feature targets, internal link targets, and anchor guidance.
This is where the plan becomes usable for writers.
The Content Briefs workflow is the next step after planning.
Step 5: Turn the Brief Into a Draft or Rewrite
Once the brief is approved, use it to create a new draft or improve an existing page.
A good draft should not only read well. It should reflect the plan.
It should have a clear opening answer, clean section order, strong entity placement, useful internal links, and proper next stage routing.
The Drafting + Rewriting workflow handles this stage.
Step 6: Review Internal Links
Internal links should be reviewed before publishing.
Do not leave link placement to a footer block or a disconnected resource list. Links should sit inside relevant paragraphs with anchor text that describes the target page.
A paragraph about moving from map to brief can link to the Content Briefs workflow because that link helps the user take the next step.
A paragraph about link placement can link to semantic internal linking because the surrounding text matches the destination.
Step 7: Add Schema Notes After Approval
Schema should follow the approved page structure.
Do not finalize schema before the draft is approved.
For most MIRENA documentation pages, schema cues may include:
- WebPage
- BreadcrumbList
- FAQPage
- SoftwareApplication reference
- Organization reference
The schema note should match the visible page content. If a FAQ block is not visible, do not add FAQPage markup.
Common Starting Points
Different users arrive with different materials, but the first step stays the same.
Start with source context. Then choose the workflow.
I Have a Keyword List
Start with source context, then use topical mapping.
Ask MIRENA to turn the keyword list into clusters, page roles, intent labels, page vs section decisions, and internal link targets.
A keyword list should not move straight into writing.
Use the Topical Maps + Planning workflow before creating briefs.
I Have a Sitemap
Start with source context, then use a sitemap audit or processed map.
Ask MIRENA to identify weak hubs, overlap, missing support pages, unclear page roles, and internal link gaps.
This works well for site restructure, content refresh, or cluster cleanup.
A sitemap can also support internal link planning when paired with the semantic internal linking workflow.
I Have GSC or GA4 Data
Start with source context, then add the search or analytics export.
Use GSC when you want to connect queries to pages, find high impression pages, spot low click pages, or find pages with weak snippets.
Use GA4 when you want to review landing page engagement, conversion routes, weak next steps, and user flow issues.
This data helps MIRENA decide which pages need briefs, rewrites, internal links, or better CTAs.
I Have Semrush or Ahrefs Data
Start with source context, then add the Semrush or Ahrefs export.
Use Semrush for organic keywords, competitor gaps, SERP feature targets, and page opportunity.
Use Ahrefs for backlinks, top linked pages, weak pages needing link support, and competitor link gaps.
This helps MIRENA connect demand, authority, and structure.
I Have Behavior Data
Start with source context, then add scroll data, heatmaps, click maps, session notes, internal search logs, or form data.
Behavior data is useful when a page gets traffic but users do not move forward.
MIRENA can use that data to improve page flow, CTA placement, internal links, and next stage routing.
I Have an Existing Draft
Start with source context, then use drafting and rewriting.
Ask MIRENA to review page purpose, entity placement, section order, snippets, FAQ blocks, tables, and internal links.
Use the Drafting + Rewriting workflow when the page already exists and needs improvement.
I Need Writer Instructions
Start with source context, then use content briefing.
Ask MIRENA to create a brief that includes the page role, target entity set, search intent, section order, SERP formatting, FAQ targets, and contextual internal links.
Use the Content Briefs workflow when you need to hand work to a writer, editor, or drafting process.
I Need Internal Links
Start with source context, then use the page list or sitemap.
Ask MIRENA to create source page, target page, anchor text, link purpose, and cluster role recommendations.
Internal links should support meaning and movement. The semantic internal linking page explains how link routes can reinforce relationships rather than act as basic navigation.
I Need to Know What MIRENA Gives Back
Start with source context, then review the output docs.
The output docs should explain what you receive, how to read it, and what to do after receiving it.
Use MIRENA outputs before running a large project so your team knows how to review the result.
Common Setup Mistakes
MIRENA works best when the task is specific.
Avoid these setup mistakes.
Mistake 1: Starting Without Source Context
Source context should always come first.
Without it, MIRENA has to infer the site, audience, offer, topic boundaries, and next step.
That increases drift.
Mistake 2: Starting With a Vague Prompt
A vague prompt gives MIRENA too much room to guess.
Do not ask:
text
Make content for my site.Ask:
text
Use this source context and sitemap to create a processed topical map with page roles, overlap warnings, publishing order, and internal link targets.A clear prompt helps MIRENA return a usable output instead of a broad response.
Mistake 3: Skipping Workflow Selection
Source context comes first, but workflow selection comes next.
Do not ask for broad SEO help.
Choose one main output:
- processed topical map
- content brief
- rewrite
- internal link plan
- output review
Mistake 4: Asking for Writing Before Planning
Do not jump straight from keywords to a draft if the structure is unclear.
Plan the cluster first. Then create briefs. Then draft or rewrite.
This is the difference between a controlled workflow and a content pile.
Mistake 5: Uploading Keywords Without a Site Goal
A keyword export without a goal can produce a large but unfocused map.
Tell MIRENA what the site needs.
For instance:
- new cluster
- content refresh
- page consolidation
- internal link plan
- writer briefs
- rewrite queue
The clearer the goal, the cleaner the output.
Mistake 6: Treating Outputs as Finished Work
Outputs need review.
A topical map should be checked before briefs.
A brief should be checked before drafting.
A rewrite should be checked before publishing.
MIRENA can produce structured outputs, but editorial review still protects the site from weak assumptions.
Mistake 7: Ignoring Internal Links
Internal links are part of the structure.
They should not be added after the draft as a link dump.
Use contextual links with clear anchor text. The destination should match the surrounding paragraph.
For anchor planning, use the anchor text by intent framework to match the link text to the user’s next step.
Mistake 8: Forgetting the Local Context File
If you want to continue across sessions, copy useful outputs into your local source context file.
That file should travel with the project.
Upload it first when you start a new session. Then add newer search, analytics, crawl, and behavior exports.
Starter Request Patterns
Use these sample requests as starting points.
New Site Request
text
Use this source context to create a processed topical map for a new site. Include pillar pages, support pages, page roles, intent labels, publishing order, and internal link targets. Keep the map focused on the product, audience, and commercial route.This request works well when paired with the Topical Maps + Planning workflow.
Existing Site Request
text
Use this source context and sitemap to audit the current site structure. Identify missing pages, overlap risks, weak hubs, pages that need consolidation, and internal link gaps. Return a prioritized action plan.This request is useful for site restructure, content refresh, and cluster cleanup.
Search Data Request
text
Use this source context, GSC query export, and GSC page export to find pages with high impressions, weak clicks, missing snippet opportunities, query mismatch, and internal link support needs.This request is useful when the site already has search visibility but the pages need stronger routing or better page purpose.
Analytics Request
text
Use this source context and GA4 landing page export to find weak engagement, poor next step behavior, and conversion path gaps. Return a rewrite and internal link priority list.This request is useful when pages attract users but fail to move them forward.
Writer Brief Request
text
Use this source context and approved page target to create an SEO content brief. Include primary entity, supporting entities, search intent, page purpose, heading structure, snippet block, FAQ targets, internal link targets, and anchor text guidance.This request belongs in the Content Briefs workflow.
Rewrite Request
text
Use this source context and draft to rewrite the page for clearer structure, stronger entity placement, better section order, snippet formatting, FAQ quality, and contextual internal links. Include rewrite notes explaining what changed and why.This request belongs in the Drafting + Rewriting workflow.
Internal Link Request
text
Use this source context and page inventory to create an internal link plan. Include source URL, target URL, optimized anchor text, link purpose, cluster role, and next stage route.This request is useful when a cluster exists but the pages are not connected well.
Local Context File Request
text
Use this source context, previous MIRENA outputs, and page queue to update the master context file. Include completed pages, open pages, internal link rules, drafting rules, data sources used, and next tasks.This request helps preserve the project between sessions.
How to Read a MIRENA Output
A MIRENA output should be readable as a work plan.
Look for these fields:
- page or cluster name
- primary entity
- secondary entities
- search intent
- page purpose
- output type
- required sections
- internal link targets
- next workflow step
- QA notes
If those fields are missing, ask MIRENA to revise the output before using it.
You can ask:
text
Revise this output so each page has a page role, search intent, primary entity, internal link target, and next workflow step.This keeps the output usable for production.
How to Move From Docs to Work
After reading this page, choose the path that fits your task.
If you need the source context structure first, start with the source context template.
If you need to prepare source material, move to the MIRENA input documentation.
If you want the full workflow sequence, review the MIRENA workflow page.
If you want to understand deliverables before starting, move to the MIRENA output documentation.
If you want to choose the right workflow, move to MIRENA use cases.
If you are ready to subscribe, review MIRENA pricing.
FAQs About Getting Started with MIRENA
What should I do first in MIRENA?
Start with source context.
Define the site, audience, offer, workflow goal, allowed topics, blocked topics, and next step before asking for an output.
Is source context different from a prompt?
Yes.
A prompt is the instruction for the task. Source context is the project base that tells MIRENA what the site is, what the audience needs, what topics belong, which topics are blocked, and what the output should support.
What should I do after source context?
Choose the workflow.
Use topical mapping if you need structure, content briefing if you need writer instructions, or drafting and rewriting if you need to improve a page.
What inputs should I prepare for MIRENA?
Prepare the input that matches your workflow.
Useful inputs include source context, seed topic, keyword export, sitemap, URL list, draft page, audience notes, region, search data, analytics data, behavior data, and internal link targets.
Can I start with only a keyword list?
You can use a keyword list, but source context should still come first.
MIRENA can use the keyword list to build clusters, but it still needs site direction to create a clean page plan.
Can I start with a sitemap?
Yes, after source context is defined.
A sitemap is useful for auditing structure, finding overlap, identifying weak hubs, and planning internal links.
Can I use GSC, GA4, Semrush, or Ahrefs data?
Yes.
Those files can help MIRENA connect search demand, page performance, link equity, user behavior, and content gaps to the workflow. Upload source context first, then add those exports.
Can I use heatmap or user behavior data?
Yes.
Behavior data can help MIRENA improve page flow, CTA placement, internal links, and next stage routing.
Can MIRENA rewrite an existing page?
Yes.
Give MIRENA the source context, draft or URL content, page goal, main query, and internal link targets. The rewrite can improve structure, entity placement, section order, snippet blocks, FAQ quality, and internal links.
Can I run a MIRENA module by name?
Yes.
Use a page title, task name, or workflow name as the module command. For example, ask MIRENA to run Behavioral Topical Map, Entity Map, Query Granularity, Internal Link Rewrite, SERP Brief, or Anchor Text by Intent.
Add the source context, the input, and the output you want.
What does MIRENA give back?
MIRENA can give back topical maps, briefs, rewrite plans, rewritten drafts, internal link plans, schema notes, QA checklists, publishing recommendations, behavior maps, and local source context files.
The exact output depends on the workflow you choose.
Should I review MIRENA outputs before using them?
Yes.
Review every output for source context fit, entity coverage, page purpose, internal links, and next step clarity.
How does MIRENA fit into a team workflow?
MIRENA can support strategy, editing, writing, rewriting, internal linking, and publishing review.
A strategist can use the map, an editor can use the brief, a writer can use the draft instructions, and an SEO lead can review links and schema notes.
How do I keep work consistent across sessions?
Copy the source context, project rules, page queue, completed outputs, and open tasks into a local .txt file.
Upload that file first in the next session.
Where should I go after this page?
Go to the source context template if you need a copyable setup file.
Go to MIRENA inputs if you need to prepare source material.
Go to MIRENA workflow if you want to understand the full sequence.
Go to MIRENA outputs if you want to understand deliverables.
Go to MIRENA use cases if you want to choose a workflow.
Go to MIRENA pricing if you are ready to start.