01Who this is for
- Founders of SaaS platforms, need to quickly diagnose page errors that affect user conversion.
- Marketing agencies, must ensure tracking scripts and custom code don’t disrupt client sites.
02Basic troubleshooting steps, explained
The platform injects tracking scripts on the client side, so they never appear in the static HTML source. Custom fields shown on pages come from browser stored data, not from backend updates. Image optimization runs automatically but can be turned off per image.
All funnel and website settings live under the Sites section. Security headers are entered in the Settings > Security tab for each funnel. Custom code blocks can be edited in the builder view where code elements are identified by the marker “c custom code.”
When a page fails to render, you can use the browser’s Network tab to discover which funnel generated the live request, clear any custom code that may be causing issues, and then edit or remove restrictive security header values.
03How businesses use basic troubleshooting steps
- Digital marketing agency. The agency opens the browser console, uses the Network tab to locate the funnel behind a client’s live page, deletes any problematic custom code in the builder, and simplifies the Content Security Policy header to restore widget loading.
- Online course provider. The provider checks that head tracking scripts are injected client side, verifies custom fields are captured via forms, and disables image optimization for high resolution course thumbnails that appear blurry.
- Fitness studio. The studio reviews security headers for its booking funnel, removes line breaks from the header string, clears the header list temporarily, and tests the page in an incognito window to confirm assets load correctly.
04The numbers and rules that matter
- Images above the fold should be under 200kb for good LCP scores on mobile.
- Benchmark scores: Above 80 on mobile, above 95 on desktop.
05How to set up and use basic troubleshooting steps in HighLevel
Identifying the funnel, page, or location of a live site
- Open the browser’s developer tools and select the Network tab.
- Clear the console output and enable the XHR filter.
- Refresh the live page to generate network activity.
- Locate the event call within the network logs.
- Open the payload section of that request to see the funnel and page identifiers.
Removing custom code causing site errors
- Open the funnel or website builder inside HighLevel.
- Switch to the page preview mode.
- Press Ctrl+F (Windows) or Cmd+F (Mac) and search for the text “c custom code”.
- Select any code element that contains the marker and delete it.
- If a hydration error appears in the console, open a support ticket.
- Reload the preview to verify the page now renders correctly.
Adjusting security headers
- Navigate to Sites > Settings > Security tab.
- Review each custom header entry such as Content Security Policy or Strict Transport Security.
- Temporarily clear all custom header values and reload the page.
- Ensure any restored header values contain no line breaks and are entered on a single line.
- After saving, clear the browser cache or test in an incognito window to confirm assets load.
06Settings that matter
- Content Security Policy. Controls which sources the browser may load scripts, images, and other assets from.
- Strict Transport Security. Enforces HTTPS connections for the site.
- X Content Type Options. Prevents MIME type sniffing by the browser.
- X Frame Options. Restricts whether the page may be displayed inside an iframe.
07Things to know before you rely on it
- Custom fields updated via backend automation are not stored in local browser storage and therefore do not appear on funnel pages.
- Image optimization applies a universal quality setting; disabling it does not stop lazy loading of images.
- Security header values must be entered as a single continuous line; line breaks cause loading failures.
08If something goes wrong
- Head tracking code does not appear inside the <head> tag in page source.. Understand that the platform injects tracking scripts on the client side; they function correctly even if not visible in static source.
- Updated custom fields are missing from the live site.. Ensure the fields are captured via a form or survey so they are stored in local storage, or add a script to push backend values into local storage before rendering.
- Images appear blurry or load slowly.. Disable image optimization for those images in the builder or upload higher resolution files; note that lazy loading remains active.
- Custom values break or do not render in the funnel preview.. Remove any hyperlinks from the custom value element and replace special characters (e.g., \n) with HTML line breaks using a text formatter action.
09How it connects to the rest of HighLevel
- Improve page speed with HighLevel’s built in tools Page speed guide
- Validate Content Security Policy syntax with Google’s CSP Evaluator CSP validation
- Set up root domains or subdomains for funnels and websites Domain setup
- Review all site related features and options All Sites features
- Explore HighLevel pricing and plans Pricing
Michael's take

Be wary of assuming everything you see in the HTML is the whole story. HighLevel adds many scripts on the fly, so missing tags in the source don’t mean tracking isn’t working. That dynamic injection keeps pages light but can confuse newcomers.
Knowing where to look. Local storage for Custom Fields, the image toggle for clarity, or the security tab for header blocks. Helps resolve issues.