You need an SEO content strategist when your team writes well and the pages still land in a pile. A useful strategist leaves you a map from each URL to the question it answers. A weak one leaves a list of headlines. You will know what the deliverable should look like once you can tell the map from the list.
This guide covers why writing well is not the assignment, what the map should look like, why a list of headlines is not a map, how the engagement should run, and what you still decide.
Takeaways
- Hire a strategist to make the assignment, not to ghostwrite the pile.
- Require a map that pairs each question with one URL and one owner.
- Treat a headline list as a draft of ideas, not as the finished work.
- Keep approval of every public claim on your side of the table.
Writing Well Is Not the Assignment
A team can write clear sentences and still publish into a pile. The pile forms when each piece is judged on its own and nobody checks whether another URL already answered the question. That check is the strategist's job. You do not need them because your writers lack voice. You need them because the voice is being applied to overlapping jobs. If the drafts are bad, fix the drafts. If the drafts are good and the site is redundant, hire for the map, because mixing those problems produces an engagement that rewrites pages which should have been merged.
Look at the last handful of URLs your team shipped. If a stranger would call them related essays on the same offer, you have the hiring signal. SEO Content Strategy is the work of giving each important query a page you will actually maintain: one query, one URL, one owner. A strategist who accepts that sentence will start by reading what you have, while a strategist who starts by asking how many posts you want has mistaken the job for production.
You might be the right owner and still be too close to see the overlaps, which is a fair reason to hire. Ask the person to show you pairs of URLs on your existing site that collide, before they propose anything new. The pairs are the evidence they understand the job, while a deck of future headlines is evidence they understand a brainstorm. You will know the difference in the first conversation if you ask for the pairs, so do not wait for a long workshop to discover you bought a list.
The Map You Should Be Able to Hold
The deliverable is a map a writer can use without you in the room. Each row has the question in customer language, the URL that owns it, the owner who approves claims, and whether the next action is an edit or a new page. Rows that fail those fields are not done. The map can be short, and short is believable, because it admits you will not maintain a sprawl of new URLs. A long map nobody will reread is a headline list with extra columns, so ask to see the format before the work starts and avoid a surprise slide.
The map should also record what you will not publish. Questions you cannot answer honestly, and pages that would only swap a label, belong in a refused column. That column is part of the value, because it stops the next enthusiastic draft. If the strategist is uncomfortable writing refusals, they are still trying to look abundant, and abundance is how the pile grew. Content Marketing gets clearer when the public set is smaller and each URL has a job. The map is how you defend that smaller set to anyone who wants more posts.
Do not accept invented search volumes as decoration on the map. A question earns a row because customers ask it, sales repeats it, or a page you already trust is the one you send by hand. A fabricated figure makes weak rows look scientific. Triwave Consulting will not invent search volumes to pad a strategy, and you should not pay someone who needs them to choose. If a row cannot be justified in a sentence, cut the row. The sentence is the deliverable's proof, not a chart you cannot source.
| Deliverable | Useful strategist | Weak substitute |
|---|---|---|
| Core artifact | A map of URL to question | A list of headlines |
| Each row | Question, URL, and owner | A topic and a suggested month |
| Overlaps | Pairs of pages that collide | A note that the site needs more content |
| Refusals | Questions you will not publish | Every idea kept so the list looks full |
A List of Headlines Is Not a Map
Headlines feel like progress because they are writable. Anyone can propose a handful in an afternoon. The test is whether each headline points at a different question and a different URL. Read them aloud and see whether two could be the same page. If they could, the list has not done the strategy, so send it back. You are not being difficult. You are refusing to turn a brainstorm into a publishing queue, and the queue is what created the pile your writers are already good at adding to.
A headline list also hides the owner problem. There is nobody to approve a claim on a title, so the claim appears later, inside a draft, when changing course feels expensive. Put the owner on the row before the title gets charming. Charming titles are optional, but the question is not. Ask the strategist to write the question as a customer would ask it, then write the title only if a title helps the writer. Many rows do not need a clever title to be actionable. They need an address.
Compare the list with homes you already have. Blog Content should not receive a headline that restates Service Page Content, and Location Page Content should not receive a stack of labels you cannot describe. If the headline list ignores those distinctions, the strategist is generating topics instead of assigning them. Content Optimization should appear whenever the right move is to edit the URL you have, and a list that only contains new titles has skipped that move on purpose.
How the Engagement Should Run
Start with Initial Contact. In that conversation, ask them to restate the job as a map of URL to question, and ask what they will need from you. A Detailed Discussion comes next, where you walk the existing site, name the offers, and mark the claims you will not make. Implementation follows, and for a strategist Implementation means producing the map and the first decisions about overlaps, not ghostwriting the pile. Drafting can be a later engagement with a writer who uses the map. Do not let drafting replace the map just because drafting is easier to invoice.
During the discussion, sit with them on the actual URLs. A strategist who will not open the site is planning in the abstract, and abstracts produce headline lists. On the URLs, decide the winner when two pages collide, and write the loser down as a redirect of attention: links should point to the winner, and the loser should stop answering. That decision is Implementation of the strategy even before new prose exists. It is also the part teams skip because it feels like deleting work, but deleting overlap is the work.
The order is not a guarantee. Contact may show you this person wants to sell a posting quota, and you should end it there. The discussion may show you that your own offers are not ready to assign, so pause and clarify the offers before anyone builds a map on sand. Implementation may produce a map you disagree with, and you should disagree in the rows, not by asking for more headlines to paper over the dispute. Nobody you hire can promise that the map will bring traffic. They can promise a document you can follow, and you can check whether they did.
- Initial Contact: they describe a map, not a quota of posts.
- Detailed Discussion: you review real URLs, offers, and refused claims.
- Implementation: they deliver the map and the overlap decisions.
- Later writing, if you want it, follows the map and does not replace it.
What You Still Decide
You still decide which claims are true and which offers are real. The strategist can notice that two pages collide, but they cannot know that one of the offers is about to be retired. Tell them. A map built on an offer you are ending will assign beautiful homes to work you will not sell. Your judgment is the input and their structure is the output, so if you hide the upcoming change to see whether they discover it, you will pay for a redo. Share the constraint in the discussion.
You also decide whether a question is important enough to maintain. A strategist can recommend, but the owner lives with the page. If you already know nobody will reread a URL, do not let it onto the map to be polite, because polite maps decay. Say no in the meeting and ask them to record the no. That recorded no is how you judge the engagement later: a deliverable with only yeses did not listen, and a deliverable that shows your refusals did.
This assignment is distinct from the broader build of Search Engine Optimization. You might hire technical help for the way the site is put together and still need a strategist for the question map, or the reverse, so do not assume one vendor's title covers both. Ask which artifact you will hold. If the artifact is the map, you are hiring the strategist. If the artifact is a rewrite of every page with no map, you are hiring a writing project, and the pile will return in a new voice.
Questions
Do You Need a Strategist If the Team Writes Every Week?
Weekly writing is a production habit. You need the strategist when that habit publishes overlapping answers and nobody assigns a home first. If every new piece already has a clear URL and a clear question, you may not need the hire. Look at the pile, not at the talent.
Should the Strategist Also Draft the Articles?
Only if the map exists as its own deliverable and the drafting is a separate, later step. Combining them often means the map is never written down, and you then have more good prose and the same overlaps. Ask for the map before any new draft begins.
What Do You Bring to the First Meeting?
The offers you sell, the claims you refuse, and a few pairs of pages you suspect repeat each other. You do not need a finished keyword file. You need enough truth for someone to assign homes without inventing demand figures.
How Long Should the Map Be?
Long enough to cover the questions you will actually maintain, and short enough that each row has an owner. A short complete map beats a long one full of headlines. If a row has no owner, it is not ready to be on the map.
What Do You Do If Two Advisors Disagree?
Open the two URLs they are arguing about and choose the one that matches the reader's next step. The disagreement is useful only if it ends in a single home, so do not keep both pages live to respect both advisors.
Conclusion
You will know what the deliverable looks like when you can hold a map of URL to question and name the owner on each row. The useful strategist leaves you that map, and the weak one leaves a list of headlines. Hire for the assignment, and let writing follow it instead of standing in for it.
If you want a first conversation about a map of questions to URLs, Speak With Us.
