Build Your Website in GHL AI Studio

Which Tool, When

GHL has three AI-assisted builders. Pick the right one up front or you will waste hours. Here is how to choose:

Decision flowchart

1. Do you already have a GHL site that needs updating? Vibe Builder.
2. Do you only need a single page or lead magnet? Funnel AI.
3. Is this a new, full website (3+ pages: services, about, contact)? AI Studio.

Before You Prompt: 10-Minute Prep

AI Studio is only as good as the input you give it. Weak prompts produce generic, template-y pages. Ten minutes of prep before you open AI Studio will directly decide how good the output is.

Get these five things sorted before you write a single word of the prompt:

1. Brand voice in two sentences

What does your business sound like? Formal, friendly, authoritative, casual? Write a two-sentence character brief, e.g. "We're a no-nonsense plumber who talks straight. No jargon, we just fix things." This goes straight into the prompt.

2. The core offer, precisely stated

Not "we do plumbing" but "we fix boiler breakdowns in South Manchester, same day, for homeowners who can't wait." The more specific your offer, the better the copy. Vague inputs produce vague pages.

3. Pages needed

List them before you prompt. Home, Services, About, Contact is a typical minimum. Add case studies, FAQs, or location pages if you need them. AI Studio can build multiple pages in one go, but you have to tell it which ones.

4. Calendar created

If you want people to book online, create the calendar in GHL before you generate the site. AI Studio can embed a booking widget at generation, but only if the calendar already exists. Check Calendars > Settings to confirm it is set up with availability.

5. Pipeline set up

If you want contact forms to feed a specific pipeline (e.g. "New Enquiries"), create the pipeline in GHL first. Know the pipeline name and the stage you want submissions to land in. That saves you re-wiring the CRM afterwards.

The Prompt Recipe + 6 Worked Examples

AI Studio accepts a freeform prompt. There is no required format, but a consistent structure gives you consistently better results. Use this recipe as your template:

Below are six worked examples for common types of business. Pick the one closest to yours, swap in your own details, and paste it straight into AI Studio.

Example 1: Local service (plumber)

Example 2: Coach

Example 3: E-commerce (product brand)

Example 4: B2B service (IT support)

Example 5: SaaS (software product)

Example 6: Restaurant

Iteration & Editing with Vibe Builder

After AI Studio generates a site, you will almost always need to tweak sections, rewrite copy, or adjust layout. Vibe Builder is the inline editor for this. It works inside the Sites builder on any existing page.

To access it: open the page in the GHL Sites editor, click the AI icon in the toolbar, and select Vibe Builder. You can then click on any section and give it a natural language instruction.

Commands that work reliably

These commands produce consistent, useful results in Vibe Builder:

• Rewrite this section in a [tone] voice, e.g. "Rewrite this section in a friendlier, less corporate voice." Good for tightening AI-generated copy.
• Make the headline more specific: "Change the headline to focus on [specific benefit]." Replaces generic headlines with something sharper.
• Shorten this section: removes filler and tightens copy. Works well on long generated paragraphs.
• Add a section for [content]: "Add a section for client testimonials with three placeholder quotes." Inserts new content blocks without rebuilding.
• Change the call to action to [text]: updates button copy and sometimes the link. Always check the link after running this.
• Reformat this as a bullet list: useful when AI Studio generates a wall of text that should be scannable.

Commands that produce unpredictable results

• Layout restructuring ("move this section above that one"): better done manually in the editor
• Colour or font changes: use the design settings panel instead
• Adding forms or booking widgets: always wire these manually to ensure CRM connection works

Wiring the CRM

AI Studio builds the pages, but the CRM connections (calendars, forms, pipelines, workflows) almost always need checking and often need finishing by hand. Before you go live, walk through each of these to make sure your CRM is actually connected.

Calendars

AI Studio can embed a booking widget if you name the calendar in your prompt. After generation:

1. Go to the booking widget in the Sites editor.
2. Click on it and check the calendar it is linked to. AI Studio sometimes creates a new calendar rather than using an existing one.
3. If it created a new calendar, delete the widget and re-embed the correct one from Add Element > Calendars.
4. Test the booking flow end-to-end before going live.

Forms and the Form ID workaround

There is a known bug in AI Studio where generated forms do not always fire to the correct GHL pipeline. The form appears to work visually but submissions either go to the wrong pipeline or do not create a contact at all.

The workaround:

1. Build your form in Sites > Forms in GHL (not inside AI Studio).
2. Once built, note the Form ID from the form's embed code or URL.
3. In AI Studio, delete the generated form element.
4. Re-embed the form using Add Element > Forms and select the form you built manually.
5. In the form settings, set the pipeline and stage explicitly.
6. Test with a real submission and check the contact appears in the correct pipeline stage.

Pipelines

After building the form manually (above), confirm the pipeline is set correctly:

• Go to CRM > Pipelines and check the target pipeline and stage exist.
• Submit a test form and confirm the contact appears in the correct stage.
• Check the contact record has the expected fields populated (name, email, phone, source).

Workflows

AI Studio does not set up workflows. Any automated follow-up (confirmation email, SMS, task assignment) needs to be built in Automation > Workflows after the site is complete. Workflows are specific to each business, so AI Studio deliberately leaves them for you to set up.

UK Compliance Layer

Every UK website needs to meet a minimum compliance standard. This lesson covers the non-negotiables. It is not legal advice.

Cookie banner: v2, Ask-to-Opt-In mode

GHL includes a built-in cookie banner. You need version 2 with Ask-to-Opt-In mode enabled. This is required to meet UK GDPR and PECR standards for websites using analytics or marketing cookies.

