Route
Homepage hero → “Who we are” CTA → company page
Illustrative deliverable
See the proof before you buy the promise.
This sample shows the structure of a completed $149 Rescue record. It is illustrative, not a customer case study or performance claim.
Observed
The visible CTA opens /our-team/, which returns a 404. The intended /who-we-are/ page works.
Agreed repair
Change only the hero CTA destination. No redesign, copy change, or navigation work.
Acceptance
The hero CTA opens the working company page on mobile and desktop without changing secondary links.
Safety
Record the original href, make the change on a branch or preview, obtain approval, then publish.
Rollback
Restore the original href or revert the single commit. No database or content migration is involved.
Verification record
Four checks. One bounded fix.
Desktop
Primary CTA reaches the intended destination in current Chrome and Safari.
Mobile
CTA remains visible, tappable, and correctly routed at 390px width.
Failure path
A bad destination no longer produces a branded or server 404.
Regression
Navigation and secondary CTAs retain their original destinations.
What the handoff contains
Before state, exact change, after state, and a way back.
Your actual record names the verified URL, timestamp, approved scope, changed files or settings, acceptance results, remaining risks, and rollback steps. If the public issue cannot be reproduced or the repair is unsafe, Poszo stops rather than expanding scope without approval.