Content Marketing
Blog and article writing that earns rankings
We write long-form articles that rank and get read. Each piece is researched, answers a question your buyers actually ask, and links to the service page that turns the reader into an enquiry.
Who it is for: Businesses that know they need content but lack the time or writers to produce it well.
Everything in this service
- Researched articles from 1,000 words up
- On-page optimisation: headings, structure, internal links
- Answer-first formatting that AI engines can quote
- Real sourcing, no invented claims or statistics
- Editorial review on every piece before delivery
What to expect
- Articles that rank for the questions your buyers ask
- Topical authority that lifts your whole site
- A publishing rhythm you no longer have to push uphill
How blog writing actually works
What a writer should know before the first sentence
Research is most of the job. A writer who opens a blank document and starts typing produces the article that already exists a hundred times over. The work that makes a piece worth reading happens before the draft.
Four inputs go into every brief. First, what already ranks for the query, read properly rather than skimmed: what those pages cover, what they all assume, and what none of them answer. That last gap is usually the reason to write at all. Second, the actual language buyers use, taken from support tickets, sales call notes, review sites and forum threads, because the words customers use are rarely the words the industry uses. Third, primary source material: the standard, the regulation, the platform documentation, the study. Fourth, and most valuable, fifteen minutes with the person in your business who does the thing. That conversation is where the specifics come from, and specifics are the only durable advantage a piece of content has.
The brief that comes out of this names the query, the reader, the promise, the structure, the sources, and the internal links. If a writer cannot answer what this piece says that the top results do not, the brief is not finished and drafting should not start.
- Read the current top results properly, and note what they all miss
- Collect real customer language from support, sales and reviews
- Gather primary sources before drafting, not during editing
- Interview the internal expert for fifteen minutes
- No draft starts until the brief names the gap it fills
The answer-first opening, and why the warm-up paragraph fails
The first job of an article is to answer the question in the title, in the first two or three sentences, before any context. Almost every business blog does the opposite and opens with a paragraph about how the industry has changed in recent years. That paragraph is a cost with no benefit.
Readers arriving from search have already decided what they want. If the first thing they see is throat clearing, they go back and pick a different result, and that behaviour is visible. Giving the answer immediately does not stop people reading on. It does the reverse, because a page that has already been useful earns the benefit of the doubt for the next thousand words, which is where the nuance, the exceptions and the how lives.
Answer-first structure also travels better into AI answer engines. A page that states its conclusion in a self-contained paragraph is easier for these systems to read and quote than one where the answer is assembled from scattered clauses across six screens. That is a directional advantage, not a promise. No one can guarantee that a given page gets cited by a given assistant, and any agency that says otherwise is selling something it cannot deliver.
- Answer the title question within the first three sentences
- Cut any opening paragraph about how the industry has evolved
- Make each key paragraph make sense if lifted out on its own
- Put the caveats after the answer, not in front of it
- Treat improved extractability as a likely benefit, never a guarantee
Structuring an article so it can be scanned and extracted
Almost nobody reads an article top to bottom on the first pass. They scan the headings, stop where their question appears, read that section, and then decide whether the rest is worth their time. Structure is therefore not decoration, it is the interface.
Headings should be written as the questions readers ask, in their words. A heading that reads how much does it cost is more useful than one that reads pricing considerations, because it matches the thought the reader arrived with. Keep the heading levels honest: one H1, H2 for each major question, H3 only for genuine subdivisions. Paragraphs run two to four sentences. Anything longer becomes a wall on a phone, and most of your readers are on a phone.
Lists, tables and short definition blocks do real work here. A comparison belongs in a table because a table is how the comparison is actually thought about. A sequence belongs in a numbered list. A set of parallel options belongs in bullets. Used where the content genuinely has that shape, these formats speed up reading. Used to break up prose that has no such shape, they just make an article look like a slide deck. The test is simple: if the bullets would read better as a sentence, write the sentence.
- Headings as reader questions, in reader language
- One H1, H2 per major question, H3 only for real subdivisions
- Two to four sentence paragraphs, checked on a phone screen
- Tables for comparisons, numbered lists for sequences
- A short summary near the top for anyone who reads nothing else
Sourcing and specificity: where credibility comes from
Credibility is built from specifics that can be checked, and destroyed by one number that cannot. We do not invent statistics, we do not repeat figures we have not traced to a primary source, and we do not attribute claims to studies we have not read.
This matters more than it used to. A great deal of marketing writing now consists of numbers that circulate between blogs, each citing the last, with no original behind them. They are easy to spot once you look, because following the citation chain leads to another blog post rather than to a study. When a piece of content puts one of those numbers in front of a prospect who knows the field, the damage is not a small correction. It is the assumption that nothing else on the site is checked either.
The alternative is not vagueness. Direction can be stated honestly without a false precision: costs vary widely by market and by competition, this approach usually shows results in months rather than weeks, this technique underperforms in our experience. Where a real source exists, name it, date it, and say what it measured and what it did not. A cited study with its limits stated reads far stronger than a bare percentage floating in a sentence.
- No number is published without a primary source someone has read
- Name the source and the year, and say what it actually measured
- State direction honestly when a precise figure does not exist
- Use concrete examples and named tools rather than abstract claims
- Never present a hypothetical result as something that happened
The editing passes, and what each one is for
Editing is several different jobs, and trying to do them at once is why editing feels endless. Separating them into passes makes each one fast, because each pass has a single question.
The structural pass asks whether the piece answers the question and whether the order is right. This is where whole sections get moved, merged or cut, and it has to come first. Rewriting sentences in a section that will later be deleted is wasted effort. The line pass asks whether each sentence earns its place. Long sentences get split. Passive constructions get turned around. Qualifiers and filler go. The fact pass checks every claim, number, name, price and link against the source. The voice pass reads the piece aloud, listening for anything that sounds like a brochure rather than a person. The final pass is a plain proofread, ideally by someone who has not seen the draft before, because a writer reads what they meant to write.
One more check belongs at the end. Read only the headings, in order. If they do not tell a coherent story on their own, the structure is still wrong no matter how good the prose is.
- Structural: does it answer the question, is the order right
- Line: split long sentences, remove filler and hedging
- Fact: every claim, number, name and link verified
- Voice: read it aloud and cut anything that sounds like a brochure
- Proofread: fresh eyes, last, on the final version
Why length follows the question, not a word target
Word count targets produce padding, and padding is visible to readers within about ten seconds. The right length is the length the question needs, which we decide from the intent rather than from a number in a brief.
Some questions are short. What is the file size limit for a platform upload is a two hundred word answer with a table, and stretching it to fifteen hundred words to hit a target makes it worse for everyone. Other questions are genuinely large. How to plan a year of content for a business with one marketing person is a decision with a dozen dependencies, and a short answer would be dishonest. The signal is usually in what the query implies about the reader: a definition query wants brevity, a how-to query wants completeness, a comparison query wants the differences laid out rather than two summaries.
The useful way to think about it is coverage rather than count. Does the piece answer the question, the obvious follow-up questions, and the objection the reader will raise before acting? If yes, it is finished, whether that took eight hundred words or three thousand. If a section exists only because the piece felt short, it should be cut. Trimming a good article by a quarter almost always improves it.
- Match depth to intent: definitions short, decisions long
- Answer the follow-up questions, not only the headline one
- Cut any section that exists to reach a number
- Test for coverage of the topic, not for word count
- A trimmed article usually reads better than the original
A clear path, step by step
- 01
Brief
We agree the goal, audience, format and references, so edits are on target.
- 02
Produce
We edit and design with platform best practice built in from the start.
- 03
Review
You review against the brief. We revise quickly with clear version control.
- 04
Deliver and learn
Final files for every platform, plus what the performance tells us for next time.
Why choose us for this
Writers who research before they write
Plain, human voice, no filler or jargon
Every article structured for search and AI citation
Common questions
How long should a blog post be?
As long as the question needs, no longer. Some queries deserve 2,000 words, some 800. We match depth to intent rather than padding to a word count.
Who owns the content you write?
You do, fully, on delivery. Publish it, edit it, repurpose it. There are no licensing strings.
Will the articles sound like our brand?
Yes. We build a short voice reference from your existing material and any guidelines, and every piece is edited against it.
Explore related work
Want this for your business?
Book a free visibility call and I will tell you honestly whether I can help.
How this is delivered
One person leads every project. Where a job genuinely needs a specialist, I bring in people I have worked with before and manage them, so you get one point of contact and one invoice rather than three suppliers blaming each other.
- You talk to the person responsible for the work, not an account manager
- Specialists are briefed and managed by me, and their work is checked before it reaches you
- One contract, one invoice, one place to chase