A brief for a net new page starts before there is a draft, a live URL, or an old structure to repair.
That changes the job.
A refresh brief starts with diagnosis. A net new page brief starts with page design. The team has to decide what page should exist, what role it should play in the site, what query path it should serve, and how it should connect to the rest of the cluster before writing begins.
This page belongs inside the Content Briefs cluster because new pages rise or fall on planning quality. If you need the foundation first, start with What Is an SEO Content Brief. If your team is reviewing brief quality before writing, move next to Brief Scoring, Brief Approval Flow, and Brief Revision Process.
Quick answer
A brief for a net new page is a planning document for a page that does not exist yet.
It should tell the writer or editor:
- why the page should exist
- what page type it is
- which query path it serves
- which entities need support
- what structure the page should follow
- which format blocks belong on the page
- how the page should link into the site
- what next step the page should push the reader toward
That is the core difference. A net new page brief is not fixing an old page. It is defining a new one from the ground up.
Why net new page briefs need their own approach
A lot of teams use the same brief format for every job.
That creates problems fast.
A new page does not need a long diagnosis of an existing draft. It needs stronger planning around page role, topic scope, internal links, and cluster fit. If those decisions are weak, the page can launch with no clear job, no clear route into the site, and no clean reason to exist apart from “we wanted another page.”
A good net new page brief avoids that. It forces the team to answer the hard questions before anyone writes a line.
That is why this page sits close to Topical Mapping and Intent Led Brief. A new page should begin with structure and purpose, not just a topic idea.
What a net new page brief should solve
A strong brief for a new page should answer one simple question:
Why should this page exist on the site at all?
That answer should be clear before writing starts.
In most cases, a net new page exists for one of these reasons:
1. The site has a real topic gap
The cluster is missing a page that should already be there.
This might be a missing comparison page, a missing support page, a missing decision page, or a missing definition page. If the page came from a map level decision, the right companion hub is Topical Mapping.
2. A query path needs its own page
Some queries should not be folded into an existing page. They need their own structure, their own angle, and their own CTA path.
This is where a page level decision gets clearer than a section level patch.
3. The cluster needs stronger coverage
A new page can support a pillar, fill a support gap, or tighten the route between authority content and commercial pages.
That is where internal links and page role planning become part of the brief, not a late add on.
4. The site needs a clearer path for the reader
A page can exist because the site has the topic, though lacks the step that moves the reader forward.
That could be a use case page, a comparison page, a glossary style definition page, or a page built for a specific stage in the journey.
Net new page brief vs refresh brief
The difference is simple.
A refresh brief asks:
- what is wrong with the live page
- what should stay
- what should change
A net new page brief asks:
- what page should exist
- what job should it do
- how should it fit the cluster
- how should it be structured from the start
That is why Briefs for Refreshes and this page belong next to each other, though they should not be treated as the same workflow.
The core parts of a net new page brief
A good brief for a new page should be clear enough that the writer never has to guess the page strategy.
Here is the cleanest structure.
1. Page summary
Start with the page idea in plain language.
Include:
- proposed URL
- working title
- page type
- parent hub
- target query or query group
- short note on why the page should exist
Example:
This page is a support page for the Content Briefs cluster. It targets teams looking for a framework for planning new SEO pages before writing starts.
2. Page role
Name the page role early.
That could be:
- definition page
- comparison page
- use case page
- process page
- supporting concept page
- template page
- example page
If the role is loose, the page structure gets loose as well. This is where Page Types becomes useful for team alignment.
3. Search intent and reader stage
A new page brief should tell the writer what kind of searcher the page is meant to serve.
For example:
- a reader trying to understand a concept
- a buyer comparing options
- a team looking for a workflow
- an editor trying to fix a process
- a marketer looking for an example or template
If that is not clear, the page can end up mixing beginner explanation with commercial language or turning a use case page into a broad education page.
That is why Intent Led Brief sits at the center of this cluster.
4. Main entity and support entities
A new page brief should name the main entity and the supporting concepts that need to sit close to it.
This is where the brief moves past a keyword list and becomes a better production document.
For a page like this one, the main entity is the net new page brief. The support layer includes content brief, page role, search intent, topical map, internal links, and page structure.
If your team needs the deeper entity layer, move next to Entity Led Brief, Entity Salience, and Entity Map.
5. Page structure
This is one of the biggest parts of the brief.
A net new page should not go into writing with a vague list of subheads. The brief should show the page shape.
That can include:
- direct intro answer
- page purpose or context
- main explanation
- framework or process
- examples or comparisons
- common mistakes
- final takeaway
- FAQ
- CTA
The point is not to lock every sentence. The point is to give the page a clean route from first answer to next step.
6. Format blocks
A new page brief should say which content blocks belong on the page.
Examples:
- short answer block
- comparison table
- process list
- FAQ block
- example block
- template block
- callout box
That is where SERP Feature Briefing becomes useful. Format should be chosen with purpose, not dropped in at random.
7. Internal link plan
A net new page needs link planning from the start.
The brief should name:
- the parent hub
- the sibling pages for inline links
- the next step page
- the supporting pages that should link back to it later
For a page in this cluster, that means linking into the Content Briefs hub, nearby brief process pages, and a next step page such as Drafting Rewriting or MIRENA for Content Briefs.
If your team treats links as a late pass, read Internal Link Briefing and Semantic Internal Linking.
8. CTA path
A new page should not end with no direction.
The brief should say what the page should push the reader toward:
- another support page
- a template
- an example
- a use case page
- the product page
- a pricing or contact step
That route depends on the role of the page, though it should be named before drafting starts.
A simple workflow for net new page briefs
The cleanest workflow looks like this:
- identify the page gap
- confirm the page role
- define the search intent
- name the main and support entities
- shape the page structure
- choose the format blocks
- set the link plan
- score the brief
- revise if needed
- approve and hand off to drafting
That ties this page directly into Brief Scoring, Brief Revision Process, and Brief Approval Flow.
Signs a net new page brief is weak
A weak brief for a new page often shows the same problems.
- the page exists for no clear reason
- the page role is fuzzy
- the topic scope is too broad
- the query path is mixed
- the structure is generic
- the internal links are missing
- the CTA path is unclear
- the writer still has to decide what the page is trying to do
When those gaps are present, the team is not ready to draft. It still needs planning.
Common mistakes in net new page briefs
Starting with headings instead of page role
Subheads come after the page purpose is clear.
Treating the brief like a keyword sheet
A new page needs direction, not just search terms.
Ignoring the cluster fit
A page can look strong on its own and still fit poorly into the site.
Skipping links until after drafting
That makes the page feel disconnected even if the copy is good.
Mixing two page jobs into one brief
A page should not try to be a glossary entry, a how to guide, and a product page all at once.
What a strong net new page brief feels like
A good brief for a new page should feel stable before the first draft exists.
The writer should be able to open it and see:
- why this page belongs on the site
- what type of page it is
- who it is for
- what the intro should do
- which concepts need support
- what order the page should follow
- which links belong inline
- what the closing step should be
That is the point where the page is ready to move into production.
How MIRENA fits net new page briefs
MIRENA is built around planning the site, briefing the page, then drafting or rewriting it into a stronger search structure. Net new page briefs sit at the planning edge of that workflow. They turn a topic gap or page idea into a page design the team can write from with confidence.
If you want the product path around that workflow, go to MIRENA for Content Briefs or MIRENA.
Final take
Briefs for net new pages help teams build new pages with purpose.
They define why the page should exist, what role it should play, what intent it serves, which entities need support, how the structure should work, where the links should go, and what next step the page should drive.
If your team is publishing new pages often, keep this page close to Topical Mapping, Entity Led Brief, Intent Led Brief, and Internal Link Briefing.
FAQ
What is a brief for a net new page?
It is a content brief built for a page that does not exist yet. It defines page role, intent, structure, entities, links, and next step before drafting starts.
How is a net new page brief different from a refresh brief?
A net new page brief plans a page from zero. A refresh brief improves a page that already exists.
What should a net new page brief include?
It should include the proposed URL, page role, intent, main and support entities, page structure, format blocks, internal link plan, and CTA path.
When should a team use a net new page brief?
Use one any time the site needs a brand new page, not just an update to an old one. fing/).
FAQ
What is a refresh brief?
A refresh brief is a content brief for improving an existing page rather than building a new page from zero.
What should a refresh brief include?
It should include the live URL, reason for refresh, what stays, what changes, intent notes, entity gaps, structure changes, format blocks, internal link updates, and rewrite instructions.
Is a refresh brief the same as a rewrite brief?
They are close. A refresh brief is a type of rewrite brief focused on improving an existing page that still has value.
When should a page get a refresh brief instead of a full rebuild?
Use a refresh brief when the page still has a solid base, fits the topic closely enough, and can improve through tighter structure, better support, cleaner routing, and sharper rewrite work.