RelatioScope

RelatioScope helps WordPress administrators explore known relationships between site content and selected WordPress components before making changes.

It indexes locally detected relationships and provides search, where-used, dependency, impact, and pre-change review tools.

RelatioScope does not use AI, external APIs, telemetry, analytics, or cloud processing. Core analysis runs locally inside WordPress.

What RelatioScope does

• Search and Where Used
• Impact Explorer and Dependency Explorer
• Scan Coverage and index health
• Reports and CSV export
• Pre-Change Impact Check for selected admin actions (post/page deletion, media deletion, and plugin deactivation)

What RelatioScope does not do

• It does not guarantee that every dependency or reference is discovered.
• It does not guarantee that deleting or deactivating something will break or not break the site.
• It does not block WordPress actions.
• It does not modify content automatically.
• It does not use AI or send site data to external services.
• It does not require an external account or internet connection for core functionality.

Privacy

• All relationship analysis occurs locally on your WordPress installation.
• No AI is used.
• No external AI service is used.
• No telemetry is collected.
• No analytics or tracking is included.
• No external account is required.
• No cloud processing occurs.
• No API key is required.
• Core features work with outbound network access disabled.

Limitations

RelatioScope can only report relationships that can be identified through WordPress data and supported detection methods. Some references may not be detectable, especially references stored by third-party plugins, custom PHP, arbitrary options, or unknown custom field schemas.

Relationship confidence is labeled Confirmed, Detected, or Possible. Declared plugin header requirements are labeled separately from detected content relationships.

Pre-Change Impact Check is informational. Administrators can always Continue or Cancel. Bulk delete/trash/deactivate actions are not intercepted in this version.

Multisite: each site uses its own prefixed tables. Network-wide indexing and network admin UI are not supported in this version.