Blog

  • How to turn one blog post into six social media posts

    Writing a good article takes hours. Promoting it with a single “new post on the blog” message wastes most of that effort. Here is a simple way to get six distinct, useful social posts from one article, without repeating yourself.

    1. The quote

    Find the sharpest sentence in the article, the one you would underline. Post it on its own. A strong line works without context and makes people curious about the rest.

    2. The fact

    Pick one concrete number or finding and state it with its source. Only use facts you can back up. A sourced fact is shareable; an unsourced one invites doubt.

    3. The question

    Turn a point from the article into a question readers can answer from their own experience. Questions start conversations that a link alone never does.

    4. The tip

    Extract one practical step that works without reading the article. Readers get value immediately, and some will click for more.

    5. Behind the scenes

    Explain why you wrote it, what prompted it, or what changed between the first draft and the final one. This is the most personal post of the six and often the most engaging.

    6. The summary

    Three short lines covering the main argument, plus the link. This is the classic promotion post, but now it arrives after five others that built interest.

    Scheduling them

    • Spread the six posts over about two weeks.
    • Adapt each for the network: shorter on Bluesky and X, more context on Mastodon and LinkedIn.
    • Put the summary with the link early and again at the end, so latecomers can find the article.

    A calendar view helps you see the whole set at once and avoid two angles on the same day. That is what we built GPTpost for: oraglegpt.org.

  • Email, calls, review links or full trust: comparing client approval methods

    Every agency and freelance social media manager ends up with a mix of approval habits, usually shaped by what each client prefers. It is worth comparing them honestly, because the method a client likes is not always the one that produces good posts on time.

    Email with screenshots or a document

    Good: familiar, needs no tool. Weak: versions multiply, feedback is scattered across replies, and it is unclear which text was finally approved. Screenshots also hide the per-network differences.

    A weekly call

    Good: builds the relationship and allows quick discussion. Weak: decisions live in memory or meeting notes, and a cancelled call delays a whole week of posts. Calls work best for strategy, not line-by-line approval.

    A review link

    Good: the client sees the exact text for each network, approves or comments in place, and does not need an account. Approval is recorded next to the post. Weak: some clients need a nudge to open it, which is why a fixed deadline matters.

    “Just post it, we trust you”

    Good: fast. Weak: trust is easy to give and painful to lose. One misjudged post and the next month is all calls and emails. If you agree to this, keep an internal review stage so a second person still checks.

    A practical combination

    Many agencies settle on a monthly strategy call, weekly review links with a deadline, and a short internal review before anything reaches the client. That keeps the relationship personal and the approvals traceable.

    GPTpost supports multi-stage approvals and review links that need no client account. Learn more at oraglegpt.org, and tell us which method your clients prefer.

  • A one-minute accessibility checklist for social media posts

    Accessible social posts are not a special project. They are a handful of habits that take about a minute per post. Here is the checklist we use, and why each item matters.

    1. Alt text on every image

    People using screen readers hear the alt text instead of seeing the image. Describe what matters for the post’s point, and include any text shown in the image, such as a quote card or a chart title. One or two sentences are usually enough.

    2. CamelCase hashtags

    Screen readers try to pronounce hashtags as words. #ContentStrategy is read as two words; #contentstrategy becomes one long, confusing word. Capitalising each word also makes tags easier for everyone to read.

    3. Emoji as decoration, not structure

    Each emoji is announced by name. A list where every line starts with a rocket emoji becomes “rocket, rocket, rocket” before each item. Use numbers or plain line breaks for lists, and keep emoji to one or two per post.

    4. Say where links go

    A bare link with no context forces readers to guess. A short phrase such as “full release notes here” or “pricing details” before the link helps everyone, including people who hear links read aloud.

    5. Plain language

    Short sentences and common words help readers with cognitive disabilities, people reading in a second language, and anyone using automatic translation. They also tend to perform better.

    Make it part of review

    The most reliable way to keep these habits is to check them during approval. If a reviewer sees an image without alt text or a lowercase hashtag wall, it gets fixed before it is scheduled, not after it is public.

    More practical guides on planning and publishing posts at oraglegpt.org.

  • Why the GPTpost trial needs no card and never converts on its own

    When we designed the GPTpost free trial, we had to answer a question every software company faces: do we ask for a card at signup? We decided not to, and we also decided that the trial would never turn into a paid subscription by itself. Here is why.

    The economics of card-up-front trials

    Asking for a card before a trial reliably produces more paying customers on paper. Part of that is genuine intent: people who enter a card are more serious. Part of it is that some people forget to cancel. That second part is revenue from inattention, and it tends to come back as refund requests, disputed charges and people who quietly warn their friends.

    What we do instead

    • 14 days, no card. You can try every feature with 5 seats, 15 connected accounts and 500 posts.
    • No automatic conversion. When the trial ends, nothing is charged.
    • Read-only, not deleted. Posts, schedules, comments and files stay readable and exportable. Everyone can still sign in.
    • You choose when ready. Pick Solo, Team or Agency in Settings, Billing, and new posts can be scheduled again.

    Why read-only instead of deletion

    Social media plans take time to build. Deleting a team’s calendar because a trial lapsed during a holiday would be unkind and would make coming back harder. Read-only keeps the work safe while making it clear that a plan is needed to continue publishing.

    The trade-off we accept

    Fewer conversions in the short term, and more people who try GPTpost casually. We are fine with that. Customers who choose a plan after seeing the product work for their team are the ones who stay.

    If you need more than 14 days to evaluate, write to hello@oraglegpt.org. Plan details are on the pricing page.

  • How to onboard a new agency client in an hour

    The first week with a new social media client sets the tone for the whole relationship. A slow, messy start leads to missed approvals and confusion about who does what. A clear one-hour setup avoids most of that. Here is the checklist we recommend.

    1. Connect the accounts properly (10 minutes)

    Never ask a client to send passwords by email or chat. Connect each network through its own sign-in (OAuth) or, for Bluesky, an app password the client can revoke at any time. It is safer, and it shows the client you take their accounts seriously.

    2. Set posting slots (10 minutes)

    Agree on two or three posting times per weekday, in the timezone of the client’s audience. In GPTpost these become weekly posting slots, and new posts can simply be added to the queue.

    3. Save hashtag groups (10 minutes)

    Collect the client’s brand and campaign hashtags and save them as hashtag groups. This prevents the classic mistake of using another client’s campaign tag.

    4. Define approval stages (10 minutes)

    Decide who approves and in which order. A common setup is internal review first, client second. Agree on a deadline too: for example, next week’s posts approved by Wednesday.

    5. Send the first review link (20 minutes)

    Write three sample posts and send them through a client review link. The client sees the exact text per network, can comment or approve, and needs no account. Low-stakes posts are the best way to learn the process before a real campaign.

    After the hour

    You have connected accounts, a posting rhythm, consistent hashtags, a clear approval path and a client who has already used it once. That is a stronger start than any onboarding slide deck.

    GPTpost was built for exactly this workflow. See how it works for small agencies.

  • GPTpost phone connection retest — 24 October 2026

    Owned-account GPTpost connection retest, 24 October 2026. Submitted from Brave on the connected Android phone to verify real delivery. This tests a reused owned identity; it does not establish every public client or server is approved.

  • RSS to social media without blind auto-posting

    Connecting an RSS feed to social media sounds like the perfect automation: publish a blog post or a changelog entry, and the announcement appears everywhere. In practice, fully automatic posting causes a familiar set of problems.

    What goes wrong with blind auto-posting

    • A draft published by mistake on the blog is announced to every network within minutes.
    • The feed title becomes the social post, with no context and the wrong length for half the networks.
    • An edited article is picked up again and announced twice.
    • The timing is whenever the feed updated, often at an hour when nobody is around to answer replies.

    How GPTpost handles RSS

    In GPTpost an RSS feed creates drafts, not posts.

    1. You add the feed and give it a repeat rule. GPTpost checks it on that schedule, at most every 15 minutes, and backs off when the feed is down.
    2. Each new item becomes a draft. Items are recognised by GUID, link or title, so the same article does not become two drafts.
    3. The draft opens in the per-network composer, where you write a short Bluesky version, a Mastodon version with hashtags, and anything else your channels need.
    4. It goes through your normal approval stages, then into the queue or a chosen time.

    Is that still automation?

    Yes. The tedious part, noticing new content and starting a post, is automated. The part that needs judgment, deciding what to say and when, stays with a person. For most teams that takes a couple of minutes per item, and it prevents the embarrassing cases above.

    Good feeds to connect

    Your blog, a product changelog, a release feed from your code host, or a podcast feed. Start with one feed and see how many drafts it produces in a week.

    You can set this up during the free 14-day trial, no card needed. More on RSS to social with review.

  • GPTpost publishing test 24 October 2026

    GPTpost production publishing test – 24 October 2026. This labelled post was composed and confirmed from our Android phone to verify delivery to our own account.

  • Why we price GPTpost per workspace instead of per seat

    When we set prices for GPTpost, the first decision was not the number. It was the unit. Most social media tools charge per user, some per connected channel. We chose per workspace, and the reason comes from how social media work is actually done.

    Reviewers outnumber writers

    Look at a typical agency post. One person writes it. An account manager checks tone. The client approves it, and sometimes the client’s manager does too. In regulated industries someone checks claims. That is three to five people around one post, and only one of them writes.

    Per-seat pricing puts a monthly price on every one of those people. Teams react rationally: they share logins, or they review over email and chat, outside the tool. Review becomes informal, and informal review is the kind that gets skipped on a busy Friday.

    What we did instead

    • Plans are priced per workspace: Solo 12 USD, Team 39 USD, Agency 99 USD per month.
    • Each plan includes seats: 1, 5 and 25.
    • Client reviewers approve through a review link. They need no account and no seat.

    The price grows with the size of the operation, measured by seats, connected accounts and monthly posts, not with every person who glances at a draft.

    The trade-off

    Per-workspace pricing is less precise. A solo consultant with five clients and an in-house team of five may pay the same. We accept that, because the alternative punishes the behaviour we want to encourage: getting a second pair of eyes on posts before they go out.

    We wrote a longer piece on why per-seat pricing hurts small agencies, including how to compare tools with different pricing units.

  • Reschedule and duplicate: two calendar habits that save hours

    Most of the time spent on social media scheduling is not writing. It is rework: a post that has to move because a launch slipped, or a monthly reminder rebuilt from scratch because nobody could find last month’s version. Two simple calendar actions remove most of that rework.

    Reschedule by moving, not recreating

    When a date changes, the tempting fix is to delete the post and write a new one for the new day. That loses the approval history and the per-network versions you already prepared. In GPTpost you move the post on the calendar to its new day. The content, the network versions and the comments stay attached, and the whole team sees the change.

    One caution: if the reason for the move changes the message, for example a product launch delayed for a quality issue, reread the text before it goes out. A post written for Tuesday’s mood can sound odd on Thursday.

    Duplicate what already worked

    Many teams publish the same kind of post every month: a meetup reminder, a newsletter teaser, a “what’s new” roundup. Duplicate last month’s post, change the date and details, and send it for approval. You keep the structure, the hashtags and the tone that worked, and you only spend time on what is new.

    When to use a template or a recurring post instead

    • Identical text on a fixed rhythm (a weekly office-hours reminder): use a recurring post with a repeat rule.
    • Same structure, different details (a monthly event): duplicate the last one.
    • Same structure across many different posts (release notes, tips): save a template.

    Picking the right one of the three keeps the calendar tidy and the copy fresh. See how the GPTpost calendar works at oraglegpt.org.