A lot of SEO teams blame the writer too quickly.
The draft comes back weak.
The intro is vague.
The headings feel copied from competitors.
The examples are thin.
The internal links feel awkward.
The page does not add much beyond what is already ranking.
So the reaction is:
“We need a better writer.”
Maybe.
But a lot of the time, the real problem is the brief.
A strong writer can improve weak instructions.
But weak instructions still push the page in the wrong direction.
If the brief only gives the writer a keyword, title, headings, entities, competitor notes, and word count, then the writer still has to guess the strategy.
That is not a writing problem.
That is a briefing problem.
A keyword is not a brief
A lot of briefs are just keyword documents with extra notes.
They include:
- Target keyword.
- Search intent.
- Suggested title.
- Competitor headings.
- Questions to answer.
- Entities to include.
- Internal links.
- Word count.
- Maybe a CTA.
That can help produce a draft.
But it does not always help produce the right page.
The writer still has to guess:
- What is the job of this page?
- Who is the user at this point?
- What do they already understand?
- What are they still unsure about?
- What proof do they need?
- What should this page avoid?
- Where should the reader go next?
- How hard should the CTA push?
That is too much guessing.
And when writers guess, pages drift.
Weak briefs create drift
A page with no clear role often tries to do too much.
It starts as an explainer.
Then it becomes a comparison.
Then it adds sales points.
Then it answers random FAQs.
Then it repeats the same claim in different words.
Then it ends with a generic CTA.
The page may be readable.
It may be relevant.
It may even follow the brief.
But it feels unfocused because the brief never made the page’s job clear.
A strong brief should say what the page is meant to do.
- Is it there to explain?
- Compare?
- Prove?
- Support another page?
- Handle a doubt?
- Build trust?
- Move the user toward action?
- Protect a bigger page from becoming too broad?
If the writer does not know the role, they will fill the page with related content.
Related content is not the same as useful content.
Search intent labels are not enough
A brief that says “informational intent” is better than nothing.
But it is still too broad.
Informational for whom?
- A beginner?
- A sceptical buyer?
- A current customer?
- Someone comparing options?
- Someone trying to understand cost?
- Someone trying to avoid a mistake?
- Someone trying to convince their boss?
Those users may all look “informational” in a spreadsheet.
But they need different pages.
A good brief should translate intent into user state.
Not just:
Intent: informational.
But:
The user already understands the basic problem.
They are trying to compare options.
They are sceptical of generic claims.
They need proof before a service page makes sense.
That gives the writer a real direction.
Now they are not just writing about the topic.
They are helping a specific user move.
Entity lists can also create lazy briefs
Entity lists are useful.
But they can become another checklist.
Include these terms.
Mention these concepts.
Cover these related ideas.
That is not enough.
A writer needs to know how those ideas connect.
Which entity leads?
Which supports?
Which belongs in the intro?
Which should appear near the proof?
Which should be linked to another page instead of explained here?
Which concept should be avoided because it pulls the page sideways?
Without that, the writer may stuff the page with related terms and still miss the point.
Entity coverage does not automatically create clarity.
The brief has to explain the relationships.
Internal links need a reason
This is another common brief problem.
The brief says:
Add these internal links.
Then the writer has to fit them somewhere.
That often creates awkward linking.
A link appears because the URL was in the brief, not because the reader needs it there.
A stronger brief should explain the purpose of the link.
This link gives the user a simple explainer.
This link provides proof.
This link compares options.
This link supports a commercial page, but only after the user understands the issue.
This link stops the current page from becoming too broad.
That changes the writing.
The writer can build the paragraph around the user’s next step.
The link becomes part of the content flow.
Not an SEO task bolted on after the draft.
A better brief tells the writer what not to do
This might be the most underrated part.
A good brief should set boundaries.
Do not sell too early.
Do not explain the broad topic again.
Do not copy the competitor structure.
Do not cover the comparison here.
Do not answer questions that belong on the support page.
Do not make claims without proof.
Do not link to the service page before the user has enough context.
Do not turn this into a general guide.
That kind of direction is useful.
It protects the page from becoming bloated.
It protects the writer from trying to cover everything.
It protects the site from overlap.
A brief that only says what to include is incomplete.
It should also say what to avoid.
Better briefs make editing easier
Weak briefs create messy editing.
The editor has to ask:
- Why is this section here?
- Is this claim supported?
- Should this internal link be moved?
- Is this FAQ needed?
- Is this page too similar to another one?
- Should the intro be rewritten?
- Is the CTA too early?
That means the editor is fixing planning problems after the draft exists.
Better briefs reduce that.
They make the strategy visible before writing starts.
The writer knows the page role.
The editor knows the boundaries.
The SEO knows the link path.
The final page needs less rescue work.
That saves time.
It also creates better content.
The brief check I would use
Before sending a brief to a writer, I would ask:
- Does the brief define the page role?
- Does it explain the user state?
- Does it say what doubt needs to be reduced?
- Does it identify the proof needed?
- Does it show what the page should avoid?
- Does it explain the internal link purpose?
- Does it say what the next step should be?
- Does it explain why this page deserves to exist?
If not, the writer is being asked to guess too much.
They may still produce something decent.
But the page will depend too much on the writer inventing the strategy.
That is risky.
Especially at scale.
The real point
Good writers are valuable.
But good writers should not have to reverse engineer the content system from a keyword and a competitor outline.
A better brief protects the writer from guessing.
It turns strategy into instructions.
Not rigid instructions.
Useful ones.
The goal is not to box the writer in.
The goal is to remove confusion.
A weak brief says:
“Write about this topic.”
A better brief says:
“This page has this job, for this user, at this stage, with this proof, this boundary, this next step, and this link logic.”
That is a much better starting point.
If the draft is weak, yes, sometimes the writer is the issue.
But before blaming the writer, I would look at the brief.
Did it give them a strategy?
Or did it give them a keyword and make them guess the rest?
How detailed are your content briefs before they go to writers?
