There is a sentence at the bottom of most affiliate posts that nobody believes. You have read it a thousand times. This post may contain affiliate links. I may earn a commission if you buy through them. It sits below the sign-off, above the copyright, in the same grey font as the privacy policy. It is technically a disclosure. It is also a hedge, and the hedge is the tell.
The instinct behind it is understandable. You want to be honest without sounding like a billboard. You want to be cautious, so you write may. You want to be unobtrusive, so you put it at the end. And you end up with a line that sounds like it was written by someone who is not quite sure whether they are selling something, which is precisely the impression you were trying to avoid.
The UK’s advertising regulator has looked at this exact phrasing and found it wanting. In a 2022 ruling about MailOnline articles, the Advertising Standards Authority considered that the phrase “may earn an affiliate commission” was ambiguous and confusing, because it suggested the publisher might not receive any payment when, barring administrative error, they would receive commission for purchases made through the links. The cautious word may was the problem. It implied uncertainty where there was none.
So the safe-sounding line is also the dishonest-sounding one. That is the real problem this piece is about, and it is a writing problem before it is a compliance problem.
Start with the floor, because it is lower and simpler than the anxiety around it suggests. The US Federal Trade Commission’s guidance for endorsers says that if you endorse a product, your message should make it obvious when you have a relationship with the brand — what the FTC calls a “material connection.” That connection includes a financial relationship, such as the brand paying you or giving you free or discounted products or services.
The FTC is specific about placement. Disclosures are likely to be missed, it says, if they appear only on an about page, at the end of posts or videos, or anywhere that requires a click on “more.” The disclosure should be placed with the endorsement message itself. And the language should be simple: the FTC offers “Thanks to Acme brand for the free product” as an example that is often enough, if placed where it is hard to miss.
It also warns against the vocabulary that has grown up around this. Vague or confusing terms like “sp,” “spon,” or “collab,” and stand-alone terms like “thanks” or “ambassador,” are not good disclosures. The disclosure should be in the same language as the endorsement itself.
The UK guidance runs in the same direction. The Competition and Markets Authority says its rules apply to creators who have received a product free or at a discounted rate, or other incentives such as direct payment or commission, regardless of follower count. That last clause matters for anyone running a blog with hundreds of readers rather than hundreds of thousands. The ASA adds that affiliates are effectively acting as secondary advertisers, because they earn in direct proportion to the interest they generate in a product.
None of this is exotic. Disclose the relationship. Make it hard to miss. Put it where the reader encounters the recommendation, not in a footer. Use plain words. That is the standard.
Here is what none of them give you: a sentence.
They give you a standard — clear, prominent, before engagement, plain language — and then they stop. The FTC’s native advertising guide is explicit that its examples are general guidance and do not provide a safe harbor from liability. The ASA’s advice page says its recommendations are not intended to be exhaustive or prescriptive, and that other approaches may be equally acceptable. So there is no approved wording to copy. There is a job to do, and the words are yours to choose.
That is not a loophole. It is the recognition that context changes what honesty sounds like. A disclosure that reads as frank on one blog reads as defensive on another. The regulators set the floor; the voice is a craft decision, and treating it as a compliance checkbox is why so many disclosure lines read like they were written by a lawyer who has never met the reader.
This is craft guidance, not legal advice. Rules differ by jurisdiction and change over time. If your situation is complicated, that is a conversation for someone qualified to have it with you.
Look again at the line you probably have somewhere on your site. May earn a commission. The word may is doing something strange. It is there to sound careful, but what it actually communicates is that the writer is not sure of their own position. And a reader who senses uncertainty about the commercial relationship will start to wonder what else is uncertain.
The ASA’s ruling on the MailOnline phrasing is useful precisely because it names the mechanism. The hedge implied the publisher might not get paid. But they would get paid. The line was less accurate than the blunt version would have been.
There is a related problem with the word affiliate itself. In a 2020 ruling about an Instagram Story, the ASA noted that the term “affiliate” was not widely understood by consumers, based on its own labelling research. A standalone “*affiliate” label was not sufficient to make the content recognisable as an ad. So the vocabulary that feels most precise to those of us inside the system is often the least clear to the people outside it.
Which leaves the sentence in an awkward spot. The cautious words are misleading. The technical words are opaque. What is left is the thing you would actually say.
I am not going to hand you a sentence to paste in, because a pasted sentence is the same problem in a new font. What I can offer is a way to arrive at your own, and a test to run it through.
The method has four moves. Name the relationship. Name what you get. Put it where the link is. Read it aloud as if to a friend.
Take a vague line and work it. Suppose the original reads: This post may contain affiliate links. It names nothing, promises nothing, and hedges everything. A first pass might be: Some links in this post earn me a commission if you buy. Better — it names the mechanism and drops the hedge — but it still does not say which links, and it still sounds like a form.
A second pass, placed inline next to an actual link: If you buy this through the link above, I get a small percentage. It costs you nothing extra. That is a sentence a person would say. It names the relationship, names what you get, and answers the question the reader is actually asking, which is whether clicking costs them more.
These rewrites are illustrative, not drawn from any source. The point is the direction of travel: from hedge to specific, from footer to link, from system vocabulary to human vocabulary.
The test is the read-it-back test. If a reader clicked the link, bought the thing, then came back and read your line, would they feel you had been straight with them? That test is stricter than the legal floor and cheaper than a lawyer, and it is the one that actually protects the thing a small blog runs on.
This is the most actionable thing in the sources and the one most commonly gotten wrong. The ASA is unusually concrete here: a disclaimer at the bottom of a post is unlikely to be sufficient, because the links and any connected claims would not be obviously identifiable as advertising at the moment the reader encounters them. The FTC says the same thing in different words — disclosures are likely to be missed if they appear only at the end of posts.
A footer disclosure is easier to write once and forget. An inline disclosure has to be placed every time. That is the whole trade. The footer is a filing cabinet; the inline line is a conversation.
There is a second placement question, about the post as a whole. The ASA distinguishes between content that wholly concerns affiliate-linked products and content where only some links are affiliate. Where the entire post is affiliate content, the commercial nature should be clear before the reader engages — the most straightforward way being an identifier like “Ad” in the title, visible before the click. Where only some links are affiliate and not all the content is directly connected to the product, a general “Ad” in the title is unlikely to be necessary, but the affiliate content and the links themselves should be identifiable as advertising.
That second case is the one that matters most for a mixed personal blog. Most of us are not running all-affiliate content. We are writing a genuine post — a book we read, a tool we use, a thing that solved a problem — and two or three links in it happen to be affiliate links. The guidance for that case is more permissive than the all-affiliate case and more useful: mark the specific links, do not brand the whole post.
The ASA suggests that placing an identifier such as “(Ad)” before the parts that relate to affiliated products is likely to be acceptable, as is stating clearly at the beginning that asterisks or other markers in the article indicate advertising, or that the author will receive a small share of sales through the related links. What it rules out is the generic, ambiguous disclaimer that says the author may receive a commission, particularly where the specific affiliate content has not been highlighted.
There is a version of this advice that assumes you are running a review site, where every post is a product post and the whole page is commercial. If that is you, the all-affiliate guidance applies and an “Ad” identifier in the title is the straightforward move.
But if you are running a personal blog — the kind where a reader comes for the voice and stays for the archive — the mixed case is your case. And the mixed case has a specific shape. The post is editorial. Two links in it are commercial. The reader needs to know which is which, at the moment they meet each one.
This is where the one-sentence discipline pays off. You are not writing a disclosure for the post. You are writing a disclosure for the link. It sits next to the link, it says what the link is, and it gets out of the way. The rest of the post stays yours.
There is a temptation to over-disclose in the other direction — to put a banner at the top of every post just in case, to hedge the whole page so no individual line has to be precise. The ASA’s ruling on the MailOnline articles is a useful caution here: a disclaimer at the top was judged insufficient, not least because the phrasing was ambiguous. Volume is not the same as clarity. A precise line next to the link does more work than a vague line above the fold.
It is worth remembering what a disclosure is not. It is not a shield. The FTC’s native advertising guide says plainly that it does not provide a safe harbor from potential liability. You cannot write a magic sentence that makes the question go away.
What the line is for is smaller and more durable than that. It is the one place in a commercial post where your interest and your reader’s interest are the same sentence. You want them to know what the link is. They want to know what the link is. The disclosure is not a tax on the relationship. It is the relationship, stated.
That is why the hedge fails. A hedge is written for an imagined regulator, not for the reader. It protects the writer from having said too much, which is the opposite of what a trust asset needs. A blog measured in hundreds of readers does not run on reach. It runs on the sense that the person writing it is a person, and that the person is not pretending.
So the sentence is worth getting right, not because a regulator is watching, but because the reader is. The reader is the one who will notice whether you meant it.
Pick one post on your blog with an affiliate link in it. Find the disclosure line. Read it aloud. If it sounds like a form, rewrite it as the sentence you would say to a friend who asked whether you get paid for that link. Then move it so it sits next to the link, not at the bottom of the post. That is the whole experiment. One post, one line, one placement.
If the new line feels too blunt, sit with that feeling for a moment before softening it. The bluntness is usually the honesty, and the softening is usually the hedge coming back.
Do I need to disclose if I bought the product myself and just happen to be in an affiliate program? The FTC’s guidance addresses the case where you have no brand relationship and are simply telling people about a product you bought and like — in that case you do not need to declare that you have no brand relationship. But if you are in an affiliate program and a link earns you commission, that is a financial relationship, and the disclosure applies. The ASA’s framing is useful: you are acting as a secondary advertiser, because you earn in proportion to the interest you generate.
Does a disclosure at the top of the post cover all the links in it? Not necessarily, and this is where the ASA is more specific than most advice. Where only some links are affiliate, the guidance points toward marking the specific links rather than branding the whole post. A top-of-post line can work if it clearly explains what the markers in the article mean — for example, that asterisks indicate affiliate links. A vague top-of-post line that does not identify which links are commercial is the kind of thing that has been ruled insufficient.
Is “affiliate link” good enough as a label? The ASA’s labelling research found that the term “affiliate” was not widely understood by consumers. It is precise to us and opaque to many readers. A phrase that says what happens — that you receive a share of the sale — is clearer than the industry term.
Do platform disclosure tools count? The FTC says not to assume that a platform’s disclosure tool is good enough, though it can be used in addition to your own disclosure. The tool is a backstop, not a substitute.
Does any of this change if my audience is small? The CMA guidance applies regardless of follower count. The size of the audience does not change the obligation. It does change the stakes of getting the tone right, because a small audience is a relationship, and a relationship is what the line is protecting.
This piece is craft guidance based on published regulator material, not legal advice. The sources cited are the FTC’s Disclosures 101 for Social Media Influencers and its Native Advertising: A Guide for Businesses, the UK Competition and Markets Authority’s guidance for content creators, and the ASA’s advice page on online affiliate marketing. Rules differ by jurisdiction and change; check the current guidance for your situation.
There is a particular kind of email that arrives when your blog has been alive long enough to look like a place where things happen. It is polite, it is brief, and it contains the word “collaboration” in a way that suggests neither of you will be doing any actual collaborating. The offer is usually a product you have never used, a fee that is not nothing, and a deadline that is sooner than you would like.
What follows is the rubric I use now. It is not a growth strategy. It is a way to make a decision in about ten minutes and then get back to writing.
Before anything else, there are two things the U.S. Federal Trade Commission says plainly, and they are worth reading in the original rather than in paraphrase. The first is about disclosure. If you endorse a product and you have a material connection to the brand — which includes being paid, or being given free or discounted products — your endorsement message should make that relationship obvious. The FTC’s guidance for social media influencers puts it this way: “If you endorse a product through social media, your endorsement message should make it obvious when you have a relationship (‘material connection’) with the brand.” A material connection includes “a personal, family, or employment relationship or a financial relationship – such as the brand paying you or giving you free or discounted products or services.”
The second constraint is about honesty, and it is the one people skip past. The same FTC guidance says: “You can’t talk about your experience with a product you haven’t tried. If you’re paid to talk about a product and thought it was terrible, you can’t say it’s terrific.” It also says you cannot make up claims that would require proof the advertiser does not have — the example given is scientific proof that a product can treat a health condition.
Those two constraints are the floor. They are not the whole rubric, but they are the part where the answer is not up to you.
The FTC is specific about placement in a way that matters for a blog. Disclosures should be placed so they are hard to miss, and they should sit with the endorsement message itself. The guidance notes that disclosures are likely to be missed if they appear only on an about page, at the end of a post, or anywhere that requires a click to see.
This is where a lot of small-blog sponsorship posts quietly fail. The disclosure goes in the footer, or in a line at the bottom that says something like “this post contains affiliate links.” The reader who encounters the recommendation at the top of the post has already formed an impression before reaching the note. The FTC’s native advertising guide makes the underlying principle explicit: “A basic truth-in-advertising principle is that it’s deceptive to mislead consumers about the commercial nature of content.” And: “If a disclosure is necessary to prevent deception, the disclosure must be clear and prominent.”
For a blog post, that means the disclosure belongs near the top, in the same visual register as the recommendation itself. Not in a smaller font. Not in a color that blends into the background. Not after the reader has already decided whether to trust you.
The UK’s Advertising Standards Authority, which regulates a different market but arrives at a similar place, is even more direct about the failure mode. Its guidance on affiliate marketing says that where content wholly concerns affiliate-linked products, the commercial nature should be clear before the reader engages with it, and that a straightforward way to do this is an identifier such as “Ad” in the title. It also says a disclaimer at the bottom of a post is unlikely to be sufficient, because the links and the claims connected to them may not be obviously identifiable as advertising at the moment the reader encounters them. A generic disclaimer that the author “may” receive a commission is unlikely to be acceptable, particularly where the specific affiliate content has not been highlighted.
So the first question in the rubric is not “can I disclose this?” It is “would the disclosure be hard to miss if I placed it where it needs to go?” If the answer is no — if the disclosure would have to be buried to keep the post feeling natural — the offer has already failed.
I run through these in order. The first two are legal constraints. The rest are craft constraints, which is to say they are about whether the post would be worth reading.
1. Would the disclosure be hard to miss in the post itself? Not on the about page. Not in the footer. In the post, near the top, in plain language. If the answer is no, stop here.
2. Have I used the product long enough to say something true about it? The FTC’s constraint is that you cannot talk about your experience with a product you have not tried. But “tried” is a low bar. A single afternoon with a product is enough to have an experience; it is rarely enough to have a useful one. The question I actually ask is whether I could describe a specific moment of using it, including a moment where it did not work the way I expected. If I cannot, I do not have a recommendation. I have a description.
3. Does the offer require claims I cannot support? This is the one that filters out most of the bad offers before they reach the writing stage. If the brief asks me to describe a product as clinically proven, or to imply it solves a problem it has not been tested on, or to repeat a claim the advertiser cannot substantiate, the answer is no regardless of the fee. The FTC guidance is clear that you cannot make up claims that would require proof the advertiser does not have. But the practical version is simpler: if I would have to hedge every sentence, the post is not worth writing.
4. Would I write this post if there were no fee? This is not a purity test. It is a test of whether the post has a reason to exist beyond the sponsorship. If the only reason the post would appear on the blog is that someone paid for it, the reader can tell. They may not be able to articulate why, but they can tell.
5. Does the offer require me to change how the blog works? Some offers come with expectations about posting frequency, format, or tone that would require the blog to become a different blog. A single sponsored post that fits the existing rhythm is one thing. A sponsorship that requires a new content category, a new voice, or a new publishing schedule is a different thing. The second kind is almost never worth it at small scale, because the cost is not the post. The cost is the disruption to the thing that made the blog worth reading.
At a certain scale, a sponsorship is a transaction between a brand and a media property. The reader knows they are reading a media property. The disclosure is a formality, and the relationship between writer and reader is mediated by the fact that both parties understand the arrangement.
At a small scale, the relationship is different. The reader is not reading a media property. They are reading a person, or at least the sustained performance of one. The trust that makes the blog worth reading is not distributed across a large audience in a way that can absorb a bad recommendation. It is concentrated. A single post that reads as unearned spends something that took years to accumulate, and the reader who feels it does not write a complaint. They just stop coming back, quietly, in a way you will not notice for months.
This is why the disclosure is not overhead on top of the recommendation. It is part of the recommendation’s credibility. A reader who trusts writing at this scale is trusting a person. A disclosure that reads as boilerplate — a line of small print that exists to satisfy a rule — costs more proportionally than it would at scale, because it signals that the writer is thinking about the rule rather than the reader.
The same logic applies to the recommendation itself. A sponsored post that reads as a description of a product the writer has not really used is not a neutral event. It is a withdrawal from an account that only has so much in it.
I do not have a specific declined offer I can point to with a brand name and a date, because I did not keep records of the ones I turned down, and I am not going to invent one. But I can describe the shape of the offers that fail the rubric, as a composite rather than a case record.
Suppose a company that sells a sleep supplement emails about a sponsored post. The fee is modest but real. The brief asks for a personal account of how the product improved the writer’s sleep, with a link to the product page and a discount code for readers. The deadline is two weeks out.
Run the rubric. The disclosure could be placed clearly, so question one passes. Question two fails immediately: I have not used the product, and two weeks is not enough time to have a useful experience with a sleep supplement even if I started that day. Question three fails as well: the brief asks for a claim about improved sleep, which is a health claim, and the FTC guidance specifically names scientific proof of treating a health condition as the kind of claim an advertiser cannot simply assert. Question four fails: I would not write this post without the fee. Question five is borderline, but it does not matter, because the earlier questions have already decided it.
The whole assessment takes about four minutes. The reply takes two. The rest of the morning is still available for the writing that the blog actually runs on.
Declining a sponsorship is not a statement about the brand. It is not a moral judgment about sponsorship in general. It is not a claim that small blogs should not take money. It is a craft decision, made quickly, in service of the thing that makes the blog worth reading.
The reason to have a rubric is not to feel good about saying no. It is to make saying no fast and non-dramatic, so that the decision does not consume the writing time it is meant to protect. A rubric that takes an hour to apply is not a rubric. It is a second job.
There is also a version of this that applies to the offers you accept. The same questions, run in the other direction, tell you whether a sponsorship is worth doing. If the disclosure can be clear, if you have used the product long enough to say something true, if the claims are supportable, if you would write the post anyway, and if the offer does not require the blog to become a different blog — then the answer is probably yes, and the fee is a reasonable exchange for work you were going to do.
The rubric is not a wall. It is a filter. Most things should pass through it. The ones that do not were never going to be good posts.
Write the five questions down somewhere you will see them the next time an offer arrives. Not as a policy document. As a note to yourself, in your own words, about what you would need to be true in order to write the post honestly.
The next time the email comes — and it will — you will have already made the decision. The only thing left is to send the reply and get back to work.
Does the FTC guidance apply to a blog with a small audience? The guidance does not set a minimum audience size. It applies to endorsements, and the question is whether there is a material connection between the endorser and the brand. A blog with a small audience is still a blog making recommendations to readers.
What counts as a material connection? The FTC describes it as including a personal, family, or employment relationship, or a financial relationship such as being paid or receiving free or discounted products or services. If you received something of value in connection with mentioning a product, that is the relevant fact.
Where should the disclosure go in a blog post? The FTC says it should be hard to miss and placed with the endorsement message itself, not only on a profile page, at the end of the post, or behind a click. For a blog post, that generally means near the top, in the same visual register as the recommendation.
Is a footer disclaimer enough? The FTC guidance suggests disclosures are likely to be missed if they appear only at the end of posts. The ASA’s guidance on affiliate marketing is more explicit for its market, saying a disclaimer at the bottom of a post is unlikely to be sufficient because the reader may not see it at the moment they encounter the relevant content.
Can I accept a free product and write about it without disclosing? No. The FTC guidance says to disclose the relationship if you got anything of value to mention a product, and to make a disclosure even if you were not asked to mention that product.
What if I tried the product and did not like it? The FTC guidance is direct: if you are paid to talk about a product and thought it was terrible, you cannot say it is terrific. The honest version of the post is the one where you say what you actually found, which may mean the sponsorship is not worth accepting in the first place.
Do I need to keep records of offers I decline? There is no general requirement to keep records of declined offers. The practical reason to keep a short note is for your own pattern recognition — to see which kinds of offers keep arriving and whether your rubric is filtering them efficiently.
There is a page in my notebook, dated last April, that lists three unfinished posts. I know the date because I wrote it in the corner the way you write a date when you are trying to convince yourself the list is temporary. One post was about why I stopped checking analytics. One was about a comment I never answered. One was a long, tangled piece about what fifteen years of the same blog has actually taught me about attention. Rereading that page recently, I noticed something I hadn’t expected: the discomfort wasn’t about the writing. It was about the rereading. Each draft still had a pulse. Each one still sounded like something I wanted to say. They had simply stopped moving.
That distinction — stopped, not dead — is where this essay lives. Because when I finally sat with why those three pieces stalled, and what role a drafting tool might honestly play in unsticking them, I found that most of the conventional advice about both problems is wrong in the same direction. It assumes the problem is production. It is almost never production.
The standard explanation for a stalled draft is mechanical: you ran out of time, or ideas, or discipline. The hustle-culture version adds a solution that is somehow both vague and demanding — build a content calendar, batch your writing, ship daily. None of it addresses what I think is the real engine of a stalled draft, which is closer to what Seth Godin describes when he writes about modern vanity: the shame attached to being “not enough.” As he puts it, “avoidance has no floor. The threat of not-pretty (or not-competent, not-respected or any other imagined failure) is always right behind you. You can never outrun it permanently.” A draft sitting in a folder is a draft nobody can judge. Publishing it is the moment the judgment becomes possible. So the draft waits, and the waiting feels like prudence when it is mostly fear wearing a cardigan.
Godin’s question is the useful one: “If you didn’t care about blame or credit, what would you ship?” The answer tells you what you’re withholding. When I asked it honestly about my three stalled posts, the answer was all three. They stalled not because I lacked the skill to finish them but because finishing them meant being seen holding a position. That is a different problem, and it needs a different response than a content calendar.
But there is a second reason drafts stall that has nothing to do with shame, and it matters for what follows. Sometimes a draft stalls because it has no spine. The idea is real, the material is real, but the structure is missing — the piece doesn’t know yet whether it’s an argument, a story, or a letter. Blogging, as I’ve written before on this site, is a form of thinking: “When I write a blog post, I’m not just telling you what I know. I’m discovering what I know.” A draft with no spine is a draft where the thinking hasn’t found its sequence yet. That is a structural problem. It is genuinely hard, and it is also — and this is the part that surprised me — the one place where a machine can help without doing anything that feels like cheating.
Before opening any drafting tool, it’s worth triaging the stalled draft by cause. A draft with no spine is a structure problem. A draft with no you is a voice problem. They can look identical from the outside — both are unfinished — but they need opposite treatments.
A voice problem means the sentences are competent but anonymous. You reread a paragraph and cannot find yourself in it. No tool fixes this, and any tool that promises to is promising to replace you, which is the one thing a personal blog cannot survive. The whole premise of keeping one blog for years is that the voice is the moat. A blog is “your home base — the one piece of internet real estate you actually own,” as this site has argued before, and what makes that real estate worth owning is that it sounds like a specific person. A tool that smooths your sentences into a competent average is not scaffolding. It is demolition with good manners.
A structure problem is different. Here the voice is intact — you could read any paragraph aloud and recognize yourself — but the paragraphs are in the wrong order, or the piece has three possible shapes and hasn’t chosen one. This is where I let a machine touch one of my drafts, and I want to be precise about what that looked like, because the word “used” covers too much ground.
For the long stalled piece — the one about fifteen years of attention — I tried a drafting tool for structural help only. Specifically, I ran the idea through the Unsloppy AI Book Writer, an AI book writing tool, to see what kind of outline it would propose for the material. I want to be careful here: this is one instance, not a verdict on the tool, and I’m not claiming it improved my writing. What it did was hand me a proposed sequence of sections — a shape — that I then argued with for an hour. I kept two of its headings as questions, deleted the rest, and rewrote everything in my own words. The outline functioned as a set of prompts for my own thinking, not a substitute for it. That, I’ve decided, is the honest definition of scaffolding: the tool proposes, you dispose, and every sentence that reaches the reader is one you wrote and would defend.
Ghostwriting is the mirror image. Ghostwriting is publishing prose you did not write, would not have written, and cannot defend if a reader asks you about it. The line between the two is not fuzzy. It is a single practical test: could you explain, in your own words, why every sentence in the published piece says what it says? If a reader emailed you about a paragraph and you’d have to check what the tool meant, the tool crossed the line.
There’s also an administrative edge to this that’s worth knowing about, even for a small blog. The distinction between AI-generated material and an author’s own contribution is becoming a formal one, not just an ethical intuition. As The Passive Voice has reported, copyright registration now asks writers to disclaim AI material and describe their own contribution, and Amazon KDP requires authors to report AI-generated text, images, and translations. None of that necessarily applies to a personal blog. But the direction is clear: the world increasingly expects writers to know exactly where the machine’s work ends and theirs begins. Practicing that knowledge on a stalled draft is cheaper than learning it under pressure later.
Here is a bounded version of what I did, small enough to try this week and reversible enough to abandon without ceremony. Pick one stalled draft — just one. Before opening anything, decide which problem it has. Read two paragraphs aloud. If you can’t hear yourself in them, close the draft and be done for the day; that’s a voice problem, and it needs you, not software. If you can hear yourself but the piece has no shape, open a drafting tool and ask it only for structure: an outline, a sequence, a set of section questions. Then close the tool’s prose out of your mind entirely and rewrite every sentence by hand. Publish only what still sounds like you — or shelve it, honestly, if it doesn’t.
To make “still sounds like you” concrete, here is a clearly hypothetical example of the test in action. Suppose the tool proposes a section heading like “Key Benefits of Slow Blogging.” If your natural instinct is to wince — because you would never write “key benefits” about something you consider a practice, not a product — that wince is the test working. You rewrite the heading as a question you actually have (“What does slow cost me that I don’t mind paying?”) and write toward that instead. The tool gave you a slot; you gave it a soul. If, on the other hand, you find yourself keeping the tool’s sentence because it says the thing better than you would — stop. That sentence is not yours, and keeping it is the first small withdrawal from the only account that matters.
Because that is what a small blog actually is: an account of trust, deposited one honest post at a time over years, read by a few hundred or a few thousand people who came for a person. The cost of a ghostwritten post is not a one-time embarrassment. It is a slow erosion of the thing that took a decade to build — the reader’s quiet assumption that the byline means something. No tool is worth that, and no stalled draft is either. The three posts on my notebook page are still unfinished as I write this. One now has a spine, argued over with a machine and rewritten entirely by hand. The other two are waiting, and I’ve stopped pretending the waiting is about time. It’s about nerve. That, at least, is a diagnosis. The machine can’t supply the nerve. Neither, honestly, can the notebook. But between the two of them, one draft moved, and it still sounds like me — which is the only test I’d trust in ten years, and the only one I’d suggest you run this week.