Questions and answers

No. It reads and records. It never updates, deactivates, cleans or optimises anything – not even when it is sure what the cause is. Isolation testing applies changes only inside an isolated session that requires a signed cookie and an administrator login, and it never writes to the plugin list in the database.

Not for the free plugin – it works entirely inside WordPress and makes no external requests until you opt in. An account (Pro) is needed to connect the site and get the correlation with external monitoring.

The budget is 5 ms and 2 MB per uncached front-end request, enforced by an automated benchmark in our build. If a release breaks the budget it does not ship.

Like any other plugin: WordPress asks Ravnsight for the latest version and shows the update in your admin. Every release is listed in the changelog on this page with its checksum.

Free observes and diagnoses your site locally: every detector, a change timeline, the likely-cause correlator, Investigation Mode (start from the problem, get the likely cause with evidence and a confidence level), and the Testing tools (isolate a plugin one at a time, whole-site bisect, test with the default theme) — all in your own database, nothing sent anywhere. Pro adds the connection to the Ravnsight platform: external uptime/SSL/domain monitoring correlated with the inside view, synthetic-flow monitors (a real browser walks home → cart → checkout and alarms on a broken step or JavaScript error), a homepage snapshot on every site, team alerts that reach the right technician first (e-mail, SMS, Slack, Teams, Telegram, webhook), Safe updates of plugins/themes/core with automatic rollback (and a file rollback point even when you update from WordPress's own screen), on-site backup & restore, known-vulnerability detection, remote control from the dashboard and monthly client reports.

Everything is stored in your own WordPress database and pruned automatically. The free plugin sends nothing on its own — the single exception is the anonymized resolution outcome you can choose to share (error type, component and fix only; never your URL, account or messages). When you connect Pro, signals are pushed to Ravnsight every few minutes, HMAC-signed, and everything is redacted first: e-mail addresses, phone numbers, card-like numbers, query-string values and full server paths are stripped before anything leaves the server.

When an error is raised, PHP records the file it came from. Detective maps that file back to its plugin or theme folder and attributes the error there. Errors from WordPress core files are marked as core. It is a factual mapping from the failing file — not a guess. For the deeper "what changed right before it" question, Detective lines the error up against the change timeline.

A signal is one recorded observation — a fatal error, a warning, a slow request, a plugin update, a setting change, and so on. Identical repeats are folded into a single row with a count, so a hundred thousand repeats of the same warning is one line, not a flooded log. Each signal carries its type, severity, the component it belongs to, and when it was first and last seen.

Yes, and it goes further for shops: it records failed orders with the payment gateway involved (order number only, never customer data), watches Action Scheduler for failed or backlogged background jobs (order e-mails, renewals, webhooks), and the page probe understands the product, cart and checkout pages. The one question that matters on a shop — "did the last update break the checkout?" — is exactly what Detective answers.

Yes. JavaScript Detective records front-end JS errors from real visitors — dead buttons, forms that do nothing, carts that will not update — and attributes them to the plugin or theme that shipped the broken script. Errors from browser extensions and third-party scripts are marked external so you can ignore them. Reports go to your site’s own REST endpoint, never to a third party.

Yes — that is the whole design. Isolating a plugin applies only inside your own signed admin session; anonymous visitors always see the site exactly as normal. Isolation never writes to the active-plugins list in the database, expires after 60 minutes, and can always be ended three independent ways (a URL flag, a PHP constant, or removing the loader file). An automated test that proves a concurrent visitor is unaffected must pass before any release ships.

Before each update Detective saves a copy of the plugin’s current files (a rollback point). It runs the update, then loads a representative set of pages — the front page, a post, a product, the cart, the checkout and any page you name — and watches for new fatal errors, warnings, database errors or HTTP failures, and pre-checks the new version’s PHP/WordPress requirements. If something broke you see exactly which update did it and can roll the files back in one click. The database is never restored, so a shop’s orders are never touched.

Start from the problem instead of the logs: pick e.g. "Something broke after an update", "A page is slow" or "Error or white screen", and Detective proposes the most likely cause with its evidence and an honest confidence level – then offers a safe test to confirm it. It includes ready-made playbooks for checkout, cron, e-mail, redirects, 404s, stubborn caches and more. Investigation Mode is part of the free plugin.

It reads the live certificate a browser sees: the issuer, the exact expiry date and days left, the full chain, and every name (SAN) the certificate covers.

Yes. Paste a domain and get the result instantly. Nothing is stored and you never sign up.

A renewal can succeed on the server while the web server keeps serving the old certificate, or a different host or CDN serves it. The checker reads what visitors actually get, so it catches the mismatch.

Ravnsight warns you well before expiry — by default about a month ahead — so there is time to renew. A manual check only tells you how it looks today; monitoring warns you automatically, weeks in advance.

The tool checks one at a time. Create an account and add your sites, and Ravnsight watches every certificate automatically and alerts you well before expiry (about a month ahead by default). Agencies see all client certificates in one view.

An outside-in scan: the platform or CMS, hosting, SSL certificate, domain and DNS, and which analytics and tracking tags are installed, plus a live homepage snapshot. No login, no plugin.

Yes, free with no account. We only read what is publicly visible from the outside, and nothing is stored.

No. It makes a few ordinary requests from the outside, exactly like a normal visitor.

This is a one-off scan. Create a free account and add the site – Ravnsight then runs the checks continuously, confirms an outage from a second location in another country before alerting, and e-mails you when something is actually wrong.

From the outside it identifies whether a site runs WordPress, the version and theme where exposed, and common misconfigurations that are publicly visible.

No. It only reads what is publicly available, no credentials, no plugin, no account.

Many sites hide the version, which is good practice. The checker reports only what is publicly exposed.

Two layers. From the outside, the free Ravnsight plan watches uptime, the certificate and the domain with no install, and alerts you by e-mail. To see inside WordPress — PHP errors, plugin and theme changes, failed updates — in Ravnsight, you need Pro: Pro connects the Ravnsight Detective plugin to your account, so those internal errors flow straight into Ravnsight, lined up with the outage that explains them. (The free Detective plugin also runs standalone inside wp-admin, but that view stays local — Pro is what brings it into Ravnsight.)

Which analytics and ad tags are installed (Google Analytics, GTM, Meta Pixel and more) and whether they actually fire on the page, not just whether the code is present.

A tag can be in the HTML but blocked by consent, a script error or a misconfiguration. The checker runs the page and reports what actually fired.

Yes, no account and nothing is stored.

This checker is a one-off scan – re-run it after any site change. For ongoing coverage you can add an HTTP check in Ravnsight with a content rule on the tag snippet, so you are alerted if the tag code disappears from the page. (That confirms the tag is present, not that it fires in a visitor browser.)

Your HTTP response headers: HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy, and grades what is present, weak or missing.

They close common attack vectors (clickjacking, MIME sniffing, downgrade) at the edge, cost nothing and do not change how the site looks. Most sites ship with almost none.

Start with HSTS, X-Frame-Options, X-Content-Type-Options and Referrer-Policy, safe on almost any site. Add Permissions-Policy, then CSP last (test carefully).

Yes – security headers are a one-off grade, so make it part of your deploy routine: a server or config change can silently drop a header. For continuous monitoring, Ravnsight watches the uptime, SSL and domain that such changes can break, and alerts you from a second country when something actually goes down.

The real checkout journey, not just a homepage that returns 200. Ravnsight checks that cart, checkout and order creation keep working, and watches uptime, SSL and WordPress errors in one place.

Your homepage can return 200 while checkout silently fails after a plugin, theme or gateway change. A generic pinger never sees it, but customers do.

Ravnsight confirms the failure from independent locations before alerting, so you are told quickly without false alarms.

External checkout monitoring works with no install. To also see the inside view in Ravnsight — the exact error and the plugin, theme or gateway change behind a broken checkout — connect the store with Pro via the Ravnsight Detective plugin. The free plugin also runs standalone inside wp-admin.

Yes. One dashboard across all client sites, with alerts and reports.

One dashboard for every client site: uptime, SSL, domain and performance from the outside. On Pro, the Ravnsight Detective plugin connects each site so the inside view — WordPress errors and plugin or theme changes — shows up in Ravnsight too, lined up with the outages that explain them. Plus confirmed alerts, per-client status pages and SLA reports, and white-label so it looks like your own service.

Yes. Add 10 to 100+ sites to one account, see them all in a single dashboard, filter to any one client, and route alerts per site.

Agency plans are priced by the number of client sites (10, 25, 50 or 100), each with 1-minute checks, more monitor types and Slack/SMS alerts. Partner plans add white-label resale under your own brand.

Yes, on Partner plans. Status pages and uptime/SLA reports carry your logo, colours and domain — nothing says Ravnsight. The plugin can be white-labelled too.

Yes. Alerts route per site to the right people and channels (email, and Slack/SMS on paid plans), so each client or team only hears about their own sites.

No. External monitoring works on any site with no install. For the inside view in Ravnsight — errors, plugin and theme changes, failed updates — connect each site with Pro via the Ravnsight Detective plugin (the free plugin also runs standalone inside wp-admin). Nothing ever changes the site.

Yes. Every certificate and domain is tracked, with alerts well before expiry, so no client site silently goes insecure or lets a domain lapse.

No. A single failed check never pages anyone — Ravnsight retries and confirms from a second location in another country before it raises an incident. A slow-but-up site shows as degraded, not an alert.

Yes. Public per-client status pages and scheduled uptime/SLA reports, white-labelled on Partner plans — the proof-of-work clients ask for.

Create an account, add a site by its address and the first checks run within a minute. Add your client sites, then install the Detective plugin where you want inside data. Upgrade to an Agency or Partner plan when you are ready to scale.

White-label monitoring you resell under your own brand. You manage client sites in one account, and the status pages, reports, dashboard and even the Ravnsight Detective plugin carry your logo, colours and domain — your clients never see Ravnsight.

Yes. You buy a Partner plan by the number of client sites at a flat wholesale price, and sell monitoring to your clients at whatever price and packaging you choose. The margin is yours.

No. On Partner plans the status pages, uptime and SLA reports, e-mail (your domain and SMTP), embeddable widgets and the Detective plugin can all be white-labelled with your brand.

Agency plans monitor many client sites for your own use. Partner adds the white-label layer so you can resell monitoring as your own product, with per-client branding, your own domain and SMTP, and branded reports and widgets.

You pay Ravnsight a flat wholesale price per active site for your Partner plan, and you invoice your clients yourself. One bill to you, your own bills to them.

Confirmed uptime, SSL and domain monitoring, per-site status pages and scheduled SLA reports — and, with the Detective plugin connected on Pro, the inside WordPress errors and changes that explain an outage. All under your brand.

No. External monitoring needs no install. Connect the free Ravnsight Detective plugin with Pro on the sites where you want the inside view in the dashboard — it never changes the site.

Create an account, pick a Partner plan for the number of client sites you manage, set your branding (logo, colours, domain), and add sites. Start on a smaller plan and scale up as you grow.

Uptime (HTTP), SSL certificates, domain expiry, DNS and API or port checks — run from independent locations in several countries, so a failure is confirmed across borders before it alerts you. With the free Ravnsight Detective plugin connected on Pro, it also brings in WordPress errors and plugin or theme changes from inside the site.

A single failed check never alerts anyone. Ravnsight retries, then confirms the failure from a second location in another country before it raises an incident. A slow-but-up site shows as degraded, not an alert.

Yes. The free plan monitors one site with HTTP, certificate and domain checks, e-mail alerts and 30 days of history. No card required.

No. External monitoring works on any website with no install. The free Ravnsight Detective WordPress plugin, connected on Pro, adds the inside view — and it never changes your site.

By e-mail on every plan, and by Slack, SMS, Teams, Telegram or webhook on paid plans. Alerts route per site to the right people.

Never. Ravnsight observes, confirms and diagnoses — it does not auto-fix, auto-update, back up or edit your site. You stay in control of every change.

Your data is handled under GDPR and stored in the EU. The monitoring checks themselves run from independent locations in several countries, confirming a failure across borders before you are alerted.

Yes. Public status pages and scheduled uptime/SLA reports, white-labelled with your own brand on Partner plans.

Yes — one site monitored every few minutes with HTTP, certificate and domain checks, e-mail alerts and 30 days of history. No card required, and it never expires.

There is no automatic trial clock. You start on the free plan and upgrade to a paid plan whenever you want — no pressure, no expiry date.

Paid plans are priced by how many sites you monitor: Pro for a handful of your own sites, Agency for 10 to 100 client sites, and Partner for white-label resale. Each paid plan adds 1-minute checks, more monitor types and Slack/SMS alerts.

Yes. Pay yearly and you get two months free — you pay for ten. Prices are shown in SEK, EUR and USD.

One website (one address) that you monitor. On Agency and Partner plans, each client site counts toward your plan limit.

Yes, any time. Upgrade or downgrade whenever you need, and if you cancel you keep access until the end of the paid period.

No. The free plan needs no card and never expires. You only add payment when you choose to upgrade.

Prices for Swedish customers are shown including VAT, and your invoice shows the breakdown.

Yes, especially for WordPress and WooCommerce sites. It monitors uptime, SSL and domain like Pingdom, confirms an outage from a second country before alerting, and adds WordPress error context and WooCommerce checkout monitoring that generic uptime tools do not have.

Yes. Ravnsight tests the cart to payment to order flow, so you catch a broken checkout even when the homepage returns 200 — something a generic Pingdom-style check never sees.

Yes. A single failed check never alerts anyone — Ravnsight retries and confirms the failure from a second location in another country before it raises an incident.

Yes — one site with uptime, SSL and domain checks, e-mail alerts and 30 days of history. No card required.

No for external monitoring — add a site by its address and checks start within a minute. The free Ravnsight Detective plugin, connected on Pro, adds the inside WordPress view.

Yes, especially for WordPress and WooCommerce sites. It monitors uptime, SSL and domain like UptimeRobot, confirms an outage from a second country before alerting, and adds WordPress error context and WooCommerce checkout monitoring that generic uptime tools do not have.

Yes. Ravnsight tests the cart to payment to order flow, so you catch a broken checkout even when the homepage returns 200 — something a generic UptimeRobot-style check never sees.

Yes. A single failed check never alerts anyone — Ravnsight retries and confirms the failure from a second location in another country before it raises an incident.

Yes — one site with uptime, SSL and domain checks, e-mail alerts and 30 days of history. No card required.

No for external monitoring — add a site by its address and checks start within a minute. The free Ravnsight Detective plugin, connected on Pro, adds the inside WordPress view.