Most organizations split SEO and content writing into two roles, sometimes two departments entirely. It seems reasonable on paper: one person understands search engines, one person understands writing. In practice, this split quietly costs both sides quality.
Worth a Conversation?
Working through something similar on your own site? Let's talk →
Technical SEO vs. content SEO: what each actually covers
Before getting into why they shouldn't be separated, it helps to be clear on what each side actually does. They're not competing approaches, they're two halves of the same job.
| Area | Technical SEO | Content SEO |
|---|---|---|
| Primary focus | How a site is built, crawled, and indexed | What a page says and who it's written for |
| Core tasks | Site speed, crawlability, indexation, schema markup, redirects, mobile usability | Keyword research, search intent mapping, on-page writing, content structure |
| Common tools | Google Search Console, Screaming Frog, PageSpeed Insights | Keyword research tools, SERP analysis, content briefs |
| Fixes what | Whether a page can be found and understood by search engines at all | Whether a page actually satisfies the person who finds it |
| Fails silently when | Content is excellent but sits on a broken or unindexed page | The page is technically perfect but doesn't match what anyone searched for |
| Owned by | Traditionally a developer or SEO specialist | Traditionally a writer or content marketer |
Neither column works well without the other. A technically flawless page with generic content underperforms. A brilliantly written page that's unindexed or slow to load never gets read at all. This is exactly why treating them as two disconnected roles causes the problems below.
The handoff loses context every time
An SEO specialist hands over a keyword list and a target word count. A writer, working from that list alone, doesn't know why those keywords were chosen, what search intent they map to, or how this page fits into the broader content architecture. The result reads like it was written to satisfy a spreadsheet, because it was.
Writers without SEO context under-structure content
A skilled writer without SEO training will often produce genuinely good prose that's structured for a linear read, rather than for how people actually scan a page, jump to a specific section, or arrive from a search query answering one specific question. The writing is fine. The structure fights against how the content will actually be found and used.
SEO specialists without writing skill under-serve the reader
The reverse failure looks different: content that hits every technical checkbox, keyword placement, header structure, internal links, but reads stiffly, because it was optimized before it was made genuinely useful to a human reading it. Search engines have gotten better at detecting this gap between optimization and actual quality, and increasingly rank against it.
What changes when one person owns both
- Search intent and content structure get decided together, not handed off across a gap
- Technical elements (titles, slugs, internal links) get built in from the first draft, not bolted on afterward
- Revisions based on performance data happen faster, without needing to loop in a second person to interpret the "why" behind a change
This isn't an argument that one person should do everything alone at scale, larger content operations legitimately need specialists. But at the level where most content actually gets planned and shipped, a single person who understands both the search mechanics and the craft of writing consistently outperforms a handoff between two people who each only see half the picture.
I work across both, strategy and execution. If your content and SEO functions feel disconnected, I'd be glad to talk through what that's costing you.
Get In Touch