Skip to main content

Client Technical SEO Audit SOP

Overview​

  • What: Check that a client's website is still technically sound for search, using SC's internal tooling, and turn every defect into a tracked fix. It covers indexability, robots, sitemap, titles and meta descriptions, schema, SEO plugin configuration, Search Console health and page performance.
  • When:
  • Who: Operator: anyone with read access to the tools in Prerequisites (SC staff, a contractor, or an AI agent). Approver for the resulting fixes: the SC account owner for the client.
  • Time Required: 30 to 60 minutes per site for the monthly pass; 60 to 90 minutes for a baseline that needs a new expectation record.

What replaced what. SearchAtlas OTTO used to monitor sites and auto-apply some fixes. It lapsed on 2026-08-21. Nothing auto-fixes now: this audit finds the drift, and an operator fixes it through Rank Math. Read-only throughout. No step in this SOP writes to a site.

Prerequisites​

AccessWhy
SC Client Dashboard (Google Sheet) and the client's Drive folder confidential-internal/seo-audits/Results of the symphony-flow sitemap audit
Google Search Console: Full user or Owner on the client's Domain property (setup@), per the GSC setup SOPIndexing, sitemap, Core Web Vitals and manual-action reports; URL Inspection live test
SSH / WP-CLI read access to the site, per the SSH and WP-CLI access SOP, plus a checkout of sc-wordpress-localaudit-seo.sh, the stored-state conformance check. Optional: step 3 has a browser fallback
WordPress admin (read)Browser fallback in step 3
A PageSpeed Insights API key configured for sc-wordpress-localmeasure-site.sh in step 5

Upstream: the site runs Rank Math configured to the Rank Math Configuration Standard (WordPress), or is a GHL-native site (steps 3 and 6 then do not apply). A site still carrying SearchAtlas / MetaSync is not audited against this SOP: it goes to the migration SOP first.

Evidence rule. Never report a presence or absence finding (title, meta, canonical, schema, noindex, a page element) from WebFetch or any LLM-summarised fetch. Use raw HTML (curl), the tools below, or a screenshot. For JavaScript-rendered pages such as GHL funnels, raw HTML is not enough either: confirm with GSC URL Inspection > Test live URL. See the webfetch-unreliable-for-seo rule.

Procedure​

1. Read the sitemap audit (all sites)​

symphony-flow audits every eligible client's sitemap daily at 03:00 UTC. It checks reachability and indexability, and per URL it checks titles, meta descriptions, truncated bodies and sitemap composition. Read its result before running anything else.

  1. Open the client's row in the SC Client Dashboard: Sitemap Status and the defect columns.
  2. Open the latest confidential-internal/seo-audits/YYYY-MM-DD-sitemap-audit.md in the client's Drive folder.
  3. Group findings by signal, not by URL. For example, 57 missing meta descriptions on one site is usually one template gap, not 57 problems.
  4. A client with no row is not necessarily healthy. The sweep only covers registry clients that have a website_testing.primary_url and pass the feature's active check (website_testing.active, falling back to the client's active flag). If the site is missing, note it as a finding ("not in the sitemap sweep") and continue.

How to read each status and failure reason, and how to trigger an on-demand run: symphony-flow docs/operations/sitemap-audit-runbook.md §2 and §3.

2. Check Search Console (all sites)​

In the client's Domain property:

ReportLook for
Indexing > PagesRising Not indexed counts; Excluded by 'noindex' tag on a page that should rank; Crawled - currently not indexed on key pages; Duplicate, Google chose different canonical
Indexing > SitemapsExactly one sitemap submitted (/sitemap_index.xml on WordPress), status Success. Remove stale entries
Experience > Core Web VitalsAny URL group rated Poor on mobile
Security & Manual actionsAnything at all is a P1

For each key page that is a GHL funnel route or otherwise JavaScript-rendered, run URL Inspection > Test live URL and confirm Indexing allowed: Yes.

3. Check stored configuration (WordPress sites)​

