# Bloggable — Help centre

> Complete product documentation for Bloggable, an AI blogging platform that researches
> topics, writes articles in a brand’s own voice, optimises them for search and answer
> engines, and publishes them to a blog it also hosts.

Source: https://getbloggable.com/help
Articles: 24

---

# Team, roles, and authors

Everything in Bloggable belongs to an **account**, and everyone you invite joins that account — sharing its blogs, its credit pool and its billing.

## Roles

| Role | Can do |
| --- | --- |
| **Owner** | Everything, including billing and cancelling the plan |
| **Admin** | Settings, team, personas, archiving blogs, all content work |
| **Member** | Create and edit content, run AI actions, publish |
| **Viewer** | Read-only — can see the work and the analytics, change nothing |

Billing is owner-only. Team management and account settings are owner or admin. Permanent deletion of content is reserved for owners.

**Joe respects exactly these boundaries.** A viewer can ask Joe anything and get real answers, but Joe won't perform an action their role doesn't allow — the tools simply aren't offered to him. There's no route around the permission model through the assistant.

## Inviting people

Owners and admins invite by email from **Settings → Team**. Your plan sets how many seats you have; **Settings → Billing** shows the live number for your account.

Two known limits worth planning around:

- **Roles are account-wide.** You can't currently scope a member to a single blog.
- **A user belongs to exactly one account.** There's no account switching, so someone who works with you and with another Bloggable customer needs separate logins.

## Viewer seats and clients

Viewer is the seat to give a client or a stakeholder who wants to watch without touching. Note that ownership transfer isn't built yet — you can't hand a blog over to a client's own account, so agencies should plan to keep client blogs under their account.

## Personas — bylines without seats

A **persona** is a virtual author: a name, a bio and a photo, with no login and no seat cost. Use them to byline posts under a pen name, a brand voice, or a subject-matter expert who doesn't need access to the tool.

Personas can be scoped to the account or to a single blog, and you can have as many as you like. Autopilot can use one as its default byline — and if you don't set a byline at all, it assigns a persona rather than publishing anonymously, because an article with a named author is treated better by both search and answer engines.

Creating a persona needs admin or owner.

Source: https://getbloggable.com/help/team-and-roles

---

# Analytics

Every Bloggable blog reports its own traffic — views and approximate unique visitors, per post and per day.

## How it's measured

First-party, with no cookies and no third-party scripts. The blog records a view itself; nothing is sent to an analytics vendor, and there's no consent banner to add because there's nothing to consent to.

That design has a trade-off worth stating: visitor counts are **approximate**. There's no cross-site identity being tracked, so "unique visitors" is a good estimate rather than a precise headcount. For deciding which posts are working, that's more than enough.

## Where to find it

On the blog's **Analytics** cards. You get views and visitors over time, and per post.

## What this is not

It isn't a replacement for Google Search Console. Bloggable's own figures tell you **what happened on your blog** — which posts got read. Search Console tells you **what happened before that** — which queries you appeared for, where you ranked, how often people clicked. You want both, and the decline detection in *Content intelligence* depends on the second.

See *Google Search Console* for connecting it, and note that it needs a custom domain to collect anything.

## Asking Joe

Joe can read your blog stats — post counts, published counts, activity — so *"how's the blog doing?"* is a reasonable question to just ask him.

Source: https://getbloggable.com/help/analytics

---

# Content intelligence

**Intelligence** is the screen that tells you what to do with the posts you've already published. Most blogs fail slowly, not loudly: articles that ranked stop ranking, two posts start competing for the same query, drafts sit half-finished. Intelligence surfaces those.

It reports across your whole account, not one blog at a time.

## What it flags

**Refresh candidates** — posts that have aged out of accuracy or relevance. Refreshing rewrites the article while keeping its URL, so whatever ranking and backlinks it has earned survive the update.

**Decliners** — posts losing rank or traffic. This is the most valuable signal in the product and it needs **Google Search Console** connected to work properly; without it there's no rank data to detect a decline in. See *Google Search Console*.

**Keyword cannibalisation** — two or more of your posts competing for the same query. They split the signal and both rank worse than one good post would. Intelligence names the pair so you can merge, differentiate or redirect.

**Stale drafts** — work that was started and never finished.

**Competitor themes and counter-angles** — from the weekly competitor scan, based on the URLs set in each blog's settings. Counter-angles feed back into autopilot's topic planning, interleaved so every monitored competitor gets a hearing rather than the loudest one dominating.

## Acting on it

Every insight has a fix attached — you can rewrite a decaying post straight from the dashboard rather than finding it, opening it and deciding what to do. Joe can do the same: *"which of my posts are losing traffic?"* then *"refresh that one"*.

## Getting the most from it

- **Connect Search Console.** Half of what Intelligence does is inference until it has real query data.
- **Fill in competitor URLs** on each blog. No competitors, no competitor intelligence.
- **Give it a back catalogue.** Intelligence is about existing posts, so it has little to say in your first month. If you've imported an existing blog, it has plenty to say on day one.

## Related

- *Analytics* — first-party traffic figures, which work without any integration.
- *Google Search Console* — clicks, impressions, CTR and position.
- *Autopilot* — where competitor counter-angles end up as planned topics.

Source: https://getbloggable.com/help/content-intelligence

---

# Connecting Google Search Console

Search Console is where Google reports what your blog actually does in search: which queries you appeared for, how often, where you ranked, and how many people clicked. Connecting it turns several Bloggable features from estimates into measurements.

## Before you start: you need a custom domain

**Google only reports on a domain you can prove you own.** A blog published to a Bloggable address — `getbloggable.com/b/…` or a `.bllog.io` handle — sits on a domain you can't verify in Search Console. The connection will succeed and then collect nothing, which is a confusing failure mode, so it's worth being clear about up front.

Connect a custom domain to the blog first. See *Publishing posts and custom domains*.

## Connecting

1. **Settings → Integrations**.
2. Connect Google Search Console and authorise access.
3. Pick which Search Console property maps to which blog.

Sync runs nightly. Expect the first useful data the next day, and expect Search Console itself to lag by a couple of days — that's Google's reporting delay, not ours.

## What it unlocks

- **Clicks, impressions, CTR and average position** per post.
- **Decline detection** — posts losing rank or traffic, flagged in **Intelligence**.
- Better refresh prioritisation, because "which posts are slipping" becomes a fact rather than a guess.

## If it's connected but there's no data

In order of likelihood:

