How PACE gets this client's content in front of their audience. Changing it never touches generated content — it only changes where it's served.
Where PACE's contact / CTA / providers info sits on blog posts and pages. Use Footer bar when the client's own site already has a sidebar (e.g. WordPress) so PACE content complements it instead of competing.
Emails whoever manages the client's site everything they need for the current delivery mode (WordPress plugin + keys, or the DNS records) PLUS the Google Analytics + Search Console access steps, in one message.
PACE publishes into the client's existing WordPress as native posts/pages via the PACE Content Bridge plugin. Recommended path: pairing, no secret is ever emailed or pasted, the plugin generates its own key and connects itself.
Generate a one-time pairing code, then give the client their license key + code. In WordPress → Settings → PACE Bridge → Pair with PACE, they enter both and click Generate secret & pair. The endpoint + secret land here automatically. Or just use Send full setup above, which emails the code with the steps.
For clients not on WordPress. Their edge (Cloudflare/nginx/Netlify/Vercel) rewrites a subfolder of their own domain to PACE — best for SEO. Set the subfolder, save, then hand them the matching config below.