Skip to main content

Google Search Console Property Setup for a New Client SOP

Overview​

  • What: Create a Google Search Console (GSC) Domain property for a client's primary domain under setup@symphonycore.com, capture the DNS TXT verification token for handoff to the DNS team, verify ownership, submit the XML sitemap, grant the client User access, and link the property to GA4.
  • When: During onboarding, after the client has approved their domain. The verification TXT can be requested from the DNS team BEFORE go-live (the TXT is safe to add at any time — it lives at the root but does not change what is served). Sitemap submission must wait until the site is live at the production domain.
  • Who: Implementation specialist operating in the Chrome profile bound to setup@symphonycore.com. Per KB-014 Shared Email Accounts, client analytics MUST be created under setup@, never admin@.
  • Time Required: 15–25 minutes per client (excluding DNS propagation wait time).

Why Domain property over URL-prefix property​

GSC offers two property types:

TypeCoverageVerification
Domain property (recommended)Every subdomain + every protocol of the root domainDNS TXT only
URL prefix propertyOnly the exact URL prefix (e.g. https://www.mootslaw.com/)TXT, HTML file, HTML tag, GA4, or GTM

SC's default is Domain property because it captures all subdomains in one place (www., go., sc., future subdomains) without separate verification per host. The trade-off is that verification is DNS-only — a TXT record at the apex.

Prerequisites​

  • Access to the Chrome profile signed into setup@symphonycore.com.
  • Client's primary domain confirmed (e.g. mootslaw.com).
  • DNS team / IT contact identified (e.g. Synergy Online for Moots Law). The TXT must be added to the apex of the client's domain — SC does not own the DNS, the IT contact does.
  • Client folder exists at 09-clients/<client-slug>/ with a populated client profile.
  • For sitemap submission: the website must be live at the production domain (post-DNS cutover).
  • For GA4↔GSC linkage: the GA4 property must already exist per GA4 Property Creation SOP. If not, link can happen later — not blocking.

Procedure​

  1. Sign in as setup@. Open the Chrome profile for setup@symphonycore.com and navigate to https://search.google.com/search-console. Confirm the avatar at the top-right is setup@. If it shows any other account, stop — do not proceed under the wrong identity.

  2. Create the Domain property. Top-left property selector → Add property → choose Domain (left column, not URL prefix).

    • Domain: the client's root domain WITHOUT protocol or www (e.g. mootslaw.com, not https://www.mootslaw.com).
    • Continue.

  3. Capture the verification TXT for the DNS team. GSC will display a TXT record in the format google-site-verification=<token>.

    • Copy the entire value (the full string starting with google-site-verification=).
    • Do NOT click Verify yet — the DNS record needs to be added by the IT contact first.
    • Click "Verify Later" to dismiss without verifying.

  4. Add the TXT to the client's DNS request doc. Create or update the DNS change doc at Client_Delivery/<client-slug>/work-in-progress/YYYY-MM/website-go-live/YYYY-MM-<slug>-dns-phase-c-records.md following the format in Client DNS Setup SOP. Single TXT record:

    • Type: TXT
    • Host: @ (root / apex)
    • Value: google-site-verification=<token> (the full string captured in Step 3)
    • TTL: 600 (matches Phase A/B convention; can raise to 3600 after verification)
    • Notes for IT contact: this is a Google verification token. It is safe to add at any time — it does not affect website serving, email, or any existing record. Adding it does not require a maintenance window.

  5. Send the DNS request to the IT contact. Email the DNS change doc (or PDF render) to the client's IT contact (per Client DNS Setup SOP §Template emails). Include the client primary contact and support@symphonycore.com on Cc. Use the existing ticket reference if one is open (e.g. Synergy RT#710255 for Moots Law).

  6. Wait for propagation. TTL is 600s but propagation typically completes within 5–15 minutes once the record is saved. Confirm via dig TXT <client-domain> +short from terminal, or dnschecker.org → TXT lookup on the apex domain. Look for the google-site-verification=... string.

  7. Verify the property in GSC. Return to https://search.google.com/search-console → reopen the unverified Domain property → click Verify.

    • On success: "Ownership verified" banner.
    • On failure: re-check the TXT was added to the apex (Host = @), not a subdomain; check dnschecker.org shows the value globally. Click Verify again. GSC sometimes needs a second click after propagation completes.

  8. Submit the XML sitemap. Sitemaps → Add a new sitemap.

    • Sitemap URL: https://<client-domain>/sitemap.xml (the default for WordPress sites running the SearchAtlas plugin — OTTO auto-generates and maintains this).
    • If the site is not yet live at the production domain, skip this step and run it after DNS cutover.
    • Confirm status shows "Success" within a few minutes.

  9. Grant client User access. Settings → Users and permissions → Add user.

    • Email: client's primary contact.
    • Permission: Full (gives them full visibility but not ownership). Owners (Admin equivalent) stay restricted to setup@.
    • Click Add.

  10. Link GSC to GA4. In GA4 (not GSC): Admin → Property column → Product Links → Search Console Links → Link → choose the GSC property created in Step 2 → choose the GA4 data stream → submit. This enables the Search Console reports panel inside GA4.

  11. Record IDs in the client profile. Edit 09-clients/<client-slug>/<client-slug>-client-profile.md and add to the Technical Access section:

    • GSC Property Type: Domain
    • GSC Property URL: https://search.google.com/search-console?resource_id=sc-domain%3A<client-domain>
    • GSC Verification Method: DNS TXT
    • GSC Verified Date: YYYY-MM-DD

Verification​

  • GSC home for setup@symphonycore.com shows the Domain property for the client's domain with "Ownership verified" status.
  • dig TXT <client-domain> +short returns the google-site-verification=... value.
  • Sitemap (if submitted) shows "Success" in GSC → Sitemaps.
  • Client primary contact received the User-access invite (or confirms access via Settings → Users).
  • GA4 property → Admin → Product Links → Search Console Links shows the GSC property linked.
  • Client profile at 09-clients/<client-slug>/<client-slug>-client-profile.md shows GSC fields populated.

Pitfalls and insights​

  1. The TXT goes at the apex (@), not a subdomain. Domain-property verification requires the token at the root. Adding it as google-site-verification.<domain> or under a subdomain will not verify.
  2. The TXT is inert — safe to add anytime. Unlike Phase B DNS changes that flip what is served, the GSC TXT is verification metadata. The IT contact does not need a maintenance window. Bundle it into a regular DNS change ticket without ceremony.
  3. Domain property cannot be re-verified by other methods. If the TXT is later removed from DNS, GSC will eventually unverify the property and SC loses access. The TXT must remain in place indefinitely. Tell the IT contact this is a permanent record, not a one-time installation.
  4. Multiple verification tokens on the same domain are fine. Each Google identity that verifies the same domain gets its own TXT. The screenshot's note about "1 unused verification tokens were found on your property" is informational — old tokens can be cleaned up via Settings → Ownership verification, but they do not harm anything if left.
  5. The TXT value format includes the google-site-verification= prefix. Some DNS panels require the value in quotes; the full string including the prefix should be inside the quotes. Do not strip the prefix.
  6. Sitemap URL depends on the WordPress SEO plugin. With SearchAtlas + OTTO, the default sitemap is <domain>/sitemap.xml. With Yoast (prohibited per the SC WP stack standard but possibly present on inherited sites), it would be <domain>/sitemap_index.xml. Confirm against the actual site before submitting.