A short, practical description of how a digital health review actually runs.
Day one is access. I need read access to GA4, Search Console, the CMS, the CRM if there is one, and the social and email tools. Without those, the review is just opinions. Most clients underestimate how much of the engagement is admin in the first 48 hours.
Days two and three are reading. I open the analytics and look at the last 90 days. Where is traffic coming from. What is the user landing page distribution. What is the bounce-then-leave rate by source. What pages convert and which do not. I am building a mental map of what the site is doing and for whom.
Days four to six are hands-on. I open the site as a user. On a desktop, on a real mid-range Android phone, with the network throttled to simulate 4G. I follow the journeys a customer would. I try the contact form. I navigate from a Google ad. I read the content as if I had never heard of the company. I take screenshots and notes.
Day seven is the technical layer. Site speed audit, accessibility scan, structured data check, internal linking review. The boring tooling work. Most of it is run with off-the-shelf scanners. The output goes into the findings.
Days eight to ten are the document. I write the report. Plain language. Findings in priority order. Each one with a specific recommended action. No theory. No 50-slide deck. Usually 15-25 pages.
Day eleven is the meeting. I walk the client through the report. The meeting is more useful than the document because they can ask questions. I take their reactions and either correct the document or note the disagreements.
After: I hand over an action list. Three to five things to do this month, owned by named people. The rest is theirs to schedule.
The whole thing takes 10-15 working days. The output is useful for about six months before the next round.
If that is the kind of engagement you need, let’s talk.