Site Info Scout
Generate a complete WordPress site report covering environment details, active plugins and configuration. Useful for support tickets and audits.
Why it exists
Every support conversation about a WordPress site starts the same way. What version of PHP? What theme? Which plugins are active, and at which versions? Is object caching on? The person asking needs ten minutes of a client's attention to collect information the site already knows about itself, and the client usually sends back a screenshot of the wrong screen.
WordPress does ship Site Health, and it is genuinely useful, but it is built for a site owner reading it interactively. It is not built for handing a complete environment summary to somebody else in a form they can paste into a ticket.
Site Info Scout does that one job. It reads the environment, formats it as a support report, and gives you a copy button and two export formats.
What it does
Why it matters
The active plugin inventory is where a conflict is usually found, and it is the list clients are least able to produce accurately by hand. Getting it as structured text rather than a screenshot of the wrong screen is what turns a two-day back-and-forth into a single reply.
How it works
The plugin is admin-only and read-only by design. It adds a single admin screen, reads what WordPress and PHP already expose, and renders it. It does not write to your database beyond its own options, it does not modify site configuration, and it does not offer a “fix this” button, because a diagnostic tool that also makes changes is a diagnostic tool you cannot trust.
There are no remote calls and no telemetry. Nothing about your site is transmitted anywhere. The report is generated on request, in your browser session, and goes wherever you choose to send it.
The codebase follows WordPress coding standards with a proper namespace and prefix, and is internationalised, because it was written for WordPress.org distribution.
Requirements and limits
- WordPress admin access — the screen is gated behind admin capability
- No external services or accounts
- Licensed GPLv2 or later
What it does not do
It is not a monitoring tool and does not track your site over time. There is no history, no alerting and no scheduled reporting — you generate a report when you need one.
It does not scan for malware, test performance or check uptime. It reports what is there; interpreting it is your job.
It also deliberately avoids collecting anything sensitive. Before sending a report onward it is still worth a glance, since plugin and theme inventories tell a reader something about your stack.
Where it earns its place
Handing a site to a developer. A client reports something broken. Instead of a back-and-forth that costs two days to establish basic facts, they open one screen, click copy and paste. The developer starts with the environment already known, which usually shortens diagnosis to a single reply.
Auditing a site you have inherited. Taking over maintenance of a site nobody documented means finding out what is actually installed, what versions are in play, and which flags are already raised. The report gives you that in one pass rather than clicking through five admin screens and a hosting panel.
Tracking a portfolio. For an agency running twenty client sites, the CSV export is the useful one. Pull a report from each site, drop them into a spreadsheet, and PHP versions and plugin inventories become sortable. The sites running an end-of-life PHP version stop being a thing you vaguely worry about and become a filtered list.
The common thread is that none of these are monitoring problems. They are handoff problems, and the fix is a clean report in a format the recipient can use — which is a smaller job than most tooling in this space tries to do.
Frequently asked questions
Who can see the report?
Only administrators. The screen is capability-gated and there is no front-end output.
Does it send data anywhere?
No. There are no remote calls and no telemetry of any kind. Exports go only where you put them.
How is this different from Site Health?
Site Health is built for reading interactively. Site Info Scout is built for handing off — one screen, a copy button, and TXT and CSV exports formatted for a support ticket.
How is this different from Site Extensions Snapshot?
Site Extensions Snapshot is about the plugin and theme inventory and exports it to CSV. Site Info Scout is about the environment around them — server and WordPress configuration, plus health flags — packaged as a report for a support ticket.
Can I export it?
Yes, TXT or CSV, plus copy to clipboard.
Will it change anything on my site?
No. It is read-only by design and has no repair actions.
How do I get Site Info Scout?
It is free and available on request. It is not in the WordPress.org directory — contact us and we will send you a packaged build.
Related plugins
Site Extensions Snapshot
View every installed plugin and theme with status, version and author, then export the lot to CSV in one click. Built for audits, compliance checks and client handovers.
View MaintenanceZignites Sentinel
Create a checkpoint of your active theme and plugins before updating, validate that the checkpoint is sound, and restore it if an update breaks the code layer.
View PerformanceTurboBlocks
Disable unused CSS and JavaScript on WooCommerce sites with per-page rules and context-aware detection. Reduce page weight and improve Core Web Vitals without breaking checkout.
ViewInterested in Site Info Scout?
Tell us about your site and we will send you a build or quote the work.