Common Substack Notes Mistakes (And How to Avoid Them)

You post a Note on Tuesday, it gets four likes, and you quietly decide that format doesn't work. You post the next one on Friday because Friday is when you happened to be at your desk. You write it as one punchy line because one line feels confident. Three months later the account is the same size it was in April, and you still can't say which Note did anything.

Most Substack Notes mistakes are not writing mistakes: they are small, repeatable habits that cap how far a Note can travel, and almost all of them are measurable. This piece walks through the seven that show up most often, with numbers from a sample of 20,000 recent Notes where the data has something to say, and a specific fix for each one.

One number worth having before you start: WriteStack has close to 100 verified reviews from Substack writers across multiple platforms. The other tools in this category have none that we could find anywhere. That matters here, because most of the advice about Notes mistakes is one person's guess about their own account.

Table of Contents

• Mistake 1: Writing Every Note as a Single Line
• Mistake 2: Keeping Notes Too Short
• Mistake 3: Judging a Note by Its Like Count
• Mistake 4: Posting Only When You Happen to Be at Your Desk
• Mistake 5: Never Restacking Anyone Else
• Mistake 6: Posting Only Self-Promotional Content
• Mistake 7: Over-Polishing Until It Sounds Generic
• The Seven Mistakes, and What Actually Fixes Each One
• A Quick Self-Audit
• How These Mistakes Compound
• What Six Weeks of Fixing These Actually Changes

Mistake 1: Writing Every Note as a Single Line

The single-line Note feels like the native format. One sharp sentence, no scrolling, nothing wasted. It reads like confidence, and it is the most common shape on the feed.

It also loses. Across a sample of 20,000 recent Substack Notes, Notes written across multiple lines averaged about 11% more reactions than single-line Notes, and about 28% more restacks. The reaction gap is the smaller story. The restack gap is the one that compounds, because a restack is the only mechanic that puts your writing in front of people who have never heard of you, and a multi-line Note is roughly a third more likely to earn one.

The reason is structural rather than stylistic. A single line gives a reader one beat, and one beat is easy to agree with and easier to scroll past. A Note with a line break has a setup and a payoff. It has somewhere for a specific detail to sit, and the specific detail is the part someone quotes when they restack you. Two or three short paragraphs with white space between them read faster than one dense line, not slower.

Fixing this costs nothing. Take the single line you were about to post, keep it as the opener, and add the thing you left out: the number, the moment it happened, the part you were not sure about. The Note gets longer and lighter at the same time.

Practical rule: if a Note fits on one line with room to spare, you cut the evidence out of it. Put the evidence back.

WriteStack's Notes generator drafts in multi-line shapes by default, reading from Notes and posts you have already published so the structure improves without the voice drifting. Start a free 7-day trial and fix the shape of a whole week of Notes in one sitting.

Mistake 2: Keeping Notes Too Short

This is the first mistake's close relative, and the dataset is blunter about it. In that same 20,000-Note sample, Notes running 150 to 300 characters outperformed Notes under 50 characters by roughly a third on reactions, and by a wider margin on restacks.

Fifty characters is about one short sentence. It is the length of a reaction, not a thought. Plenty of writers land there without deciding to, because brevity has been sold as the whole craft of short-form writing and because a short Note is faster to publish on a busy morning. The feed treats it accordingly: there is nothing in it to argue with, nothing to quote, nothing worth passing along.

The 150 to 300 character band is not long. It is two to four sentences, still comfortably under a screen. That range gives you room for one claim and one piece of support, which happens to be the minimum unit that earns a restack. Going much longer is not automatically better either. The band exists because it holds a complete thought without asking the reader to commit to an essay.

Note length	How it performs on reactions
Under 50 characters	Baseline, and the weakest band in the sample
150 to 300 characters	Roughly a third higher than the sub-50 band, and further ahead on restacks
Multi-line vs single-line	About 11% more reactions, about 28% more restacks

The practical version: write the Note you were going to write, then ask what a skeptical reader would need before they believed it. Add that. You will land in the band without counting characters.

Mistake 3: Judging a Note by Its Like Count

This is the expensive one, and it is invisible while you are making it.

Likes are the number Substack shows you, so likes become the scoreboard. A Note with 40 likes reads as a hit and gets repeated. A Note with six reads as a miss and gets abandoned. The trouble is that likes measure whether someone approved of a Note while scrolling past it, which is close to unrelated to whether that Note sent anyone anywhere. The six-like Note that dropped 30 people onto your archive page did more for the publication than the 40-like Note that ended the conversation where it started.

You cannot see that difference natively. Substack's Notes view will not tell you which link inside a Note got clicked, or how many times, or which of the two links you included did the work. So writers optimize the metric they can see and slowly reshape their writing toward the kind of Note that collects approval instead of the kind that moves people.

WriteStack tracks link clicks across your full Notes history, per link inside each Note, going back to your very first one. That turns "this one performed well" into "this one sent 40 people to the archive, and the second link got all of them." It is the difference between a popularity reading and a traffic reading, and once you have it for three months of Notes, the pattern of what actually converts is usually not the pattern you assumed.

