One Long Article, Five Short Posts

The article is the asset; the posts are how it travels. Five cuts cover a week without writing anything new.

Last updated: October 24, 2026

A long article isn't one piece of content. It's five, if you cut it the right way. The cut that works isn't the section break — it's the question. Each section of a good article contains two or three arguments, and every argument is a post. One article, five questions, five days. Nothing gets written from scratch, and the article keeps working as the source everything points back to.

Key Takeaways

• Cut by question, not by section. A section holds three arguments and makes three weak posts. A question makes one strong one.
• Five shapes cover a week. The answer, the number, the mistake, the list, the open question — one of each, in that order.
• The figures have to match exactly. Same number, same period, same unit, in the article and in every post that quotes it.
• The article stays the source. Posts carry the claim; the link carries the evidence. Don't restate the whole argument in a caption.
• Schedule the slots, not the inspiration. Five days, one post a day, weekend off — and a sixth slot the following week for whatever performed.

Cut by question, not by section

Open your last article and count the headings. Most pieces have four or five, which looks like a natural set of posts and usually isn't. A heading like "what the fee base contains" covers three separate arguments, each of which needs its own setup. Posted as one block, it reads as a summary nobody finishes.

Now read the piece and write down every question it answers. Not the headings — the questions. "Does the cleaning fee count?" "Which number do I quote to a guest?" "What happens if I change the rate after someone books?" A single article usually answers eight or ten of these. Each one is a post that stands on its own.

The test is simple. Cover the rest of the article with your hand. If the paragraph still makes sense and still says something a host could act on, it's a post. If it needs the previous two paragraphs to land, it's a section, and cutting there produces a fragment.

This is why repurposing fails so often. People export the headings, paste them into a scheduler, and get five excerpts that begin mid-thought. The work isn't formatting. It's choosing which question each post answers before you write a word of it.

There's a second benefit to cutting this way. Questions are what people search, so the cut doubles as a keyword list. If a question doesn't appear in the article at all, that's a gap worth an article later, not a post now.

The five post shapes

Five shapes cover a week, and they're deliberately different in temperament. Same source, different jobs.

The answer. One sentence that resolves the question, then two sentences of why. This is the post that gets screenshotted. It works because it commits — no "it depends" without a follow-up that says what it depends on.

The number. One figure from the article, with its period and its unit attached. "Occupancy ran at 71% in the quarter to June, across nine listings" is a post. "Occupancy was strong" isn't. Numbers travel because they're specific enough to argue with.

The mistake. The thing hosts get wrong, stated plainly, then the correction. This is the highest-engagement shape and the one that needs the most care, because a mistake framed as an accusation gets a different reception from one framed as a common shortcut.

The list. Three to five items, each short enough to read on a phone. Pull it from a section that already has the structure; don't invent a list to fit the format.

The open question. The thing the article couldn't settle, put to the reader. This is the post that produces comments and DMs, and it's the one that gives you next week's material.

Order matters less than variety. Five answer posts in a row train people to skim; alternating a number with a mistake keeps the feed from flattening.

Keeping the numbers identical

The fastest way to lose trust is to quote the same figure two ways. The article says occupancy ran at 71% across nine listings for the quarter to June. A post that says "71% occupancy" without the period is a different claim, and a reader who checks will find the mismatch.

Lock three things on every figure: the value, the period, the population. Then write them the same way each time, including the preposition. "Across nine listings in the quarter to June" is a phrase you can reuse verbatim, and reusing it is the point.

Pick one source view and quote from it. If the figures come from the reports view where occupancy, ADR and RevPAR sit for the whole portfolio, screenshot that view and keep the screenshot as the reference for the week. On localsbnb.com that view is the same place the four connected channels report into, which is why a single screenshot can serve five posts. Every post then quotes one screen rather than a memory of it.

Two habits prevent most errors. Keep a single line in your draft file listing each figure with its period and population, and copy from that line rather than from the article body. And when a number changes — a correction, a restated month — change it in the article first, then in every post, in that order.

There's a version of this that matters more than tidiness. Hosts read these posts to make decisions about price and availability. A figure quoted without its period invites someone to compare two numbers that were never comparable. If you can't state the period, cut the number and use a different shape.

A week of scheduling

Five posts, five days. Monday the answer, Tuesday the number, Wednesday the mistake, Thursday the list, Friday the open question. The order front-loads the two shapes that get saved and shared and ends on the one that generates replies, which gives you something to read over the weekend.

Write all five in one sitting, from the article, before any of them goes out. Writing them one at a time across the week is how the tone drifts and the figures diverge — by Thursday you're working from memory.

Keep one asset per post. The answer takes the article's lead image, the number takes the screenshot, the list takes a plain text card. Reusing one image five times flattens the week; making five new images is how the plan dies in week two.

Leave the weekend empty and use it to read. Whatever got replies becomes next week's first post, and the article gets a small edit where a reader found it unclear. That loop is the actual return on the piece: one article, a week of posts, and a list of questions you didn't know you hadn't answered.

Then repeat with the next article. After a month you have a shelf of posts that all point back to two or three long pieces, which is a better position than twenty posts that point nowhere.

FAQ

Does every post need the full argument?

No, and trying to include it is what makes repurposed posts unreadable. A post makes one claim and links to the article for the reasoning. If the claim can't survive without the reasoning, it isn't a post yet.

Can I reuse the same image across all five?

You can, but the week reads as one post repeated. One image per shape is enough, and the screenshot of the source view does most of the work for the number post.

What if I only publish once a week?

Then run one cut a week and let the article carry five weeks. The shapes still apply; only the spacing changes. What doesn't work is publishing all five on the same day, which turns five posts into one long one.

The article is the part that took the thinking. The posts are the part that gets it read, and they cost an afternoon once the cut is right. If the figures in your articles come from a calendar you already keep for the whole portfolio, localsbnb.com is where that view lives — one calendar for every listing, with the four connected channels sitting in it.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Rules on advertising, on quoting performance figures and on how you describe a property differ by market and by platform. Confirm what applies to you and check the current terms of each channel you use before you publish.