1. **The blog isn't on a custom domain.** See above. This is the common one.
2. **The wrong property is mapped.** A `domain` property and a `URL-prefix` property in Search Console are not interchangeable; make sure the one you picked covers the URLs your posts actually live at.
3. **It's too soon.** Google needs the site indexed and needs a few days of data before it reports anything.
4. **The blog isn't indexed.** Check the blog's SEO settings allow indexing, and that the posts are published.

## Disconnecting

**Settings → Integrations**. Disconnecting stops the nightly sync; previously synced figures stay on your posts.

## A known gap

Search Console data is stored per post but isn't yet surfaced in the editor — there's no per-post Search Console panel while you're writing. The data is used by **Intelligence**, which is where to look for it today.

Source: https://getbloggable.com/help/search-console

---

# Autopilot

**Autopilot** runs the content loop for a blog on a schedule: it finds topics, writes them, checks them, and — if you let it — publishes them. It's configured per blog under **Autopilot**, with a six-step setup wizard that can activate several blogs in one pass.

Autopilot spends credits like any other AI generation. Everything below exists to make sure it spends them on posts you'd have wanted anyway.

## The three levels

Autopilot is one setting with three positions, and you should climb them in order.

**1. Topic discovery.** Keeps a buffer of researched, ranked topic ideas topped up. Nothing is written. You approve or reject each one, and every suggestion comes with the research that justified it, so you can see *why* it was proposed. This is the level to start on: it tells you whether Bloggable understands your niche before it spends anything on drafting.

**2. Auto-drafting.** Writes full drafts from approved topics and leaves them for you. Nothing goes public without you opening it.

**3. Full autopilot.** Sources, writes, checks, schedules and publishes unattended. It runs hourly.

Off is the fourth position, and pausing the blog also stops autopilot.

## Setting the volume

Rather than picking an abstract "level of aggression", you configure output: *five planned, three drafted, one published a week* (or per month). The pipeline sizes itself to hit that. Cadence — daily, three times a week, weekly, fortnightly, monthly — sets the rhythm.

Before you switch anything on, the wizard shows a **live credit forecast** for the volume you've asked for. You'll know the monthly cost before it starts, not after.

## The guardrails

**The publish gate.** Nothing publishes unless it passes every threshold you set: minimum word count, minimum AEO score, and the AI-integrity check. These are objective measurements, not the model's opinion of its own work. A draft that fails is held back and flagged for you, not quietly published anyway.

**A hard budget cap.** Set a monthly credit ceiling per blog and autopilot stops at it. This is separate from the forecast — the forecast is an estimate, the cap is enforced.

**Approval.** At discovery level, every topic waits for your yes or no. Nothing gets written from a topic you rejected.

**It never repeats itself.** A topic that has already been published, drafted or queued cannot be planned again — on any path. That covers autopilot, "ask AI for ideas", and Joe. You will not wake up to three articles about the same thing.

## Where topics come from

You choose which sources feed it:

- **Your own site.** Indexed pages from your website and helpdesk steer what gets planned — not just where posts link.
- **Competitors.** The blogs you listed in the blog's settings. Counter-angles found by the weekly competitor scan become next week's planned posts, interleaved so every monitored competitor gets a hearing rather than the loudest one dominating.
- **Keyword seeds.** Terms you supply directly.
- **Cluster mode** organises output around pillar topics instead of scattered one-offs.

You can also give a **briefing** — free text that constrains everything it plans, e.g. "no listicles, and never write about pricing".

## Optional stages

Each adds credits per post, so each is a toggle:

- **Featured image** — picks and attaches an image automatically.
- **Humanise** — rewrites the draft to strip AI patterns and apply your voice.
- **AI-pattern check** — scores how machine-written the draft reads, and flags anything below your threshold for human review.

## Publishing settings

Set the publish time and timezone, default tags, the target funnel mix (top / middle / bottom of funnel) and the default byline. The byline can be a team member or a persona; if you don't set one, a persona is assigned automatically so posts aren't published anonymously.

## Running on demand

**Run now** triggers a manual pass. It's rate-limited to roughly once an hour per blog, which keeps a stuck loop from becoming an expensive one.

## Watching it

The **activity log** records every run: what ran, what it produced, what it cost, and why anything was held back. If autopilot fails repeatedly, we email you.

> **A note on the per-event notification toggles.** The wizard offers switches for "planned topic added", "draft ready" and "published". These are not yet wired up — failure emails do send, but those three per-event notifications currently do nothing. Don't rely on them.

## A sensible rollout

1. Run at **discovery** for a couple of weeks. Approve and reject honestly.
2. Move to **auto-drafting**. Read the drafts. Adjust the briefing and voice based on what's wrong with them.
3. Only then go to **full autopilot**, with the quality gate set where you'd actually be comfortable, and a budget cap you'd be happy to pay.

Source: https://getbloggable.com/help/autopilot

---

# Planning topics and the content calendar

Before anything gets written, it gets planned. The **content calendar** is where planned posts live, and every post moves through the same states:

**idea → planned → scheduled → drafting → generated → published**

You can see and act on this pipeline whether the topics came from you, from autopilot, or from Joe.

## Where topics come from

- **Ask for ideas.** Have the AI plan a batch against your blog's niche, audience and competitors.
- **Autopilot's topic discovery.** Keeps a buffer of researched, ranked ideas topped up automatically. See *Autopilot*.
- **Joe.** *"Give me five post ideas about X"*, and he'll add the good ones to the calendar on request.
- **You.** Add a topic directly.

## Why this topic

Suggested topics come with the research that justified them — the gap, the query, the competitor angle. It's there so you can reject the ones based on reasoning you disagree with, rather than judging a bare title.

## Approving and rejecting

Planned topics wait for a yes or no. Rejecting is not a wasted step: it's the cheapest possible correction, because a rejected topic is one you didn't pay to have written.

## It won't suggest the same thing twice

A topic already published, drafted or queued cannot be planned again — on any path. Autopilot, "ask for ideas" and Joe all check against the same history. You won't end up with three articles on one subject because three different routes suggested it.

## Cluster mode

Autopilot can plan around **pillar topics** rather than scattered one-offs, building a cluster of related articles that link to each other. This is usually a better use of the same number of posts, particularly on a young blog.

## Funnel balance

You can set the target mix across top-, middle- and bottom-of-funnel posts. It stops a blog drifting into either all-introductory explainers that never sell anything, or all-sales posts nobody reads. It also pairs with **reusable elements**, where a bottom-funnel CTA can be set to appear only on bottom-funnel posts.