The dashboard shows stored settings and a crawl shows served output. Some failures show only when the two are compared; the worst is a block-all robots value stored in Rank Math but masked by a physical robots.txt. audit-seo.sh compares them.

  1. Expectation record. Find profiles/seo-expected/<slug>.json in sc-wordpress-local. If it does not exist, create it from symphonycore.json and commit it through a pull request in that repository. The script refuses to run without a record by design. symphonycore.json carries values that are true of SC's site only, so reset these for every new record:

    FieldSet to
    slug, siteurlThis client's slug and live URL
    standard.sourceKeep: the Rank Math Configuration Standard
    modules.onThe modules the standard's module table marks On. Check image-seo explicitly: the standard marks Image SEO On, but SC's record omits it, so a straight copy fails SEO-008 on a site built to the standard
    updatePolicy.pinnedVersions, updatePolicy.excludedFromAutoUpdateEmpty, unless this site has its own recorded pin. SC's Elementor pins would raise false SEO-010 / SEO-011 divergences
    pages.outOfScopeThis site's own funnel routes or other non-WordPress pages, or empty. SC's /pricing/ and /platform/ do not apply

    Change nothing else unless the site has an approved exception recorded in its client folder.

  2. Run it from the sc-wordpress-local checkout:

    ./scripts/audit-seo.sh <user@host:/wp/path> --profile <slug>

    Exit 0 conforms, 1 diverges, 2 nothing diverged but something could not be verified, 3 usage error. Keep the table output for the record in step 7.

  3. What it checks (SEO-001 to SEO-016): robots from all three sources, stored and served agreeing, and the served policy (001-003); the expected sitemap served and no retired sitemap still answering (004-005); required plugins active and no prohibited or retired plugin, including MetaSync and Auctollo (006-007); the Rank Math module set and licence (008-009); update policy and pinned versions (010-011); Analytics and Search Console connected (012); a single GA4 ID in page source (013); fresh page evidence, titles and descriptions present, and one organisation entity per page (014-016).

  4. No SSH access: browser fallback. Check by hand, and record the result as partial: stored state unverified:

    • Rank Math > Dashboard > Modules matches the standard's module table.
    • Rank Math > General Settings > Edit robots.txt shows allow-all and is not locked by a physical file.
    • Plugins screen: Rank Math SEO and PRO active; no MetaSync, Auctollo, Yoast, AIOSEO or SEOPress.
    • Rank Math > General Settings > Analytics shows no red status after Test Connections.

4. Check what is served (all sites)​

Run against the live domain, adding a unique query string to bypass the edge cache:

curl -sI "https://<domain>/robots.txt?cb=<unique>"
curl -s "https://<domain>/robots.txt?cb=<unique>"
curl -sI "https://<domain>/sitemap_index.xml?cb=<unique>"
curl -s "https://<domain>/sitemap_index.xml?cb=<unique>" | grep -oE '<loc>[^<]+'
CheckPass
robots.txt200; no Disallow: /; exactly one Sitemap: line, pointing at the sitemap that actually serves
Sitemap200, XML; children are content sitemaps only (post-, page-, a service CPT). No wp-sitemap-*, no tag, author or date archives, no builder post types (Rank Math standard, Archives and Builder post types rows)
/sitemap.xml301 to /sitemap_index.xml
Rich Results Test on the homepage, one service page and one postExactly one Organization or LocalBusiness; no errors; no FAQPage
curl -s https://<domain>/ | grep -ciE 'metasync|searchatlas|name="otto"'0

Any sitemap failure: Appendix A.

5. Measure performance (key pages)​

Measure the homepage and the top two landing pages from sc-wordpress-local:

./scripts/measure-site.sh https://<domain>/ --runs 3 --label <YYYY-MM>-audit

Exit 0 is trustworthy. Exit 1 is a usage error or a missing PageSpeed Insights key. Exit 2 means the measurement itself was unreliable (the runs spread too widely, too few distinct analyses came back, or none succeeded), so do not report it as a finding; see docs/runbooks/measuring-a-site-honestly.md in that repository. Treat a mobile score more than 10 points below the previous audit's as a finding.

6. Spot-check on-page metadata (WordPress sites)​

