The opening block sets the tone for the whole page.
If the opening is loose, slow, or vague, the rest of the draft has to fight uphill. If the opening is clear, direct, and placed with intent, the page gets a far better start.
That is why intro block briefing belongs inside the Content Briefs cluster. A strong brief should not just list headings. It should tell the writer how the page needs to open, what the first answer should say, and what block comes next.
If you want the wider brief framework first, start with What Is an SEO Content Brief. If you want the page purpose layer before the opening block, go next to Intent Led Brief. If you want to control the full page flow after the opening, move into Section Order in Briefs.
The short version
A good intro block brief should tell the writer five things before drafting starts:
- what the page needs to answer first
- how direct the opening should be
- which entity, concept, or comparison belongs in the first lines
- what block follows the opening
- where the first internal link belongs
That is the job.
The opening block is not just an intro
Teams often treat the top of the page like warm up copy.
That is where pages go soft.
The opening block is not there to circle the topic. It is there to do the first job of the page. On some pages that job is a direct definition. On others it is a short comparison call, a process summary, or a fast answer that prepares the next block.
A stronger brief calls that job in plain language.
For example:
- answer the query in two short paragraphs
- define the concept in the first lines
- frame the key difference before the table
- state the decision before the analysis
- explain the process before the steps
That is far more useful than writing “intro” and moving on.
Why the opening block belongs in the brief
If the opening block is left open until draft time, writers tend to fall into the same patterns:
- broad openings before the answer
- repeated background before the page purpose is clear
- slow starts that bury the point
- first paragraphs that could fit ten different pages
- feature targets missed because the answer shows up too late
That is why SERP Feature Briefing sits close to this page. A page built for a direct answer, list, table, or PAA style question needs the right opening shape from the start.
Start with the first job of the page
The first line in the brief for the opening block should answer one question:
What does this page need to do first?
That keeps the opening tied to page purpose.
A concept page may need to define the term fast. A comparison page may need to frame the decision fast. A rewrite page may need to correct a buried answer fast. A process page may need to explain the outcome before the steps begin.
When that first job is clear, the writer has a real starting point.
What the brief should say about the opening block
A strong opening block brief does not need to be long. It needs to be specific.
At minimum, it should state:
- the first answer or claim
- the opening format
- the target length
- the main entity or concept to name early
- the block that follows
- any internal link that belongs near the top
That gives the writer a clear opening move and keeps the page from wandering.
The opening shape should fit the page type
Not every page should open the same way.
Definition pages
A definition page often works best with:
- a direct definition in the first lines
- a short explanation of why the page exists
- a clear move into the next block
If the page sits near Entity SEO, the opening may also need to name the main entity right away.
Comparison pages
A comparison page often works best with:
- a short decision summary
- the core difference between the two options
- a move into the table or criteria block
For those pages, the opening should not stall before the comparison logic arrives. Keep Comparison Tables close when briefing the next block.
Process pages
A process page often works best with:
- a short overview of what the process does
- who the process is for
- what comes after the overview
If the page needs a steps based format, pair the opening with How To Intros or List Snippets.
Rewrite pages
A rewrite page often works best with:
- a direct statement of what is wrong
- a short statement of what the page should do instead
- a move into the fix or example block
For this path, it helps to keep Rewrite Existing Content in the workflow.
The opening should name the page purpose fast
A weak opening sounds generic because it hides the page purpose.
A better opening tells the reader why this page exists without wasting space.
For example, a page about brief depth should not open with broad commentary on content planning. It should state that brief depth is about how much control a page needs before drafting starts.
That first purpose line does a lot of work. It tells the writer what to say early and tells the reader why the page deserves attention.
Put the main entity near the top when the page needs it
On entity led pages, the opening block should name the main entity early.
That helps the page lock onto the right semantic center before the writer moves into support ideas. It also gives the next block a stronger handoff.
If the page needs tighter entity control, pair this page with Entity Led Brief and Briefs for Entity Pages.
The opening should prepare the next block
A good opening does not just answer. It also sets up what comes next.
That next block might be:
- a table
- a comparison frame
- a proof block
- a list of steps
- a deeper explanation
- a FAQ block later in the page
The brief should name that handoff. This keeps the opening from floating alone with no transition into the rest of the page.
A simple note works well:
Next block after opening: comparison table Purpose of handoff: move from summary into criteria
That is enough to keep the top of the page clean.
Do not overload the opening
The top of the page has to do the first job well. It does not need to do every job at once.
A lot of weak briefs overload the opening with too much background, too many support points, and too many claims. The result is a crowded start that still says very little.
Keep the opening block tight. Let later blocks carry the explanation, the proof, the edge cases, and the follow up questions.
If you need stronger control over what comes after the opening, use Section Order in Briefs.
Where the first internal link should go
The brief should also decide if the opening block needs an early internal link.
Not every page needs one near the top. When a link does belong there, it should support the reader path, not interrupt it.
Good early link placements often include:
- the cluster hub on concept pages
- a sibling page that sharpens a distinction
- a use case page when the opening sets up a workflow
- a product path when the page is close to evaluation intent
For pages in this cluster, an early route into MIRENA for Content Briefs can work well when the opening frames the workflow clearly.
A simple opening block format for briefs
This is a clean way to write the opening block inside a brief:
Opening job: What the page needs to do first.
Opening format: Direct answer, definition, summary, comparison call, or short process note.
Target length: How long the opening should be.
Main entity or concept: What needs to appear early.
Next block: What follows the opening.
Early internal link: Which page belongs near the top, if any.
That format gives the writer a usable opening plan without scripting every sentence.
Common opening block mistakes
Starting too wide
A broad opening often delays the point instead of helping the page.
Hiding the answer
If the reader has to scroll too far to find the core answer, the opening brief was too loose.
Mixing too many ideas
The opening should frame the page, not carry the whole page at once.
Forgetting the handoff
A good opening should prepare the next block, not sit there on its own.
Leaving the format uncalled
If the brief does not say definition, answer, list intro, table lead in, or comparison summary, the writer ends up guessing.
Opening block notes by page type
Here is a simple working table.
| Page type | Best opening move | What should follow |
|---|---|---|
| Definition page | direct definition | explanation or related concept block |
| Comparison page | decision summary | table or criteria block |
| Process page | short process overview | steps or checklist |
| Entity page | entity definition | attributes or related entities |
| Rewrite page | direct problem statement | fix, contrast, or example |
The brief should call both the opening move and the next block. That pair keeps the page from losing shape near the top.
How this fits in the MIRENA workflow
This page sits in the middle of the briefing flow.
A clean path looks like this:
Start with Content Briefs. Set page purpose with Intent Led Brief. Set the opening block here. Control the wider page flow with Section Order in Briefs. Add format notes with Table Briefing or FAQ Briefing when the page needs them. Then move the work into MIRENA for Content Briefs.
That keeps the opening tied to the rest of the page plan.
Final take
Intro block briefing is about deciding how the page should start before writing begins.
That means naming the first job of the page, the opening format, the main entity or concept to place early, the block that follows, and the first link if it belongs near the top.
When the brief controls that opening, the page gets a cleaner start and the rest of the draft has a far better base.
FAQ
What is intro block briefing?
It is the part of a content brief that tells the writer how the page should open.
What should the opening block do first?
It should answer the first job of the page as quickly and clearly as the page type allows.
Does every page need the same opening style?
No. Definition pages, comparison pages, process pages, entity pages, and rewrite pages need different opening shapes.
What should I read after this page?
Go next to Section Order in Briefs, Table Briefing, and FAQ Briefing.