Rounds is a website-care service for developers and agencies. Your client opens a small panel on their own site, points at a text, and asks for a change or makes it. You decide which texts they may touch, and every change can be undone. This plugin connects a WordPress site to Rounds. It does nothin
PricingFree downloadThe WordPress.org download is free. Pro versions, add-ons or external services may cost extra.
CompatibilityRequires WordPress 6.4 and PHP 7.4.
SourceWordPress plugins · Nov 18, 2026
01 / Source details
Aboutthistool.
Rounds is a website-care service for developers and agencies. Your client opens a small panel on their own site, points at a text, and asks for a change or makes it. You decide which texts they may touch, and every change can be undone.
This plugin connects a WordPress site to Rounds. It does nothing on its own: you need a Rounds account (free to start, paid plans for more sites) at rounds-for.dev .
What the plugin lets Rounds do, and nothing else:
Read the editable texts of a page: Elementor text, heading, button and similar widgets; block editor paragraphs, headings, list items and buttons; headings, texts, buttons, alt texts, accordions and tabs made with WPBakery, Divi 4, Avada, Beaver Builder, Bricks, SiteOrigin Page Builder, Kadence Blocks, Spectra and GenerateBlocks; and a post’s title, excerpt and text custom fields (never one that holds a script link, a path or data).
Prepare a change in the plugin’s own table. The page does not change yet.
Put a change live in the page as its builder stores it, changing only that text, after a snapshot, with a revision that names the change where WordPress keeps one.
Roll a change back from that snapshot.
Report versions of WordPress, PHP, the database, the theme and the plugins, so you can see what needs updating, with whether PHP has its sodium extension, the installed themes and how many administrators the site has (a number, never who).
Publish your scheduled posts on time. WordPress publishes a scheduled post only when somebody visits the site, so on a quiet site it can go out late. The plugin tells Rounds when your scheduled posts are due (their IDs and times, nothing else), and at each one’s time Rounds asks your site to publish it, with WordPress’s own function. Rounds can publish only what you scheduled, and never early.
Settings changes: off until you turn them on. Under Settings → Rounds , an administrator can allow Rounds to change some of the site’s settings, group by group, each with its own checkbox:
site identity (title, tagline, logo, site icon); menus (classic and block theme navigation); header and footer text in widgets and template parts; the homepage and the posts page; turning comments off on a page;
contact forms’ recipient, subject and messages (Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Elementor Pro), with an e-mail to the site’s admin address whenever a form’s recipient changes; a page’s SEO title and description (Yoast SEO, Rank Math, SEOPress, All in One SEO); 301 redirects (Redirection, Rank Math, Yoast SEO Premium), never from the login, wp-admin, the REST API, WordPress’s own files or the homepage;
media: an image’s alt text, and replacing an image’s file with another from the media library (its old files, every size of it, are kept for 30 days in a folder of the plugin’s own, so it can be put back; the folder refuses web requests on servers that read .htaccess , and deleting the plugin removes it);
WooCommerce: prices, stock, short descriptions and the store notice;
the page cache: emptying it through your cache plugin’s own purge.
A setting is changed only from that fixed list, only in the groups you allow, and only after your developer approves the change in Rounds, having seen it before and after. Most can be undone. Unticking a group stops its changes at once. Who changed the choice and when is kept here and sent to Rounds (see External services).
What is kept, and for how long: who changed the choice and when, here and at Rounds, while the site is connected (Rounds keeps an older choice 24 months after it was replaced, to show what was allowed when, and deletes all of a removed site’s within 30 days); each change, here, for 12 months from its last step, which is also how long it can be undone; a replaced image’s old files for 30 days. Deleting the plugin removes all of it from the site.
What it can never do, by construction:
Run code, SQL or commands sent from outside.
Install or delete plugins or themes, or edit theme, plugin or any other code files. (The one file it ever writes is an image you replace from the media library, when you allow media changes.)
Administer the site: create, invite or delete accounts, change anyone’s role, or switch plugin or WordPress updates on or off. Those stay with the site’s administrators, in WordPress.
Read orders, form entries or comments, or delete posts.
Every request from Rounds is signed with a key made for your site alone and checked by the plugin. No WordPress password, Application Password or cookie ever leaves your site. Under Settings → Rounds you can pause Rounds or disconnect it at any time, and see a log of everything it did.
The plugin adds nothing for your visitors: no script, no style and no request to Rounds, until you connect the site.
Source code
The plugin’s PHP is in this package, readable, and follows the WordPress coding standards; its translations come from translate.wordpress.org. assets/rounds.js , the panel your clients open, is the readable (not minified) build of the same Rounds widget code sites load, built from one entry with esbuild; it is the whole of that code, with nothing left out.
External services
This plugin connects your site to Rounds , a service run from rounds-for.dev ( https://www.rounds-for.dev , or the address in the ROUNDS_CONNECTOR_API_URL constant). It needs Rounds to work. Every call below goes to Rounds and nowhere else, and none of them carries a WordPress password, an Application Password or a cookie. It does not contact Rounds or anyone else until an administrator connects the site.
From your server to Rounds:
/v1/wp/connect/start – when an administrator presses Connect to Rounds . Sends your site’s address, the address of its REST API and of the plugin’s screen, a public key the plugin has just made, the plugin’s version, whether PHP has its sodium extension and the administrator’s language. Rounds answers with the one-time code the screen shows.
/v1/wp/connect/status – while a code waits to be entered in your Rounds account (fifteen minutes at most), each time an administrator opens the plugin’s screen or presses Check now . Sends the same public key and the language, and receives Rounds’ public key once the code is claimed.
https://www.rounds-for.dev/v1/wp/pair – when you connect with a pairing code from your account instead. Sends the code, your site’s address and REST API address, the new public key, the versions of the plugin, WordPress and PHP, and whether PHP has its sodium extension.
/v1/wp/probe – once, right after connecting, signed with your site’s key. Asks Rounds to try to reach your site, so the plugin knows whether calls from outside get through.
/v1/wp/work – signed, once an hour, or every minute when your site blocks calls from outside (or ROUNDS_CONNECTOR_POLL is set); less and less often, once a day at most, while Rounds no longer accepts your site’s keys (the site was removed from its Rounds account). Collects the requests Rounds has signed for your site and sends back their results, which can include the editable texts of the pages asked about, the result of a change, and the versions report.
/v1/wp/consent – signed, each time an administrator changes which settings changes are allowed (Settings → Rounds). Sends the groups now allowed, who changed them as user: and their WordPress user number (never a name or address), and when, so that Rounds offers only the changes you allow. Nothing is sent while Rounds is paused or the site is not connected; Rounds then learns the choice from the site’s next report.
/v1/wp/schedule – signed, at the end of a request in which a post was scheduled, rescheduled or unscheduled, and from wp-admin once an hour at most. Sends the ID and the time (UTC) of each of your scheduled posts, the soonest hundred, and nothing else: no title, no text, no author. The signed calls above carry the same list. Rounds uses it only to ask your site, at each post’s time, to publish it. Nothing is sent while Rounds is paused, or with ROUNDS_CONNECTOR_ON_TIME set to false in wp-config.php .
From Rounds to your site: Rounds calls your REST API under /wp-json/rounds/v1/ , signed, when you or the people you invited work on a page, and when one of your scheduled posts is due, to publish the scheduled posts whose time has come. Your site answers with the editable texts of that page, the settings Rounds may change with their values (among them the addresses your contact forms send to, which Rounds shows to your developer but never gives to its AI), the result of a change, or the versions of WordPress, PHP, the database, the theme and the plugins.
From the browser of somebody who opens the panel (you, your client, or a person you invited; never a visitor who does not):
/v1/wp/widget/<project> – the panel’s settings and words, and whether the site is in strict mode. Outside strict mode no code is loaded from Rounds.
/widget/v/1.2.1/strict.js – in strict mode only, which you turn on or off in your Rounds account: a small script from Rounds that draws the highlights and opens the panel in a frame on www.rounds-for.dev, where its sign-in and session stay. The plugin names this exact file and its SHA-384 hash, and the browser runs that file or nothing; a newer one comes only with a plugin update. It holds no password, session or cookie, and the frame hands the page only the ticket below.
/widget/edit-kit.js – in strict mode only, when somebody previews a formatted text or a photo on the page: the formatting and photo previews that strict.js loads, named and pinned by its own SHA-384 inside that file, so it too is that exact file or nothing.
/v1/wp/panel-ticket – a short-lived ticket that lets your site mark the editable texts on the page for that person.
/v1/content/<project> – reading the text they point at, and saving or asking for a change to it.
/v1/requests – a request for a change, with the words they typed and the page it is about.
/v1/panel/session and /v1/rounds/* – an invited person’s sign-in, and the round of changes they ar
See it in action
Screenshots & previews.
Settings → Rounds before the site is connected: paste the one-time code from your Rounds account.Connected: pause Rounds or disconnect at any time, and see everything Rounds did on this site.
02 / Source details
Gettingstarted.
01Install the plugin from Plugins → Add New , or upload the zip under Plugins → Add New → Upload Plugin , and activate it.
02In your Rounds account, add the site as a WordPress site and copy its one-time pairing code. A code works once, for fifteen minutes.
03In wp-admin, open Settings → Rounds , paste the code and press Connect to Rounds .
04The screen says Connected . Your site is now listed in Rounds.
To stop, press Pause Rounds or Disconnect on the same screen. Deleting the plugin removes its tables, settings, role and service user (on a multisite network, from every site); your pages and their revisions stay.
03 / Source details
Frequently asked questions.
Do I need a Rounds account?
Yes. The plugin is the site’s side of Rounds and does nothing without an account. You can start for free at rounds-for.dev .
Which page builders are supported?
Elementor (its text, heading, button, icon box, image box and similar widgets, add-on packs too), the block editor (paragraphs, headings, list items and buttons, and the text blocks of Kadence Blocks, Spectra and GenerateBlocks), Beaver Builder and SiteOrigin Page Builder, each tested with the real plugin. WPBakery Page Builder, Divi 4, Avada and Bricks are tested with saved pages in each builder’s format, not yet with the builders themselves. Pages made with Oxygen, Breakdance or Divi 5 are not changed directly yet: the panel says which builder made the page, and your client can still describe the change and send it to you as a request. The plugin reads each builder’s stored page; it never runs the builder to make a change. Beaver Builder and SiteOrigin also keep a copy of a page’s text in the post itself, which search and excerpts use; Rounds leaves that copy as it was, and it is brought up to date the next time the page is saved in the builder.
Can my client break the site?
They can only change the texts you allow, as text: scripts, styles, event handlers, unsafe links and shortcodes are removed before anything is saved. Every change can be rolled back from the snapshot Rounds keeps before it. Where WordPress keeps revisions for it (Elementor, the block editor, WPBakery, Divi, Avada, and a post’s title and excerpt), the change is also saved as a revision; Beaver Builder, Bricks, SiteOrigin and custom fields keep none.
Does the plugin slow my site down or track my visitors?
No. It adds nothing to your pages for visitors and sends nothing about them. Until you connect, it sends nothing about your site and makes no call at all.
What happens when I disconnect?
The site’s keys are deleted at once and Rounds can no longer reach the site. The settings you allowed Rounds to change are all unticked, and changes still waiting for approval are closed. Pairing again with a new code makes new keys.
Where is my data?
The texts and their history stay in your WordPress database. Rounds keeps the site’s address and versions, and what it needs to show and undo the changes made through it. See the privacy notice .
FinderPress Media Auditor helps site administrators scan for broken images, missing Media Library files, unreachable media URLs, and other media issues across WordPress content. Use it to audit images, video, audio, PDFs, featured images, and attachment files without sending scan data to an external
The Accepted Payment Methods plugin is a straightforward, lightweight solution that enhances your website by displaying visually appealing icons of the payment methods you accept. This plugin is ideal for a variety of websites, including e-commerce platforms, service-oriented websites, and informati