James Ashworth
Why Sharing Is a By-product of Being Useful
Nobody shares a blog post to be kind to the writer. They share it because it makes them look helpful, clever or in-the-know to the person they send it to. That is a slightly cynical framing, but it is a useful one. The moment you accept it, you stop writing posts designed to impress and start writing posts designed to be passed on.
The good news is that shareable posts are not a different species from good posts. They are simply the ones that answer a question clearly enough that a reader thinks: "I know exactly who needs this." Your job is to make that thought easy to have.
Start With the Question, Not the Topic
Most weak blog posts begin with a topic. "Freelance pricing" is a topic. It gives you nothing to aim at. A question gives you a target:
- How much should I charge for a first freelance project?
- What do I do when a client keeps moving the goalposts?
- Should I put my rates on my website?
Notice how much more specific those are. Each one has an implied reader, an implied problem and an implied moment in time. When you know the question, you know what the post must deliver, and the reader knows within two sentences whether it is for them.
A practical method: keep a running list of questions people actually ask you. Not the polished ones you get at networking events, but the scrappy ones that arrive in emails and direct messages at eleven at night. Those are your best headlines. If one person was brave enough to ask, a hundred more are quietly wondering.
Write Headings That Carry Their Own Weight
Headings are the most underrated part of blogging. Many writers treat them as decoration. Readers treat them as navigation, and skimmers treat them as the whole article.
Test each heading by asking whether it tells the reader something. "Pricing" tells them nothing. "Charge for the outcome, not the hours" tells them the argument before they have read a word. The second version is also far easier to share, because someone can quote it.
A few habits worth building:
- Read your headings in order, ignoring the body text. They should read like a list of useful statements, not a table of contents.
- Avoid wordplay that hides the point. Clever is fine, clear is better.
- Keep them short enough to scan on a phone, which is where most of your readers will be.
If your headings alone teach someone something, you have written a post that survives being half-read. That matters more than you might think, because a half-read post that helped is more likely to be shared than a fully read post that meandered.
Be Specific Enough to Be Quoted
Vague advice feels safe to write and useless to receive. "Communicate clearly with clients" could belong to any article on any subject. "Send a one-paragraph recap after every call, listing what you agreed and what happens next" is a sentence someone will screenshot.
Specificity shows up in three places. Numbers, where you have them. Examples, ideally drawn from your own work. And language, using the words your readers actually use rather than the polished synonyms you might prefer.
This is where a lot of freelance writers undermine themselves. We are trained to smooth things out, to sound measured, to avoid committing. But a reader cannot share a post that refuses to say anything. Take a position. Name the mistake. Say which approach you would choose and why.
Write So It Is Easy to Recommend
Think about the moment of sharing. Someone is midway through a message to a colleague and wants to drop in a post that supports their point. Anything that slows that down costs you a share.
So make the piece easy to summarise. Give a short, plain opening that states the problem and the promise. Keep the structure visible. Put the most useful idea early, not buried two-thirds of the way down. And finish with something the reader can act on this week, rather than a vague encouragement to keep going.
It also helps to write in a voice a reader would not mind being associated with. Blunt is fine. Smug is not. If your post makes the sharer feel superior to the person they are sending it to, they will hesitate.
Edit for the Reader Who Arrives Late
Most of your readers will find the post weeks or months after you publish it, with no context about your week or your mood. Read your draft as though you are that person. Does the opening make sense without the backstory? Are the examples self-contained? Have you explained the terms you use casually with your regular readers?
Two passes will do most of the work. In the first, cut anything that exists to make you look good rather than help the reader. In the second, read only the headings and the first sentence of each paragraph. If that skim still delivers the argument, the post is ready. If it does not, the structure needs work before the sentences do.
Sharing is not something you bolt on at the end with a prompt or a button. It is the natural result of a post that respects the reader's time, answers a real question and says something worth repeating.
