# Custom GoHighLevel pages: separate the design from the lead workflow

Use the recorded custom-code route, preserve a working version and test the form beyond its visual success message.

[HTML](https://lukejbyrne.com/library/guides/cmuu9h_gk1m/)
Content language: en
Author: Luke Byrne
Video published: 2026-06-26
Guide published: 2026-11-02

[Watch the video](https://www.youtube.com/watch?v=cmUu9h_Gk1M)
Video language: English

## Define what Claude should generate

The June walkthrough builds a custom website with Claude Code or Claude rather than starting from a standard GoHighLevel template. HTML, JavaScript and CSS are moved into GoHighLevel. The published description covers the transfer and later updates; it does not specify every current dashboard control.

1. Describe the business, page sections, supplied copy and the action visitors should take. Ask for clearly separated HTML, JavaScript and CSS.
2. Include the form fields and expected submission behaviour in the brief. Keep unconfirmed claims and testimonials out of the generated page.

## Transfer the page and preserve a baseline

Follow the blank-site section at 2:36 and the custom-code section at 3:55 with the original video open. The demonstration includes a custom code block, separate CSS and a page-background correction. A correct-looking generated preview does not establish that the hosted version matches it.

1. Add the generated code and styling through the demonstrated route, then compare the actual GoHighLevel page with the preview.
2. Check background, mobile layout, navigation and form visibility. Save a working version before asking Claude for further changes.

## Connect and test the lead handoff

At 8:58, the workflow connects the form to GoHighLevel contacts through an inbound webhook. Treat page rendering and lead capture as separate checks: a success message alone cannot confirm a saved contact.

1. Follow the recorded inbound-webhook workflow and map the supplied form fields to the intended contact data.
2. Submit synthetic details, locate the resulting contact and compare the saved fields. Also inspect how a failed submission is presented before sending real visitors.

## Update the site without losing the connection

Keep the code version and the lead workflow together in your handoff. Use the original product destination for setup: http://www.gohighlevel.com/ailuke. This companion does not reproduce the separate community prompt or claim access to it.

1. Request one targeted page revision, paste the revised code and repeat the rendering and contact checks.
2. Retain the previous working files and note which version produced the verified contact.

## The takeaway

A custom page is useful when its design and lead capture both work. Verify the saved contact after each meaningful form change.

## Workflow resources

- [gohighlevel.com](http://www.gohighlevel.com/ailuke)

## Chapters

- [0:00 Build a custom GoHighLevel site with Claude Code](https://www.youtube.com/watch?v=cmUu9h_Gk1M&t=0s)
- [1:02 What Claude needs to generate](https://www.youtube.com/watch?v=cmUu9h_Gk1M&t=62s)
- [2:36 Set up the blank GoHighLevel site](https://www.youtube.com/watch?v=cmUu9h_Gk1M&t=156s)
- [3:55 Add the custom code and styling](https://www.youtube.com/watch?v=cmUu9h_Gk1M&t=235s)
- [6:35 Edit, iterate, and keep version history](https://www.youtube.com/watch?v=cmUu9h_Gk1M&t=395s)
- [8:58 Connect the form to GoHighLevel contacts](https://www.youtube.com/watch?v=cmUu9h_Gk1M&t=538s)
- [14:22 Wrap-up and next steps](https://www.youtube.com/watch?v=cmUu9h_Gk1M&t=862s)

## Sources and limitations

Prepared 1 November 2026 from this exact published video description and chapter sequence. Steps are editorial follow-along guidance, not quotations from a reviewed transcript. The full video was not independently watched or transcribed and the product was not retested. Historical offers and setup details need a fresh check at the original resources.

[Original video](https://www.youtube.com/watch?v=cmUu9h_Gk1M)