Quick summary
A site support note about adding a persistent phone CTA, review badges, cached rating data, and click tracking inside a static export workflow.
The problem
The site needed easier phone access and stronger review proof without breaking the existing static route setup.
What I checked
- Shared layout shell
- Mobile and desktop CTA placement
- Review badge display areas
- Cached rating and review-count behavior
- Static export compatibility
What I changed
- Added a floating click-to-call button across the site
- Wired the phone CTA into the shared layout so it appeared consistently
- Set up homepage and footer review badge support
- Added cached fallback handling for review rating and count data
- Verified phone-click tracking within the static export flow
Result
Visitors had a more persistent phone path and the site could show review proof while keeping the static build stable.
What I'd watch next
- Whether review API credentials are configured on the server side
- Whether phone-click events remain visible in analytics
- Whether mobile CTA placement conflicts with future widgets