How posting to WordPress works
WordPress is where a thought becomes a real article, not a short post. You share the idea (a voice note, a longer written brief, whatever context you have) and the team drafts a full piece in your voice: a title and a body with subheads. You read it, revise it, and approve it. Once approved, it publishes to your site on schedule.
That makes WordPress a different kind of channel from your social accounts. A quick observation might become a two-line Bluesky post and a 700-word WordPress article on the same day, drawn from the same underlying thought but written for how each audience actually reads.
What Bangers knows about WordPress
WordPress has no hard character limit in Bangers. It's treated as a longform destination. The drafting playbook follows the longform format: a title under 100 characters, and a body between 500 and 1,200 words with subheads, written the way a real post reads rather than a stretched-out social caption.
If a draft for WordPress ever comes through as a shorter, plain note instead of a full longform piece, Bangers still publishes it: it splits the first line off as the title and posts the rest as the body, the same way you'd paste a quick note into WordPress's editor and let the first line become the headline.
WordPress doesn't support threads. There's no chained-post concept on a blog, so a thread draft is rejected with a clear reason rather than mangled into something that doesn't make sense there.
A generated image attaches as the post's featured image automatically when one is part of the draft. Photos or videos you send Bangers yourself through Telegram aren't read for WordPress publishing.
Posts publish directly with a "publish" status. There's no separate draft-in-WordPress step; Bangers is the review stage, and once you approve, it's live on your site.
Connecting it
Connecting WordPress takes three fields: your site URL, your username, and an application password.
The site URL is your blog's address. The username is the WordPress user account Bangers should publish as. The application password is not your login password. Generate one from your WordPress admin under Users → Profile → Application Passwords, and paste the generated string in.
This only works with self-hosted WordPress sites that expose the REST API with application passwords. A wordpress.com-hosted site generally won't support application passwords, so if the connection check fails there, that's almost always why.
Bangers checks the credentials against your site before saving them, confirming it can identify the account they belong to. Because the application password is scoped to the account it was created for, you can revoke it from your WordPress admin at any time without touching anything else on the site. The next publish attempt simply fails with a clear reason until you generate a new one and reconnect.
When it fails
Every post is reviewed and approved by you before it goes anywhere: nothing publishes on its own. If the actual publish to WordPress fails afterward (the application password was revoked, the site is unreachable, the featured image upload didn't go through), you're notified in Telegram within a minute with the specific reason, and you can retry from there.
Frequently asked questions
Does Bangers write full WordPress articles, or just short posts? Full articles. WordPress is treated as a longform destination: a title under 100 characters and a 500 to 1,200 word body with subheads, not a shortened social-style post.
Can I use my regular WordPress login to connect? No. You need an application password, generated separately from your site's Users → Profile → Application Passwords screen. Your normal login password isn't accepted.
Will Bangers post to my wordpress.com blog? Only if it's set up to support application passwords, which most wordpress.com-hosted sites aren't. Self-hosted WordPress with the REST API enabled is what this connection is built for.