SyncDock Client 1.2: WordPress Publishing on Autopilot

The first version of SyncDock Client solved a problem that anyone running more than two WordPress sites knows by heart: a browser full of wp-admin tabs, each with its own login and its own slightly different block editor. It gave those sites one console. You could write, schedule and publish everywhere without logging in anywhere.

What it could not do was keep going when you stopped. Every automation lived inside Chrome. Close the laptop on a Friday and the content calendar paused with it until Monday.

SyncDock Client 1.2.1 fixes that, and it is the biggest update since launch. Automations can now run on your own WordPress server. Fifty posts across ten sites fit in one batch. The editor streams AI text as it is written. And for the first time you can see which of your posts are losing search traffic, then refresh them in one click.

This post covers everything new since 1.0. That is the 1.1, 1.2 and 1.2.1 releases taken together, and why each change matters if you publish at volume.

Autopilot: automations that run on your server

The headline feature is a single switch. Any automation can now be set to Run on the server (Autopilot), and from that point your WordPress site takes over.

It runs on the site's built-in scheduler. Chrome does not need to be open. Your computer does not need to be on. The automation generates, formats and publishes on the cadence you set, whether that is daily, weekly, monthly or continuous, and it keeps its topic de-duplication, so it does not quietly repeat itself three weeks later.

The details are what make it safe to leave alone:

• Your AI key stays locked. A site administrator stores one provider key on the site. It is encrypted, never shown again and never logged.
• A hard monthly budget. Set a spending cap and Autopilot will not go past it. This matters more than any feature on the list, because a runaway automation with an API key costs real money.
• No duplicate posts, even when a run is retried after a failure.
• Multi-site automations. One automation can cover several sites, each with its own topics and a staggered start time, so ten sites do not all hit their AI provider in the same minute.
• A full audit trail. Every run appears in the activity log, and your webhooks are notified.

On the plugin side there is a new Jobs & Automations screen in wp-admin. You can filter jobs, retry or cancel them, see each automation's runs and spend, and check webhook health. It is the one place you might still open wp-admin for, and it exists so you can see what the server has been doing on your behalf.

Built for 10 to 50 posts a day

Autopilot handles the posts nobody needs to touch. The rest of 1.2 is about the ones people do touch, at a volume where doing it one post at a time stops being realistic.

Bulk actions with a safety net

On the Posts screen you can now select many posts and rewrite them, run SEO on them, add or remove categories and tags, change their status, schedule them, or send them to the trash, all in one action.

The obvious worry with a bulk AI rewrite is that it changes forty posts in ways you never saw. So bulk rewrites do not publish directly. They are held in the Queue for approval, each with a side-by-side diff. You read the change, you approve it, and only then does it reach the site.

From a spreadsheet to a publishing schedule

Most content plans start life as a spreadsheet of keywords or topics. SyncDock Client now imports that sheet directly. A CSV or TSV of up to 500 topics becomes queued posts, with column mapping, validation, multi-site modes, and a cost estimate before you commit. That last part is the one that saves you: you find out what 500 AI-generated drafts will cost before you spend it.

One post, many sites

You can fan a post out to several sites at once, use Send to more sites… from the Queue later, and hit Retry failed sites if one site was down when the batch ran. Featured images are copied too. The All sites view merges every connected site's posts into a single list, and Choose sites… narrows it to a few. A Needs attention view collects the posts that need work across all of them.

Adding sites got faster as well. The plugin now gives you a one-line connection code. Paste it into the extension and the site is connected, with no copying of URLs and keys field by field. When you run twenty sites, that is twenty fewer chances to paste a key into the wrong box.

Finding the posts that need you

Publishing more is only half of running a content operation. The other half is knowing which of the posts you already have are slowly dying. Until now that meant exporting from Search Console, cross-referencing a spreadsheet, and working out which URL maps to which post on which site.

SyncDock Client 1.2 brings that view inside the console:

• Content audit filters find posts older than a given date, posts under or over a word count, and posts missing an SEO description, a featured image or an excerpt.
• A Google Search Console connection uses your own sign-in and your own OAuth client, so the data stays yours and never passes through us.
• A Clicks 28d column appears next to every post.
• A Losing traffic filter jumps straight to the posts whose clicks are dropping.

From there it is one click to rewrite the post that is slipping, which then goes through the same diff-and-approve flow as any other rewrite. Finding the problem and fixing it now happen in the same place.

An editor that writes alongside you

The editor got the most individual improvements, and most of them remove a small, repeated irritation.

• Streaming AI. Rewrites and AI assists appear word by word as they are generated, not after a spinner.
• One-click AI inserts: Key Takeaways, TL;DR, FAQ, Comparison Table, Pros & Cons, and How-To Steps.
• A media library picker for images, covers, galleries, media-and-text blocks and featured images.
• AI alt text for one image in the editor, or in bulk on the Media page, with a "missing alt text" filter to find the gaps. Accessibility debt on an old site is usually a few hundred images, and nobody writes alt text for three hundred images by hand.
• Revision compare before restore, so you see exactly what changes before you roll back.
• Snippets for reusable blocks like CTAs, disclaimers and author boxes. Insert them from the slash menu, or bulk-insert them into many posts at once.
• Smart find and replace across a post.
• Internal link backfill. SyncDock suggests links from your related older posts. Each suggestion is validated and reviewed before anything is written.
• Edit-conflict protection. If someone changed the post in wp-admin while you were editing, SyncDock tells you and lets you reload or overwrite. Your work is never silently lost.

