Map the site before you touch it.
Avestris Site Doctor is a read-only first look for inherited, fragile, or suspicious WordPress sites. It runs inside WordPress, gathers local evidence, and helps you see what plugins, themes, files, database tables, PHP symbols, and browser scripts appear to be doing.
Boundary: no automatic repairs, no update-all button, no background telemetry, and no routine call back to Avestris. Normal diagnostic work stays on the customer site unless an administrator chooses to export a bundle for paid review.
For the person who inherited the site.
A diagnosis lane, not a repair robot.
Avestris Site Doctor is deliberately descriptive, not prescriptive. It maps evidence and flags conditions that deserve review. It does not delete files, change database schemas, install updates, clean malware, or claim that one signal proves a full compromise.
- Read-only collection by default.
- Customer-owned evidence stays local unless exported.
- Findings are framed as operational risk, not theater.
The gremlin atlas.
Ownership Graph
Core, plugins, themes, directories, files, database tables, PHP symbols, inline scripts, and remote browser calls are shown as navigable relationships instead of a wall of disconnected tables.
Site Reality
Installed components, active themes, WordPress runtime details, user posture, file surfaces, database residue, JavaScript behavior, and operational findings are collected into a local report.
Review Signals
Site Doctor looks for the kinds of evidence that matter before repair: stale admins, suspicious code placement, exposed artifacts, plugin residue, huge files, odd scripts, and brittle dependencies.
Local evidence first. Paid interpretation only if useful.
Run the free plugin from the WordPress admin area. The scanner is read-only and does not phone home.
Use the graph and component tabs to see what core, plugins, themes, files, tables, PHP symbols, and scripts are tied together.
If the site is fragile, inherited, suspicious, or headed for migration, export the bundle and buy a scoped Avestris interpretation.
Repairs, cleanup, migrations, malware response, and production changes are separate engagements after the diagnostic boundary.
When the map needs an interpreter.
For normal use, the plugin runs locally and shows the report inside WordPress. If the site needs a professional read, the administrator can export a diagnostic bundle and submit it to Avestris for a scoped review.
For inherited, confusing, or pre-migration sites where the customer wants an Avestris interpretation of the exported Site Doctor bundle.
For production-is-burning situations where the customer wants the diagnostic bundle prioritized for rapid interpretation.
Separate remediation
Fixes, cleanup, malware work, migrations, and production changes are separate scoped engagements. The paid intake buys interpretation, not ownership of the problem.
It translates the exported bundle into practical risk, dependency, migration, and escalation notes.
That keeps the first purchase bounded and prevents accidental support obligations.
If the customer wants Avestris to touch the site, the next scope and price are agreed separately.
WordPress.org package in preparation.
Directory submission requires the free plugin to be useful on its own. That matches the product boundary: the customer gets local diagnostics without creating an Avestris account or sending private evidence anywhere.
- Free plugin remains useful without paid service.
- Diagnostic bundle export requires administrator action.
- Paid review path is optional and separate from plugin operation.
Inspection ends when remediation begins.