Add a CTA or disclosure to all your posts

There is a class of edit that should be one action and is instead a hundred: adding the same block to every post. A newsletter call-to-action at the foot of each article, an affiliate disclosure at the top of your reviews, a standard “about the author” footer. The Ghost editor has no way to insert a block across many posts, so people either skip it, paste it by hand for weeks, or give up — which is a real problem when an affiliate disclosure is not optional but a requirement. Working on your posts as files makes it a single pass.

Append the block as markdown

Specter syncs your blog to a folder of markdown, so each post is a text file you can edit in bulk. The cleanest version of this job is adding plain markdown — a heading, a sentence, a link — to the body of each post, because markdown round-trips through Specter reliably in both directions. Connect via the first-sync guide, then scope the instruction tightly:

Append this block, exactly as written, to the end of every .md file
in this folder, on its own new line. Don't add it to a post that
already contains it, and don't change anything else:

---
*Enjoyed this? Join the newsletter for a post like it each week.*

For a disclosure that belongs at the top, target a category instead of the whole blog:

For every post tagged "reviews", insert this disclosure as the first
paragraph of the body if it isn't already present. Leave all other
posts and all other content untouched.

An honest note on schema and raw HTML

You may want to add structured data — FAQ or Article JSON-LD schema — to every post. Be a little careful here. Two things are true. First, the most robust place for site-wide schema is usually Ghost’s own code injection or your theme, not pasted into each post body. Second, if you do put raw HTML into a post body, remember that Ghost stores posts in its Koenig format, and complex HTML does not always round-trip losslessly back to clean markdown — the same caveat covered in how Specter handles Ghost Cards. For plain text CTAs, disclosures, and footers written as markdown, you have nothing to worry about; for embedded HTML blocks, test on one post first and check the round trip before running it across the archive.

Review and preview

As always, read the diff, then run Specter’s dry-run preview to see exactly which posts would update before anything goes live, and snapshot the folder with git first. A block applied to two hundred posts is easy to apply and, thanks to that snapshot, just as easy to pull back if you change the wording. This is the same workflow behind bulk SEO edits and refreshing old posts — one decision, applied everywhere, reviewed before it ships.