Source: https://getbloggable.com/help/planning-topics

---

# Creating and configuring blogs

A **blog** is a publication under your account. One account can run several — how many depends on your plan, and you can buy capacity for one more blog as an add-on rather than jumping a whole tier. Each blog is fully independent: its own voice, theme, domain, SEO settings, autopilot configuration and posts.

## Create a blog

**Blogs → New blog**. Two routes in:

- **From your website's URL.** Bloggable reads the site and infers your branding, niche and audience. Fastest start, and usually more accurate than describing yourself from scratch.
- **From scratch.** Fill in the fields yourself.

Either way you'll set:

- **Name** — what readers see.
- **Slug** — the address, e.g. `getbloggable.com/b/<slug>`. Slugs are **globally unique across all of Bloggable**, not just your account, so a common word may already be taken. You'll be told before you save.
- **Niche** and **target audience** — the two fields that most affect output quality. Every topic suggestion, every draft, every internal link decision is made against them. "Marketing" produces generic articles; "B2B SaaS pricing pages for seed-stage founders" produces specific ones.

## Renaming a blog

You can change the slug later. Bloggable keeps the old one and permanently redirects it to the new address, so published URLs, backlinks and indexed pages keep working. Retired premium `.bllog.io` handles behave differently — they are retired for good and can't be claimed again by anyone, including you, because a cross-origin redirect that a browser caches forever must never be able to point at a stranger's blog.

## The settings that matter

| Setting | Why it matters |
| --- | --- |
| **Brand voice** | Writing samples become a voice profile applied to every draft. Free to generate. See *Brand voice*. |
| **Competitor URLs** | Feeds competitor monitoring and topic research — it's how Bloggable finds angles your competitors have missed. |
| **Target countries** | Steers spelling, currency, units, examples and regulatory context. |
| **Theme** | The look of the public blog. See *Themes and appearance*. |
| **SEO defaults** | Site-level meta, canonical base, indexing and AI-crawler policy. See *SEO and answer-engine optimisation*. |
| **Custom domain** | Serve the blog from your own domain. See *Publishing posts and custom domains*. |
| **Autopilot** | Hands-off generation, configured per blog. See *Autopilot*. |

Most per-blog display toggles — table of contents, share button, "Ask AI about this article", showing the description — are **on by default**. Turn off what you don't want.

## Working across several blogs

- The **blog switcher** moves you between publications.
- **Posts** has an all-blogs view, so you can see and act on everything at once.
- **Intelligence** reports across the whole account, not one blog at a time.
- **Credits are pooled** — every blog draws from one balance.

## Pausing, archiving and deleting

- **Paused** stops autopilot but leaves the public blog live.
- **Archived** removes the blog from your active list. Reversible.
- Permanent deletion of content is reserved for owners.

## Limits

Blog count, team seats, storage and your monthly credit allowance all come from your plan, and the live numbers for *your* account are shown in **Settings → Billing** rather than being fixed here — plans change. If you need one more blog than your tier allows, the capacity add-on is usually cheaper than upgrading.

Source: https://getbloggable.com/help/creating-blogs

---

# Brand voice

The single biggest difference between a Bloggable draft you'd publish and one you'd delete is whether the blog has a voice profile. It takes five minutes and costs nothing.

## Setting it up

In the blog's settings, paste **one to five samples** of writing you want to sound like. Bloggable analyses them and extracts a voice profile — sentence rhythm, vocabulary, how formal you are, how you open and close, what you never say.

That profile is then applied to every draft, every rewrite, every humanise pass and every autopilot run for that blog.

**Extracting a voice profile is free.** It doesn't cost credits, and you can redo it whenever your writing changes.

## What to paste

- **Your own writing, if you have any.** Old blog posts, a good email, a conference talk transcript. It doesn't have to be polished.
- **Writing you admire**, if you don't. Be honest with yourself that you're borrowing a voice rather than describing one.
- **Enough of it.** Two paragraphs isn't a voice, it's a sample size problem. A few hundred words per sample is a reasonable floor.
- **Consistent samples.** Five pieces in five different registers average out into nothing in particular.

## What it doesn't fix

A voice profile controls *how* something is said. It can't supply what you know. If drafts read as fluent but empty, the problem is usually the niche and audience fields, or a topic too broad to say anything specific about — not the voice.

## Voice per blog

Voice is set per blog, not per account. If you run a technical blog and a consumer one from the same account, they get different profiles, which is the point of them being separate blogs.

## Related

- **Brand memory** — things you tell Joe to remember about your business also feed generation. See *Meet Joe*.
- **Target countries** — spelling, currency and examples adapt per blog. See *Creating and configuring blogs*.
- **Humanise** — strips AI patterns and re-applies this voice. See *Writing posts with AI*.

Source: https://getbloggable.com/help/brand-voice

---

# Themes and appearance

Your public blog is rendered by one of four themes. Pick one per blog; you can change it later without touching your posts.

| Theme | Character |
| --- | --- |
| **Minimal** | Text-first. Nothing between the reader and the writing. |
| **Cards** | Grid of post cards on the index. Visual, good with strong featured images. |
| **Hybrid** | A featured lead post plus a card grid beneath it. |
| **Editorial** | Magazine-styled, denser typography. |

## Customising

Per blog you can set:

- **Logo** and how the identity displays — logo only, name only, or both
- **Colour**
- **Navigation** links
- **Social links**
- Whether the blog description shows on the homepage

## Reader-facing toggles

These are per blog and **on by default** — turn off what you don't want:

- **Table of contents** in the post sidebar, sticky, with scroll tracking
- **Share button**
- **"Ask AI about this article"** — opens the post in ChatGPT, Claude, Perplexity or Kagi
- Reading progress bar and reading-time estimate

Readers also get full-text search across the blog, category and tag archives, and related posts, without any configuration.

## Removing Bloggable branding

The white-label add-on removes our branding from the public blog — both the footer badge and the page title. See *Plans, upgrades and top-ups*.

## Newsletter

There's no built-in newsletter or subscriber list. You can add a **subscribe link** pointing at your existing email provider, and readers go there. See *Importing an existing blog* if you're moving from a platform where your list currently lives.

Source: https://getbloggable.com/help/themes-and-appearance

---

# How AI credits work

**Credits** are what AI work costs. Your plan includes a monthly allowance; each AI action deducts from it.

Chatting with Joe is free. So is manual editing, reading things back, and extracting a brand voice.

## The essentials

