Launch Local Everywhere · Site Builder

Build Guide – From “Installed” to a Real Website with Pages, Tokens, GEO, Leads & Payments

This guide starts exactly where the Install Guide ends: the site is deployed, but it still looks “empty”. Your job now is to create the home page, decide which parts should be tokens, turn on GEO where it helps SEO, and wire up leads, comms, and payments.

Open your newly installed site in a browser. You’ll typically see:

• A default header (or placeholder header) if you haven’t built your own yet.
• An empty content area (because you haven’t published any pages yet).
• A GEO link directory / GEO link tree area (depending on license entitlements).

The home page is the default front page. In most Launch Local Everywhere setups, if someone hits an invalid/unknown slug, they are redirected to the home page—so this page becomes your “catch-all” first impression. Build it before anything else.

1. Open the Builder dashboard → select your site → go to Pages.
2. Click New Page.
3. Set Slug to home (lowercase, no slashes).
4. Set status to Published.
5. Save.

These fields populate the page head and visible headings. They are not “optional polish”—they are the core of what Google understands about the page.

GEO-enabled pages are “location-aware”. One page template becomes many location variants. These three placeholders are the core building blocks:

Tokens are centrally controlled blocks of text/HTML that can be dropped into any page. If something appears on multiple pages, it should usually be a token.

If you build pages first and later decide “this should be a token”, you end up revisiting many pages to swap raw HTML for token references—exactly what tokens are meant to avoid.

Start with a small set of pages you can expand later. Keep internal linking consistent, and use {{geo_suffix}} only in href links on GEO pages.

Use the Media tab to upload site images (logos, hero images, service images, team photos). Then reference them in tokens and pages. This keeps your layout consistent and makes later redesigns faster.

• Keep hero images optimized (reasonable file sizes, modern formats if available).
• Use consistent naming (e.g., hero-home.webp, service-roofing.webp).
• Prefer reusable sections as tokens that reference these images.

The Socials tab lets you connect social accounts and publish content from within the builder. Current support typically includes Facebook Page and Instagram.

• Connect accounts early so you can reuse content from page launches as social posts.
• Use new page launches (especially GEO/service pages) as regular posting prompts.

If you use the in-house form generator (recommended for speed), every form submission becomes a lead. Leads appear in the Leads panel, where you can track and export submissions.

Use the Payments tab to connect your payment processor (Stripe supported) and create payment links for products or services. Then embed those links on pages via tokens so pricing/checkout buttons are consistent site-wide.

• Create payment links in the dashboard.
• Store buttons/price blocks as tokens (e.g., {{token:pricing}}, {{token:buy_now}}).
• Drop the token into any page where you want conversion.

The Config tab is where you set site-wide values used across templates and tokens. This is also where you typically wire in protection and tracking configured in the Install Guide.

Pages can be created one-by-one, but the fastest workflow is: export a CSV template → have AI generate rows → import the CSV back in. This lets you make mass changes in a spreadsheet editor.

By default, Body HTML is typically authored using Tailwind CSS utility classes. You can override styling with your own CSS or framework, but Tailwind is recommended for speed, consistency, and predictable responsive behavior.