DEV Community: Writeous

Signs of AI Writing: What Readers Actually Notice (and How to Sound Like You)

Writeous — Sat, 04 Jul 2026 14:32:54 +0000

You've felt it before you could name it.

Three sentences into an email, a post, a landing page, and something goes flat. You're still reading the words, but you've stopped listening. There's nobody in there.

That feeling is the real AI detector. Not the software. You.

And it fires long before you consciously think "a machine wrote this." So if you write with AI (most people now do), the question worth answering isn't how do I beat a detection tool. It's what makes a human reader quietly check out?

Here's what they actually notice.

The signs of AI writing readers pick up on

Forget the tools for a second. These are the tells a real person feels, whether or not they can explain them.

Every sentence is the same length. AI writes in a smooth, even hum. Subject, verb, object. Subject, verb, object. No short punches. No long, winding ones that earn a hard stop at the end. Human writing has a heartbeat. Machine writing has a metronome.

It hedges on everything. "It's important to note." "There are several factors to consider." That's a writer with no skin in the game, because there is no writer. A person who actually did the thing says the specific true thing and moves on.

It opens with throat-clearing. "In today's fast-paced digital landscape." Nobody talks like this. These openers exist to fill the space before a point arrives. A human who has something to say leads with the thing.

It reaches for the same fancy words. Delve. Tapestry. Leverage. Landscape. Realm. Elevate. Seamless. Stacked together they read like a model reaching for the statistically-safe word instead of the true one.

It loves the "it's not just X, it's Y" move. One of those is a nice turn. Six in a row is a tic. Readers clock the pattern even when they can't name it.

Listicle-itis. Every idea broken into a tidy numbered list of exactly three, each with a bolded label and one supporting sentence. Clean. Scannable. Completely without a pulse.

Notice what's not on that list.

The em dash is not the tell

The internet has decided the em dash means a robot wrote it. As soon as some readers see one, they stop reading.

The writer Ann Handley had the best line on this. She described a CEO banning em dashes from company copy to avoid looking like AI, and called the panic what it is: reputational self-surveillance. Her analogy: Batman wears a cape, so by that logic anyone in a bath towel is Batman.

Punctuation is a terrible detector. Plenty of careful humans have used em dashes their whole lives. Plenty of AI slop uses none. Policing dashes just teaches good writers to pre-defend normal choices from imaginary accusations, and does nothing about the actual flatness.

So stop hunting the dash. Fix the real thing: the missing person.

How to put yourself back on the page

The fix for AI-sounding writing is not another tool that "humanizes" text. Running flat words through a second model gives you differently flat words. The fix is you.

Vary the rhythm on purpose. Follow a long sentence with a short one. A fragment. Like that. Read it aloud and let your own breath tell you where the metronome crept back in.

Trade hedges for specifics. Cut "this can often improve results" and name the result. The number, the moment, the thing that happened last Tuesday. A model invents plausible specifics; only you have the true ones.

Take a position. AI argues any side with equal, weightless conviction. Pick one. Say the thing you're a little worried is too strong. That worry is usually the sign it's yours.

Keep the aside only you would write. The joke, the tangent, the oddly specific reference. That's the fingerprint. It's the first thing a model sands off, so it's the first thing you should put back.

Read the whole thing out loud, last. The sentences you stumble over are the ones the machine flattened. Rewrite those in the words you'd actually say.