- **Credits are pooled per account.** One balance, shared by every blog and every team member. Not per-seat, not per-blog.
- **Your allowance refills each billing cycle.** Higher plans include more.
- **Each action has a price.** A full research-and-write costs many times what a short inline edit does, because it does many times as much. The exact cost varies by plan, and the interface always shows it before you commit — you can't start a run you can't afford.
- **Failures are refunded automatically.** If a generation fails, you don't pay for it. This is enforced in the billing layer, not left to goodwill.
- **Voice extraction is free.**

## Roughly what things cost, relative to each other

You'll see exact figures in the app; this is the shape of it:

- **Cheapest** — an inline edit at your cursor, a repurpose destination, an AI-pattern check.
- **Middling** — SEO generation, link suggestions, a competitor analysis, a topic-discovery run.
- **More** — live web research, a draft, a refresh, humanising, an AI-generated cover image.
- **Most** — the full pipeline, which is research plus draft plus SEO plus links, and priced accordingly.

## Running low

If an action needs more credits than you have, it won't start. You'll get a single prompt showing your balance with two ways out: **buy a top-up** or **upgrade**. Nothing runs halfway and leaves you with a broken post.

We email you before you run out, not after.

Check your live balance and this cycle's usage in **Settings → Billing**, in the sidebar meter, or by asking Joe.

## Allowance versus top-ups

Two buckets:

- **Monthly allowance** — resets each cycle. Use it or lose it.
- **Top-ups** — bought separately, and they persist across cycles rather than resetting.

The usage meter shows *used out of total*, where total accounts for both. When it says you've used 80% of your total, that's the moment to decide between a top-up and an upgrade.

## Keeping the bill predictable

- **Autopilot has a hard budget cap** per blog — a monthly credit ceiling it will not cross. Set it. The forecast shown during setup is an estimate; the cap is enforced.
- **The setup wizard forecasts the monthly cost** of the volume you're asking for, before you switch it on.
- **Joe shows the total before a batch** and waits for you to confirm.

> Joe can read your balance and estimate costs, but never makes purchases. Buying credits and changing plans is always something you do yourself, and he never sees card details.

Source: https://getbloggable.com/help/ai-credits

---

# Plans, upgrades, and top-ups

Billing sits on the **account** and is shared by everyone on it. Compare tiers on **Plans**; manage your own on **Settings → Billing**.

## What a plan sets

- Your **monthly credit allowance**
- How many **blogs** and **team seats** you get
- **Storage** for uploaded media
- Which **features** are unlocked — custom domains, content sources, white-label, and so on
- The **rate you pay for top-up credits** (cheaper per credit on higher tiers)

Tiers run **Starter → Growth → Pro → Agency**. Prices, allowances and limits are live on the **Plans** page and on **Settings → Billing** for your own account — those are the authoritative numbers, and they're not repeated here so this article can't go stale on you.

## Add-ons

Some things are bought separately rather than by moving tier — an extra blog, autopilot capacity, white-label. When you only need one more of something, an add-on is usually cheaper than the next tier up. Add-on prices vary by plan.

## Upgrading, downgrading and top-ups

- **Upgrade** at any time to raise your allowance and limits.
- **Top-ups** buy one-off credits without changing your plan. Unlike the monthly allowance, top-up credits carry across billing cycles.
- **Downgrading** reduces your limits at the next cycle. It won't tombstone your blog addresses — a downgrade never costs you a URL.

## Payments

Stripe handles everything. Cards, invoices, receipts and cancellation are all in the billing portal, reachable from **Settings → Billing**. Bloggable never stores your card details, and neither Joe nor our support team can see them.

We can sell in several currencies. Which ones are available depends on the plan — a currency is only offered where a real price exists for it, so what you see quoted is what you'll be charged.

## Trials, cancellation and account lock

Accounts start on a trial. When a trial ends without a plan, or a subscription lapses, the account **locks**: the app pauses and you're sent to **Plans** to reactivate. Your content is not deleted — it's waiting for you.

While locked:

- Joe stays available, read-only.
- **You can still reach a human.** Escalation to support is deliberately kept open on a locked account, because billing trouble is the most likely reason you'd need one.

Cancelling is done through the Stripe portal and takes effect at the end of the period you've paid for.

## If billing looks wrong

If your credits didn't reset when they should have, or your plan shows the wrong state after a payment, tell support rather than working around it — those are usually fixable in minutes at our end. See *Getting support*.

Source: https://getbloggable.com/help/plans-and-billing

---

# Getting started with Bloggable

Bloggable is an AI blogging platform. You create one or more blogs, generate and edit posts with AI, and publish them to a blog we host — either at a Bloggable address or on your own domain.

It is the CMS *and* the host. Bloggable doesn't publish out into WordPress or Ghost; it replaces them. If you already have a blog elsewhere, you bring it across once (see *Importing an existing blog*) and publish from Bloggable afterwards.

## Your first 20 minutes

1. **Create a blog.** **Blogs → New blog**. Give it a name, a niche and a target audience. These aren't decoration — every topic suggestion and every draft is written against them, so a vague niche produces vague articles. If you already have a website, you can create the blog from its URL and Bloggable will infer the branding, niche and audience for you.
2. **Set your brand voice.** Paste one to five samples of writing you want to sound like into the blog's settings. Bloggable extracts a voice profile and applies it to everything it writes. This step costs no credits. See *Brand voice*.
3. **Write your first post.** Open **Posts → New post** and either give the AI a topic, or run the full pipeline (research → draft → SEO → internal links) in one pass. See *Writing posts with AI*.
4. **Review it properly.** Read the draft. Check the content score panel, fix anything flagged, and edit the parts only you could have written — the specifics, the opinion, the first-hand detail.
5. **Publish.** Publish now, or schedule it. See *Publishing posts and custom domains*.
6. **Then consider Autopilot.** Once you know what a good Bloggable post looks like for your blog, switch on Autopilot to keep producing them on a schedule. Doing this before step 4 is the most common way to end up with content you don't like at volume.

## The onboarding checklist

New accounts get a checklist in the top bar that tracks the setup that actually affects output quality — voice profile, niche and audience, competitor URLs, a first published post, and so on. Each item deep-links to the exact field it's asking about. It's derived live from your account, so it stays honest: ticking things off means the setting really is set.

## Where things live

| Section | What it's for |
| --- | --- |
| **Dashboard** | Account overview, recent activity, credit balance |
| **Blogs** | Create and configure blogs — voice, theme, SEO, domain, competitors |
| **Posts** | Every post across every blog, and the editor |
| **Autopilot** | Hands-off content generation on a schedule, per blog |
| **Intelligence** | Which existing posts need attention, and why |
| **Settings** | Account, profile, integrations, team, billing |

