Manage Multiple WordPress Sites Without wp-admin

If you manage more than one WordPress site, you already know the tax: a different wp-admin login for each one, a block editor that behaves slightly differently depending on which theme and plugin stack is running, and a mental map of which dashboard you're even looking at right now. Multiply that by five client sites, or a personal blog plus a couple of niche projects, and "quickly publish a post" stops being quick.

That's the specific problem SyncDock Client is built to remove. It's a free Chrome extension that replaces a browser full of wp-admin tabs with one console — write, schedule, and automate publishing across every WordPress site you manage, without logging into any of them directly. This post covers what that actually looks like, how it's built, and where it fits if you're already running WordPress at any scale.

The wp-admin problem, stated plainly

wp-admin was designed for one person managing one site. It does that job well. It was never designed for someone managing eight sites who needs to know, at a glance, what's scheduled where, whether a draft still needs an SEO pass, and whether last week's post on Site C ever actually went live.

The workarounds people reach for are familiar and all somewhat broken:

• A browser tab per site. Works until you have six tabs open and can't remember which one is which, and every session times out independently.
• A shared password manager entry per site. Solves login friction, not the actual problem of editing and publishing from one place.
• A custom script against the REST API. Solves the "one place" problem but now you're maintaining authentication, error handling, and block formatting yourself — which is exactly the gap headless publishing plugins like SyncDock exist to close on the API side.

None of these fix the actual workflow: writing, reviewing, and publishing content across several sites without treating each one as a separate errand.

What changes when publishing lives in a browser console instead

SyncDock Client isn't a bookmarklet or a shortcut into wp-admin — it's a separate interface entirely, built as a Chrome extension, that talks to your sites over an API instead of rendering their admin dashboards. Practically, that means:

One panel, every site. Add a WordPress site once, and it stays connected. Switching between sites is a click, not a re-login.

Writing happens outside the block editor's constraints. Draft in Markdown, paste from wherever you actually write, and the extension converts it into real Gutenberg blocks before it reaches WordPress — not raw HTML dumped into a paragraph block.

Automation is native, not bolted on. Scheduling, reusable workflow templates, and a content calendar live in the same interface you're already writing in, instead of a separate scheduling plugin per site.

Nothing routes through a third-party server. The extension talks directly to your WordPress sites and, optionally, to an AI provider you configure yourself. There's no Degird backend in the middle logging what you write.

How SyncDock Client is actually built

The architecture is a client-server split, and it's worth understanding because it explains both the capabilities and the security model.

The server side is SyncDock, a free WordPress plugin that registers its own /wp-json/syncdock/v1/ namespace — separate from, and additive to, WordPress's native REST API. You install it once per site and generate an API key from its admin screen. That plugin is what actually reads, writes, and queries the site's content; SyncDock Client never touches your database directly.

The client side is the extension itself. It holds your API keys, renders the writing and scheduling interface, and makes authenticated calls into that namespace — the same one AI agents and automation pipelines already use when they publish to WordPress programmatically. In other words, SyncDock Client is what you get when you point a human-friendly console at an API that was originally built for machines.

SyncDock: the plugin doing the actual work

The extension is the console; SyncDock is the engine underneath it, and it's worth knowing what it does on its own merits — because it's the half of this setup you install on WordPress, and the half that determines what's actually possible. On each site, it's a genuinely capable API gateway in its own right:

• SHA-256 hashed API keys, with optional HMAC-SHA256 request signing and a replay-protection window, so a captured request can't be reused later.
• Ten granular permission scopes per key — a key scoped to draft-only can't delete a post or change settings, even if it leaks.
• Bidirectional Gutenberg block conversion for 18+ core block types, plus block-level partial updates instead of full-post overwrites.
• SEO metadata sync into Yoast, Rank Math, or AIOSEO, and content-gap endpoints that expose what's already been covered.
• Real-time API metrics and an activity log, visible from the plugin's own admin screen, so every request — from the extension or anywhere else — is auditable.

It's free on WordPress.org, version 1.0.1 or newer, and it isn't built exclusively for this extension. The same /wp-json/syncdock/v1/ namespace is what AI agents and custom automation pipelines use to publish programmatically — our post on headless WordPress for AI publishing covers that side in depth. SyncDock Client just happens to be the friendliest way to sit on top of it: install the plugin once per site, and both a human with a browser and a script with an API key can publish through the same door.

What you can actually do with it

Connect an unlimited number of sites. There's no seat limit and no per-site fee — add every property you manage, from a client's storefront to your own hobby blog, under one console.

Convert Markdown and HTML into Gutenberg blocks. Paste a draft written anywhere — a notes app, another CMS, a Markdown editor — and it arrives in WordPress as clean, native blocks, editable in the block editor exactly as if you'd built it there by hand.

Draft with AI, using your own key. AI generation is bring-your-own-key: OpenAI, Anthropic, a custom endpoint, or a locally hosted model. Generate a draft from a topic and the extension handles SEO metadata, internal-linking suggestions, and featured-image selection around it — or skip AI entirely and write everything by hand. Neither path is required to use the other.

