Semantec SEO

MIRENA Workflow: From Input to Plan, Brief, and Draft

Written by

Kevin Maguire

in

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 to jump straight into copy. It starts by setting the topic boundaries, mapping the support concepts, choosing the page role, and shaping the structure before the draft begins.

Back to Docs

Why the workflow exists

A lot of SEO content breaks down for one simple reason.

The draft starts too early.

The topic is loose. The page role is unclear. The support concepts are half chosen. The internal links get added at the end. The rewrite comes too late.

The MIRENA workflow fixes that by moving through a clear sequence.

It starts with context. Then it plans the topic. Then it builds the page. Then it checks the output.

That creates cleaner pages, stronger clusters, and a better handoff from planning to publishing.

To see the inputs that start the process, go to Inputs. To see the deliverables that come out the other side, go to Outputs.

The high level flow

At a high level, the workflow looks like this:

  1. Source context
  2. Topic or page intake
  3. Topical mapping
  4. Content brief
  5. Draft or rewrite
  6. Internal link pass
  7. Publish pack

Each stage has a job.

Each stage also sets up the next one.

That is why the workflow reads more like a build sequence than a writing prompt.

Stage 1: Source context

Everything starts here.

Before MIRENA plans a page, it needs the context that defines the site and the topic space around it.

This stage sets:

  • what the site is about
  • who the audience is
  • what the offer is
  • what topics belong in scope
  • what claims should stay out
  • which pages or workflows deserve more focus

This stops the system from drifting into broad content that does not fit the site.

For Semantec SEO, this stage keeps the work tied to semantic SEO, topical mapping, content briefs, drafting, rewriting, internal linking, SERP formatting, and schema support.

If the source context is weak, the rest of the workflow gets loose fast.

Stage 2: Topic or page intake

Once the source context is clear, the next stage is intake.

This is where the user brings one of the starting points into the workflow.

That can be:

  • a seed topic
  • an existing page
  • a rough draft
  • a rewrite target
  • a sitemap
  • a content goal
  • a cluster idea

This stage defines the starting unit.

It tells MIRENA what it is working on and what kind of output needs to come next.

For example:

  • a topic may need a topical map
  • a page idea may need a brief
  • an old article may need a rewrite
  • a weak cluster may need structural support pages

Stage 3: Topical mapping

This is where planning gets serious.

The topical mapping stage turns the topic into a structured view of the page or cluster.

That can include:

  • the main entity
  • support entities
  • topic boundaries
  • intent layers
  • page roles
  • supporting pages
  • cluster links
  • gaps that still need coverage

This stage is what gives the workflow its shape.

It helps answer questions like:

  • what belongs on this page
  • what belongs on a different page
  • which support topics are missing
  • which pages should link to each other
  • where the cluster is thin

For the planning side of the system, see Topical Mapping and What Is a Topical Map.

Stage 4: Content brief

Once the topic shape is clear, MIRENA builds the brief.

The brief is the page plan.

It tells the next stage what the page needs to cover and how that coverage should be structured.

A strong brief can include:

  • page goal
  • search intent
  • main entity
  • support entities
  • section order
  • key distinctions
  • SERP feature opportunities
  • internal link targets
  • next step CTA direction

This stage is where the workflow moves from cluster thinking into page thinking.

The brief does not try to write the page.

It tries to make the page easier to write well.

For more on that layer, see Content Briefs, Entity Led Brief, and SERP Feature Briefing.

Stage 5: Draft or rewrite

Now the page gets built.

At this point, MIRENA has enough structure to draft a new page or rewrite an old one with a clear direction.

This stage can produce:

  • a new draft
  • a rewrite of an older page
  • a cleaned structure
  • stronger section flow
  • tighter topic focus
  • better SERP formatting
  • stronger internal link placement
  • clearer CTA routing

The goal is not to write more for the sake of it.

The goal is to turn the brief into a page with a strong center, useful support sections, and a clear place inside the cluster.

For that production layer, see Drafting + Rewriting, Rewrite Existing Content, and Fix Semantic Drift.

Stage 6: Internal link pass

Internal links are part of the workflow, not a cleanup task at the end.

Once the page structure is in place, MIRENA can route the page into the wider site.

This stage helps define:

  • which hub the page belongs to
  • which sibling pages should support it
  • which deeper pages it should point to
  • which parent page should link back
  • which anchor text fits the section

This turns a single page into part of a working cluster.

That is a big difference between content that sits alone and content that strengthens the site around it.

For that part of the system, see Semantic Internal Linking and Anchor Text by Intent.

