Command note: we repainted a template into a client's brand colours, read the page back, and it still rendered in the template's teal.
The read-back wasn't wrong. It was pointed at the wrong layer.
GoHighLevel keeps a design's colours at the funnel level as named site colours, and the shared header, footer and FAQ sections are served last on every page. We rewrote each page's own data. The funnel-level copy overrode it. The page said "repainted." The browser said otherwise.
What shipped:
• The repaint now writes the funnel's shared sections through GoHighLevel's own save, then reads them back
• Every page is judged from what GoHighLevel actually serves, not from what it stored
• Five honest verdicts per page: brand, still the template, mixed, nothing to judge, or unreadable
• A page that isn't the brand's blocks removal of the originals — nothing gets deleted on an unproven repaint
The takeaway works without our tool:
1) Name the layer — which object does the visitor's browser resolve last?
2) Verify there, not where you wrote
3) Treat "can't judge" as its own answer, not a pass
4) Make the unproven case block the destructive next step
One side effect we print in the result rather than hide: shared sections are funnel-wide, so the template's original pages render in the brand's colours too. Better said out loud than discovered.
Verifying the thing you edited is not the same as verifying the thing they see.