When this is useful
Situations that can start the work.
- A site is being handed over by another team.
- The cost and order of improvements are unclear.
- Updates feel risky and documentation is missing.
Evidence / preflight
We first verify what is available.
- WordPress versions, configuration, and component inventory.
- Code, database, cron, caches, and observable server constraints.
- Technical SEO, templates, forms, responsive behavior, and accessibility signals.
Deliverables
What remains with the owner.
- A map of confirmed findings with evidence.
- Coverage and explicit not-tested reasons.
- A prioritized sequence without automatically changing the site.
Honest boundary
What cannot be promised in advance.
The review is not a penetration test, legal opinion, or a guarantee that no hidden problem exists. Inaccessible scope stays not tested.
Tell us what the site needs.
A goal, the current difficulty, and an optional website address are enough. Do not send passwords, keys, or private exports.