Introducing the New Atarim WordPress Plugin: Everything You Need to Know

The Atarim WordPress plugin brings visual collaboration onto the site itself, rather than onto a fetched copy of it. That is what makes it the right choice for staging environments and any site that is not publicly reachable — and it gives Atarim’s AI a defined set of actions it can carry out on the site directly, on WordPress 6.9 or later with PHP 8.0 or later.

The plugin is listed in WordPress as Atarim – AI Agency for WordPress: Edit Pages, Fix Code, Update Plugins, SEO & Client Feedback, and the current release is version 5.1.6.

What the Plugin Enables

Installing the plugin changes where collaboration happens. Instead of reviewing a copy of the page, you and your team work on the site itself — which unlocks a set of things a shared link cannot do.

Install from the WordPress Plugin Repository

The fastest route if you have not downloaded the plugin from your Atarim dashboard.

Instructions:

1. In your WordPress admin panel, go to Plugins → Add New.
2. Search for Atarim.
3. Select Install Now on the correct plugin. Look for Atarim – AI Agency for WordPress: Edit Pages, Fix Code, Update Plugins, SEO & Client Feedback so you install the right one.
4. Activate the plugin when the option appears.

Or Download It from Your Atarim Dashboard

Take this route when the site cannot reach the WordPress repository, or when you want a specific build.

Instructions:

1. Log in to your Atarim workspace.
2. Go to Projects if you are not already there.
3. Select Add new and choose Manage a WordPress site.
4. Select Download the plugin. It opens the plugin’s WordPress.org page, where you can download the latest version as a .zip file.

Installing the Downloaded File

Uploading a zip is the standard WordPress route, so nothing here is Atarim-specific until activation.

Instructions:

1. Go to your WordPress dashboard.
2. Navigate to Plugins → Add New Plugin.
3. Select Upload Plugin, choose the .zip file, and select Install Now.
4. Activate the plugin.

Connect the Plugin to Your Atarim Account

Until the plugin is connected, it is installed but inert — the connection is what pairs the site to your workspace.

Instructions:

1. After activation, WordPress opens Settings → Collaborate. On a site that has never been connected, the Connect WordPress to Atarim screen covers the page.
2. Select Connect site (or Connect with Atarim on the settings page). Atarim opens in a new tab.
3. Sign in or create a free account.
4. Check the site address and the workspace shown under Added to workspace on Connect this WordPress site to Atarim?, then select Connect site. To use a different workspace, switch workspace in Atarim before you connect.
5. Back in WordPress, You’re connected appears, then the site’s homepage opens with Atarim loaded on it.

Multisite networks

On a WordPress multisite network, connect each sub-site separately from its own Settings → Collaborate. Each sub-site keeps its own connection and settings. There is no network-wide screen.

The Settings Screen

Plugin settings live in WordPress admin under Settings → Collaborate. You can also select Settings under the plugin’s name on the Plugins screen. Only Administrators can open this page.

Sharing from the Settings Screen

Explore Sharing Options opens the same sharing options you would use in Atarim — copy the collaboration link, invite clients, or add team members — without leaving WordPress.

How WordPress Users Start Collaborating

A WordPress user whose role is allowed in the settings, and who has not connected yet, sees a small Atarim launcher icon on the page. Users marked as Webmaster skip this step, and the admin who connected the site is a Webmaster automatically.

1. The user selects the launcher icon.
2. The Dive Into Real-Time Collaboration window opens.
3. They select Connect Your Account to proceed. They are connected to the project and can collaborate immediately, and are added to the project as a collaborator.

Collaborating with Your Team and AI on a Page

The Review tab of the collaboration sidebar has a Chat for internal team members, so a team can work through a page together and bring AI into the same conversation. From there you can discuss page-level changes, run internal AI reviews, check the page across desktop, tablet and mobile, and leave feedback on a single element or the whole page. AI works with the full page context — layout, spacing, copy, visuals and structure.

Collaborating Inside WP Admin

Collaboration is not limited to front-end pages — it also works on WP Admin screens. That is useful for leaving internal reminders, flagging settings that should not be changed, and coordinating backend implementation work. Feedback left in WP Admin can be marked internal in the same way. Inside WP Admin, Atarim always opens in Browse mode, so switch to Comment to leave feedback.

What “Do It” Can Do on the Site

Two things are easy to confuse here, so it is worth separating them before the capability list.

Show Me

When an AI reply suggests a change to something on the page, it comes with a Show me button. Click it to see the change applied right on the page before anything is saved.

Show Me is only a preview. The change appears in your browser and nothing is saved to your site. If you reload the page, the preview is gone.

While the preview is showing, you’ll see three icons:

• Eye hides or shows the preview, so you can compare it with the original.
• Image takes a screenshot of the page with the preview and posts it in the task as a new comment. Everyone on the task can see it, which makes it handy for getting a client’s approval before publishing.
• Refresh asks the AI for a new version of the change if you don’t like the first one.

When you’re happy with it, click Do It to apply the exact version you previewed to your WordPress site.

“Do It” makes the change for real. It works through the capabilities below, writing to the actual WordPress site — content, media, themes, settings and the rest. It is not visible to clients or guests.