The second half of the problem is worse: even a good number means nothing without a reference point. A 3% restack rate is either strong or weak depending entirely on what publications your size are doing, and your own dashboard structurally cannot answer that question, because it only contains you. WriteStack benchmarks your reactions, restacks, and reply rates against other publications, so "is this good" becomes answerable instead of "is this better than last week." Trend analysis sits on top of that, showing whether the direction is climbing or sliding month over month rather than handing you another snapshot.

Practical rule: before you retire a Note format, check what it did to link clicks. Formats get killed on like counts every week that were quietly the best converters in the account.

Mistake 4: Posting Only When You Happen to Be at Your Desk

Nobody decides to post erratically. It happens because publishing and writing are the same action on Substack by default, so your posting rhythm ends up tracking your calendar rather than your strategy. A busy week turns into two. A good idea at 11pm has nowhere to go, so it goes nowhere. Then a burst of five Notes on a Sunday afternoon tries to make up for it, and the feed treats that burst as one event.

The failure is unpredictability rather than low volume. Three Notes a week held steady for months will beat fifteen Notes crammed into one excited week followed by a month of silence. Distribution on Notes leans on recent, regular activity, and followers build an expectation the same way. Both of those break on gaps, not on modest numbers.

Posting pattern	Typical outcome
3 to 4 Notes a week, held for months	Steady, compounding reach
10+ Notes in one week, then silence	Momentum resets each time
Only when you're at your desk with an idea	Feed and followers stop expecting you

The fix is removing the daily decision. Write four or five Notes in one sitting when the ideas are there, drop them into a queue, and let them publish on a schedule you set once. WriteStack does this through a browser extension that hands each Note to Substack's own native scheduler at publish time, so your session never leaves your browser and nothing runs on someone else's server pretending to be you. The queue and calendar view shows the whole week at a glance, which is the part native Drafts cannot do. WriteStack's heatmap then shows when your specific audience is actually active, so the slots you fill are chosen rather than inherited from whenever you happened to be free. For a fuller diagnostic on what a stalled schedule does to reach, see why your Substack Notes aren't getting views.

Practical rule: pick a posting rhythm you could hold during a bad month, then build a queue deep enough to survive one. A rhythm that only works when life is easy is not a rhythm.

Start your free trial and load next week's Notes before Monday.

The part people don't expect

WriteStack schedules Substack chat posts, which no other tool in this category does at all. It tracks which of the two links inside a Note got clicked, going back to your very first Note, so a Note stops being a like count and becomes a traffic number. And it benchmarks your restack rate against other publications your size, then shows the direction it is moving month over month. Open the dashboard on a Tuesday and see that the Note you almost didn't post drove 40 link clicks, and that your restack rate is running well above typical for a publication your size. Not better than last week. Better than the field.

Mistake 5: Never Restacking Anyone Else

The easiest mistake to fix is also the one writers are least aware they are making. Someone opens Notes, writes their own thought, hits publish, closes the tab. They never restack another writer, never leave a real reply, never treat the feed as a feed. From the outside the account looks like a broadcast channel dropped into a conversation platform.

Notes distribution depends heavily on the people you interact with interacting back, and that only happens if you are present in other people's threads. Restacking someone puts your commentary in front of their followers, which is one of the few organic paths to an audience you do not already have. Writers who never restack anyone have closed that path and then wonder why growth feels stuck.

The fix costs a few minutes: before writing your own Note, scroll the feed and restack or reply to two or three Notes genuinely worth reacting to. For the mechanics of doing this well, see the full guide to restacks. WriteStack's Activity Center pulls replies, restacks, and mentions into one place instead of five browser tabs, which is the difference between doing this daily and meaning to do it daily. The live inspiration feed sits next to it, updating continuously from real Notes data, so what you see on a Tuesday reflects what is working on Substack that week rather than a list someone assembled last year.

Practical rule: if you cannot remember the last time you restacked someone, fix that before touching your own posting schedule or format.

Mistake 6: Posting Only Self-Promotional Content

A feed made entirely of "new post is live" announcements and subscribe reminders reads the way an Instagram account made entirely of ads would. Readers learn to scroll past fast, and the algorithm learns the same thing from the lack of response. The instinct is understandable, since the newsletter is the product, so promoting it feels like the obvious use of every channel available.

Accounts that actually grow through Notes use it as a place to think out loud. A rough split that holds up: four out of five Notes are a genuine thought, story, or opinion from your niche, and the fifth points back at a post when there is a real reason to. The promotional Note works far better when it is rare enough to read as a recommendation instead of routine noise.

This one interacts with the length data from earlier. Announcement Notes are usually short and single-line by nature, which means a feed of announcements is also a feed sitting in the weakest-performing shape in the sample. Two mistakes stacked in the same Note. If you are unsure what a non-promotional Note should look like, Substack Notes formats that actually work breaks down the structures that consistently perform without being an ad for anything.