Richer posts, still native Gutenberg

Markdown-to-Gutenberg conversion has been SyncDock's flagship feature from the start, because it is the reason a draft written anywhere can arrive in WordPress looking like it was written there. Markdown Schema v2 extends what that converter understands:

• New block types: an auto-anchored table of contents, pros and cons, galleries, video, audio, files, styled tables, separators and embeds.
• Richer inline text: highlights, superscript, subscript, and links with rel and target.
• Nested lists that publish correctly, and numbered lists that keep their starting number.
• FAQ schema generated automatically from FAQ and accordion sections, which is structured data you would otherwise add by hand.
• A lossless round trip: a post can go from Gutenberg to Markdown and back without losing structure.
• Blocks from other plugins survive AI rewrites. Blocks from your page builder, forms plugin and similar tools are protected during a rewrite instead of being flattened into paragraphs.

That last one sounds minor until you have watched an AI rewrite turn a pricing table from a third-party plugin into three lines of plain text.

The whole site, not just blog posts

SyncDock started as a posts tool, and a real WordPress site is a lot more than posts. 1.2 adds pages and custom post types to the editor, with Type and Parent pickers. Custom taxonomies, ACF fields and native footnotes get their own editor panels, and multisite networks are supported. If your sites use a product post type, a portfolio, or a set of ACF fields for every article, SyncDock can now work with them.

AI your way: 10 built-in providers

SyncDock Client 1.2.1 ships with 10 built-in AI provider integrations, so there is no lock-in to a single vendor:

• Revoye, the first-party AI service from the makers of SyncDock. It uses the AI account you are already signed into, so there are no per-token API bills. If you are curious how that works, we wrote about using your AI subscriptions as an API.
• OpenRouter, where one key opens a large catalogue of models with the exact per-request cost reported back.
• The major commercial AI services, any compatible custom endpoint, and fully local or offline models running on your own machine.

Cost tracking is honest by design. When a provider does not report token usage, SyncDock estimates it locally and marks it "≈". Calls without a known price show "—" and are never counted as zero, and price tables carry "as of" dates. The Insights screen adds trends against the previous period, a tokens-per-day chart, each provider's share and average cost, the error rate, and tokens per published post.

One smaller change is worth knowing about. When AI picks categories, it now chooses from the ones your site already has and never invents new ones. New tags are clearly flagged. If you have ever cleaned up a taxonomy after an AI tool created "Tech", "Technology" and "Tech News" as three separate categories, you will understand why.

And AI remains optional. The editor, multi-site publishing, media and scheduling all work without it.

Audited before release

Before 1.2 shipped, both the extension and the plugin went through a full security audit. The changes that came out of it:

• A hardened content sanitizer that blocks script, iframe and event-handler injection.
• Safer imports. Settings restores ask for confirmation first and can never quietly weaken your security settings.
• Encrypted backups can now include your API keys, protected by a separate export passphrase. This is optional.
• Stronger PIN rules, with an 8-character minimum and throttling on wrong attempts.
• Request signing v2 also covers the query string, and every request stays replay-protected.
• No double runs. Jobs use leases, so two browser windows can never run the same job twice, and stuck jobs are recovered automatically.
• Rate-limit awareness. Each site has its own request lane, SyncDock pauses when a site says "slow down", and requests time out cleanly.
• Scheduled publishing never posts to a date in the past and handles daylight-saving changes correctly.
• Resumable pipelines. An interrupted generation resumes where it stopped without repeating finished steps.
• Tighter extension permissions, with one unused permission removed, and a stricter content security policy.

None of this changes the principle SyncDock started with. There is no SyncDock server in the path. Requests go directly from your browser to your site and to the AI provider you chose. Your keys live in an AES-256-GCM vault behind a mandatory PIN, and there is no telemetry.

Smaller things you will notice

• A one-row context bar that fits any window width, with less-used actions moved into a "More" menu.
• @handles for sites that work the same everywhere: the command bar, mentions and forms.
• Visible progress. The button you clicked becomes the progress indicator, and long generations show something like "Stage 4 of 17 · 2m 10s".
• Translation-ready. More than 2,300 interface strings now sit in a single catalogue, ready for localization. The interface ships in English today.
• Keyboard navigation throughout Posts and Queue.

Who this release is for

If you run one WordPress site and publish once a week, the old SyncDock Client already did what you needed, and 1.2 simply makes it nicer to use.

This release is for the other group: agencies with a roster of client sites, niche-site operators with ten properties and one person, and content teams whose editorial calendar spans more sites than anyone wants to log into. For them, the difference between 1.0 and 1.2 is the difference between a faster way to publish and a system that keeps publishing, tells you what it did, and shows you where to look next.

Getting started

1. Install SyncDock Client from the Chrome Web Store. It works in Chrome or any Chromium browser, version 102 or newer.
2. Install the free SyncDock plugin, version 1.6.0 or newer, on each site. 1.6.1 is strongly recommended because it includes important security fixes.
3. Paste each site's connection code into the extension and set your PIN.
4. Switch your first automation to Autopilot, set a monthly budget, and let it run.

There is no seat limit and no per-site fee, so connect as many sites as you manage. If you are still deciding whether a console beats wp-admin at all, our guide to managing multiple WordPress sites without wp-admin walks through the trade-offs. For the plugin underneath, read about headless WordPress publishing with AI or see the SyncDock plugin page.