/ GPT Reference Internal
SOPs — Tools

GPT Reference

Client-specific and platform GPTs for MM tasks
ℹ️
LP pipeline note: The MM LP pipeline (Claude-powered) is replacing the LP Generator GPTs for new page builds. The GPTs below remain the fallback while the pipeline is in testing, and are still used for blog posts, ad copy, and SEO tasks.
1

Client-specific GPTs

Use these for copy that needs to match the client's specific voice, services, and location. Always prefer a client GPT over a platform GPT when one exists.

2

Platform GPTs

TaskGPT
SEO — existing pagesMM SEO Analyser ↗
Landing page — first pageMM LP Generator (Single Page) ↗
Landing page — additional pagesMM LP Creator (Sub Pages) ↗
MM blog postsMM Blog Post Writer ↗
Client blog postsMM Blog Writer (Client) ↗
Google Ads — Search copyMM GAds Copy Creator ↗
Google Ads — PMax copyMM PMax Copy Creator ↗
Google Ads — optimisationGoogle Ads Optimisation GPT ↗
Keyword researchKeyword Research GPT ↗
Topical authorityTopical Authority GPT ↗
Topical authority mapTopical Authority Map GPT ↗
3

Notes on GPT use

  • Always prefer the client GPT over a platform GPT when one exists — client GPTs have the brand voice, location, and service details pre-loaded
  • LP pipeline replaces LP GPTs for new page builds — the Claude-powered pipeline generates copy automatically from the brief form. Use GPTs only as fallback or for manual sub-page builds
  • Ad copy GPTs are still in use — the Autopilot generates ad copy rewrites internally, but for new campaign copy at setup, use the GAds Copy Creator GPT
  • Store all GPT output in Google Drive — in the client's folder, named clearly with date and page/ad type
  • Human review is mandatory — all GPT output goes through Guy (initial review) and Teddi (buddy review) before anything goes live