Acquia Web Governance
Acquia Web Governance Wordpress plugin
Install
No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:
wp plugin install https://github.com/justinnde/acquia/archive/refs/heads/main.zipIntegrates Acquia Web Governance (Monsido) into your WordPress admin dashboard.
Description
This plugin connects your WordPress site to the Acquia Web Governance API (app1.us.monsido.com) and surfaces key data directly inside the WordPress admin area, including:
- Domains – View all monitored domains, trigger crawls, check crawl status
- Pages – Browse page data and scan status with search and pagination
- Accessibility – Review WCAG accessibility issues by severity
- Policies – List and sort governance policies
- Notifications – Track asynchronous events like crawl completions and report generation
- Dashboard – Summary view with stats across all feature areas
Installation
- Upload the
acquia-web-governancefolder to/wp-content/plugins/ - Activate the plugin in Plugins → Installed Plugins
- Navigate to Web Governance → Settings
- Enter your Acquia Web Governance API Bearer Token (and optional Account ID)
- Save and use Test Connection to verify
Getting Your API Token
- Log in to your Acquia Web Governance account
- Go to Admin → Users → API Users
- Create a new API user and copy the Bearer token
- Paste it into the plugin Settings page
Full instructions: https://docs.acquia.com/acquia-optimize/docs/admin/users/api-users
Frequently Asked Questions
Which Acquia region does this plugin use?
This plugin is pre-configured for USA (app1.us.monsido.com). To change the region, update the AWG_API_BASE constant in acquia-web-governance.php.
How long are API responses cached?
Responses are cached using WordPress transients for 5 minutes. You can clear the cache using the "Refresh Data" button available on each tab, or via Settings.
Are my API credentials stored securely?
Credentials are stored in the WordPress options table. For additional security, consider storing them in wp-config.php and reading them via define( 'AWG_API_TOKEN', '...' ).
Changelog
1.0.0
- Initial release