SOPs — Landing Pages

Landing Pages SOP

New client pages and additional pages within existing builds

⚡

Pipeline-first always. For all new LP builds, try the LP Automation Pipeline first. Submit the brief form, review the output, merge. The manual GPT process below is the fallback while the pipeline is in testing.

New client pages

Step 1 — Keyword research & TAM

Use the Keyword Research GPT ↗ — enter business name, location, primary services

Use the Topical Authority GPT ↗ — use client's primary domain as the seed keyword. Fill all prompts.

Extract 1–3 primary keywords for the first page build. Add to the TAM (Topical Authority Map) for tracking.

Step 2 — Schema plan

Before drafting any copy, document the schema requirements for the page:

Page type	Schema to use
Service page	`Service`
Location service page	`LocalBusiness` + `Service`
About page	`Organization`
Review page	`Review` or `AggregateRating`
Blog post	`Article` or `BlogPosting`

Required fields to document: Business Name, URL, Phone, Service Type, Location, Price Range (if applicable), Areas Served, SameAs social links. Add schema notes to the page brief so the builder knows what structured data to add.

Step 3 — Generate copy

For the first page of any client, use the Single Page LP GPT ↗ (Ignition clients and first Accelerate page).

If the client has a dedicated GPT, use that instead — see GPT Reference ↗.

Store generated output in the client's Google Drive folder.

Step 4 — Review & refine

Guy: initial review — adjust messaging, offer language, or branding as needed
Optional: send GPT a follow-up refinement prompt if copy needs significant changes
Teddi: final buddy review before build

Step 5 — Build & deploy

See LP Editing Guide ↗ for GitHub editing and Cloudways Deployment guide ↗ for going live.

Additional pages (within existing builds)

For clients who already have a live LP and need additional service or location pages.

Step 1 — Determine focus keyword

Check the TAM — the keyword for this page should already be identified. If not, add it before proceeding.

Step 2 — Generate copy

Use the Sub-Pages LP GPT ↗ for all Accelerate additional pages. For Ignition additional pages, use the Single Page GPT. Store output in Google Drive.

Step 3 — Schema plan

Same process as new client pages (Step 2 above). Even for sub-pages, document the schema type and required fields before building.

Step 4 — Review

Guy: initial review and adjustments
Teddi: final buddy review

Step 5 — Build in repo

In GitHub, duplicate the existing index.html into a new file (e.g. brake-servicing.html)

Replace content section by section with the new GPT output — headings, body, testimonials, CTAs

Update form settings if the page has a unique CTA or thank-you redirect

Update page title, meta description, and OG tags for the new keyword

Confirm tracking scripts carry over correctly — check GTM fires on the new page

QA & go-live

Preview on desktop and mobile — check layout, fonts, images, CTAs
Submit a test form — confirm it appears in WhatConverts and CRM
Check GA4 DebugView — confirm page view event fires
Check Meta Events Manager — confirm pixel fires on page load
Verify "Read More Reviews" link points to real Google Maps URL (not #)
Phone number visible in all button labels — not just a generic "Call Now"
No placehold.co placeholder images visible
Canonical tag points to the live Cloudways URL (not GitHub Pages)
Notify team via Slack once live
Monitor KPIs in dashboard

Ongoing optimisation

Landing pages aren't set-and-forget. Review each page monthly alongside the Google Ads and WhatConverts data.

Check landing URL in WhatConverts — are leads coming from the right pages? If not, check campaign final URLs.
Check GA4 engagement rate — below 40% on a key LP is worth investigating.
CTA button text — test different labels if CTR is low. Brief the change through Claude Code.
Copy refresh — update seasonal offers, new reviews, updated hours or services as needed. Text edits go directly in GitHub.
New pages — Accelerate clients should be building 2 new pages per month. Track in ClickUp.