You already wrote the hard part. Postquarry is a content repurposing plugin that reads a blog post you have published and writes the rest of the week from it: an X thread, a LinkedIn post, an Instagram caption, a Facebook post, an email newsletter, a key takeaways recap, a TL;DR, an FAQ block with schema, quote cards, a carousel script and a short video script.

Then it schedules them and auto posts them to your social media accounts through the automation tool you already use.

The part that makes it different

There is no AI service behind this plugin. No OpenAI key, no Claude key, no monthly credits, no per-post cost, and nothing about your content is sent to a third party to be processed. The whole engine is PHP running on your own server.

It works by reading the post properly rather than guessing:

TextRank ranks every sentence by how central it is to the article, the same graph method used in academic summarisation.
Key phrase extraction finds what the post is actually about, weighting the title and headings.
Extractive compression shortens a sentence to fit a character limit by dropping discourse openers, parentheticals and trailing subordinate clauses, in that order, before it will ever cut a sentence mid-thought.
Deduplication stops a slice repeating the same point twice in different words.
A hook library of 81 openers across 15 angles supplies the first line, chosen from the strongest tier and seeded from the post so two posts never open the same way.

Because it is deterministic, the same post always produces the same slices. The preview is what gets published.

Voice matching, honestly explained

Postquarry reads posts you have already published and measures how you write: average sentence length, whether you use contractions, whether you address the reader as “you”, how often you ask questions, whether you use emoji, and your typical reading ease. Those measurements are then enforced on every slice.

It is your own numbers applied to your own words. It is not a model imitating you, and the plugin does not claim otherwise.

A readiness score you can argue with

Every slice gets a score out of 100 with the full breakdown shown: hook strength, first line length, length fit for the platform, reading ease, whether there is a number in it, whether it is skimmable, whether it asks for anything, and hashtag discipline. Each lost point comes with a specific fix.

It is a transparent rubric, not a prediction. No plugin can tell you what will go viral, and this one does not pretend to.

Getting it out of WordPress

Postquarry never asks for your social passwords and never asks you to register a developer app. A finished slice leaves your site one of four ways:

Copy it yourself. One button, straight to the clipboard.
A private RSS feed per platform. Point Zapier, Make, IFTTT, n8n or Buffer at the URL and anything you queue is picked up automatically.
A webhook. Postquarry POSTs the slice as JSON to any URL you configure, optionally signed with a shared secret.
Back to your own site. Recaps and FAQ blocks can be published here as posts, with a canonical link to the original and an optional noindex so they never compete with it in search.

Automation

Turn on automatic slicing and every post you publish is sliced in the background, saved to the library, and optionally queued across the days and times you choose, with a minimum gap between posts.

What it does for your SEO

Two of the twelve formats are worth more inside the original post than they are on a social feed, so Postquarry can write them straight back into it:

Meta descriptions. The TL;DR format produces a description trimmed to the length search engines actually show. One button writes it into Yoast SEO, Rank Math, SEOPress, The SEO Framework or All in One SEO, whichever you run, and keeps its own copy so the work survives a change of SEO plugin.
FAQ rich results. The FAQ format finds the questions your post already answers, builds the block, and adds it to the post with valid FAQPage schema. Google can use that markup to show the questions under your listing. The answers come from words you already published, rather than filler written to fill a slot.
No duplicate content. A recap published back to your site carries a canonical link to the original article and, by default, a noindex directive. A summary should send readers to the real thing, not compete with it for the same query.

Nothing is written to a post until you press the button. Postquarry never edits your content in the background.

For developers

Custom formats: extend Postquarry_Format and add your class through the postquarry_format_classes filter.
Custom hooks: postquarry_hook_templates.
Custom niches and hashtag sets: postquarry_niches.
Webhook payload: postquarry_webhook_payload.
Actions: postquarry_slice_saved, postquarry_published_post, postquarry_delivered.
WP-CLI: wp postquarry slice <id>, wp postquarry run, wp postquarry voice, wp postquarry library.

External services

Postquarry does not depend on any external service and sends nothing anywhere by default. There are exactly three cases where it makes an outbound request, all of them started by you:

Slicing a URL. If you paste a URL into the studio, your server fetches that page so it can read the article text. The request goes only to the address you typed.
RSS sources. If you point Postquarry at a feed, your server fetches that feed using the RSS client bundled with WordPress.
Webhooks. If you configure a webhook, the slice you queued is POSTed as JSON to the URL you entered, with your site name and URL included so the receiving end can identify it.

No analytics, no telemetry, no licence check, and no call home. Your content is never sent to an AI provider, because there is no AI provider.