How MIRENA Briefs a Net New SEO Page

New URL planning brief

MIRENA proves why a new URL should exist before writing begins.

A net new brief starts with page ownership, not a blank outline. MIRENA checks the gap, assigns the page role, confirms the query and reader task, maps the entity layer, designs the section order, and places the new URL in the site route.

Static explanation Native disclosure controls Current MIRENA routes Human review required
Starting point Approved page gap
Primary control One page role
Site fit Parent and sibling routes
End state New page brief

How MIRENA handles Briefs for Net New Pages

Six stages move the evidence into an approved brief or handoff.

Validate the gap

MIRENA checks that an existing URL, section, or sibling cannot own the need more cleanly.

Assign the page role

Definition, comparison, use case, process, support, template, example, or another approved role is selected.

Model intent and reader stage

The query, user task, answer depth, and next action shape the brief.

Build the entity layer

The main entity, support entities, attributes, relationships, and exclusions are named.

Design the page

Opening answer, explanation, proof, formats, questions, internal links, and closing route are ordered.

Prepare dependencies and handoff

Source needs, parent links, sibling links, approval checks, and drafting readiness are recorded.

Brief fields

The brief records the decisions the writer and editor should not have to rediscover.

Brief field Why the URL exists

The approved gap, user need, or site route the new page owns.

Brief field Proposed URL and title

A working destination and page identity.

Brief field Page role

The approved page type and dominant job.

Brief field Intent and reader stage

The query frame, user state, and completion event.

Brief field Entity layer

Primary entity, support entities, attributes, relationships, and exclusions.

Brief field Section and format plan

The order and answer blocks that fit the job.

Brief field Internal routes

Parent, sibling, proof, support, and next action links.

Brief field Dependencies

Source material, upstream approvals, and pages that should exist first.

Illustrative MIRENA output

Illustrative net new page packet

The packet shows why the URL belongs in the site before the writing handoff. The example shows structure rather than a client result or search performance claim.

Gap

The cluster lacks a page that explains how to approve a brief before drafting

Role

Process and decision page

Parent

Content Briefs

Main entity

Brief Approval Flow

Key route

Brief Scoring to Revision to Writer Handoff

Next route

Brief Approval and drafting

What MIRENA blocks

The brief stays upstream when these planning problems remain open.

Blocker Duplicate intent

An existing URL already owns the query and user task.

Blocker No parent

The new URL has no clear place in the site hierarchy.

Blocker Topic without page job

The team has a subject but not a useful page role.

Blocker Mixed reader stage

Beginner explanation and commercial decision language compete.

Blocker No source plan

The brief depends on evidence or examples that have not been identified.

Blocker No next route

The page would end with no useful action or link path.

Related MIRENA routes

Move the approved work into the smallest useful next route.

Alternative job

Briefs for Refreshes

Use diagnosis when a live URL already exists.

Open the route
Quality gate

Brief Scoring

Review the new page operating plan.

Open the route
Writer handoff

Brief Handoffs to Writers

Deliver the approved new page packet.

Open the route
Product workflow

MIRENA for Content Briefs

Review the full briefing lane.

Open the route

Questions

Briefs for Net New Pages questions.

What should happen before a net new brief?

A map, query, cluster, or evidence review should confirm that the need belongs on a new URL rather than an existing page or section.

What is the first brief field?

State why the page should exist and which page role it owns.

Does a net new brief need internal links before writing?

Yes. Parent, sibling, support, proof, and next action routes belong in the brief.

Can a new query always become a new page?

No. MIRENA reviews page, section, question, merge, anchor, and rejection treatments before approving a URL.

What happens after approval?

The approved packet moves into the writer handoff with its sources, dependencies, formats, and routes.

Next route

Give MIRENA the source context and evidence. Receive the controlled brief or handoff.

Founder access is €20 per 30 days excluding VAT for one seat and one active MIRENA instance. OpenAI account rules and usage limits remain separate.

MIRENA output requires factual, editorial, legal, technical, and business review before publication or client delivery.