Integrations
Scan your website. Connect when you want help applying supported fixes.
webioom can scan and report on your site without a CMS integration. Connecting a supported platform allows webioom to apply supported changes — only after your review and approval.
Two paths
Scanning and connecting lead to different outcomes
Not every finding becomes a direct fix — this is the path a supported issue can take once connected.
Available now
Three supported platforms
WordPress
Available- Page title
- Meta description
- Missing H1
- Missing image alt text
Shopify
Available- Product, collection, page, and article title
- Product, collection, page, and article meta description
Wix
Available- Blog post title and meta description
- Store product title and meta description
Custom or other platform: any website can be scanned and reported on with no integration at all. Direct fixes are WordPress, Shopify, and Wix only today — every other platform still gets the full health report.
Every other report finding still gets a clear recommendation, whether or not a supported platform is connected.
Set the record straight
What connecting does — and doesn't do
Connecting does
- Authorizes webioom to access supported resources on that site
- Unlocks supported direct-fix workflows for that site
- Allows a fresh check right before any supported write
- Enables verification and history for supported changes
Connecting does not
- Give webioom permission to change anything whenever it wants
- Turn every report finding into an automatic fix
- Bypass your approval for any current supported workflow
- Guarantee every theme, plugin, or page-builder configuration is writable
How a supported fix happens
The controlled workflow
Prepare & Preview
webioom checks the target and prepares exactly what would change.
You Approve
You see the proposed change and choose whether to apply it.
Verify
webioom checks the applied change actually appears correctly.
History & Undo
The change is recorded, and can be undone where it’s safe to do so.
Conservative by design
If webioom can't safely confirm the change, it doesn't guess
webioom may decline to make a direct change rather than risk an incorrect one — a deliberate safeguard.
webioom may refuse a direct change when:
- The exact target can’t be confirmed
- The page’s content source is ambiguous
- The required permission isn’t available
- The website changed after the preview was prepared
More integrations are planned
webioom's scanning and reporting layer isn't tied to WordPress, and the integration system is intended to expand over time.
Want the details behind how a connected fix is kept safe? Read about webioom's trust model.