Stage 7: Publish pack

The final stage is the output pack.

This is the handoff layer.

By this point, the workflow has moved through planning, briefing, drafting, rewriting, and link routing. The final output can now be packaged for publishing.

That pack can include:

  • the final draft
  • headline and metadata
  • internal link targets
  • CTA placement
  • section structure
  • related page suggestions
  • follow on page ideas
  • rewrite notes

This stage makes the output easier to move into a CMS, a team handoff, or a production queue.

To see the finished deliverables, go to Outputs.

How the workflow changes by use case

The same sequence stays in place, but the starting point can shift.

If the user starts with a topic

The workflow leans harder on topical mapping and briefing before the draft begins.

If the user starts with a weak article

The workflow leans harder on audit, rewrite structure, and internal links.

If the user starts with a site gap

The workflow leans harder on cluster roles, missing support pages, and routing.

If the user starts with a content operation problem

The workflow leans harder on process pages, briefs, templates, and output consistency.

That is why the workflow is flexible without becoming loose.

It keeps the same sequence while changing the entry point.

For examples of those entry paths, see Use Cases.

How approvals fit into the flow

Approvals sit between the major stages.

That means a team can stop after mapping, stop after the brief, or stop after the draft before the next stage begins.

A clean approval path can look like this:

  1. approve the topic direction
  2. approve the map
  3. approve the brief
  4. approve the draft or rewrite
  5. approve the link routing
  6. approve the publish pack

This keeps the process controlled and easier to review.

It also makes the workflow more useful for teams that do not want planning, writing, and publishing to happen in one jump.

Common workflow mistakes

Mistake 1: Starting from the draft

If the workflow starts with copy and not with context, the page often needs more repair later.

Mistake 2: Skipping the map

Without the map, the brief gets thinner and the cluster logic gets weaker.

Mistake 3: Treating the brief like filler

A weak brief leads to weak structure.

The brief is the bridge between the topic plan and the page build.

Mistake 4: Leaving internal links to the end

That can turn a strong page into an isolated page.

Mistake 5: Publishing after one draft

A lot of pages improve most during the rewrite and routing pass.

Workflow inputs vs workflow outputs

This is the simplest way to think about it.

Inputs

Inputs are what the user brings into the system.

Examples:

  • topic
  • draft
  • URL
  • sitemap
  • cluster goal
  • page goal

See Inputs.

Outputs

Outputs are what MIRENA sends back.

Examples:

  • topical map
  • content brief
  • draft
  • rewrite
  • internal link plan
  • publish pack

See Outputs.

Workflow

The workflow is the path that connects the two.

That is what this page explains.

A simple version of the workflow

If you want the shortest version, it is this:

  • define the context
  • define the topic
  • map the topic
  • brief the page
  • draft or rewrite it
  • route the links
  • package the output

That is the engine behind the full system.

How MIRENA fits into the workflow

MIRENA sits across the full flow.

It helps shape the topic before the page is written, then supports the page as it moves into structure, copy, links, and delivery.

That is why it works as more than a writing tool.

It is closer to a semantic SEO operating system with planning, briefing, drafting, rewriting, and routing built into one sequence.

To see the product page, go to MIRENA. To see pricing, go to Pricing.

Quick checklist

  • Is the source context clear?
  • Is the intake point clear?
  • Has the topic been mapped before briefing?
  • Does the brief define the page structure?
  • Has the page been drafted or rewritten with that structure in place?
  • Are the internal links routed into the cluster?
  • Is the final output ready for publishing?

If not, the workflow is still incomplete.

FAQ

What is the MIRENA workflow?

The MIRENA workflow is the sequence that moves from source context and topic intake to topical maps, briefs, drafts, rewrites, internal links, and final outputs.

What comes first in the workflow?

Source context comes first, then topic or page intake, then topical mapping.

Does every page need a topical map first?

Not every page needs a full cluster build, but every strong page benefits from clearer topic planning before drafting starts.

What is the role of the brief in the workflow?

The brief turns the topic plan into a page plan. It defines what the page should cover and how the structure should work.

When do internal links get added?

Internal links fit into the workflow after the page structure is built, so the page can be routed into the wider cluster in a cleaner way.

Final take

The MIRENA workflow gives the page a path before the copy begins.

That path moves from context to structure, from structure to briefing, and from briefing to production and routing.

The result is a cleaner build process with stronger clusters, clearer pages, and a better handoff into publishing.

Start with Inputs, review the deliverables in Outputs, or see the full product in MIRENA.

Soft next step: See pricing