Practical rule: keep roughly one in five Notes tied to promoting your own post. The rest should stand on their own as something worth reading whether or not the reader ever clicks through.

Mistake 7: Over-Polishing Until It Sounds Generic

This mistake is newer than the others and easy to fall into without noticing. A writer drafts a Note, runs it through a few rounds of editing or a generic AI tool to clean it up, and ends up with something smoother and flatter. The specific detail that made the first draft interesting gets sanded off in favor of a sentence that reads well and says nothing in particular. The polished version is often better written and performs worse, because the rough, specific edge was the thing worth reacting to.

Readers can tell the difference between a Note that sounds like a person had a specific thought on a specific day and a Note that sounds like advice anyone could have written about any topic. The second kind rarely gets a reaction because there is nothing to react to: no opinion to disagree with, no number to check, no evidence a real person wrote it.

Most AI drafting tools make this worse by design, because they generate from a prompt and produce the average of everything ever written about your topic. WriteStack drafts from your own published Notes and posts instead, so the output starts in your voice rather than arriving there after three rounds of editing, and if a draft misses you switch models rather than living with one fixed voice. WriteStack's pricing runs three tiers with AI credits on all of them, and a 7-day free trial on every tier.

Practical rule: if an edit removes a specific detail, number, or opinion to make a Note read more smoothly, that edit made the Note worse.

The Seven Mistakes, and What Actually Fixes Each One

Mistake	What it costs	What fixes it
Judging a Note by likes	You retire your best converters	Link-click tracking across your full Notes history, per link
No reference point for your numbers	"Better than last week" instead of "good"	Benchmarks against other publications your size, plus month-over-month trends
Posting only when you're at your desk	Gaps that reset momentum	A queue and calendar view, filled in one sitting
Posting at inherited times	Notes land when your readers aren't there	A heatmap of when your audience is actually active
Over-polished, voiceless Notes	Nothing to react to	AI drafting from your own published Notes, with model selection
Never restacking anyone	The one organic path to new readers stays closed	Activity Center, replies and restacks in one place
Single-line, sub-50-character Notes	About 11% fewer reactions, about 28% fewer restacks	Two to four sentences with the evidence left in
Verified reviews behind the tool you pick	You are trusting a launch announcement	~100 across multiple platforms for WriteStack, none found for the others

A Quick Self-Audit

Pull up your last ten Notes and check them against the list:

• How many were a single line, and how many ran past 150 characters?
• Can you name which of the ten sent the most people to your publication, or only which got the most likes?
• Did you post on a rhythm someone could predict, or in bursts followed by silence?
• Did you restack or reply to anyone else this week?
• What share of the ten were pure self-promotion?
• Do they still sound like you, or have they been smoothed into something anyone could have written?

Most accounts that feel stuck are failing three or four of these at once. That is normal, and it is also why fixing one thing in isolation often does not move the numbers much.

How These Mistakes Compound

These mistakes rarely show up alone. An account that never restacks anyone tends to post purely promotional Notes too, because both come from treating Notes as a megaphone. An account posting in bursts is harder to read analytics from, because there is not enough regular activity to see a pattern. Short, single-line Notes and a like-count scoreboard reinforce each other directly: one-line Notes collect approval without driving clicks, and a writer watching only likes has no reason to suspect anything is wrong.

The compounding runs the other way too, which is the useful part. Fix the measurement and the shape of your Notes changes on its own, because you can finally see that the longer ones are doing the work. Fix the schedule and you generate the sample size the measurement needs. Two structural changes, and four of the seven mistakes start correcting themselves. For how these pieces fit into a broader growth approach, see how to grow your Substack using Notes.

Practical rule: fix measurement and schedule first. They are the two that make the other five visible.

What Six Weeks of Fixing These Actually Changes

Track one week before you change anything. Write down every Note you posted, its length, whether it was one line or several, and whether you meant to post then or remembered late. Almost everyone who does this finds the same shape: a few strong days, a gap, a catch-up burst, another gap, and a set of Notes that all look like the same short line.

Six weeks in, the change is not that you post more. It is that you stopped guessing. Next week's Notes are written and queued, so the 11pm idea has somewhere to go and Thursday stops being a coin flip. The Note you almost deleted turns out to have sent 40 people to the archive, and you know that because the click history says so. Your restack rate has a number next to it from publications your size, so you know the direction you are moving instead of just the reading. The writing energy that was going into logistics and second-guessing goes into the Notes.

Every mistake on this list is a measurement problem or a schedule problem wearing a writing problem's clothes, and both are the layer WriteStack is built for: a queue you fill in one sitting, chat post scheduling no other tool has, link-click history going back to your first Note, and benchmarks against the field rather than against yourself. Close to 100 verified reviews from Substack writers back that up, and no other tool in this category has any we could find.

Start a free 7-day trial. Fix the seven mistakes in one afternoon, then watch next week go out without you.