Run SEO checks before you publish, not after. Readability, heading structure, keyword usage, and meta-description length are scored inside the console, so a post doesn't need a second pass from an SEO plugin after it's already live.

Automate the calendar, not just the writing. Set a publishing cadence, save a workflow as a reusable template, and let a content calendar show you what's scheduled across every connected site — plus content clustering that flags likely duplicate topics before you accidentally publish the same idea twice under two different sites.

Handle media and bulk actions without opening the library. Browse, search, and upload media, batch-publish a set of drafts, or queue a translation job, all from the same panel.

The security model, in specific terms

Handing a browser extension the API keys to every WordPress site you run is a reasonable thing to be cautious about, so it's worth being precise about what actually happens to those credentials.

Every connected site's key is encrypted at rest with AES-256-GCM, and unlocking the extension at all requires a PIN protected with PBKDF2-SHA256 at 600,000 iterations — which happens to match OWASP's current recommended minimum for that specific hash function, not an arbitrary number. There's no cloud sync of your credentials and no backend server sitting between the extension and your sites: requests go directly to your WordPress installs (via the SyncDock plugin) and to whichever AI provider you've configured, with no telemetry logging what you write or publish in between.

Setting it up

Getting from a fresh Chrome install to publishing across multiple sites takes four steps:

1. Install SyncDock Client from the Chrome Web Store. There's no account to create.
2. Install the SyncDock plugin (version 1.0.1 or newer) from WordPress.org on each site you want to manage, and generate an API key from its admin screen.
3. Connect each site and set a PIN. Paste the API key into the extension; from that point on it's encrypted locally and unlocked only with the PIN you choose.
4. Write, schedule, and automate from the console — across every connected site, without a single wp-admin login.

Who this actually saves time for

Agencies managing client sites get one console and one PIN instead of a spreadsheet of client logins, with each site's access still independently revocable.

Content and marketing teams running several WordPress properties get a shared view of what's scheduled where, without training everyone on five slightly different admin setups.

Solo bloggers and creators get to write in whatever tool they already like and publish clean, formatted posts without a manual copy-paste-and-fix pass into the block editor.

SEO-focused publishers get readability and metadata checks built into the writing flow instead of a separate plugin per site to configure and audit.

If none of that describes your setup — say, you run exactly one WordPress site and rarely leave wp-admin — the extension has less to offer you, and that's fine. It's built for the multi-site case specifically, not as a universal wp-admin replacement.

SyncDock Client vs. the alternatives

Approach	Setup effort	Scales to many sites	Security model
wp-admin per site	None	Poorly — one login and dashboard per site	WordPress's own login + 2FA plugin if installed
Custom REST API script	High — you build auth, block conversion, error handling	Yes, if you build it well	Whatever you implement yourself
SyncDock Client	Low — install extension + plugin, generate a key	Yes, unlimited connected sites	AES-256-GCM + PIN, no backend server

The middle row is worth being honest about: building your own client against the WordPress REST API (or against SyncDock's namespace directly) is a completely reasonable choice if you have specific requirements the extension doesn't cover, and our post on headless WordPress for AI publishing walks through what that actually takes to build correctly. SyncDock Client exists for everyone who'd rather not build that layer themselves.

Frequently asked questions

Do I need the SyncDock plugin to use SyncDock Client?

Yes. SyncDock Client is a console for the free SyncDock WordPress plugin — it authenticates against a site's /wp-json/syncdock/v1/ namespace using an API key generated in the plugin's admin screen. Install SyncDock (v1.0.1+) on any site before connecting it in the extension.

Is SyncDock Client free?

Yes, and so is the SyncDock plugin it depends on. There's no subscription and no Degird account required. The only optional cost is whichever AI provider's API you choose to bring your own key for — the extension itself doesn't charge for AI usage.

Does it work with sites I don't self-host?

It requires installing the SyncDock plugin, so it works with any WordPress install where you can add plugins — self-hosted sites, and managed WordPress hosting that permits custom plugins. It does not work with WordPress.com sites on plans that restrict plugin installation.

Is my content or AI provider key ever sent to Degird's servers?

No. SyncDock Client has no backend server of its own. Requests go directly to your WordPress sites through the SyncDock plugin, and to whichever AI provider you configure — there's no intermediary logging what you write or publish.

Does it support custom post types?

It inherits the SyncDock plugin's current content model, which covers default WordPress posts. Custom post type support is planned for a future SyncDock release, and the extension will support it automatically once the plugin does.

The takeaway

Managing one WordPress site rarely needs anything beyond wp-admin. Managing several exposes exactly the gap SyncDock Client is built to close: one browser console, one PIN, and a publishing workflow — writing, SEO checks, scheduling, and AI drafting if you want it — that doesn't care how many sites are on the other end of it.

If you're running the kind of multi-site setup this post describes, install SyncDock Client and the SyncDock plugin it pairs with, both free. For the rest of the WordPress lineup — including AuthDock for login security and GuestDock for guest posting — see the full WordPress solutions overview, or browse every browser extension Degird ships.