WP Foreman brings WordPress updates, backups, monitoring, user management, and client reports into one dashboard. Our first look left us impressed with the easy site connection and range of maintenance tools.
If you manage client websites or your own WordPress installation, the free first-site account gives you a way to explore the platform.
Key Takeaways
- WP Foreman brings WordPress updates, backups, monitoring, user management, and client reporting into one dashboard.
- In our first look, connecting a sandbox site was quick, and a manual backup completed successfully.
- The dashboard also includes remote plugin, theme, and user controls, plus visual checks, uptime monitoring, renewal reminders, and automated form testing.
- We didn’t test every feature. For example, we didn’t complete a form test, restore a backup, or send a client report.
WP Foreman—First Look Video

Trust Pages That Made a Strong First Impression
Before creating an account, we checked three areas: the About page, documentation, and changelog.
The About page identified founder Nate Baldwin and included his photo, company background, and product information. We like seeing a face alongside a name because it helps establish who is behind the software.
Next, we tried the documentation search with the word “backup.” It returned relevant information, including screenshots with annotations. The search worked, and the material looked clear enough to support a new user. WP Foreman’s introductory documentation also explains the platform’s central management role.
The changelog was available within the documentation. It included dates and detailed explanations of changes, rather than a vague list of version numbers. All three checks gave us a positive first impression before we entered the application.
How the Crew Organizes Website Maintenance
WP Foreman’s website presents its features as a crew working on your websites. We liked that approach. It adds personality to a product category that can otherwise feel highly technical.
The seven crew roles described on the website cover the following work:
- Crew 1 manages WordPress core, plugin, and theme updates, either with one click or on a schedule.
- Crew 2 provides update safeguards, including backups before updates and screenshot checks that flag changed pages.
- Crew 3 checks pages with before-and-after screenshots, looks for errors on key pages, and brings together speed and traffic information.
- Crew 4 handles encrypted, incremental backups, with restore and migration options and support for your own storage.
- Crew 5 handles monitoring, including confirmation from a second region and alerts about SSL certificates and domain expiration.
- Crew 6 flags vulnerable and abandoned plugins across managed sites.
- Crew 7 creates plain-English client reports using your agency’s branding.
The website also describes rules, approval controls, and a job log. You can decide which actions run automatically and which require your approval. Its logging covers actions taken through WP Foreman and changes made directly in the WordPress admin.
These were website descriptions at this stage. The hands-on portion gave us a closer look at many of the corresponding screens.
Released Features and Plans Shown During the Walkthrough
The website highlighted two additions that had shipped by the time of the recording: Ask the Foreman and the form tester.
Ask the Foreman provides an AI interface for asking about managed websites and requesting work. The form tester checks selected forms and alerts you when they stop working. We explored both later in the dashboard.
The site also showed planned SEO-related tools, including page editing, SEO setup, settings changes, and approval of each change. Host connections were another upcoming area, with Xcloud and GridPane named.
Those SEO and hosting controls were planned features during our first look, not capabilities we demonstrated.
A Free First Site and a Fast Sign-Up
WP Foreman presented the first website as free forever, with the full feature set available and no card required. The paid pricing also looked competitive with other WordPress management tools we had seen, although we didn’t conduct a detailed pricing comparison.
The sign-up screen offered Google or email registration and an optional newsletter subscription. We chose Google to avoid a separate email verification process just for purposes of the video.
Registration was unusually quick in our experience. After a few clicks, we were inside the dashboard.
The main navigation included Sites, Updates, Clients, Renewals, Rules, an activity log, and Ask the Foreman. Several areas included walkthrough wizards, which helped explain the screens as we encountered them.
We also found light, dark, and system appearance settings. Dark mode was a welcome detail because we spend a lot of time in website management tools. The solution used in our agency didn’t offer it, so the new feature immediately caught our attention.
Account Settings, Storage, and Analytics
Account settings were available through the username menu in the lower-left corner.
The profile area included a time zone setting. That matters when you’re reading timestamps or scheduling work, reports, and alerts for client websites.
Backup Storage Connections
The backup storage settings supported Google Drive, Dropbox, and S3-compatible storage. Named examples included Amazon S3, Backblaze B2, Wasabi, Cloudflare R2, and DigitalOcean Spaces.
We didn’t connect an external storage provider during this walkthrough. We reviewed the available options, then tested a manual backup later.
Analytics and Account Usage
Analytics connections included Google Analytics 4, Plausible, and Umami. We didn’t connect those services, so we didn’t test the resulting analytics dashboard.
The billing area also brought together information about sites, team members, Ask the Foreman allowance, and backup storage usage. It provided a place to review the account’s resources without searching through separate feature screens.
Agency Branding and Plugin White Labeling
The branding settings gave agencies several ways to make client-facing material their own.
You could enter an agency name, upload a logo, and choose brand and accent colors. Report email settings included sender and reply information, with options to use WP Foreman’s default sending setup, configure your own domain through DNS records, or use an SMTP mail server.
There was also a report domain setting.
On the WordPress side, the connector plugin could be white-labeled. The fields included its name, description, author information, author link, and settings menu name. For example, the walkthrough discussed naming it something like “InfluenceWP Website Care” so a client would recognize its purpose.
The plugin could also be hidden from the plugins list. Later, when we checked its settings inside WordPress, we saw the connection controls. Keeping those controls out of a client’s routine view can reduce the chance of an accidental disconnection.
Security, Teams, and Site Transfers
Two-factor authentication was available in the account settings. We strongly favor using it for tools with administrative access to websites.
The team section included an invitation option, so additional people could join the account.
Site transfers were another useful control. WP Foreman described moving a site to another WP Foreman account with its backups and history while letting you choose what transfers and what stays behind. Nothing moves until the receiving owner accepts.
We discussed a few situations where that could help: handing a client to another agency, transferring responsibility when leaving the business, or moving a website into a client’s own WP Foreman account. We didn’t perform a transfer during the walkthrough.
Rules, Notifications, and Integration Controls
The Rules area lets you start with a recipe or build a rule yourself. The available categories covered updates, alerts, backups, and reports.
Examples included weekly updates and monthly client reports. We returned to the account-wide view near the end of the walkthrough and found more of these controls than we had explored initially. That broader view was a useful reminder that the platform manages a collection of sites, not just the individual site screen.
Alerts and Delivery Channels
Notification settings included push notifications, Slack, and Discord. You could choose alert types and frequency, including downtime, certificate expiration, form failures, and changes made outside WP Foreman.
Text messaging, Microsoft Teams, and Google Chat were marked as coming soon during the recording.
API Tokens and Webhooks
API tokens allowed scripts, Zapier, and other tools to interact with WP Foreman, with controls over what a token could do.
Webhooks could post JSON to a URL when events occurred, supporting connections to Slack, Zapier, or your own systems. An MCP server was also listed as coming soon. We didn’t test these integrations.
Connecting a WordPress Site
We added a sandbox site to see how the connection process worked. The setup followed a short sequence:
- Enter the website’s name and URL in WP Foreman.
- Download, install, and activate the WP Foreman connector plugin.
- Copy the connection key into the plugin’s settings inside WordPress.
- Connect the plugin, then refresh the WP Foreman dashboard to confirm the connection.
The process was smooth. The site initially showed a pending status, then changed to connected after we refreshed.
The connection screen also included private notes and a pin-to-top option. A guided tour introduced the site overview, site menu, health information, notes, and one-click access to WordPress admin.
We didn’t need to work through the documentation to finish the connection, although it was available if needed.
The Site Overview and Work Log
The connected site’s overview brought together WordPress and PHP versions, plugin and theme versions, pending updates, and the latest backup information.
It also displayed areas for uptime, speed, visitor counts, SSL, domain monitoring, website email, and security status. Visitor data required an analytics connection, so we didn’t have those numbers in this test.
A shortcut opened WordPress admin. We also found desktop and mobile snapshots associated with the visual-check feature.
The Log Work action was a useful addition for client maintenance. It let us record what we did, the date, time spent, and supporting details. We could also choose whether that entry should appear in client reports.
That provides an agency a place to document work outside the automatic maintenance activity, including additional tasks that a client might otherwise never see.
Managing Plugins, Themes, and Users Remotely
The plugin and theme screens provided controls without requiring a separate visit to the WordPress admin.
We could review active and inactive items and access actions such as installation, updates, activation, deactivation, and deletion. WordPress core management was available in the same area. WP Foreman’s documentation describes these remote plugin, theme, and core controls.
The Users tab pulled in accounts from the connected website. It showed usernames, email addresses, roles, and post counts.
From there, we could add a user, choose a role, edit an existing account, send a password reset, or remove a user. These centralized WordPress user management controls are useful when you’re responsible for several installations.
We explored the available controls, but we didn’t demonstrate every action during this first look.
Backups and Searchable Activity Logs
The backup screen showed scheduled backups and the next run time. It also included a manual backup option, which we started while exploring the other tabs.
When we returned, the backup had succeeded.
Its details included the backup type, duration, size, and file count. A download option provided the backup as a ZIP file.
We didn’t test a restore, migration, or external storage connection. The successful manual backup was the recovery-related action we confirmed in this session.
The activity log was also easy to work through. It supported searching, filtering, and downloading records as a CSV file. As we used more features, the log began filling with additional activity.
Having an activity log in the management platform may remove the need for a separate logging plugin in some setups. The same applies to several other included tools, depending on what a site already uses.
Performance Checks, Screenshots, and Uptime
Google PageSpeed Testing
The Performance tab described daily Google PageSpeed checks for mobile and desktop. It showed the next scheduled run and included a button to run a test immediately.
We started a test and later saw a score of 100 on the sandbox site. That site had very little content, so the result shouldn’t be treated as evidence of production-site performance. The useful observation was that WP Foreman returned the results within its dashboard.
Visual Change Checks
The visual-check tool captures selected pages on desktop and phone, then compares them with earlier screenshots.
Our initial attempt reported that one of two screenshots had failed. We didn’t establish the cause. We then changed the selected page, removed the original homepage entry, and ran the check again.
The later check completed and reported that the screenshots looked the same. That was a successful retry, rather than proof that the original issue came from a particular cause.
Uptime and Expiration Monitoring
The monitoring area included uptime, response time, SSL expiration, and domain expiration.
We emphasized certificate and domain tracking during the walkthrough because both belong in routine website maintenance. An expired domain can take a site offline, while certificate problems can affect visitors’ ability to access it securely.
The security tab reported no issues on the test site and indicated that more checks were planned.
Automated Form Testing
The form tester was one of the features that stood out.
WP Foreman described filling in selected forms as a visitor would. Scheduling options included daily checks, weekly checks, and checks a few minutes after WP Foreman updates the site.
If a form stopped working, the tool could send an email and a push notification when those channels were enabled.
The supported form plugins shown during the walkthrough were Gravity Forms, WPForms, Contact Form 7, and Fluent Forms. A Find Forms button was available to discover forms, after which you could choose the ones to test.
Because we didn’t have a form ready on the sandbox site, we couldn’t confirm a submission or failure alert. Our positive reaction was to the available feature and controls, not a completed form test.
Form testing can otherwise require a separate paid tool. Its inclusion here was part of the broader appeal of having maintenance checks in one dashboard.
Renewal Reminders and Client Reports
Tracking Important Dates
The site-level Renewals area could hold dates for care plans, hosting, plugin licenses, and other commitments.
Entries could appear in client reports when a renewal approached. SSL certificates and domain registration also appeared as automatically tracked items.
This was a welcome detail. We hadn’t seen this type of renewal tracking in the website maintenance tools we had used. It gives agencies a place to keep their own reminders and communicate upcoming dates to clients.
Building and Scheduling Reports
The reporting area supported both on-demand and scheduled reports.
Available date ranges included the previous month, the current month so far, the past 30 days, the past seven days, the previous quarter, and custom dates. You could choose which information to include, add a site logo, and write a closing message.
A podcast conversation between Rob Cairns and founder Nate Baldwin had drawn our attention to reporting before the walkthrough. Seeing the report controls reinforced our positive impression, although we didn’t build and send a complete client report.
The combination of selectable information, agency branding, renewal dates, and manually logged work looked promising for showing clients what their maintenance plan includes.
Site-Level Settings and Feature Controls
Each site had its own settings for the name, website address, and client assignment.
We also found a sign-in-as-user option and switches for individual features. For example, if analytics weren’t part of a particular client’s setup, that feature could be turned off to simplify the site’s dashboard.
The same screen provided options to transfer the site to another account or remove it from WP Foreman.
These controls complemented the account-wide settings. Agency branding, notification preferences, and integrations lived at the broader level, while the individual site screen let us adjust what applied to that website.
Ask the Foreman: Fast Answers With Unclear Allowances
What the AI Settings Offered
The built-in Ask the Foreman option covered questions about managed sites, WP Foreman, and WordPress upkeep. The pricing explanation described a monthly allowance shared by the team, plus up to 100 messages a day per person.
You could add credit or supply an Anthropic API key. With your own key, usage would be billed directly to Anthropic, bypassing WP Foreman’s message limits.
We also found Ask the Foreman at both the account level and within a site.
The Two Questions Tested
We asked for the sandbox site’s PHP server version, then asked how many plugins were inactive. Both answers returned quickly.
We also discussed the usefulness of asking across multiple sites, such as requesting a list running PHP 8.2 or below. That was a possible use described in the walkthrough, not a multi-site test we performed.
Where the Usage Explanation Needed Work
After the PHP question, the interface showed 6% of the monthly allowance used. After the inactive-plugin question, it showed 8%.
That left us unclear about how the daily message limit, monthly allowance, and credit purchases related. The top-up options showed $10, $25, and $50 amounts, but we couldn’t tell how much usage each would provide.
We didn’t establish a billing error. Our feedback was about clarity for a new user: the interface needed a more understandable connection between the allowance percentage and purchased credit. We also mentioned waiting for the planned MCP server as another possible path for connecting an existing AI setup.
Final Impressions of WP Foreman
Our strongest takeaway was how much routine maintenance work WP Foreman brought together without making the initial connection difficult. The successful manual backup, remote management controls, monitoring screens, reporting options, and dark mode all contributed to a positive first impression.
The main unresolved question was AI allowance clarity, but we’re confident the vendor will shed some light on this so we can update this post.
Frequently Asked Questions About WP Foreman
What Does WP Foreman Do?
WP Foreman is a dashboard for managing WordPress websites. Its tools include updates, backups, monitoring, user management, activity logs, and client reports.
How Do You Connect a WordPress Site to WP Foreman?
Add the site’s name and URL in WP Foreman, then install and activate the connector plugin on the site. Copy the connection key into the plugin settings, connect it, and refresh the dashboard to confirm the site appears as connected.
What Features Did You Test in the WP Foreman First Look?
We connected a sandbox site, explored remote management screens, and ran a manual backup and a PageSpeed test. We also reviewed monitoring, reporting, visual checks, and form-testing controls, but we didn’t test every feature or complete actions such as a form submission, backup restore, or client report.
Is the First WP Foreman Site Free?
During our walkthrough, WP Foreman presented the first site as free, with access to the full feature set and no credit card required. Check WP Foreman’s current pricing before signing up, since plan details may change.