On the five most important pages and the three most recent posts, view source:

  • <title> present, 60 characters or fewer, matching the Custom titles rule (pages end in the brand; posts do not).
  • Exactly one meta description, 150 to 160 characters.
  • Exactly one <h1>.
  • Canonical pointing at the page's own URL.

7. Triage and record​

  1. Classify each finding:

    SeverityExamplesResponse
    P1Block-all robots served or stored; key pages noindex; sitemap down; manual action; MetaSync still active; site serving blank 200sTicket today; tell the account owner
    P2Signal-wide gaps (missing meta across a template), duplicate entity schema, retired sitemap still answering, Search Console disconnected, Core Web Vitals PoorTicket this week
    P3Individual titles over length, a stale GSC sitemap entry, a single 404 in the sitemapBatch into the next monthly fix ticket
  2. Ticket per signal, not per URL, in the client's ClickUp list, tagged domain:seo. Search the list first (search-before-creating-tickets); an open ticket for the same signal gets a comment, not a sibling. Each ticket names the evidence (the audit table, the Drive report path, a Rich Results screenshot) and carries an Evidence: acceptance bullet.

  3. Record the audit as YYYY-MM-DD-technical-seo-audit.md in the client's Drive confidential-internal/seo-audits/, beside the sitemap reports. Include: date, operator role, which steps ran (mark any that ran only as browser fallback), the audit-seo.sh exit code and table, the findings table with severity, and the ticket links.

  4. Fixes are made through Rank Math or the site build, following the owning SOP: the Rank Math Client Site Configuration SOP for configuration, or Make a GHL Funnel Page Indexable on WordPress for funnel routes. Changes to a live site follow that SOP's change-table approval.

Verification​

  • An audit record exists in confidential-internal/seo-audits/ for this month, naming every step as run, fallback or not applicable.
  • Every P1 and P2 finding links to a ClickUp ticket; no finding was raised from a WebFetch result.
  • If audit-seo.sh ran: the exit code is recorded, and a 2 names what could not be verified.
  • The next scheduled audit is the first week of next month.

Appendix A: Sitemap failures​

SymptomCauseFix
/sitemap_index.xml 404Rank Math Sitemap module off, or permalinks not flushed after a promotionRank Math > Dashboard > Modules: Sitemap on; Settings > Permalinks > Save; purge the edge cache; re-check
Children named wp-sitemap-*WordPress core is serving the sitemap because Rank Math's module is off. It publishes author archives and internal post typesTurn Rank Math's Sitemap module on
A second sitemap answers at /sitemap.xml with its own content (not a 301)A retired plugin (Auctollo, MetaSync) still activeDeactivate it; audit-seo.sh SEO-005 / SEO-007 confirm. A MetaSync site goes to the migration SOP
x-metasync-* headers or an otto meta tag in the responseSearchAtlas still installedMigration SOP; do not tune the old plugin
Sitemap lists tag, author, date or builder URLsArchive or post-type rows not appliedRank Math Titles & Meta and Sitemap Settings, per the standard's Archives and Builder post types rows
robots.txt Sitemap: line points at a 404A physical robots.txt left over from a previous pluginDo not delete the file first: check Rank Math's stored robots value is safe, then remove the file, per the migration SOP Phase 3 step 8 and Phase 4 step 7
A new post is missing from the sitemapRank Math's sitemap cache ignores WP-CLI writesRe-save the post in wp-admin, or clear the sitemap cache per the Rank Math Configuration Standard publishing row
A funnel route (/pricing/) is not in the sitemapExpected: funnel routes are not WordPress pages (D6)GSC URL Inspection > Request Indexing, per the funnel SEO SOP
Sitemap audit reports a non-HTML file (e.g. .kml) with no title or descriptionKnown false positiveCheck the URL, then ignore

Revision History​

DateVersionChange
2026-10-310.1Created to replace the monitoring SearchAtlas OTTO provided and the archived SearchAtlas sitemap troubleshooting and indexation control SOPs. Built on SC's internal tooling only (the symphony-flow sitemap sweep, audit-seo.sh, measure-site.sh) plus Search Console and Google's Rich Results Test. Draft until it has been run on a client site