Sample report
Site Rescue Review sample report
Sanitized demo deliverable for a WordPress/WooCommerce site reliability and trust review.
Status: diagnostic evidence only
No security, indexing, revenue, or repair guarantee.
Executive summary
Demo evidence shows several site trust and reliability signals that should be reviewed before they affect customer confidence, checkout flow, or search visibility. The review prioritizes what is observable, what could affect revenue, and what should be fixed only after scope is agreed.
Findings
Security/trust issues
HighSecurity headers are incomplete, XML-RPC is reachable, and demo exposed-file checks need confirmation against the live host.
Checkout/trust issues
MediumCheckout and order-received pages should be reviewed for mixed trust signals, redirect behavior, and payment-critical plugin changes.
Visibility/indexability issues
MediumDemo sitemap and canonical evidence suggests some important pages may be harder for search engines to discover or trust.
Plugin/update risk
MediumA cluster of commerce and security plugins needs version, ownership, and change-history review before fixes are applied.
Security/trust issues
- Missing or incomplete security headers should be reviewed at the hosting/CDN layer.
- Reachable XML-RPC may be acceptable for some stores, but it should be intentional and rate-limited if kept.
- Public debug, backup, log, or configuration-adjacent files should be checked and removed or blocked where appropriate.
Checkout/trust issues
- Cart, checkout, order-pay, and order-received pages should be checked before changing plugin settings.
- Gateway, fulfilment, email, stock, and order-status behavior should be treated as revenue-critical.
- No checkout fix work should start without an agreed rollback and test path.
Visibility/indexability issues
- Important pages missing from XML sitemaps may need sitemap or indexability cleanup.
- Canonical tags that point elsewhere can make the wrong URL look authoritative.
- Robots, noindex, canonical, and sitemap signals should be reviewed together rather than one at a time.
Plugin/update risk
- Recent plugin/theme changes should be matched against the timing of any checkout or visibility issue.
- Commerce, caching, security, and SEO plugins should be reviewed as a connected stack.
- Update work should be scoped separately from the review and tested before production changes.
Recommended next steps
- Confirm which findings are live, repeatable, and relevant to customer trust or revenue.
- Prioritize exposed files, missing headers, checkout-path risks, and indexability blockers.
- Avoid broad plugin changes until the checkout and payment-critical path is backed up and testable.
- Quote a Fix Pack only after the diagnostic evidence identifies a clear repair path.
Included in the £249 review
- Manual review of supplied scanner exports, screenshots, site context, and written concerns.
- Findings table with severity, evidence, and recommended next steps.
- Security/trust, checkout/trust, visibility/indexability, and plugin/update risk review.
- Plain-English summary suitable for owner, agency, or ops handoff.
- Optional fixed-scope Fix Pack quote when the evidence supports implementation work.
Not included
- Penetration testing, destructive testing, denial of service, credential attacks, persistence, or exfiltration.
- Compliance certification or guarantee that every issue has been found.
- Fix implementation, plugin updates, production changes, or cleanup without a separate quote and approval.
- Guaranteed ranking, indexing, recovery, revenue, or security outcome.
Fix Pack quote path
A Fix Pack is quoted only after the review confirms a specific implementation path, such as exposed-file cleanup, header configuration, XML-RPC hardening, checkout-path correction, sitemap/canonical cleanup, plugin update planning, or monitoring setup.