Skip to main content
ScaleMath
← Leaderboard
87
ScaleMath score
3 critical2 significant0 minor
Rerun audit
1
CriticalConnecting Your WordPress Site to Workover

Incorrect Login Domain in Documentation

ProblemThe documentation instructs users to log in to 'wpdocsync.com', which is the legacy/incorrect domain instead of 'workover.dev'.
ConsequenceDevelopers and AI agents following the instructions will reach a broken or incorrect login page, failing to authenticate and stopping the onboarding process immediately.
Current
First off, you’ll need to sign in to your existing Workover account (or create one if you haven’t already) – to do so, simply head to: https://wpdocsync.com/app/login
Recommended
First off, you’ll need to sign in to your existing Workover account (or create one if you haven’t already) – to do so, simply head to: https://workover.dev/app/login
The fixUpdate the URL in Step 1 of the 'Connecting Your WordPress Site to Workover' article to point to workover.dev.
Was this finding useful?
2
CriticalUpdating Your Payment Method

Incorrect Billing Settings Domain

ProblemThe documentation links to 'wpdocsync.com' for billing settings, which is the incorrect domain.
ConsequenceUsers attempting to update payment methods will be directed to the wrong URL, causing confusion and blocking them from managing their subscription.
Current
Simply navigate to your Workover Billing settings: https://wpdocsync.com/app/settings/billing
Recommended
Simply navigate to your Workover Billing settings: https://workover.dev/app/settings/billing
The fixUpdate the billing settings URL in the 'Updating Your Payment Method' article to point to workover.dev.
Was this finding useful?
3
CriticalHow to Update Your Existing Content With Workover

Incorrect Login Domain in Update Workflow

ProblemThe documentation instructs users to log in to 'wpdocsync.com', which is the legacy/incorrect domain instead of 'workover.dev'.
ConsequenceUsers attempting to update content will fail to log in, halting their workflow and causing frustration.
Current
First off, you’ll need to sign in to your existing Workover account (or create one if you haven’t already) – to do so, simply head to: https://wpdocsync.com/app/login
Recommended
First off, you’ll need to sign in to your existing Workover account (or create one if you haven’t already) – to do so, simply head to: https://workover.dev/app/login
The fixUpdate the URL in Step 1 of the 'How to Update Your Existing Content With Workover' article to point to workover.dev.
Was this finding useful?
4
SignificantHow To Whitelist Workover To Prevent Your Firewall From Blocking Requests

Typo in Plugin Name

ProblemThe name of the security plugin 'Solid Security' is misspelled as 'Soild Security' in the sub-heading.
ConsequenceEngineers searching the docs for 'Solid Security' may miss this section, and AI agents parsing the docs will ingest incorrect terminology.
Current
To do this with Soild Security, please refer to their official guide here.
Recommended
To do this with Solid Security, please refer to their official guide here.
The fixCorrect the spelling from 'Soild' to 'Solid' in the whitelist instructions page.
Was this finding useful?
5
SignificantHow To Whitelist Workover To Prevent Your Firewall From Blocking Requests

Missing Links for External Guides

ProblemThe text 'official guide here' appears for Patchstack, Wordfence, and Sucuri, but the word 'here' is not hyperlinked and no URLs are provided.
ConsequenceDevelopers cannot quickly navigate to the vendor documentation to complete the whitelisting steps, increasing friction and support requests.
Current
To do this on Patchstack, please refer to their official guide here. Wordfence To do this on Wordfence, please refer to their official guide here. ... Sucuri To do this with Sucuri, please refer to their official guide here.
Recommended
To do this on Patchstack, please refer to their official guide at [URL]. Wordfence To do this on Wordfence, please refer to their official guide at [URL]. ... Sucuri To do this with Sucuri, please refer to their official guide at [URL].
The fixLocate the correct URLs for the whitelisting guides for Patchstack, Wordfence, and Sucuri, and hyperlink the text 'here' or replace it with the explicit URLs.
Was this finding useful?

What they do well

  • ✓The integration guides (Plain, Help Scout, Freshdesk, GitHub) are exceptionally well-structured with numbered lists, clear permission scopes, and specific UI paths.
  • ✓The workflow for identifying and resolving specific WordPress errors (e.g., Application Passwords) is logical and provides helpful context on *why* a step is required (security).
  • ✓The 'How it works' sections in integration docs do a great job managing expectations (e.g., explicitly stating 'Read-only access').
  • ✓Documentation clearly distinguishes between current manual processes and future planned automation (e.g., updating existing content).

Top recommendations

  1. 1.Perform an immediate audit to replace all instances of the legacy domain 'wpdocsync.com' with 'workover.dev' across the help center and UI text.
  2. 2.Add a dedicated 'API Reference' or 'Technical Specification' section (or an llms.txt/OpenAPI spec) to allow AI agents to programmatically validate configurations and endpoints rather than scraping human-facing guides.
  3. 3.Implement a global link checker to catch and fix dead or un-hyperlinked references like the 'official guide here' errors in the firewall documentation.
Pages we read (12)
Was this report useful?

Want us to fix these?

You build the product. ScaleMath handles the docs (and QA).

This is an automated audit of public documentation. It may contain mistakes, so use it as a starting point, not the final word.