How to Auto-Post RSS to Micro.blog and Any Micropub Site

Updated: 2026-09-28

Short answer: create an app token in your Micro.blog account and paste it into PostRSS under Accounts → Add new Micro.blog / Micropub account. PostRSS discovers your Micropub endpoint on its own, so there is nothing else to configure. Then open Cele → Add feed, choose Micro.blog / Micropub in Target settings and add your feed under Add source (Type = RSS feed, Link = your feed address). The same connection works with any site that supports Micropub, not only Micro.blog. Micro.blog / Micropub is included from the Professional plan.

Micro.blog is a small, deliberately calm social network built on open web standards rather than on a proprietary API. That choice is why this integration is unusually broad: the connection is not really to Micro.blog at all, but to Micropub, a W3C standard that Micro.blog happens to implement. This guide is the long version; the auto-post RSS to Micro.blog page has the short one.

Micropub is the point, not Micro.blog

Micropub is a standard for publishing to a website from any client — a phone app, a command-line tool, or an automation service. A site that supports it advertises an endpoint, a client discovers that endpoint, and posts are created through it.

Because PostRSS speaks the standard rather than one company's API, the same connection works with any Micropub-capable site. That includes self-hosted IndieWeb setups, static sites with a Micropub server in front of them, and whatever comes next — because the standard outlives the individual products that implement it.

This is the opposite of how most social integrations work, and it is why an IndieWeb-minded publisher should care: connecting to a standard means the setup survives a platform you use being sold, shut down or rewritten.

Endpoint discovery, and what it saves you

PostRSS finds your Micropub endpoint by itself. You paste an app token; you do not have to know or enter an endpoint URL.

That matters more for self-hosted setups than for Micro.blog. On a hand-built IndieWeb site the endpoint may live anywhere, and it may move when the site is rebuilt. Discovery means the connection keeps working across those changes instead of quietly pointing at an address that no longer answers.

What this is good for

• POSSE. Publish on your own site, syndicate elsewhere — the IndieWeb principle Micro.blog was built around. Your site stays the original; Micro.blog carries the copy.
• A quieter audience. Micro.blog has no likes, no follower counts and no algorithm, which attracts people who left larger networks deliberately.
• Any Micropub site you run. The same Target shape works for a self-hosted blog with a Micropub endpoint.
• Cross-posting onward. Micro.blog can itself syndicate to other networks, so one connection can reach further than it looks.

Micro.blog next to Mastodon and Bluesky

All three are answers to the same question — what replaces a centralised timeline — and they answer it differently. Mastodon federates servers over ActivityPub. Bluesky separates identity from hosting over the AT Protocol. Micro.blog starts from the position that you should own a blog and that the social layer is secondary.

That last stance is why it feels quieter. There are no public follower counts, no boosts to chase and no algorithmic feed, so the failure mode of the others — optimising for reach — does not really exist. What you get instead is a readership that arrived deliberately.

They are not exclusive. The same feed can reach all three from three Targets, and for a publisher following the POSSE principle that is precisely the intended shape: one original on your own site, copies wherever people read.

Setting it up, step by step

1. Create an app token in your Micro.blog account, or on whichever Micropub-capable site you are publishing to.
2. In PostRSS, open Accounts and choose Add new Micro.blog / Micropub account. Paste the app token. The Micropub endpoint is discovered automatically.
3. Open Targets and click Add feed. One feed going to one destination is one Target.
4. In Target settings, choose Micro.blog / Micropub and the account you just connected.
5. Click Add source. Set Type to RSS feed and paste your feed address into Link. Save.
6. Check the first item that arrives. PostRSS checks the feed every 5 minutes, and every minute on Enterprise plans.

PostRSS publishes items that appear in the feed after the Target starts running. It does not import the back catalogue — the alternative would be a destination flooded with years of archive on its first day.

Check the feed before you check the integration

When a destination goes quiet, the feed is usually the cause. Open the feed URL in a browser first.

• Anything new since you connected it? Only items appearing after the Target starts running are published.
• Full text or a summary? A summary-only feed produces thin posts, and nothing downstream can restore text the feed never sent.
• Absolute links? Relative URLs work on your site and break everywhere else.
• Valid XML? A feed address returning an HTML error page produces silence rather than an error.

All four are fixed in your content system.

Which plan includes it

Micro.blog / Micropub is included from the Professional plan. Each destination you connect counts as one Target, and your plan decides how many Targets and how many posts a month you get. An annual subscription is cheaper than paying monthly. Current limits per tier are on the pricing page, and the full lineup of 66 networks is on the supported networks page. The Micro.blog / Micropub page has the short version of the setup.

When posts stop appearing

• The app token was revoked. Tokens are managed in your Micro.blog account and stop working the moment they are removed.
• The site stopped advertising a Micropub endpoint. On a self-hosted setup, a rebuild can remove the discovery link the client relies on.
• Nothing new in the feed. Only items appearing after the Target starts running are published.
• Posts look truncated. The source feed ships summaries. That is a setting at the source.

Frequently Asked Questions

Does this only work with Micro.blog?

No. PostRSS publishes through Micropub, a W3C standard, so the same connection works with any website or blog that supports it — including self-hosted IndieWeb setups.

Do I need to enter a Micropub endpoint?

No. PostRSS discovers the endpoint from your site, so an app token is the only thing you paste in.

What is an app token?

A credential you create in your Micro.blog account for one application. It can be revoked on its own without changing your password or affecting anything else.

Is this a good fit for POSSE?

Yes, it is essentially the point. You publish on your own site, and the feed syndicates the post to Micro.blog while the original stays authoritative.

Will connecting a feed post my archive?

No. Only items appearing after the Target starts running are published.

Which plan includes Micro.blog?

The Professional plan, alongside the other open-web destinations such as WriteFreely, Telegraph and Dreamwidth.

Can Micro.blog then cross-post onward to other networks?

Micro.blog has its own syndication features, so a post arriving there can travel further without PostRSS being involved. Whether you use that or connect the other networks directly from the same feed is a matter of preference.

The bottom line

Micro.blog is the destination where connecting to a standard rather than to a product actually pays off: one app token, automatic endpoint discovery, and a setup that works with any Micropub-capable site you run now or later. It is included from the Professional plan.