## Two things worth knowing early

- **Credits are pooled per account**, not per blog or per person. Everything your team generates comes out of one balance. See *How AI credits work*.
- **Joe is free to talk to.** The orb in the bottom-right of every signed-in page answers product questions, reads your account, and can carry out real work on request. Asking him questions costs nothing. See *Meet Joe*.

Source: https://getbloggable.com/help/getting-started

---

# Meet Joe, your AI copilot

**Joe** is the assistant on every signed-in page — the orb in the bottom-right corner. He isn't a chatbot bolted onto a help centre: he can read your account and carry out real work in it.

**Talking to Joe is free.** Chat, questions, lookups and reading things back to you cost no credits. Only work that calls the content AI — writing, researching, SEO, repurposing — costs credits, at exactly the same price as doing it yourself from the interface.

## What Joe can do

**Answer questions about the product.** He searches these help articles directly, so anything documented here is something he can answer — usually with a link to the full article.

**Answer questions about your account.** Which blogs you have, how many posts are published, your credit balance and this cycle's usage, what's in the pipeline.

**Do the work.** Plan topics, research, write a post, run SEO, suggest internal and external links, refresh an ageing article, repurpose a post for social, publish or unpublish, create a blog, change blog settings, save and place reusable elements.

**Work inside the editor.** With a post open, Joe acts on *that* post: write it, improve it, redraft it from your written feedback, fix a specific flagged issue, rewrite a selection, set the title.

**Remember things.** Tell him something about your business and he keeps it; it then feeds future drafts. Ask him to forget it and he will.

**Get you a human.** If he can't help, he can escalate to support and hand over the conversation as context.

## What Joe won't do

- **He never touches payments.** He can tell you your balance and estimate what something will cost, but buying credits or changing your plan is always something you do yourself. He never sees card details.
- **He mirrors your role exactly.** A viewer can ask him anything but can't get him to change anything. Account-level actions — creating a persona, archiving a blog — need admin or owner, the same as they do in the interface. See *Team, roles and authors*.
- **He asks before spending on batches.** For a multi-post job he shows the total cost and waits for a yes.
- **He can't act on a locked account.** If a plan has lapsed he stays available and read-only. Escalating to a human stays open, deliberately — a billing problem is exactly when you need to reach someone.

## Good things to ask

- "How do credits work?"
- "How many posts are published on my blog?"
- "Give me five post ideas for my niche."
- "Write a post about *X*, then run SEO on it."
- "Which of my posts are losing traffic?"
- "Repurpose my latest post for LinkedIn."
- "What did you write for LinkedIn?" — free; he reads it back rather than regenerating.
- "Remember that we don't sell to enterprise."

If a question needs an answer we haven't documented, Joe will say so rather than invent one — and that's worth telling us about. Joe and this help centre read from the same source, so anything added here he can answer immediately.

Source: https://getbloggable.com/help/meet-joe

---

# Importing an existing blog

If you already publish somewhere else, bring it across once and publish from Bloggable afterwards. Bloggable is the host as well as the writing tool — it doesn't push posts out to WordPress or Ghost, it replaces them.

## What can be imported

WordPress, Ghost, Medium and Substack. The importer discovers posts from the source site, so it works on the public site rather than needing an export file.

## How it works

1. Open the blog you want to import **into**, and start the import.
2. **Discovery** scans the source and lists what it found — up to 100 posts in a pass.
3. **Choose what to bring.** You don't have to take everything, and usually shouldn't.
4. **Run the import.** Posts come across as markdown, and images are re-hosted on Bloggable rather than left hot-linking to a site you may switch off.

Import is included on paid plans. It's capped at 100 posts per discover-and-import session, and at 25 re-hosted images per post; anything beyond that keeps its original image URL.

## After importing

- **Check the slugs.** Your URLs may differ from the source site's. If you're pointing the old domain at Bloggable, matching the paths matters.
- **Set your brand voice** using imported posts as the samples — you have a body of your own writing right there. See *Brand voice*.
- **Run internal link suggestions.** Imported posts don't know about each other yet.
- **Look at Intelligence.** With a back catalogue in place, it can immediately tell you which posts are worth refreshing. See *Content intelligence*.

## Moving the domain

Import the content first and check it looks right, *then* repoint DNS. Doing it the other way round means a window where your domain serves an empty blog. See *Publishing posts and custom domains*.

## What doesn't come across

Comments, subscribers and email lists. Bloggable doesn't have a built-in newsletter — you can link out to your existing provider from the blog, but subscriber data stays where it is.

Source: https://getbloggable.com/help/importing-an-existing-blog

---

# Publishing posts and custom domains

## Publishing a post

From the editor's **Publish** panel:

- **Publish now** — live immediately.
- **Schedule** — pick a date and time; the scheduler runs every five minutes, so a post goes out within a few minutes of its slot.
- **Unpublish** — takes a live post back to draft.

You can also **duplicate** a post (useful as a template) and **archive** one. From the **Posts** list you can publish, archive, draft or repurpose in bulk, across blogs.

Editing an already-published post gives you a choice: edit in place, or fork a **V2 draft** so the live version stays untouched while you work.

## Where posts appear

Three possible addresses, in ascending order of ownership:

| Address | Looks like |
| --- | --- |
| Bloggable path | `getbloggable.com/b/<blog>/<post>` |
| Premium subdomain | `<handle>.bllog.io/<post>` |
| Your own domain | `blog.yourcompany.com/<post>` |

The premium subdomain is a middle tier — cheaper than a custom domain, and it looks like yours rather than ours.

Every blog also serves an RSS/Atom feed at `/feed`, `/feed.xml` and `/rss.xml`, and these follow whichever address the blog is on.

## Changing a post's URL

If you change a post's slug, the old URL permanently redirects to the new one. The same applies to a renamed blog. Nothing you've published strands a reader on a 404 because you renamed something.

## Connecting a custom domain

1. In the blog's settings, add your **custom domain**.
2. Add the **DNS records** shown to your domain provider.
3. Click **Verify**.

Once DNS has propagated and verification passes, the blog serves from your domain and that becomes its canonical address.

**If verification fails:**