Where AI belongs (and where it doesn't)

We build an AI tool, so this is the honest part.

AI is genuinely good at the grunt work. The blank-page rough draft you'll mostly throw away. The outline. The tedious job of reshaping one thing you wrote into every format you need to publish it.

That last one is where Writeous lives. You write the piece in your own voice, one markdown file, then paste it in and get back a blog post, a newsletter, an X thread, and a LinkedIn post, each formatted right, in about a minute. It reshapes the words you already chose. It doesn't reach in and average out your point of view.

We'll name the limit too. When your blog runs on Ghost, Writeous re-syncs the published post in place, so editing your source updates what's already live. Social publishing through Typefully works, but a sent post can't be edited after it goes out, so that part is best-effort, not true sync.

The line to hold is simple. Hand AI the mechanics. Keep the thinking, the position, and the specifics for yourself.

The takeaway

The signs of AI writing aren't a font or a dash. They're the sound of nobody being home: even rhythm, endless hedging, borrowed openers, tidy lists with no pulse.

You fix it the same way you'd fix a boring conversation. Say the true, specific thing. Take a side. Sound like a person who cares.

Because the only writing that reads like a human is the writing a human actually showed up for.

Originally published on the Writeous blog.

AI Visibility: How to Get Your Writing Cited by AI, Not Just Ranked

Writeous — Sat, 27 Jun 2026 13:54:20 +0000

This post first appeared on the Writeous blog.

Someone asked ChatGPT a question your blog post answers perfectly.

It gave them an answer. A good one. Sourced, confident, useful.

It just didn't mention you.

That's the new shape of getting found. Google ranks you. AI answers cite you. And those are not the same game, even though everyone keeps treating them like one.

So here's what AI visibility actually means, why most of the old SEO tricks fall flat in an answer engine, and how a writer or a small team earns a citation without trying to game a machine.

What AI visibility actually means

Search used to end with a list of links. You ranked, someone clicked, you got the visit.

AI visibility is what happens when the click disappears.

A reader asks a question. The model writes a paragraph. Somewhere in that paragraph, or in a little "sources" footer, your name shows up as where the answer came from. Or it doesn't.

That's the whole thing. Not "did I rank number one." It's "when the machine explains my topic, am I one of the sources it leans on."

It matters more every month. The slice that's actually in your control is the writing. That's the part you own, and the part a tool can't fake for you.

Why keyword stuffing stopped working here

The old playbook was mechanical. Find a phrase with volume. Repeat it. Hit the word count. Win the slot.

An answer engine doesn't reward that. It can't.

A model isn't scanning for keyword density. It's trying to find the clearest, most trustworthy explanation of a thing so it can compress it into two sentences. When your page is keyword soup wrapped around a thin point, there's nothing to compress. The model skips you for the source that said something.

Here's the uncomfortable part: you can't stuff your way to a citation. You earn one by being the clearest source in the room.

The three things that actually get you cited

A real point of view. Models cite sources that take a position. "Here are ten tips" gets averaged into the soup. "Most newsletters die at issue three, and here's the one reason why" gives the machine something specific to attribute. Say the thing only you would say.

Structure a machine can read. A clear heading that asks the question. A direct answer in the first two lines under it. Short paragraphs. Definitions that stand on their own. You're writing for something that reads like a fast, literal reader. Make the answer easy to lift.

Consistency across where you show up. When the same clear idea appears on your blog, in your newsletter, in a thread, the signal compounds. The model sees one coherent source, not a person who said three half-things in three places.

The honest limits

You can't buy your way into an AI answer, and you can't reverse-engineer the exact recipe. Anyone selling you a guaranteed "get cited by ChatGPT" package is selling you 2012 SEO in a new hat.

What you can do is be the source worth citing. Clear point of view. Clean structure. The same idea, said the same way, everywhere you publish.

Where Writeous fits

You write one source doc in markdown, and Writeous turns it into a properly formatted blog post, newsletter, X thread, and LinkedIn post in about a minute, each one carrying the same clear idea.

Connect your blog and Writeous can publish and re-sync it in place: edit the source, push again, the live post updates. True sync for your blog, best-effort for social, because a sent post can't be unsent and we'd rather say so.

One clear idea, the same spine across every channel. That's the writing an answer engine actually reaches for.

Free to try. Write once. Publish everywhere. Actually.

The Best Blog Post Template Is the One You Can Reuse Everywhere

Writeous — Thu, 25 Jun 2026 13:51:22 +0000

Originally published on the Writeous blog.

You downloaded a blog post template once.

Maybe twice.

A neat little skeleton: intro, three subheads, conclusion, "insert CTA here." You filled it in for your first post. Felt organized. Felt like a system.

By post three, you stopped opening it.

Here's why: most templates are scaffolding for the wrong building. They tell you where the walls go but nothing about why anyone would walk in. So you outgrow them the second you have something real to say.

The fix isn't a better skeleton. It's a structure that does two jobs at once: it makes the post good, and it makes the post reusable.

What a blog post template should actually do

A template is supposed to remove decisions, not add them.

When you sit down to write, the expensive choices are: where do I start, what's the one idea, and how do I keep someone reading. A good template answers those before you type a word. A bad one just gives you boxes to fill, which is how you end up with a tidy, forgettable post that hits every section and lands nowhere.

So strip the template down to the parts that earn their place:

The hook. One concrete, slightly tense line. Not "In today's fast-paced world." A specific moment your reader recognizes. This is the whole game. If the first line doesn't pull, the rest doesn't get read.

The promise. Right after the hook, tell them what they'll walk away with. Plainly. "Here's a structure you'll actually reuse." People stay when they know where you're taking them.

One idea per section. Each subhead earns its keep by making one point and handing off to the next. If a section is doing two jobs, split it. White space is a feature, not a gap.

The slippery slide. Borrowed from old-school copywriting: every line exists to make the next line irresistible. Short paragraphs. The occasional fragment. Momentum over polish.

The soft close. A turn that lands, then one clear next step. Not a hard sell stapled to the bottom.

That's it. Five parts. Notice there's no "insert three benefits and a stock photo." This template is about movement, not slots.

The mistake that kills reusable templates

Here's the trap, and it's a sneaky one.

When the structure is too rigid, every piece you write starts to feel identical. Same intro shape, same CTA in the same dead corner, same rhythm. Your reader's eye learns the pattern and glides right past the parts that matter. There's a name for this in copywriting circles: the "PS hole," where your offer always lands in the same safe spot at the bottom and quietly disappears because readers learn exactly where to skip.

A reusable template isn't a fixed mold. It's a flexible spine. The five parts stay, but where the point of view lives, where the ask goes, where you break the rhythm on purpose, that moves. The structure carries you; it doesn't flatten you.

So treat the template as a rhythm you can play, not a form you fill out.

The part nobody puts in the template: reuse

Now the move that makes a blog post template worth keeping.

Most templates stop at the blog post. But you're not just writing a blog post. You're writing a newsletter, an X thread, and a LinkedIn post too, usually about the same idea, usually as four separate late-night rewrites.

That's the real waste. Not the writing. The re-writing.

Here's the better way to think about it: write the post once, in a plain markdown file, and treat that file as the source. The same hook becomes the first line of your thread. The same promise becomes your subject line. The one-idea-per-section structure becomes the beats of your LinkedIn post. You're not starting over four times. You're reshaping one good thing into four rooms.

The template makes the post good. The single source file makes it travel.

That reshaping step is exactly where Writeous lives. Write your post once in markdown, using the spine above. Paste the file in, and get back a blog post, a newsletter, an X thread, and a LinkedIn post, each formatted correctly for where it's going, in about a minute. It reshapes the words you already wrote. It doesn't make you write them four times. Free to try, no login.

And we'll name the limit, because we always do: when your blog runs on Ghost, Writeous re-syncs the published post in place, so editing your source updates what's already live. Social publishing through Typefully works too, but a sent post can't be edited after it goes out, so that part is best-effort, not true sync.

The takeaway

A blog post template you can reuse everywhere isn't a tighter skeleton. It's a flexible spine, hook, promise, one idea per section, the slippery slide, a soft close, that keeps your writing moving instead of boxing it in.

Build the post on that spine. Keep one markdown file as the source. Then let the same words become every channel, instead of writing them from scratch at midnight.

Write once. Publish everywhere. Actually.

Writing Voice: How to Find Yours (and Keep It When You Use AI)

Writeous — Tue, 23 Jun 2026 13:51:44 +0000

Originally published on the Writeous blog.

You've read two posts on the same topic this week.

One you forgot before you finished it. The other you sent to a friend.

Same subject. Same facts. The difference wasn't the information. It was the voice. One sounded like a press release. The other sounded like a person who'd actually thought about the thing and couldn't wait to tell you.

That's the whole game. And it's the one thing a tool can't hand you.

What your writing voice actually is

Your writing voice is not a vibe. It's a set of choices you make so consistently that readers could recognize you with your name removed.

It's the words you reach for. The length of your sentences. The jokes you can't help making. The opinion you hold a little too strongly.

Most people think voice is something mysterious you either have or don't. It isn't. It's a pattern. And patterns can be found, named, and reused.

The reason it feels mysterious is that you can't see your own pattern from the inside. The same way you can't hear your own accent, you can't hear your own voice on the page. You need a way to step outside it.

How to find your writing voice

Voice is excavated, not invented. You already have one. The work is getting it out of your head and onto the page without sanding it flat.

Write the way you talk. Open a doc and explain your topic to one specific person, out loud, then type what you said. The cadence you use when a friend asks "wait, why does that matter?" is your voice. The cadence you use when you're trying to sound smart is somebody else's.

Read it aloud. The fastest voice tool there is. The sentences you stumble over are the fake ones. Cut them. The lines that sound like you when you say them are the keepers.

Name your tics. Read five things you've written. Look for what repeats. Do you open with a tiny scene? Lean on one-line paragraphs? Always end on a turn? Those repeated moves are your voice, made visible. Write them down. Now they're a recipe instead of an accident.

Cut the borrowed phrases. "In today's fast-paced world." "At the end of the day." Nobody talks like this. These slide in when you stop writing and start performing writing. Every one you cut, your real voice gets one notch louder.

Where AI flattens your voice

We build an AI tool, so this is the awkward part to admit. But pretending otherwise would be its own kind of fake.

AI models are trained to be agreeable and average. They predict the most likely next word, and the most likely word is the unsurprising one. Your voice lives in the unlikely words. The weird specific detail. The fragment that breaks the rhythm on purpose. The opinion you weren't sure you should say out loud.

Hand the whole job to a model and it smooths all of that away, because smoothing is what it's built to do. You get the average of everything ever written on the subject. Competent. Forgettable.

So don't hand it the parts that are supposed to be yours:

The point of view is yours. AI argues any side with equal conviction because it has no skin in the game.
The specific details are yours. The number, the name, the moment from last Tuesday. AI invents plausible-but-false specifics, and that's the worst thing you can publish.
The final read-aloud is yours. The places you stumble are where a model flattened you back to average. Rewrite those in your own words.

Let AI take the busywork: the rough draft you'll mostly discard, the outline, the reshaping of one piece into the formats you need. Keep your hands on the thinking and the voice.

Make your voice survive the reformat

Here's the trap that quietly erases voice: you write something good, in your real voice, then rewrite it from scratch for your newsletter, then again for an X thread, then again for LinkedIn. Four rewrites, four chances to flatten yourself back to average, usually late at night when you're tired and willing to settle.

The fix is to write once, in your voice, and reshape the same words for each room instead of rewriting them.

That reshaping is where Writeous lives. Paste one markdown file, the one you wrote in your own voice, and get back a blog post, a newsletter, an X thread, and a LinkedIn post, each formatted right for its platform, in about a minute. It reshapes the words you already chose. It doesn't average out your voice. Free to try, no login.

We'll name the limit too: when your blog runs on Ghost, Writeous re-syncs the published post in place, so editing your source updates what's live. Social publishing through Typefully works, but a sent post can't be edited after it's out, so that's best-effort, not true sync.

The takeaway

Your writing voice is a pattern, not a gift. Find it by talking instead of performing, reading aloud, and naming the moves you already make.

And when you bring in AI, keep the point of view, the real details, and the final read for yourself. Hand it the grunt work, never the voice.

Do that, and your writing keeps sounding like a person. Because it is one.

Write once. Publish everywhere. Actually.

The best time to post on X is a trap. Here's what actually moves reach.

Writeous — Sat, 20 Jun 2026 13:52:42 +0000

You found the chart. The one that says 9:47 a.m. on a Tuesday is the magic window.

So you set an alarm. Write the post the night before. Hover over the button at 9:46, hit publish at 9:47 on the dot.

Eleven likes. From the same eleven people.

Here's what the chart never tells you: the time you post barely moves your reach. The first line of your post moves your reach. Spend your energy on the clock instead of the hook and you're tuning the radio in a car with no engine.

Why the best time to post on X doesn't matter like you think

The "best time to post on X" advice assumes a feed that hasn't existed in years.

Old Twitter was reverse-chronological. Post at the right minute, catch the most live eyeballs. The clock genuinely mattered.

X today is algorithmic. Your post doesn't expire at the bottom of a timeline. It gets shown to a small test pool first. If those people stop, reply, or repost, it gets shown to a bigger pool. Then bigger. A good post from 11 p.m. on a Sunday can still be spreading Monday afternoon.

So the question isn't "what minute do I post." It's "what makes the test pool stop scrolling." That's a writing problem, not a scheduling problem.

The three levers that actually move reach

1. The first line. You get one line before the "show more" cutoff. It has to create enough tension that stopping feels involuntary.

Weak: "Some thoughts on consistency in content."
Strong: "I posted every day for 90 days. Most of it was forgettable. Three posts did 80% of the work."

Same idea. One earns the next line. One doesn't.

2. The early signal. The algorithm watches the first 30 to 60 minutes, and replies count more than likes. Write posts people can answer, not just nod at. End on a question, a spicy claim, a fill-in-the-blank.

3. Showing up at all. The account that posts one sharp thing a day beats the account that dumps ten on Monday and vanishes till Friday. Reps sharpen your hooks. Notice what's not on this list: the clock.

A sane cadence you can actually keep

Post once a day. One genuinely good thing beats five reposts.
Roughly when your people are awake. Late morning or early evening in your audience's main time zone. "Fine" is the goal. Stop hunting for the magic minute.
Reply for 20 minutes after. Highest-leverage post-publish move, and the one the charts never mention.
Repurpose, don't reinvent. Most days you shouldn't write from scratch.

That last point is where people quietly fall apart. They burn out not from posting at the wrong time, but from trying to invent a brand-new thought every single day.

The real unlock: one source, many posts

Write one substantial thing a week. A blog post, a long newsletter, a teardown, a story. One file you actually thought about.

Then treat it as a quarry, not a one-time event. The same idea becomes a post Monday, a different angle Wednesday, a thread Friday. You're not winging it daily. You're mining one good source from a dozen directions.

That's the workflow Writeous is built around: paste one markdown file, get a blog post, newsletter, X thread, and LinkedIn post, each formatted right for where it's going. Connect your Ghost blog and re-pushing an edit updates the published post in place. (Social is best-effort, not true sync, because a sent X post can't be edited. We'd rather say so than pretend.)

So, when should you post?

Whenever you'll actually do it consistently.

Pick a slot that fits your real life, show up daily, spend your obsession on the first line instead of the clock, and reply when people show up.

The best time to post on X isn't a time. It's the next time you have something worth stopping for.

This post first appeared on the Writeous blog.

30 Newsletter Ideas for When the Cursor Is Blinking and You Have Nothing

Writeous — Thu, 18 Jun 2026 13:57:56 +0000

Originally published on the Writeous blog.

It's Tuesday. The newsletter goes out Thursday. The cursor is blinking and you have nothing.

You scroll your own brain looking for a topic. Everything sounds either too obvious or too big. So you open a "100 newsletter ideas" listicle, skim 40 of them, feel slightly worse, and close the tab.

Here's the thing: you don't have an ideas problem. You have a sorting problem.

"What should I write about?" is impossible. "What am I trying to do for the reader this week?" is answerable in about ten seconds.

So this isn't a pile of 100 random prompts. It's a small bank of ideas sorted by intent. Pick the job first. The topic falls out of it.

Newsletter ideas, sorted by what you're actually trying to do

There are really only four jobs a newsletter issue can do. Teach. Tell. Curate. React. Almost every great issue you've ever read is one of those four, done well.

Teach (you know something they don't)

The one mistake you see beginners make, and the fix.
A process you do on autopilot, broken into numbered steps.
"Here's how I'd do X if I were starting today."
A myth in your industry, named plainly, then dismantled.
The three tools you actually use, and the one overhyped one you quit.
A before-and-after: a thing you got wrong, then how you fixed it.
A glossary issue: five terms your audience pretends to understand.
The decision framework you use when X happens, written as if/then.

Pick something small enough to finish. Depth on a narrow thing beats a shallow tour of a wide one.

Tell (a story only you have)

People forward stories. They rarely forward tips.

The time something went wrong and what it cost you.
A decision you almost made differently, and what tipped it.
What you believed a year ago that you no longer believe.
A behind-the-scenes look at how the thing actually got made.
The reader who changed how you work.
A win that looked like luck but was really a system.
The boring habit that quietly changed everything.
"I tried the thing everyone recommends. Here's what actually happened."

Curate (you did the reading so they don't)

Three things you read this month that are still rattling around your head.
A swipe file of one thing done well, with a line on why each works.
The five links you keep sending people in DMs.
A roundup of what changed this week, with your one-line take on each.
Tools or books you'd hand a younger version of yourself.

The value is in the take, not the list. Don't just point. Point and tell them why.

React (something happened, and you have an opinion)

A hot take on the news everyone in your niche is talking about.
"Everyone's doing X. Here's why I'm not."
A respectful disagreement with advice that's become gospel.
Your honest review of a tool or trend, the parts nobody mentions.
A pattern you've noticed that nobody's named yet.

When you genuinely have nothing

Answer the question you get asked most.
Reply to one subscriber's email in public (with permission).
Reshare your best old issue with a fresh intro.
Ask one good question and tell people to hit reply.

Two rules that make any of these work

First: pick one idea, not three. The panic comes from holding five half-ideas at once. Commit to one and the issue writes itself.

Second: watch where you bury the point. Don't always tuck your actual point or offer into the PS at the bottom, where it shrinks to nothing. Put the point where it can't be skipped. Sometimes the first line. Just not always the same forgotten corner.

The repurposing shortcut hiding in this list

Each of these ideas is a single point, written once. And a single point doesn't have to stay a newsletter.

That "one mistake beginners make" issue is also an X thread. The decision story is a LinkedIn post. The swipe file is a carousel. You wrote one thing. It can show up in four places, formatted right for each.

That's the workflow we built Writeous around. Paste one markdown file, get a blog post, a newsletter, an X thread, and a LinkedIn post, each formatted for where it lands, in about a minute. Connect your blog and your X account and publish from one place. Edit the source, re-push, and your blog post updates in place. Social is best-effort, since a sent post can't be unsent, but your owned channels stay in sync.

So the next time the cursor is blinking, don't reach for the big idea. Reach for the small job.

Pick the job. The newsletter is already half-written.

LinkedIn formatting that actually sticks (markdown in, real bold out)

Writeous — Tue, 16 Jun 2026 14:45:52 +0000

You wrote a great post in markdown.

Clean headers. Tight bullets. A bold line that lands.

Then you pasted it into LinkedIn.

And LinkedIn ate it alive.

Your ## headers became literal hash marks. Your **bold** kept its asterisks. Your bullets collapsed into one gray wall of text.

Here's the thing: LinkedIn has no markdown. None. The box you type into is plain text. Always has been.

So if you want bold, italics, and bullets that survive the paste, you have to know what LinkedIn actually reads. Let's fix it.

LinkedIn post formatting: how to keep your markdown (the part nobody tells you)

LinkedIn doesn't support markdown. But it does support Unicode — and that's the loophole.

When you see a "bold" LinkedIn post, you're not looking at bold text. You're looking at different characters. They're called Unicode Mathematical Alphanumeric Symbols, and they happen to look like bold and italic letters.

So **Hire me** doesn't become bold. It becomes 𝗛𝗶𝗿𝗲 𝗺𝗲 — a string of separate glyphs that your eye reads as bold.

That's the whole trick. Three things to translate:

Bold → swap each letter for its bold Unicode twin.
Italic → swap for the italic Unicode twin.
Bullets → markdown - and * aren't recognized, so use a real bullet character (•, ◦, ▸) plus a manual line break.

Do it by hand and it's tedious. Do it wrong and half your letters render as empty boxes on mobile. But do it right and your post reads like it was designed.

The catch most "formatter" tools won't mention

Unicode bold has a cost: screen readers can't read it.

To assistive tech, 𝗛𝗶𝗿𝗲 𝗺𝗲 isn't "Hire me." It's a pile of math symbols, often read out one alien character at a time — or skipped entirely.

So a rule worth keeping: use Unicode bold for a word or two of emphasis. Never for whole sentences, never for your hook, never for anything a reader actually needs. Whitespace and short lines do more for readability than fake-bold ever will, and everyone can read them.

That's the honest version of "format your LinkedIn post." Most tools sell you the trick and skip the caveat.

A faster way to get there

If you write in markdown already, converting every post by hand is a tax you pay forever.

That's the gap Writeous fills.

Paste one markdown file. Get back a blog post, a newsletter, an X thread, and a LinkedIn post — each formatted for where it's going, in about 60 seconds. The LinkedIn version handles the Unicode conversion for you, with the emphasis kept tight on purpose. No login to try it. Free.

And if you sign in, it goes further. Connect your Ghost blog and you get the thing schedulers never gave you: edit the source markdown, re-push, and your published post updates in place. True sync for your blog. (X is best-effort — a sent post can't be edited, and we won't pretend otherwise.)

The takeaway

LinkedIn formatting isn't broken. It's just plain text wearing a Unicode costume.

Now you know the rules:

LinkedIn reads no markdown — only characters.
Unicode bold is a glyph swap, not real formatting.
It breaks screen readers, so keep it to a word or two.
Whitespace beats fake-bold every time.

Write it once. Format it right for every place it lands.

Actually.

One good post is a week of content. You just haven't unpacked it yet.

Writeous — Fri, 12 Jun 2026 14:44:37 +0000

You publish a post. It's good. It took you most of a day.

It goes up on your blog.

And then... nothing. It sits there. One URL, hoping people stumble across it.

Meanwhile you're already staring at the next blank page, because the content treadmill doesn't care that you just shipped something good. It wants more. Tomorrow.

Here's the thing nobody tells you when they say "just repurpose your content":

One good post is already a week of content. You just haven't unpacked it yet.

Not by rewriting it five times. By reshaping the thing you already wrote for the places your readers actually are.

Here's the playbook.

Start with the post. Not the calendar.

The mistake is planning a week of separate ideas — a tweet Monday, a LinkedIn thing Tuesday, a newsletter Thursday. Five blank pages. Five fresh starts. No wonder it feels like a second job.

Flip it.

Write one real thing — the blog post you'd be proud to put your name on. Make it good. That's the source. Everything else is a projection of it onto a different surface.

One idea. Many shapes. Not many ideas, half-formed.

Pull the thread out of it (literally)

Every solid post has a spine — the three or four points that carry the argument.

Those points are your X thread.

Not the post chopped into 280-character chunks. The skeleton, rewritten to stand alone: a cold-open hook, one idea per tweet, a turn at the end. The thread is a trailer for the post, not a hostage version of it.

Lead with the sharpest line you wrote. Make people need tweet two.

Reshape it for LinkedIn — different room, different voice

Same spine. Different physics.

LinkedIn rewards the first two lines (everything after is behind a "...see more" fold) and punishes walls of text. So you take the post's core insight, open with a concrete moment, and write short. Generous whitespace. One thought per line.

It's not your blog post pasted into a feed. It's the same truth, told to someone scrolling on their phone between meetings.

Lift the takeaway into a newsletter

Your newsletter isn't a blog post with a "Hi friends" stapled on top.

It's more personal. It has a subject line doing the heavy lifting (your markdown doesn't even have one). It earns the open, delivers the one idea, points back to the full post for anyone who wants the depth.

Short. Warm. A single click-through. That's the job.

Now you have four assets. From one afternoon.

Count them:

The blog post (the source of truth)
An X thread
A LinkedIn post
A newsletter

Space them across the week and one good writing day becomes five days of presence. You stopped feeding the treadmill and started leveraging the work you already did.

But here's the part that quietly kills this workflow in practice:

The reformatting is the tax

Reshaping one post into four formats — by hand — is its own afternoon. You're counting characters for the thread. Stripping markdown LinkedIn won't render. Fighting your email tool's formatting. Re-chopping when a tweet runs long.

By the time you've done it twice, the "free leverage" doesn't feel free anymore. So most people do it once, get tired, and go back to publishing in one place and hoping.

That's the exact gap I built Writeous to close.

Paste one markdown file. Get the blog post, the newsletter, the X thread, and the LinkedIn post back — each shaped right for where it's going, in about a minute. No login. Free.

So the workflow above stops being a chore you talk yourself out of, and becomes the thing you actually do every time you publish.

The takeaway

You don't need more ideas. You need to stop leaving your best one on a single page.

Write the post once. Then meet your readers everywhere they already are — in the format each platform actually wants.

Write once. Publish everywhere. Actually.

Markdown to X thread: the rules nobody writes down

Writeous — Tue, 09 Jun 2026 14:44:21 +0000

You wrote a post you're proud of. Now you want it as an X thread.

So you copy the first paragraph. Paste it into the composer.

"Tweet exceeds character limit."

You start hacking. Cut a clause. Cut another. Now it reads like a ransom note. You paste tweet two — it ends mid-sentence. Tweet three has a heading floating at the top like a typo. Your link broke across the seam. Somewhere in the middle, a code snippet detonated into raw backticks.

Twenty minutes later you have nine tweets that sound nothing like the thing you actually wrote.

Here's the thing: a thread isn't your post chopped into 280-character pieces. It's a different format with its own rules. And almost nobody writes those rules down.

So here they are.

Rule 1: 280 is not your budget. ~275 is.

Every tweet in a numbered thread carries a prefix — 1/, 7/12, whatever convention you use. That prefix eats into the limit.

If you write right up to 280 and then number the thread, your longest tweets blow past the ceiling and X rejects them. You find out one at a time, by hand, at tweet six.

Reserve the room up front. Write to ~275 and let the numbering live in the slack.

Rule 2: Never split a URL across two tweets.

A link that breaks across a tweet boundary doesn't become two half-links. It becomes zero links. The first half isn't clickable; the second half is gibberish.

The fix is a rule, not a vibe: a URL is atomic. It lives entirely inside one tweet or it doesn't go in. If the tweet's too full, the link bumps to its own line — never to the next tweet.

Rule 3: Your code block can't come along.

Paste a fenced code block into X and you get the worst of both worlds: no monospacing, no syntax highlighting, and the backticks show up as literal backticks.

A thread can't render code. So don't make it try.

Summarize what the code does in plain language, and point to where the actual code lives. "Here's the three-line fix" belongs in the blog. In the thread, it's: "The fix was three lines — swap the synchronous init for a deferred one. Link below."

Rule 4: Headings don't survive — and shouldn't.

## Rule 4 is a blog affordance. It tells a scanning reader where they are.

A thread reader isn't scanning. They're being pulled, one tweet to the next. A bare heading sitting at the top of tweet four breaks that pull — it's a speed bump with no road behind it.

Translate the heading into a hook instead. Don't announce the section. Start it.

Rule 5: The first tweet is the whole ballgame.

In a blog post, your headline did the selling and the first paragraph can warm up.

A thread has no headline. Tweet one is the headline, the lede, and the promise — in 275 characters, while it competes with the entire timeline.

If tweet one doesn't earn tweet two, nothing downstream matters. Spend your editing time here. It's worth more than the other tweets combined.

Notice what all five rules have in common: none of them are about writing. They're about translation. The same idea, re-shaped for where it's going to land.

Which is exactly the part that's mind-numbing to do by hand — and exactly the part a machine should do.

That's the boring problem we built Writeous to handle. Paste one markdown file. Get back a blog post, a newsletter, a LinkedIn post, and an X thread — each one formatted for where it's going, in about a minute. No login.

For the thread specifically, the rules above aren't suggestions in the output — they're enforced. Every tweet is guaranteed under 280 after numbering. URLs never split across a seam. Code blocks get summarized, not pasted. And the thread is renumbered deterministically at the end, so you can't end up with a 4/ that's secretly the fifth tweet.

It's free right now. The honest roadmap: connect your blog, your newsletter, your socials, and push the formatted versions out from one source — edit once, sync everywhere. That sync is clean for blogs and newsletters. For append-only feeds like a posted thread, it's best-effort by nature — you can't un-send a tweet. We'd rather tell you that than pretend otherwise.

But the thread-formatting part — the five rules nobody writes down — works today.

Write once. Publish everywhere. Actually.

You fixed the typo. It's still wrong in four places.

Writeous — Mon, 08 Jun 2026 13:55:16 +0000

You finish the post. Finally.

You paste it into your blog. Reformat it for the newsletter. Chop it into an X thread. Strip the markdown for LinkedIn.

Four versions. One idea. You hit publish on all of them and lean back.

Then you see it.

A typo. Right there in the second sentence.

And now it's wrong in four places — and you get to fix it four times, in four tabs, by hand.

Here's the thing nobody tells you about publishing:

The writing was the easy part.

I built Writeous to kill the first half of that pain — paste one markdown file, get all four formats, each shaped right for where it's going. It's live. It's free. People use it.

But formatting four versions was never the whole problem.

You still have to place them. Four tabs. Four publish buttons. And the second anything changes, four copies to chase down.

So here's what I'm building next.

Connect your channels once. Publish from one screen.

Your blog. Your newsletter. Your socials. Linked up, so a post goes everywhere — in the right format for each — without the tab circus.

And the part I actually care about: your file is the source of truth.

Schedulers keep copies. Copies drift. Copies lie.

Writeous won't. Your markdown file stays canonical. Fix the typo in the source, and the posts it published fix themselves.

Edit once. Sync everywhere.

That's not a scheduler. It's a single source of truth for everything you publish.

Now, the honest part — because you're builders, and you'd smell a lie:

Publishing APIs are a swamp.

Some platforms let you cleanly update a post you already shipped. Blogs, newsletters — sync works perfectly there.

Others are append-only. You can't un-send a tweet. So "sync" there means the next one's right — not retroactive magic.

I'd rather show you exactly where the seams are than pretend there are none. Handling each platform's reality, gracefully and honestly, is the whole game.

The reformat engine is live today, free to try. The publish-and-sync layer is what I'm building now.

If "write once in markdown, publish everywhere, fix it once and stay in sync" is a workflow you'd want — grab early access, and play with the free tool while you're there.

You did the hard part. You wrote.

The rest should just… happen.

Your markdown doesn't survive the trip: formatting gotchas for X, LinkedIn, newsletters & blogs

Writeous — Mon, 08 Jun 2026 13:46:32 +0000

You wrote a great post in markdown. Clean headings, tidy links, a code block or two. Then you go to share it — and the real work begins.

Because markdown doesn't survive the trip. Each platform mangles it a different way, and "just paste it" quietly breaks your formatting in four directions at once. Here's what actually happens, platform by platform.

X / Twitter — there is no markdown, and there's a wall at 280

Paste your post and your **bold** becomes literal asterisks, your headings vanish into the void, and your 1,200-word essay becomes one un-tweetable blob. To thread it properly you have to manually chop it into ≤280-char segments, decide where the breaks land, lead with a hook, and number them so people can follow. By hand, every time.

LinkedIn — it renders no markdown, and rewards skim-ability

LinkedIn strips it all: no #, no **, no [text](link). Headings collapse, emphasis disappears, and link syntax shows up as raw [brackets](and-parens). The format that works is the opposite of a blog — short lines, generous whitespace, a hook in the first two lines before the "…see more" fold.

Your newsletter — structure, not styling

Email clients are a formatting minefield, so newsletters want simple structure over rich markup: a subject line (which your markdown doesn't have), short paragraphs, clear sections. A wall of blog prose lands very differently in an inbox.

Your blog — the one place markdown belongs… mostly

Here your hierarchy and links should survive — if your renderer is configured for it. But images, relative links, and footnotes are where pastes silently drop things.

The through-line: the writing was done the moment you finished the draft. Everything after is reformatting labor — the same idea, reshaped four times, by hand, every single time you publish.

That's the problem I got tired of, so I built Writeous: paste one markdown file, get a blog post, a newsletter, an X thread (auto-split, numbered, hook-first), and a LinkedIn post (markdown stripped, built to skim) — each formatted right for where it's going, in about 60 seconds. No login to try it.

This very post? Written as one markdown file. The X and LinkedIn versions promoting it were made by Writeous itself.

Write once. Publish everywhere. Actually.