Independent WordPress tools studio
Small studio. Focused plugins. Direct accountability.
WPGO builds practical WordPress tools for publishers, site owners, and agencies—with product decisions, maintenance, and support close to the developer doing the work.
Built by a WordPress developer
WPGO is the work of David Gwyer.
David first started using WordPress in 2006 and founded WPGO to turn recurring publishing and site-management problems into focused tools.
The studio model is deliberately compact: product scope stays clear, support retains technical context, and the public catalogue only promotes plugins that have passed the current commercial and maintenance review.
Product principles
What WPGO optimises for.
A smaller catalogue is useful when every product has a clear job, an understandable workflow, and an honest boundary.
01
Solve a defined problem
Each current plugin starts with a specific publishing or site-structure outcome—not a long feature list looking for a use case.
02
Fit the WordPress workflow
WPGO favours tools that feel at home in the editor and help site owners stay in control of their content and presentation.
03
Make the boundary visible
Current capabilities, edition differences, requirements, support routes, and legacy status should be understandable before someone relies on a product.
The current product line
Three plugins with three clear jobs.
Data storytelling
ChartQuill
Create responsive, self-hosted charts and linked data tables from the WordPress editor.
Site structure
Simple Sitemap
Build and preview a useful HTML sitemap with visual blocks and established shortcode support.
Display filtering
Content Censor
Filter selected words from public-facing output while preserving the original stored content.
Independent in practice
A direct route from product question to product context.
Focused catalogue
ChartQuill, Simple Sitemap, and Content Censor appear in the current sales catalogue. Older products remain available only where customer, documentation, or account obligations require them.
Direct support context
Support stays close to the products and their technical decisions, with separate routes for free, paid, legacy, account, and general questions.
Start with the problem
See which current plugin fits your workflow.
Compare the three focused products, their licence paths, and the outcomes they are designed to deliver.