- Check the record type and value exactly as displayed — a trailing dot or a wrong record type is the usual cause.
- Give it time. DNS can take a few hours to propagate; some providers are slower than others.
- If your DNS is behind a proxy (Cloudflare's orange cloud, for example), try setting the record to DNS-only until verification passes.
- Check you added the record to the right zone — `blog.example.com` goes in the `example.com` zone.

Custom domains are plan-dependent; **Settings → Billing** shows what your account includes.

## Why the domain matters more than it looks

**Google Search Console only works on a domain you can verify.** A blog on `getbloggable.com/b/…` or a `.bllog.io` handle sits on a domain you don't own, so Search Console will connect but will never collect data for it. If you want real click and impression data — and the decline detection in *Content intelligence* that depends on it — you need a custom domain. See *Google Search Console*.

## White-label

The white-label add-on removes Bloggable branding from the public blog: both the footer badge and the page title. Without it, the blog is still yours in every other respect, but it says where it was made.

Source: https://getbloggable.com/help/publishing-and-domains

---

# SEO and answer-engine optimisation

Bloggable optimises for two audiences at once: search engines that send you clicks, and answer engines that quote you inside an answer. They want overlapping but different things, so they're handled separately.

## SEO

The **SEO panel** in the editor generates:

- an optimised **title tag** and **meta description**
- **keywords** and a suggested **category**
- **structured data** (JSON-LD) for rich results
- **social card previews** — how the post will actually look on Google, Facebook and X

At blog level you control the default meta suffix, the canonical base, and whether the blog is indexed at all.

## AEO — being the source that gets quoted

The **AEO audit** scores how well a post can be lifted into an AI-generated answer. It measures:

- **Answer-first openings** — does the article answer the question in its first lines, or clear its throat for three paragraphs?
- **Structure** — headings that are questions, scannable sections, self-contained passages that make sense quoted alone.
- **An on-page FAQ**, with schema generated *from the visible article* so the structured data can never drift from what a reader sees.
- **Sourced claims** — assertions with something behind them.
- **Complete schema.**

The score is **computed from the document**, not asked of the model. A model rating its own output is a compliment, not a measurement.

## Internal and external links

**Internal link suggestions** cover your own published posts *and* pages from your crawled website — so a post can link into your product pages, not only into other blog posts. A retro pass can add internal links to already-published articles when new posts make new connections available.

**External link suggestions** propose authoritative outside sources. Linking out is not a leak; it's a signal both search and answer engines read as care.

The **link management panel** lists every link in the document so you can audit or remove them in one place.

## Machine-readable output

Every blog serves an `llms.txt` — a menu of your best posts for AI crawlers — and every post has a `.md` version advertised to crawlers alongside the HTML. You also control which AI crawlers may read the blog at all. See *AI crawlers and llms.txt*.

## Real data

If you connect **Google Search Console**, Bloggable syncs clicks, impressions, CTR and position nightly, and uses them to flag posts that are losing ground in **Intelligence**. Without it, you still get first-party traffic figures — views and visitors per post, no cookies or third-party scripts. See *Analytics*.

> **Search Console needs a custom domain.** Google only reports on a domain you can prove you own. A blog published to a Bloggable address (`getbloggable.com/b/…` or a `.bllog.io` handle) sits on a domain you can't verify, so Search Console will connect but collect nothing for it. Connect a custom domain to the blog first.

## Localisation

Set a blog's **target countries** and generation adapts: spelling, currency, units, examples and the regulatory framing it assumes. A UK financial post and a US one are not the same article with different spellings.

Source: https://getbloggable.com/help/seo-and-aeo

---

# AI crawlers and llms.txt

Answer engines can only cite you if they can read you. Bloggable publishes your blog in the formats they look for, and gives you explicit control over who's allowed in.

## What every blog serves

**`llms.txt`** — at your blog's root. A short, machine-readable menu of the blog and its best posts, in the emerging convention answer engines look for when asked "what is this site?".

**A `.md` version of every post** — the same article as clean markdown, at the post's URL with `.md` appended, and advertised to crawlers. HTML is full of navigation, scripts and layout; markdown is the article. Giving a model the markdown means it quotes your writing rather than your page furniture.

Both are on by default. The markdown variants can be switched off per blog if you'd rather not serve them.

## Controlling which AI crawlers may read the blog

Per blog, in the SEO settings, set the **AI-crawler policy**:

- **Allow** — an explicit permission for eleven named AI crawlers: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, CCBot, Bytespider, Amazonbot and Applebot-Extended.
- **Block** — disallow them, and suppress `llms.txt`.
- **Default** — emit no named rules and let the wildcard robots.txt rule apply.

This is a real trade-off, not a formality. Blocking keeps your writing out of training data and out of AI answers. Allowing is how you get cited. Most people publishing in order to be found should allow; if the content *is* the product rather than the marketing for it, blocking may be right.

One honest limit: `robots.txt` is a request, not a fence. Well-behaved crawlers respect it.

## For your readers

Posts can carry an **"Ask AI about this article"** link that opens the post in ChatGPT, Claude, Perplexity or Kagi. It's on by default, per blog.

## Bloggable's own

We serve what we sell. Bloggable's `llms.txt` is at [/llms.txt](/llms.txt), every help article has a `.md` version, and the whole help centre is available as one file at [/help/llms-full.txt](/help/llms-full.txt) — the **Copy page** button on any help article hands it to a model directly.

Source: https://getbloggable.com/help/ai-crawlers-and-llms-txt

---

# Getting support

## Start with Joe

Joe is on every signed-in page and searches these same help articles — but with your account in front of him. He'll usually answer faster than we will, and he can often just do the thing you were about to ask how to do.

Talking to Joe is free.

## Getting a human

If Joe can't help, **ask him to escalate**. He opens a support form and hands over the conversation as context, so you don't have to re-explain what you were trying to do.

Joe doesn't create tickets on his own — the form is always yours to submit. That's deliberate: a ticket you didn't knowingly raise is a ticket you'll never see the answer to.

**If you can't sign in**, email support directly using the "Email support" button at the bottom of any help article. Mail to that address becomes a ticket the same way the in-app form does, so either route reaches the same place.

## If your account is locked

A lapsed trial or a failed payment locks the app. Escalation to a human deliberately stays available on a locked account — that's the situation most likely to need one. Joe also stays available, read-only.

See *Plans, upgrades and top-ups*.

## What to include

The more of this you can give us, the faster this goes:

- **What you expected to happen**, and what happened instead
- **Which blog and which post**, by name or URL
- **When** it happened, roughly
- Anything the interface told you — an error message, a code, a screenshot

For a billing question, say what you were charged and what you expected. For a generation that went wrong, tell us which action you ran and, if you still have it, leave the draft in place rather than deleting it.

## Things that are usually us, not you

Report these rather than working around them:

- Credits that didn't reset at the start of a cycle
- A plan showing the wrong state after a successful payment
- An action that failed but wasn't refunded — failures are supposed to refund automatically
- A published post that isn't reachable at its public URL
- A custom domain that verified and then stopped serving

Source: https://getbloggable.com/help/getting-support

---

# Troubleshooting common problems

## "Insufficient credits" when I try to generate

The action costs more than your balance. Nothing was spent and nothing half-ran. You'll be offered a top-up or an upgrade; either works. See *How AI credits work*.

## A generation failed

Failed generations are **refunded automatically** — you shouldn't be charged for one. If your balance didn't come back, tell us; that's a bug, not a policy.

If the same action keeps failing, try a narrower topic. Very broad subjects sometimes produce a research pass with nothing specific enough to write against.

## My chosen blog slug is taken

Slugs are unique across all of Bloggable, not just your account, so common words go early. Pick another, or use a custom domain, where the address is entirely yours. See *Creating and configuring blogs*.

## My custom domain won't verify

In order of likelihood:

1. **DNS hasn't propagated.** Give it a few hours.
2. **The record is wrong.** Check the type and value exactly as displayed.
3. **It's behind a proxy.** Try DNS-only (Cloudflare's grey cloud) until verification passes.
4. **Wrong zone.** `blog.example.com` goes in the `example.com` zone.