To set it up:

1. Go to Settings > Compliance > Cookie Consent in GHL.
2. Select Version 2.
3. Set mode to Ask to Opt In (not "Notify Only": that does not meet current UK standards).
4. Configure the categories: Essential (pre-ticked, not toggleable), Analytics, Marketing. Do not pre-tick Analytics or Marketing.
5. Link to your cookie policy page in the banner.
6. Test the banner on a fresh browser session to confirm it fires on first visit.

Starter prompt: Cookie policy page

Starter prompt: Privacy policy page

Starter prompt: Terms & conditions page

GA4 consent mode

If you are using Google Analytics 4, consent mode must be enabled so GA4 only fires tracking scripts after a visitor has consented to analytics cookies. GHL's cookie banner v2 handles this automatically when connected to a GA4 property, but you need to verify:

1. The GA4 measurement ID is entered in Settings > Integrations > Google Analytics in GHL.
2. The banner is in Ask-to-Opt-In mode (not Notify Only).
3. Test in a private browser: visit the site, do not accept cookies, then check GA4 DebugView. No full event data should appear before consent.

GHL as data processor

GHL acts as the data processor for any personal data collected through your site. You (your business) are the data controller. That means:

• Your privacy policy must list GHL as a third-party processor.
• You should have a Data Processing Agreement (DPA) with GHL. This is available in GHL's legal documentation.
• Data collected via your GHL forms must only be used for the purpose stated in your privacy policy.

SEO Quick Wins

AI Studio generates basic on-page content, but SEO requires deliberate setup. These are the actions to take immediately after a site is generated.

Auto-schema per industry

GHL supports structured data (schema markup) to help search engines understand your content. Apply the correct schema type for your industry:

Meta checks

AI Studio generates meta titles and descriptions, but they are often too long or too generic. For each page:

1. Go to Sites > [Page] > Settings > SEO.
2. Meta title: 50-60 characters. Should include the primary keyword and the business name. Format: Primary Keyword | Business Name.
3. Meta description: 140-160 characters. Should include the primary keyword, a clear benefit, and a soft CTA.
4. Check there are no duplicate titles across pages; each page needs a unique title.

Google Rich Results Test

After launch (or on the staging URL), run each important page through Google's Rich Results Test to confirm schema is being read correctly. Navigate to search.google.com/test/rich-results, enter the page URL, and check for errors. Fix any schema warnings before launch.

Additional quick wins

• Set the H1 on every page. AI Studio sometimes generates pages without a clear H1 or with the business name as the H1 instead of a keyword-led heading.
• Add alt text to all images. Placeholder images need descriptive alt text, not just "image1".
• Set the canonical URL on pages that might have query string variants.
• Check page load on mobile. AI Studio sites can be image-heavy; compress any large images before embedding them.

Pre-Launch Checklist

Don't skip this. Print it, tick it off, and save yourself a mess on launch day.

Content

• All placeholder text replaced with real content
• All placeholder images replaced with real images (or approved stock)
• Business name, address, and phone number correct on every page they appear
• All links tested and working (internal and external)
• Spelling and grammar checked in British English

Compliance

• Cookie banner is live, set to Ask-to-Opt-In, and fires on first visit
• Cookie policy page is published and linked from the cookie banner
• Privacy policy page is published and linked from the footer
• Terms & conditions page is published and linked from the footer
• Legal pages reviewed by a solicitor (or you have accepted responsibility)
• GA4 consent mode confirmed working (no tracking without consent)

CRM wiring

• All forms tested with real submission: contact appears in correct pipeline stage
• Booking calendar works end-to-end. Test booking created and appears in GHL calendar
• Confirmation email or SMS fires after form submission or booking
• Pipeline stages named correctly and notification set up for new leads

SEO

• Meta titles set on all pages (50-60 chars, unique per page)
• Meta descriptions set on all pages (140-160 chars)
• Schema markup applied and tested in Rich Results Test
• All images have descriptive alt text

Mobile & performance

• Site tested on mobile: layout, forms, and CTAs work correctly
• Page load speed acceptable (under 3 seconds on a standard connection)

Known Limitations

AI Studio is in beta. It is good enough for most websites, but it has real limitations you should know before you commit.

No code export

AI Studio sites cannot be exported as raw HTML or moved to another platform. Your site lives in GHL. If you ever leave GHL, the site does not come with you. Know this before you commit.

Template-y output on weak prompts

Weak or vague prompts produce generic, indistinguishable sites. The tool is only as specific as your input. If you put in a one-liner, you will get a placeholder-grade result. Use the prompt recipe in Lesson 03.

Beta stability

AI Studio is not rock-solid yet. GHL updates it often, and behaviour can change between sessions. Something that worked last week might act differently today. Keep an eye on GHL release notes and the CRM Club community for reported changes.

What not to try

• Complex e-commerce: AI Studio is not a shop. Product grids and payment flows need the GHL Products module and manual setup. Use AI Studio for your marketing site and wire the shop up separately.
• Multi-location pages at scale: Generating 20+ location pages in one go produces inconsistent results. Build the template manually and replicate.
• Custom JavaScript or third-party embeds: AI Studio has no way to handle custom code. Use the Sites builder for anything requiring custom scripts.
• Rebuilding an existing site: If you already have a site in the standard Sites builder, do not try to "migrate" it into AI Studio. Rebuild from scratch, or use Vibe Builder to edit the existing pages.
• When you want total design control: AI Studio sites are edited via prompts and Vibe Builder. If you want to drag-and-drop and tweak every element by hand, you will get frustrated. Know this up front.