When you select Do It yourself, the change is applied straight away. When the AI runs a Do It for you from a chat or a task, a change to a published, private or scheduled page waits in the Approval Queue (Beta) until someone approves it. On a draft it runs straight away.

Applying a change with Do It uses no credits. The AI reply or review that suggested the change is charged as usual. Explore Credits & Usage

If Do It is greyed out, hover over it or select it to see why. The message is one of these:

• Log in to your WordPress to use Do It
• Your WordPress account can’t edit this page
• Do It is turned off in the Atarim plugin settings
• Do It works on individual pages and posts, not on listing pages like the blog or archives
• Update the Atarim plugin to use Do It
• Do It isn’t available on this page

On a project without the plugin, Do It has an arrow instead. It lists WordPress and the platforms marked Coming soon. Choose WordPress to open Connect WordPress to use Do It, where Install Plugin opens the plugin’s install page on your site.

The plugin exposes a defined set of capabilities on the site, grouped by area. Knowing what is in scope tells you what to expect — and what to be careful about.

The specialist asks for the area it needs rather than the site’s whole list, and runs many operations in a single request instead of one call each. On a site with several plugins active that is the difference between fetching hundreds of operations for every task and fetching the handful the job actually uses, which means less waiting for you and fewer credits spent reaching the same result.

Following changes in the Do It Queue

When you select Do It, the button changes to Queued and the change joins the Do It Queue at the bottom of the collaboration sidebar. Changes run one at a time, in the order you selected them, so you can keep working while they apply.

Until a change is applied, Remove from queue (the ×) takes it off the list. Removing a change that is already applying does not stop it.

The queue belongs to the page you are on. Reloading or leaving the page clears it, and changes still waiting will not run, so stay on the page until they show Changes applied.

Asking for a change in a chat

Besides selecting Do It on a suggestion, you can describe a change in your own words and have a specialist make it on the connected site.

Instructions:

1. Open the task for the page in the Inbox, type your request and select Send to Claro, or @-mention a specialist. Or ask in workspace chat (Beta), where typing / offers Work on a WordPress site and Give a site instruction.
2. Say what to change and where, for example “Change the phone number in the footer to 555-0142.”
3. Read the reply to see what was changed.
4. In workspace chat, when the work includes editing a file such as a theme file, an edit card follows it: Queued, Editing, then Completed, Failed or Cancelled. To stop an edit that hasn’t finished, select Cancel edit on its card.
5. If the change needs approval, it waits until someone approves it. See What Waits for Your Approval.

On a site without the Atarim plugin, the specialist gives you advice and assets but cannot change the site.

Page Builders It Can Edit

The plugin writes through the builder your page was actually built with, rather than editing the HTML underneath it. Which builder is in use is worked out per page.

On a page built with a builder the button does not support, Do It looks the same as anywhere else. It does not check the builder before you select it, so if the change cannot be applied, the reason shows in the Do It Queue.

Elementor edits are checked before they are saved. A value that Elementor’s own rules would reject, such as a heading tag outside h1 to h6, is refused up front and reported with the element and setting that failed, rather than saving quietly and then aborting the whole page the next time somebody presses Publish.

Plugins the AI can work with

When one of these plugins is active on the site, the AI gets matching actions automatically. There is nothing to set up.

Some actions need the plugin’s paid edition. Redirects need Yoast SEO Premium or AIOSEO Pro, and form entries need WPForms Pro rather than WPForms Lite. Contact Form 7 keeps no entries of its own, so those come from the Flamingo plugin. Deleting any of these things waits for your approval.

Undoing a Change

A content change the AI applies can be put back. How that works depends on what was edited.

• For Gutenberg and classic content, the edit is saved as a WordPress revision, and undo restores the revision saved just before the change.
• For Elementor, Beaver Builder and SiteOrigin, Atarim saves the page’s state before each change and keeps the last 10, so undo puts it back.

The control sits on the comment the change came from, so undo is next to the request rather than in a separate history screen.

Image Optimization

Rather than adding another optimizer, Atarim drives whichever one is already installed on the site.

How the Connection Is Secured

An Administrator makes the connection from the site’s WordPress admin, and it belongs to the site rather than to anyone’s WordPress login, so people can change their WordPress passwords without affecting it.

What Waits for Your Approval

The set of actions is different on every site — only the ones your active plugins support are registered, so a plain WordPress site offers a fraction of what a site running WooCommerce and a page builder does. Whatever the set, each action declares at the point it is registered whether it is destructive, and Atarim reads that declaration back from your site before it runs anything.

Destructive covers more than deletion. Removing content, terms, menus, media, users or a theme; merging terms; replacing or restoring a theme file; updating, deactivating or deleting a plugin; restoring a revision or a backup; changing global styles, a site template, a navigation menu or a widget area; deleting form entries or a form; removing a product, coupon or product attribute; and deleting a custom field group are all declared destructive, and all of them wait for you. Edits in the block editor or a page builder are judged by the page instead: they wait for you on a published, private or scheduled page, and run straight away on a draft.