See *Publishing posts and custom domains*.

## Search Console is connected but shows no data

Almost always because the blog isn't on a custom domain — Google can only report on a domain you can verify. See *Connecting Google Search Console* for the full list of causes.

## A published post isn't showing on my blog

Check, in this order: that it's actually published rather than scheduled; that the blog isn't paused or archived; that you're looking at the right address if the blog has both a Bloggable path and a custom domain; and that the blog's SEO settings haven't disabled indexing (which affects search engines, not whether the page loads).

If you renamed the post or the blog, the old URL should redirect rather than 404 — if it doesn't, report it.

## Autopilot isn't producing anything

- **Check the level.** At topic-discovery level it plans but never writes; at auto-draft level it drafts but never publishes.
- **Check for unapproved topics.** Nothing gets written from a topic still waiting for your yes.
- **Check the budget cap.** If it's hit its monthly ceiling it stops until the next cycle.
- **Check the quality gate.** Drafts below your word count, AEO score or AI-integrity thresholds are held back, by design. The activity log says which.
- **Check the blog isn't paused.** Pausing a blog stops autopilot.
- **Check your credit balance.**

The **activity log** records every run and why it did what it did. Start there.

## Autopilot notifications aren't arriving

Failure emails do send. The per-event toggles in the setup wizard — planned topic added, draft ready, published — are **not yet wired up** and currently do nothing. This is a known gap, not a misconfiguration at your end.

## Joe won't do something I asked

Three possible reasons: your **role** doesn't allow it (viewers can ask but not change; personas and archiving need admin), your **account is locked**, or it's something Joe deliberately never does — anything touching payment. See *Meet Joe*.

## Still stuck

See *Getting support*.

Source: https://getbloggable.com/help/troubleshooting

---

# Writing posts with AI

Posts are written in the full-screen **editor**, opened from **Posts**. Markdown is the source of truth — blocks, formatting and media round-trip cleanly, so nothing is trapped in a proprietary format.

Every AI action that generates content spends credits. Manual editing is free, and so is asking Joe about a post.

## Ways to generate a draft

**Full pipeline** — research → draft → SEO → internal links in one pass. The default for a post you want ready to review. Costs more than the individual steps because it *is* the individual steps.

**Draft from a topic** — you give the topic, the AI streams a first draft against your blog's niche, audience and voice. No live research, so it's cheaper and faster, and better suited to subjects where you supply the substance.

**Research first, then draft** — a live web research pass gathers real sources, statistics and competitor gaps, then the draft is written against those findings. Use it for anything where being wrong is expensive.

**Inline AI** — with a post open, use the slash menu (`/`) or select a passage and choose an AI edit. Drafts or rewrites *at your cursor* rather than regenerating the article. The cheapest AI action there is, and the one you'll use most.

## Making a draft actually good

**Improve** targets the article's own weakest scoring signals rather than rewriting indiscriminately — it reads the score breakdown and fixes what's dragging it down.

**Humanise** strips the patterns that make AI writing recognisable: uniform sentence rhythm, hedging, tidy tricolons, the summary paragraph that repeats the intro. It then re-applies your brand voice.

**Redraft from feedback** takes your written notes — "too long, and it never says who this is for" — and repositions the article accordingly. This is a strategic rewrite, not a polish.

**Track changes** shows AI edits as a word-level diff you can review and undo, so an AI pass is never a black box you have to accept whole.

## The scores

The editor shows a live **content score** — a composite of how human the writing reads, the AEO score, SEO signals and readability.

The **human-ness score** is a 0–100 rating with the specific passages that triggered it flagged. Each flag has a one-click fix, which does a surgical find-and-replace rather than a full rewrite. It is a heuristic, not a guarantee about any particular third-party detector, and it should be read as "this reads like a machine wrote it" — which is a writing problem regardless of who's checking.

The **AEO audit** is computed from the document, not asked of the model. See *SEO and answer-engine optimisation*.

## Working with a published post

Editing a live post gives you a choice: edit in place, or fork a **V2 draft** and work on that while the current version stays live. Use the fork when the change is substantial enough that a half-finished edit would embarrass you in public.

**Refresh** rewrites an ageing article while keeping its URL, which preserves whatever ranking and backlinks it has earned. It's the right tool for a post that used to perform and no longer does — *Content intelligence* will tell you which ones those are.

## Getting better output

- **Fill in the niche and audience properly.** They are used on every generation.
- **Set a brand voice.** It's free and it changes every draft. See *Brand voice*.
- **Add your competitors.** Research uses them to find the angle nobody has taken.
- **Add reusable elements.** Your standard CTA, disclaimer or product callout can be injected automatically instead of pasted every time. See *Reusable elements*.
- **Edit the parts only you know.** The AI can research and structure. It cannot supply your customer's actual objection, last quarter's real number, or the thing you learned the hard way — and those are what make a post worth reading.

Source: https://getbloggable.com/help/writing-with-ai

---

# The editor

Posts are written in a full-screen block editor. **Markdown is the source of truth** — everything you build round-trips to markdown and back, so nothing you write is locked into Bloggable's format.

