This is a planned website rebuild for a paramedical training academy, documented as a roadmap rather than a completed engagement. The intended standard is a 10/10 experience across discovery, decision-making, lead capture, event visibility, and measurement. That is a design and acceptance target, not a reported score, performance result, or proof of implementation. No client name, city, project date, launch date, or current implementation status was supplied, so none is inferred here. The plan focuses on making a complex educational offer easier to understand and act on while establishing a technical foundation that can be reviewed objectively before launch.
Situation
The academy needs a website plan that can support prospective students from an initial question through to a confident next step. Training decisions tend to involve more than a single course description. Visitors may be comparing learning paths, considering whether a course fits their goals, looking for a scheduled class, or asking what a future career route could look like. A rebuild should give each of those questions an intentional destination instead of asking visitors to interpret a broad, undifferentiated catalogue.
The planned experience is therefore broader than a visual refresh. It is a content, conversion, search, and measurement system designed around the academy’s information needs. The target is a 10/10 standard for clarity and technical readiness at acceptance, not an assertion that the current site has reached that standard. Location was not supplied in the evidence, so this case does not attach the academy to a city or make local-market claims.
What was broken
No completed audit, analytics review, implementation record, or before-and-after evidence was supplied. It would be inaccurate to state which existing pages, forms, tracking tags, search listings, or class calendars are broken today. The work is framed as a planned rebuild precisely because the available evidence defines desired scope and acceptance criteria rather than observed defects.
The planning problem is still clear: a training academy needs a coherent way to present many decision points without sending every visitor through the same generic route. A simple page collection can leave course exploration, career research, class discovery, and conversion measurement disconnected. This plan addresses those risks as requirements to solve, not as verified descriptions of the academy’s current website. No before-and-after visuals have been created or sourced, because visual proof of outcomes is not available.
Rebuild plan
The planned build includes more than 30 prerendered pages. Prerendering is intended to provide crawlable, consistently delivered page content for the academy’s core information architecture. The page set would be organized around the questions a prospective student needs answered: what training is available, how to evaluate an option, how to prepare for a class, and what action to take next. Each page would have a defined purpose in the decision journey instead of functioning as duplicate search inventory.
A quiz is planned as a guided decision tool with 12 result paths. Its purpose is to turn an open-ended visitor question into a more relevant next step. The requirement is not simply to publish 12 result screens; each path should connect the answer pattern to useful guidance and a clear action. Until the quiz is built and tested, no claim is made about completion rates, lead quality, or the appropriateness of any individual recommendation.
The plan also includes a career guide lead magnet paired with an automated email sequence. The guide would offer a useful resource at the point a visitor is still researching, while the follow-up sequence would continue the conversation with timely, relevant information. The intended automation must be configured, consent-aware, and tested before it can be described as live. This case does not name an email platform, assert deliverability, or report subscriber results because those details were not supplied.
Measurement is designed into the rebuild rather than added as an afterthought. GA4 and Meta Pixel conversion events are planned for the actions that matter to the academy’s funnel, such as lead capture and other agreed conversion points. The event list, trigger conditions, and validation method would be documented before release so that reporting can distinguish an observed action from an assumed outcome. No tracking configuration is claimed to be installed or firing at this stage.
For search readiness, the plan calls for Search Console connection and a sitemap that exposes the intended public page inventory to search systems. Scheduled classes are also planned as Google class events so prospective students can discover timely training opportunities where those events are supported. These are scoped integrations and publishing tasks, not completed connections or evidence of visibility. Their value depends on accurate course and event information being available when implementation begins.
Planned acceptance criteria
Results are targets for acceptance, not observed business results. The website would be considered ready for handoff only after the planned 30+ prerendered pages are present and reachable, the quiz exposes and routes to all 12 intended result paths, and the career-guide capture and automated email journey are tested end to end. GA4 and Meta Pixel conversion events would need to be verified against the agreed actions, while Search Console and the sitemap would need to be connected and checked as part of launch readiness.
The class-event requirement would be accepted only when the agreed class information is represented for Google in the intended format and reviewed for accuracy. Technical acceptance is explicitly set at a zero-error audit: no unresolved errors in the agreed audit scope at the point of review. That criterion does not guarantee search ranking, enrollment volume, advertising performance, email engagement, or a permanent error-free future state. It defines the quality bar for the planned release review.
A 10/10 standard is likewise a target used to guide decisions across clarity, conversion paths, discoverability, and technical quality. It should not be translated into a completed score, a testimonial, or a quantitative result. Success metrics can only be reported after implementation, agreed measurement windows, and source data are available.
Timeline
No completion date, launch date, or delivery schedule was supplied. This case therefore does not promise a turnaround or imply that work has started. Timing would need to be set after the academy confirms the available course material, class-event details, content approvals, measurement definitions, and the acceptance-audit scope.
The practical sequence is planned as discovery and content mapping first; page production and quiz-path design next; lead-magnet and email-journey configuration alongside conversion-event planning; then search, sitemap, and class-event setup; and finally end-to-end validation against the zero-error acceptance criterion. This is an order of work, not a dated schedule or a statement of implementation status.
Had a good experience? Leave a Google review