GlarionStart with the scope you can defend
Record the client’s domain, the permitted checks and the date of the assessment. Use Glarion’s domain-verification workflow before running checks that require proof of control. Authorization to maintain a WordPress installation should not be treated as permission to test every service belonging to that client.
Review the public-facing observations in context: certificate configuration, security headers, email authentication and the checks included in your chosen assessment. Keep the report’s scope and limitations alongside the findings so a client can distinguish a detected issue from an area that was not assessed.
Connect a finding to the maintenance task
An expired certificate may belong to the hosting team; an email-authentication finding may belong to the domain administrator. Assign the next action to the team that controls the relevant setting. Explain the observed condition, its likely effect and the evidence needed to confirm the correction.
For a WordPress care plan, keep core, plugin and theme updates, backups, access reviews and recovery testing in your maintenance checklist. Glarion’s external observations do not establish that every plugin is current, a backup can be restored or a site is free of malware. Verify those tasks through the appropriate WordPress and hosting workflows.
Send a report the client can use
Agency-branded reports are included on Glarion’s paid plans. Use your name and logo, preserve the assessment date and explain the next step in plain language. Severity describes a finding; business priority also depends on the site’s exposure and the client’s operations.
After a change, repeat the relevant check and compare the observation with the earlier report. Keep implementation and recovery records in your maintenance workflow. Glarion reports observations; it does not apply WordPress fixes or guarantee that a change resolved every related risk.
A simple attribution for work you actually performed
If you used Glarion to check this site and the client permits attribution, this optional HTML link identifies the tool. Place it in a WordPress Custom HTML block or your theme’s footer. It contains no script, tracking pixel or live-status request.
<a href="https://glarion.app/">Checked with glarion.app</a>Only use “Checked with” after an actual check. The link does not claim that Glarion has certified the site, that every finding has been fixed or that a check is still current. Share the dated report separately with authorized recipients.
Review the method before offering the service
- Scope and limits of the checksUnderstand what a report can establish.
- The complete sample reportReview the output before adding it to a care plan.
- WordPress: hardening guidanceKeep maintenance and recovery responsibilities explicit.