Docs
-
Use Drafting and Rewriting Workflow prompts when MIRENA needs to turn an approved brief into page copy or repair an existing page. This workflow writes, rewrites, trims, expands, reorders, links, formats, and checks copy before the page moves into approval. Start with source context. Do not draft from a loose keyword, title, URL, competitor page,…
-
Use Content Brief Workflow prompts when MIRENA needs to turn strategy into writer-ready instructions. This workflow defines what a page must include, avoid, prove, link to, format, and hand off before drafting starts. Start with source context. Do not create a brief from a loose keyword, topic, URL, competitor page, or map item until MIRENA…
-
Use Behavioral Mapping and User Path prompts when MIRENA needs to understand how users should move through a page, cluster, draft, internal link plan, SERP block, or schema cue. This workflow looks at user state, journey stage, friction, trust, effort, path priority, proof needs, comparison needs, support needs, CTA timing, and satisfaction signals. Start with…
-
Use Topical Mapping and Site Architecture prompts when MIRENA needs to turn source context and discovery evidence into a clean page structure. This workflow decides which pages should exist, which topics should become sections, which pages should merge, which hubs should lead a cluster, which support pages are needed, which routes should connect pages, and…
-
Use Workflow Routing and Module Selection prompts when MIRENA needs to decide what should run next. This workflow does not execute the work. It selects the route. A user may paste a draft, upload a sitemap, add GSC data, share a keyword export, ask for a page, request a rewrite, or ask MIRENA to “run…
-
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…
-
Use Source Context, Project Control, and Guardrail prompts when MIRENA needs a clean project base before any topical map, content brief, rewrite, internal link plan, information gain pass, SERP feature plan, or schema note begins. This is the control layer. It defines the site, audience, offer, primary entities, allowed topics, blocked topics, page queue rules,…
-
Use Information Gain prompts when a page needs stronger differentiation. This workflow helps MIRENA find what the page can add beyond repeated result set coverage. That may be a missing answer, a missing example, a missing comparison, a missing attribute, stronger proof, first hand input, better section structure, or a clearer decision path. Start with…
-
Use Raw Semantic Discovery prompts when MIRENA needs to collect semantic evidence before building a topical map, content brief, rewrite plan, entity layer, internal link plan, information gain pass, SERP feature plan, or schema notes. This is the upstream discovery layer. It collects candidate entities, concepts, modifiers, query paths, intent signals, SERP patterns, competitor signals,…
-
Use MIRENA’s Entity SEO and Salience workflows when a page needs clearer meaning. This prompt set helps you define the main entity, map supporting entities, assign attributes, show relationships, improve salience, repair entity drift, plan support pages, and prepare schema-ready entity notes. Start with source context. Do not run entity prompts against a loose keyword,…
-
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…
-
Rewrite outputs are the deliverables that come out of the rewrite stage after an existing page has been reviewed, restructured, and improved. In simple terms, this is the output pack for pages that already exist but need a stronger shape, clearer topic focus, better support sections, and cleaner routing into the wider site. That is…
-
Topical map outputs are the planning deliverables that come out of the mapping stage before the brief or draft begins. This is the package that shows how a topic should be shaped across pages, sections, and clusters. That is the purpose of this page. A topical map is not just a list of keywords. It…
-
The MIRENA workflow is the operating path that takes a topic, page, draft, or site goal and turns it into a structured SEO output. In plain terms, it moves from input to planning, from planning to briefing, and from briefing to drafting or rewriting. That is the purpose of this page. MIRENA is not built…
-
MIRENA does not just return text. It returns structure. If you are new here, begin with the MIRENA product overview or review what you can give the system. This page answers the next practical question: what does MIRENA return once the work is done? Outputs get stronger when source context gets stronger This page should…
-
MIRENA is built on the ChatGPT interface, so you can give it the same kinds of data and files you would give ChatGPT. The difference is in how MIRENA uses that material. The more proprietary context you give it, the better the output gets. That means you are not limited to a simple prompt. You…