You can switch between the rich editor and raw markdown at any time.

## Slash commands

Type `/` anywhere to insert a block without leaving the keyboard. That's the fastest way to reach any of the eighteen content blocks: callouts, CTAs, buttons, toggles, galleries, vouchers, quotes, code, tables and the rest.

## Paste-to-embed

Paste a URL and it becomes an embed or a bookmark card automatically. YouTube, Vimeo, Spotify, SoundCloud, CodePen and X are recognised as media; anything else becomes a link card.

## AI where your cursor is

Select a passage, or use the slash menu, to run an AI edit on *that text* rather than the whole article. This is the cheapest AI action in the product and the one worth building a habit around. See *Writing posts with AI*.

## The panels

- **Sidebar** — post metadata: title, slug, excerpt, featured image, author, category, tags.
- **SEO panel** — title tag, meta description, keywords, structured data, and previews of how the post will look on Google, Facebook and X.
- **Content score** — live composite of human-ness, AEO, SEO and readability, with specific flagged passages and one-click fixes.
- **Link panel** — every link in the document, in one list, so you can audit or remove them.
- **Publish panel** — publish, schedule, unpublish.

## Saving

The editor autosaves as you work; there's no save button to forget. Editing an already-published post asks whether you want to change the live version or fork a V2 draft.

## Reusable elements

Anything you paste into every post — a CTA, a disclaimer, a product callout — should be a reusable element instead. Save it once and have it injected automatically, including by autopilot. See *Reusable elements*.

## What isn't there yet

- **Revision history.** There's no version timeline to roll back through; the V2 draft fork is the safety net for substantial edits to live posts.
- **A media library browser.** You can upload images, but there's no screen for managing what you've already uploaded. See *Images and media*.

Source: https://getbloggable.com/help/the-editor

---

# Images and media

## Getting an image into a post

Four routes, all from the featured-image picker or the editor:

- **Upload** your own — drag and drop, or pick a file.
- **Unsplash** — a built-in library of free photography, attributed automatically as their licence requires.
- **By URL** — paste a link to an image you host elsewhere.
- **AI-generated cover** — Bloggable generates one for the post. This costs credits, unlike the other three.

Autopilot can pick a featured image for you automatically, as an optional stage. See *Autopilot*.

## Video and social embeds

Paste a URL and it becomes an embed: YouTube, Vimeo, Spotify, SoundCloud, CodePen and X are recognised. Everything else becomes a bookmark card. See *The editor*.

## Storage

Uploads count against a per-plan storage quota — **Settings → Billing** shows yours. Unsplash images and images referenced by URL don't consume it, since they aren't hosted by us.

## Alt text

Write it. It's an accessibility requirement first, and both search engines and answer engines read it. An article that scores well on AEO and ships images with no alt text is only half-finished.

## What isn't there yet

There's **no media library browser** — you can upload images, but there's no screen listing everything you've uploaded to reuse or tidy up. Plan to re-upload or use a URL if you need the same image across several posts, or make it part of a reusable element.

Source: https://getbloggable.com/help/images-and-media

---

# Reusable elements

A **reusable element** is a block you save once and have inserted into posts automatically — your standard call-to-action, a compliance disclaimer, a product callout, a newsletter prompt.

It replaces the habit of pasting the same paragraph into every article and then discovering, six months later, that eleven versions of it are in circulation.

## Saving one

Build the block in the editor, then save it to your account's element library. It's stored as a real block, not as flat text, so a saved CTA is still a CTA with its button and styling intact.

## Placement rules

An element isn't just available — it can be *placed*. You set where it appears and when, and Bloggable injects it into posts that match, including posts written by autopilot.

The rule worth understanding is **funnel-stage targeting**: a bottom-of-funnel CTA can be set to appear only on bottom-of-funnel posts. A hard sell on an introductory explainer converts nobody and costs you the reader; the same CTA on a comparison post is exactly right. Autopilot already balances its output across funnel stages, so the two features work together.

## Editing

Update the element and the change flows through where it's placed — that's the point of it existing. Deleting an element needs admin.

## Joe can do this too

Joe can save an element, list what you have, place one, and update one. Deleting is admin-only, as it is everywhere else.

## Note on snippets

Reusable elements supersede the older "snippets" concept and the editor's **Save snippet** action. Use elements.

Source: https://getbloggable.com/help/reusable-elements

---

# Repurpose a post for social

**Repurpose** turns a published post into channel-native copy you can paste
straight into your social accounts — a LinkedIn post, an X (Twitter) thread, a
short caption for Instagram/Threads/Facebook, or a one-line bio blurb.

It works on **published posts only**: the generated copy links back to the live
article, so there needs to be a public URL to point at.

## How to use it

From the **Posts** list, open the `···` menu on any published post and choose
**Repurpose…**. You can also do it from the editor's top bar (the megaphone
icon) while viewing a published post, or straight after you publish.

1. **Pick your destinations.** Each one shows its credit cost. LinkedIn and X are
   selected by default. LinkedIn comes back as three distinct angles — contrarian,
   practical and story — rather than one take you have to accept.
2. **Generate.** Each destination is written separately, so if one fails only
   that one is affected — the rest still come through, and a failed one is
   refunded.
3. **Edit and copy.** Tweak the wording (your edits are saved), then use the
   copy button on each card. The article link is added for you in the right place
   for each platform.

Your original post is never changed.

## Credits

Repurposing is charged **per destination**, so you only pay for the formats you
generate. Generating LinkedIn and an X thread for one post is two destinations.
You'll always see the total before you spend, and you can't start a run you
can't afford.

**Regenerating** a destination is free the first time each day, and always free
when your edits to the post have made the existing version out of date.

## Doing several posts at once

Select multiple published posts in the **Posts** list and click **Repurpose**.
You'll pick the destinations once, see the total cost with your balance, and can
skip posts that already have that copy. There's a progress bar and a live credit
counter, and you can stop partway — anything already generated is kept.

## Asking Joe

Joe can do it too: *"repurpose my latest post for LinkedIn"*. For more than one
post Joe will show you the cost first and ask you to confirm. You can also ask
*"what did you write for LinkedIn?"* and Joe will read it back for free without
regenerating.

## What's not included yet

Repurpose creates the copy for you to post yourself — it doesn't post or schedule
to social networks directly, and it doesn't add images. Newsletter/email copy
isn't a destination yet.

Source: https://getbloggable.com/help/repurpose

---