Skip to main content

Client SEO Foundation Setup SOP

Overview​

  • What: Give a client's website a working technical SEO foundation and a measured baseline. That means managed titles, meta descriptions and schema from the client profile, one clean sitemap, a verified Search Console property, GA4 linked, rankings tracked for an agreed keyword set, and a recorded baseline audit.
  • When: A client takes the SEO add-on, or SC agrees an SEO setup as part of a website engagement (it is not part of the core plan pricing). Run it after the website is live on its production domain.
  • Who: Operator: Implementation Lead, or an SEO operator or AI agent working under them. Approver: the SC account owner for the client, for any live change and for the keyword list.
  • Time Required: 3 to 5 hours of work over about a week. The time is mostly DNS verification lead time and the first analytics and rank-tracking runs.

Scope. This SOP is the one-time foundation: Rank Math, Search Console, GA4, rank tracking and a baseline audit. The monthly SEO add-on builds on it with content, backlinks, local citations and Google Business Profile optimisation (run in GHL). Backlinks and citations are fulfilled through third-party vendors not yet selected, and have no SOP yet. Decisions D7 and D8 in the SEO tooling migration decision log.

What this replaced. The SearchAtlas-based One-Time SEO Setup service, archived 2026-10-31 after SearchAtlas lapsed (2026-08-21). Every step that ran through the SearchAtlas dashboard or OTTO now runs through Rank Math, Search Console and SC's own tooling.

Prerequisites​

ItemSource
Client profile with the SEO identity fields filled (legal and public business name, public address or service area, public phone, logo, socials, services, service areas). Unfillable fields go in the profile's Deferred SEO fields register, never invented09-clients/<slug>/<slug>-client-profile.md; client-profile-hygiene-process
WordPress admin on the live site (WordPress sites)Client access per client-self-service-access
DNS contact able to add a TXT record at the apexClient or their IT contact
setup@symphonycore.com Chrome profileKB-014
GA4 property and GTM container already liveGA4 Property Creation SOP, GTM Integration SOP
The site is not carrying SearchAtlas / MetaSyncIf it is, run the SearchAtlas to Rank Math Migration SOP first and resume here at step 3

Live-site rule. Every write to a live client site is presented as a change table and approved first. Take the Rank Math settings export (step 2) before the first change.

Procedure​

1. Search Console​

Run the Google Search Console Property Setup SOP end to end: a Domain property under setup@, DNS TXT verification, the sitemap submitted, the client as Full user, and the GA4 link. It is the only verification path; do not use the HTML-file, tag, GA4 or GTM methods.

DNS propagation can take a day. Start this first and do step 2 while you wait.

2. Rank Math (WordPress sites)​

  1. Not installed: install and connect per WordPress Setup SOP §5.3.
  2. Configure to the standard by running the Rank Math Client Site Configuration SOP: modules, titles, archives, builder post types, the sitemap, the Search Console + GA4 connection, email reports and the settings export. The values are in the Rank Math Configuration Standard; do not restate them in the ticket.
  3. Identity and schema: enter the business identity in Rank Math from the client profile only, using the field map in the migration SOP Appendix A. LocalBusiness subtype when the address is public, otherwise Organization.

GHL-native website: Rank Math does not apply. Set robots.txt per the robots.txt SOP and follow the SEO section of the GHL Native Website Build SOP. Schema and a platform sitemap on GHL-native pages are open questions in that SOP (§9). Record them as limits in step 6 rather than promising them.

3. On-page metadata on priority pages​

Agree the priority pages with the account owner: the homepage, each service page, the about and contact pages, and each service-area page, typically 6 to 10 pages. For each:

  1. An SEO title written to the Custom titles rule: 60 characters or fewer, primary keyword near the front. A custom title replaces the template, so on pages end it with | <Brand> (the audit checks for it). Or leave the page title to the template and write only the description.
  2. A meta description of 150 to 160 characters, written for the click.
  3. Exactly one <h1>; headings in order; descriptive alt text on content images.
  4. The page's schema type per the standard's Schema row. Never FAQPage. While the page-schema default is an open question in that row, leave the installed default and compare the JSON-LD (Rich Results Test) before and after any schema change.

Present the titles and descriptions as a change table for approval, then apply them in the Rank Math meta box. For more than about 10 pages, use Rank Math's CSV import (export first to match its columns).

4. Keywords and rank tracking​

  1. Shortlist 10 to 15 keywords with the account owner. Build them from the client's services crossed with their service areas, as recorded in the profile. Add any query the client already ranks for in Search Console Performance once data exists. Record the approved list in the client profile.
  2. Provision rank tracking in symphony-flow per symphony-flow/docs/sop/rank-tracking-operations.md §2: the client's rank-tracking Sheet, its keywords tab, and the registry entry. Weekly DataForSEO checks then append positions to the Sheet's history tab.
  3. Rank Math's own Rank Tracker is a convenience view capped at 10 keywords. DataForSEO is the record (Rank Math standard, Rank reporting row).

5. Baseline audit​

Run the Client Technical SEO Audit SOP as a baseline. That includes creating the site's audit-seo.sh expectation record, and confirming the site appears in the symphony-flow sitemap sweep (it needs a website_testing.primary_url in the registry and must pass the feature's active check). Fix every P1 before step 6; ticket the rest.

6. Hand off​

  1. Write a one- to two-page client summary covering what was set up, the priority pages and their new titles, the tracked keywords and their starting positions (after the first rank-tracking run), open items, and anything the stack cannot do (step 2's GHL limits). Use plain language, white-label terms only: your website, Google Search Console, never internal tool names.
  2. Save it as YYYY-MM-seo-report-<slug>.pdf in the client's Drive reports/seo/ (Drive standard, reports/ spec). Internal audit records stay in confidential-internal/seo-audits/.
  3. Fill the client profile's Analytics & Measurement table: GA4 property, GTM container, Search Console, last audited date.
  4. Put the site on the monthly audit cadence in the Client Technical SEO Audit SOP.

Verification​

CheckPass
Search ConsoleDomain property verified under setup@; one sitemap submitted, status Success; client has Full access; linked to GA4
Rank MathThe configuration SOP Verification table passes
Priority pagesEach has an approved title and a single 150 to 160 character meta description in its source; Rich Results Test shows one Organization or LocalBusiness
Rank trackingThe client's Sheet has an approved keywords tab and at least one history run
Baseline auditAudit record in confidential-internal/seo-audits/; no open P1
HandoffClient summary in reports/seo/; profile Analytics & Measurement table filled

Revision History​

DateVersionChange
2026-11-020.2Scope paragraph corrected to D8: the add-on keeps backlinks, citations and GBP optimisation; this SOP covers only the foundation
2026-10-310.1Created to replace the SearchAtlas-based One-Time SEO Setup (seo-one-time-setup.md, archived). Scoped to the reduced SEO add-on (D7): Rank Math, Search Console, GA4, DataForSEO rank tracking and the internal technical audit. No backlinks or citations. Draft until it has been run on a client