Not everything that changes a site is marked that way, and the exceptions are worth knowing before you hand one over. Activating a theme, updating or reinstalling WordPress core, installing a theme, editing a user or changing their role are all registered as non-destructive, so they run without waiting for you. Running a backup is treated the same way, on the grounds that it adds a snapshot rather than replacing anything — restoring one is held.

Some jobs are too large or too slow for an ordinary page action — replacing a domain across a large database, exporting the database, regenerating a whole media library. For those, Atarim can run a command through WordPress’s own command line on your server. You will not write these yourself: what reaches you is the finished command in the Approval Queue, exactly as it will run, and its output afterwards. Read it the way you would read a command before pasting it into a terminal on a client’s site, because it changes files and database content directly. It is available on administrator accounts only, and every run is recorded in the site’s log.

Security Scan

A connected site can be scanned for known vulnerabilities in the plugins, themes and WordPress core it currently has installed. Where a component matches a published advisory, the scan reports the version sitting on the site alongside the version that fixes the problem — so the question becomes whether to update, rather than whether there is anything to update at all. You can ask for a scan in chat, or from a connected assistant.

Reading is safe: the scan never installs, updates, activates or changes anything, and acting on a finding is an ordinary update that goes through the approval gate like any other. Two results are worth reading properly rather than at a glance. If the site’s installed inventory could not be read, nothing was assessed. And a component reported as untracked was never checked against the advisory data in the first place. Neither of those is a clean bill of health.

Running a scan

Instructions:

1. In workspace chat (Beta), ask for a scan and say which project, for example “Scan the Bloom Bakery site for known vulnerabilities.” In a project’s own chat, “Scan this site” is enough.
2. Read the reply. In a project’s own chat, a scan that runs in the background also shows a scan card, which reads Scanning while it checks what is installed.
3. Read the result. On a scan card, Clean means nothing installed matched an advisory. A count such as 2 vulnerable lists each affected item with its severity and either Update to the fixed version or Abandoned, no fix available. Inventory unavailable means nothing was checked, as described above.
4. To act on a finding, ask for the update. It waits for your approval like any other plugin update.
5. After updating, ask for another scan to confirm, or select Scan again on the scan card.

Backups and Restores

These capabilities only appear on sites running JetBackup for WordPress. Without it there is nothing here — there is no generic backup layer behind them.

A restore is by snapshot, never by upload — you cannot hand it a backup file. Files and the database are handled separately, and each can be restored in full, limited to named folders or tables, or skipped altogether; the default is a full restore of both. Only account backups can be restored, and only WordPress administrators can reach any of this.

Example Use Cases

What can stop the AI working on your site

The AI reaches your site through the plugin, from Atarim’s servers rather than your browser. Three things on the site’s side can stop it:

• File editing is switched off in your site’s configuration. The AI cannot run code or create or change theme files. If all file changes are switched off, it also cannot install or update plugins and themes, or update WordPress core.
• A security plugin or firewall blocks Atarim. If Atarim’s requests to the site are blocked, the AI cannot reach it. Explore Whitelisting Atarim
• The AI’s WordPress account lacks the rights. The AI acts as the account chosen under 1 click login from Atarim as, so it can only do what that account can. Explore Autologin

Known Limitations

• PHP 7.4 and WordPress 6.0 are minimums. The AI actions need PHP 8.0 and WordPress 6.9.
• Plugin settings are separate from Atarim settings. The role picker and 1 click login from Atarim as live in WordPress admin.
• Settings need Save & Apply. Nothing takes effect until you select it.
• Consent creates collaborators, not team members. Team membership requires an Atarim invitation.
• AI actions reach beyond content — including themes, plugins, users and settings.

FAQs

Common issues

• The plugin will not install or activate — check the site runs PHP 7.4 or later and WordPress 6.0 or later.
• The AI actions are missing although the plugin works — the site is below WordPress 6.9 or PHP 8.0, or Enable "Do it" via Atarim AI is unticked in Settings → Collaborate. Everything else keeps working.
• No collaboration interface after activation — confirm the site is connected, and that your WordPress role is selected under Who can collaborate.
• A colleague cannot see the launcher — their role is not selected in the settings, or Guest Mode is off and they are not logged in.
• Settings changes had no effect — select Save & Apply. The screen does not autosave.
• Someone joined as a collaborator instead of a team member — invite them to your Atarim account first, using the same email address as their WordPress account.
• 1 click login signs in but nothing works — the chosen account lacks the permissions it needs. Choose an Administrator under 1 click login from Atarim as.
• An AI action changed more than expected — restore from backup and run future actions on staging first.
• The site is behind a firewall and will not connect — whitelist Atarim at the host or WAF level. See the whitelisting guide.

Conclusion

Installation is straightforward: install from the repository or upload the file from your dashboard, connect, then set who can collaborate. The settings worth deliberate thought are the role picker and 1 click login from Atarim as, because both decide who can act on the site.

The plugin also gives Atarim’s AI a defined set of actions it can perform — reaching content, media, themes, plugins, users and settings — on WordPress 6.9 or later with PHP 8.0 or later. Set it up the way you would set up anything with that reach: backup first, staging before production.