Why We Built It
Guest Posting Should Not Mean
Handing Over the Keys
Every publisher who accepts outside contributions runs into the same wall. To write in WordPress, someone needs an account. The account WordPress offers for this job is Contributor, and Contributor was designed for a colleague down the hall, not a writer you met over email last week.
So editors improvise. They create accounts and forget to delete them. They ask writers to send Google Docs and paste the formatting back in by hand. They install a form plugin that emails a draft and loses the images. None of it is secure, and none of it scales past a handful of posts a month.
GuestDock takes the other approach: keep the contributor inside WordPress, where the editor and the media library and the preview all work properly, and make the boundary real. Isolation at the query level, access that expires, submission limits that count themselves, and an editorial queue where approval and feedback actually live. Free, GPL, and complete — because guest posting security should not be a paid upgrade.
Isolation That Holds
Filtered at pre_get_posts, AJAX, and REST — not hidden with CSS.
Access That Expires
Guest accounts close on their own date instead of living forever.
A Real Editorial Desk
One queue, inline preview, feedback that reaches the author.
Quality Enforced Upfront
Word counts, featured images, excerpts, and SEO checked while writing.
SEO You Control
Link caps and automatic rel="nofollow sponsored" on outbound links.
Free and GPL
Every feature ships in the WordPress.org release with no premium tier.