sarcio

How it worksWordPressPricingDemosDocsSecurity
Sign inGet started
← Docs

Sarcio for WordPress

Install the plugin, connect it, and approve your first fix from your WordPress admin. About ten minutes, no developer, nothing to configure.

  1. Install the plugin

    Once the plugin is listed in the WordPress plugin directory, search for Sarcio under Plugins → Add New Plugin and click Install. Until then, download the file below, go to Plugins → Add New Plugin → Upload Plugin, choose it, click Install Now and then Activate Plugin. A newer version installs the same way over the old one; your settings are kept.

    Download the plugin

    Version 0.6.2, released 17 October 2026, 220 KB. The plugin is awaiting its listing in the WordPress plugin directory; until then, install it from this file.

    Download sarcio-0.6.2.zip
    SHA-256 4635b54e31eb62897daacc873e674267836df7d5072bfb40945dd66458968a08

  2. Connect to Sarcio

    Open Sarcio in the left menu and click Connect to Sarcio. New to Sarcio? Click Create your workspace instead, or create your account here first: a name, an email, a password, a card, and you are in. Sign in, confirm the site, and you come back to WordPress with the status box saying Connected to Sarcio. The plugin received its keys itself; there is nothing to copy.

    Everyone else who reviews fixes opens Sarcio → Inbox and clicks Connect your Sarcio account once. WordPress then keeps them signed in to the Inbox.

  3. A visitor reports a bug

    A Report a bug button now sits on your site. A visitor clicks it, says what went wrong in their own words, and can point at the broken part of the page. Who sees the button is up to you: people who can edit posts (the default), every signed-in user, or everyone. Its colour, icon, text and corner are yours too, under Settings → Sarcio.

  4. Preview, approve, keep

    Each report lands in Sarcio → Inbox with its fix explained in plain words, and a count appears on the menu and on your WordPress Dashboard. Preview opens the fix on your live site for you alone. Approve asks for your Sarcio password, then every visitor gets the fix. Not sure? Ask someone else on your account to check it first, or Try drafting again with a note on what to change.

    Once a fix is live, Keep this fix saves it on your site. It keeps working even if the site is no longer connected to Sarcio, and Sarcio → Kept fixes lists every kept fix with a switch to turn it off and a button to remove it.

Looking after sites for clients

One Sarcio account covers every client site. Connect each site from its own WordPress admin; each gets its own Report a bug button and its own Inbox there, and your dashboard at Sarcio shows them side by side with a site picker. Invite your team once under People: any of them can review a fix, and a risky fix can wait for a second person before it goes live. The Agency plans pool the monthly fix allowance across every site.

  • Sites in your Sarcio dashboard lists every connected site and when it last checked in.
  • People is where you invite a colleague or a client who should approve fixes on their own site.
  • Settings → Plan & billing shows how many sites and fixes the plan includes, and lets you move between plans as your client list grows.

What you do not need

No developer: nobody edits theme files or PHP, and Sarcio never writes to your site's files. No server to run: the plugin works on ordinary shared or managed WordPress hosting. No code repository or issue tracker: a kept fix is the permanent fix. A team that does have those can connect them later under an engineering workspace, but a WordPress site never needs them.

For developers

The plugin's settings (who sees the reporter, where server-side fixes apply, the refresh interval, pinning keys in wp-config.php, and the optional sidecar for hosts that can run a service) are in the server-side fixes guide.

Ready to try it on your own site?

Create a workspace, add a site, and follow these steps on your own app.

Create a workspace