Impact with context
See an impact level and score without treating impact as an error or automatic removal decision.
WordPress dependency & impact analysis
See what deserves care before you change it.
WP Impact Map analyses the components on your WordPress site, shows impact, confidence, used content and connections, and separates uncertain findings into a clear Needs review workflow.
Read-only analysisLocal-firstNo telemetry by defaultEvidence-led
62Components analysed
2High impact
17Need review
2,502Connections
2,711Evidence items
Example results from a real test installation shown in the screenshots above.
The problem
The Plugins screen tells you what is installed. Not what deserves caution.
A WordPress site can contain plugins, a theme, drop-ins and must-use components that interact through hooks, registered resources, content references and other relationships.
WP Impact Map turns those signals into a maintenance-oriented view: impact, confidence, used content, connections and findings that still need human review.
Confidence stays visible
High- and low-confidence findings are shown separately so certainty is never implied where evidence is weak.
Read-only analysis
WP Impact Map analyses the installation without deactivating plugins, modifying content or executing third-party callbacks.
The real interface
What you see in the product is what we show here.
No invented dashboard. These screenshots come from the current WP Impact Map Free build running on a real WordPress installation.
Plugins & componentsSearch, filter and sort the analysed inventory.
Free
Needs reviewLow-confidence findings stay explicit.
Free
Scan historyReview recent analyses and warnings.
Free
Settings & scan scopeChoose what is analysed and keep the interface language independent.
Free
What it gives you
One scan. Six useful views of maintenance risk.
The goal is not to make the decision for you. It is to give you better evidence before you make it.
Component inventory
Analyse plugins, the active theme, WordPress drop-ins and optionally inactive or must-use plugins.
Impact score
A 0–100 impact score with clear impact levels helps surface components that deserve more care.
Confidence
Confidence is displayed independently from impact, so a strong impact signal is not confused with strong evidence.
Needs review
Components without enough evidence are separated into a dedicated review workflow with a plain-language reason.
Connections & content use
See connection counts and whether registered components are referenced in WordPress content.
Scan scope & privacy
Control inactive plugins, must-use plugins and content-reference analysis while the analysis stays on the WordPress installation.
How it works
From inventory to a maintenance decision in four steps.
Scan
Inventory the current WordPress environment using the scan scope you choose.
Analyse
WP Impact Map evaluates relationships, content references and other available evidence without changing the site.
Compare
Review impact, confidence, used content and connection counts across detected components.
Review
Investigate high-impact components and anything placed in Needs review before deciding what to change.
Free vs Pro
The current Free build stands on its own. Pro will add deeper operational evidence.
Nothing in the Free column below is a teaser screen: these capabilities are already part of the current product.
| Capability | Free | Pro |
|---|---|---|
| Component inventory & static analysis | ✓ | ✓ |
| Impact score & impact level | ✓ | ✓ |
| Confidence scoring | ✓ | ✓ |
| Used-content & connection counts | ✓ | ✓ |
| Needs Review workflow | ✓ | ✓ |
| Scan history & configurable scan scope | ✓ | ✓ |
| Interface language selection | ✓ | ✓ |
| Runtime observation layer | — | Planned Pro |
| Deeper operational evidence & change history | — | Planned Pro |
Pro features are shown as planned until they are commercially released. The landing page will be updated as the Pro build is finalized.
Built for trust
Impact is context, not an alarm.
WP Impact Map explicitly states that impact reflects how widely a component is connected to the site. It does not claim that a high-impact component is broken or unsafe.
01Read-only analysis
No plugin deactivation, content modification or third-party callback execution during analysis.
02Uncertainty is visible
Low-confidence findings are moved to Needs review instead of being presented as facts.
03Local-first data handling
The interface states that analysis stays on the WordPress installation.
04Configurable scope
Choose whether inactive plugins, must-use plugins and content references are included.
Pricing
Start with the complete Free analysis. Add Pro when you need runtime depth.
Free
€0
For site owners and developers who want a clearer picture before routine WordPress maintenance.
- Component inventory
- Impact & confidence scoring
- Connections and used content
- Needs Review workflow
- Scan history and scope settings
For production workflows
Pro
Annual license · price shown at checkout
For agencies, maintainers and teams that want runtime observation and deeper operational evidence.
- Everything in Free
- Runtime observation layer
- Deeper operational evidence
- Advanced maintenance workflows
- Commercial updates & support
FAQ
Clear answers, just like the plugin.
WP Impact Map is designed to improve maintenance decisions, not replace administrator judgment.
Does WP Impact Map automatically tell me to delete a plugin?
No. Impact shows how widely a component is connected to the site. It does not indicate an error and it does not make the maintenance decision for you.
Does a High impact label mean something is broken?
No. High impact means the component deserves more care because of its detected role or connections. Confidence is displayed separately.
Does the scan modify my WordPress site?
The current analysis is read-only. It does not deactivate plugins, modify content or execute third-party callbacks.
What does Needs review mean?
It means the current evidence is not strong enough for a confident classification. The interface tells you why the component was placed there.
Is WooCommerce required?
No. WP Impact Map is plugin-agnostic. WooCommerce appears in these screenshots because it is installed on the test site, not because it is required.
What will Pro add?
The Pro direction is runtime observation and deeper operational evidence. Until those features are commercially released, the site labels them as planned rather than presenting them as finished.
Before your next WordPress change
Scan first. Decide with context.
See impact, confidence, connections and uncertain findings before you start removing or changing components.