WordPress SEO Plugin Migration: SearchAtlas to Rank Math SOP
Overview
- What: Remove SearchAtlas (the MetaSync / OTTO plugin) from a WordPress site, install Rank Math PRO under SC's Business licence, and set it up from the client's details.
- Why: SearchAtlas lapsed on 2026-08-21. MetaSync no longer generates titles and carries open security issues.
- Who:
- Ticket owner: prepares the ticket (Prerequisites).
- Operator: does Phases 1 to 4 in the browser, with WordPress admin access.
- Approver: the SC account owner for the client; signs off before publish.
- Tester: checks the live site in the browser (Phase 5).
- Where: every change is made on a staging copy. It reaches the live site only through the host's publish (push to live), after the approver signs off. Nothing is done twice.
- Time: 2 to 4 hours per site.
What Rank Math should end up looking like (modules, schema, sitemap, robots, analytics) is set in the Rank Math Configuration Standard. This SOP gets a site there.
<staging> is the staging site's address and <domain> is the live site's. Evidence (screenshots, files, notes) goes in the site's ClickUp ticket; working files go in the client's Drive folder under work-in-progress/YYYY-MM/.
STOP and ask the approver
Do not work around these:
- A value is missing. Rank Math needs a value that is not on the ticket's field sheet. Never type one from memory or from the old SearchAtlas settings.
- The site breaks. A page shows a white screen, an error, or loads nearly empty. See the WordPress WSOD Recovery Runbook.
- The live site would be blocked from Google. The live
robots.txthas a line reading exactlyDisallow: /, or a live page is set tonoindex. Narrower lines such asDisallow: /wp-admin/are fine. Staging's own block (Phase 1 step 1) is expected, but it must never reach the live site.
Prerequisites
The ticket owner has these in place before assigning the ticket:
- A staging copy cloned from the live site on the day work starts (host panel, one-click staging). Its address is in the ticket
- A content freeze on the live site, agreed with the client, from the clone until publish. Publish overwrites the live database, so a post or form entry made there in between is lost
- A field sheet in the ticket: every Appendix A value, copied from the client profile, or marked "deferred" where the profile defers it
- The operator has WordPress admin on staging, the host panel (backup, file manager, publish) and the Rank Math account login (1Password, per the configuration standard)
- Someone with access to the client's Google Search Console and GA4 is available for the analytics connection
Procedure
Phase 1: Check staging and record the live site
-
Hide staging from search engines. On staging, Settings > Reading: tick Discourage search engines from indexing this site. Phase 4 turns it off again on the live site.
-
Plugins. On staging's Plugins page, note the SEO plugins:
- MetaSync → do every step.
- Rank Math already installed → do every step, skipping the installs in Phase 2 steps 5 and 6. Installed is not the same as configured.
- Yoast, All in One SEO or SEOPress → STOP and ask the approver.
-
robots.txt. Open
https://<domain>/robots.txtin the browser. A line reading exactlyDisallow: /→ STOP condition 3. -
Record the live titles and descriptions. OTTO rewrites pages as they are shown, so the live page is what you migrate. Purge the cache first (host panel, and Cloudflare if used): a cached page can be days old and makes the baseline wrong. Then crawl
https://<domain>with Screaming Frog (free version). Export the address, title and meta description of every page asYYYY-MM-data-<slug>-seo-before.csvinto the Drive folder. -
MetaSync sites only:
- Note the MetaSync version.
- Copy every redirect from MetaSync's redirects screen into
YYYY-MM-data-<slug>-seo-redirects-before.csv. If there is none, write "no redirects" in the ticket. - Note whether MetaSync's settings show a connected Google service account.
-
Find leftover SearchAtlas code. Check:
- Elementor > Custom Code;
- Code Snippets (WPCode);
- the theme's header and footer settings;
- the live homepage's page source (right-click > View Page Source), searched for
otto,metasyncandsearchatlas.
List anything that mentions SearchAtlas, or that adds
noindexor schema, in the ticket. The approver decides about anything that is not SearchAtlas. -
List the conversion elements. Click through every page on the live site. List in the ticket everything a visitor acts on: booking buttons, forms, chat, phone links, embeds. The Tester checks this list after publish.
Pages on the domain that WordPress does not serve (for example CRM funnel pages) are listed in the ticket and left out of every check.
Evidence: plugin list, the two Drive files, leftover-code list, conversion-element list.
Phase 2: Swap the plugins (staging)
- Deactivate MetaSync. Do not delete it yet.
- Smoke test. On staging, open the homepage, two service pages, two posts and the contact page. Each must show its normal content. A blank, near-empty or error page → STOP condition 2.
- Remove the SearchAtlas code found in Phase 1 step 6.
- Delete MetaSync. Its leftover data is cleared later (Phase 5).
- Install Rank Math. Plugins > Add New: install and activate Rank Math SEO (free). Then upload
seo-by-rank-math-pro.zip(Rank Math account > Downloads) and activate it. - Connect the licence. Rank Math > Dashboard > Connect account with SC's login. Confirm PRO is active and the site appears in the account's Websites list. Judge the licence only here: a licence notice on the Plugins page belongs to another plugin. Note it and leave it.
- Import the SC baseline. Rank Math > Status & Tools > Import & Export > Settings: import the baseline file named in the configuration standard. Never import Redirections from another site, and skip the importers for other plugins.
- Modules and sitemap.
- Rank Math > Dashboard > Modules: match the module table, with Sitemap on.
- Open
https://<staging>/sitemap_index.xml. It should load and listpost-sitemap.xmlandpage-sitemap.xml. Names startingwp-sitemap-mean the Rank Math sitemap is not running. - Auctollo (XML Sitemap Generator) active:
- Copy its Additional Pages list into the ticket. Those pages leave the sitemap for good.
- Once Rank Math's sitemap loads, deactivate Auctollo. Do not delete it yet.
Evidence: screenshot of the Rank Math dashboard with PRO connected; the sitemap page.
Phase 3: Configure (staging)
Every value comes from the ticket's field sheet.
-
Local SEO (Rank Math > Titles & Meta > Local SEO).
- Entity type:
- LocalBusiness, using the most specific type (for example
LegalService), when the street address is public on Google Business Profile. - Organization when the address is not public.
- Person for a named professional's personal brand.
- LocalBusiness, using the most specific type (for example
- Fields: name, logo, URL, email, phone, address, opening hours and map position, from the field sheet. Leave deferred fields empty.
- Entity type:
-
Social Meta (Titles & Meta > Social Meta): Facebook page, default share image (1200 × 630), and the X handle only if the field sheet has one.
-
Homepage title and description from the field sheet. If it has none, use the
seo-beforefile and confirm with the approver. -
Page titles and descriptions:
- Rank Math > Status & Tools > Import & Export > CSV: export.
- Fill
seo_titleandseo_descriptionfrom theseo-beforefile. Leave a cell blank where the old value was just the WordPress default, so Rank Math's template applies. - Import, then open ten random posts in the editor and check the Rank Math box shows the new values.
For one page, edit it in the post editor's Rank Math box instead.
-
Redirects. Rank Math > Redirections: add the Phase 1 redirects (use its CSV import for more than ten). Turn on "Auto post redirect" for changed slugs.
-
Schema templates (Rank Math > Schema Templates):
BlogPostingon all posts. Add oneServicetemplate per service on the field sheet, shown on its service page. List the service pages in the ticket. -
One schema source.
- Run Google's Rich Results Test on the staging homepage, one service page and one post. Each must show exactly one Organization or LocalBusiness.
- A second one comes from somewhere else: the theme, an Elementor widget (FAQ, breadcrumb, business info), a snippet or another plugin. Turn it off there. If you can't → ask the approver.
-
robots.txt.
-
Rank Math > General Settings > Edit robots.txt. If the box is locked because a
robots.txtfile exists, delete that file in the host's File Manager (staging only), then reload.- If the box now shows
Disallow: /, the old configuration stored a block-all that the file was hiding. Step 2 replaces it. Never delete the live site'srobots.txtbefore publish: the same hidden block-all would go public at once.
- If the box now shows
-
Set the content to:
User-agent: *
Allow: / -
Never save
Disallow: /here. -
Open
https://<staging>/robots.txt. Pass on staging: oneSitemap:line pointing at/sitemap_index.xml, plusDisallow: /. ThatDisallow: /is WordPress's own output while Settings > Reading > Discourage search engines is ticked on staging (Phase 1 step 1), and it overrides the stored value. The stored value in the editor must still readAllow: /; that is what the live site serves after Phase 4 step 7 unticks the setting.
-
-
Analytics. Connect Google Search Console and GA4 by following steps 4 and 7 of the Rank Math Client Site Configuration SOP. Leave "Install analytics code" off, because Google Tag Manager already sends GA4.
-
Role Manager. Contractor accounts never get Rank Math settings, Redirections or Role Manager.
-
Export the settings (Status & Tools > Import & Export > Settings) as
YYYY-MM-data-rank-math-settings.jsoninto the client's Driveclient-reference/folder.
Evidence: CSV import result; Rich Results screenshots; robots.txt page.
Phase 4: Approve and publish
- Check staging. Run the Verification checklist on staging. Attach the results to the ticket.
- Approval. The approver signs off in the ticket. No sign-off, no publish.
- Confirm the freeze held. Nothing was published, edited or submitted on the live site since the clone. If something was → STOP; the approver decides.
- Back up the live site (files and database) in the host panel. Record the backup's name and time in the ticket.
- Publish staging to live with the host's publish (push to live), including the database.
- Purge the cache in the host panel (and Cloudflare, if used).
- Straight away, on the live site:
- Search engines:
- Settings > Reading: untick Discourage search engines. Publish copies staging's setting, so this is always needed.
- Open
https://<domain>/robots.txt. It must allow all and have oneSitemap:line. - If it still shows the old file, delete
robots.txtin the File Manager, purge and check again. - A
Disallow: /→ STOP condition 3.
- Pages: repeat the Phase 2 step 2 smoke test on the live site.
- Licence: Rank Math > Dashboard. If it shows disconnected, Connect account again. Remove the staging site from the Rank Math account's Websites list.
- Search engines:
- Google Search Console > Sitemaps: submit
https://<domain>/sitemap_index.xmland remove every other sitemap. - MetaSync's Google service account, if Phase 1 found one: remove it in Google Cloud > IAM.
- Hand the ticket to the Tester.
Evidence: staging results; sign-off; backup name; step 7 results.
Phase 5: Test and close
- Test. The Tester runs the Verification checklist on the live site. That includes clicking through every page and every conversion element from Phase 1 step 7. Anything missing → fix on staging and publish again. If the site is unusable, roll back.
- Close, after the test passes:
- Attach the evidence and close the ticket.
- Update the site's row in the SEO Tooling Migration Roadmap.
- Create a follow-up ticket, due in 30 days: clear MetaSync's leftover data from the database, and delete Auctollo if it was deactivated.
- Remove your own access: delete the WordPress user you used, or change its password, and delete any saved logins for the site.
- Delete the staging copy in the host panel.
Rollback:
- Before publish: nothing on the live site has changed; discard staging.
- After publish: restore the Phase 4 step 4 backup, only if the site will not load. A restore brings back the old titles and does not undo the Search Console or Google Cloud changes.
Verification
Run on staging before approval (Phase 4) and on the live site after publish (Phase 5). Rows marked live apply to the live site only.
| Check | Pass |
|---|---|
| Plugins | MetaSync gone. Rank Math and Rank Math PRO active. No other SEO plugin; Auctollo inactive |
| Licence | Rank Math dashboard shows PRO connected |
| Titles and descriptions | On the homepage, two service pages and two posts: the title and description are the migrated ones, not the bare page name. A one-page site may reuse the homepage description |
| Schema | Rich Results Test on the homepage, one service page and one post: no errors, exactly one Organization or LocalBusiness, details match the field sheet |
| Sitemap | /sitemap_index.xml loads and lists the site's pages. Live: it is the one submitted in Search Console |
| Search engines | Live: Settings > Reading is unticked, and /robots.txt allows all with one Sitemap: line |
| Conversion elements | Every page loads, and every item on the Phase 1 step 7 list is present and works |
| Analytics | Live: Search Console and GA4 connected in Rank Math, "Install analytics code" off |
Related Documents
- Rank Math Configuration Standard: target configuration
- Rank Math Client Site Configuration SOP: Google connection
- SEO Tooling Migration Roadmap
- SC WordPress Stack Standard
- WordPress WSOD Recovery Runbook
- Client Profile Template
- SC SOP Standard
Appendix A: Client profile to Rank Math field map
For the ticket owner, who copies these values into the ticket's field sheet. Each client's profile is 09-clients/<slug>/<slug>-client-profile.md. The profile is canonical. A value that is neither filled nor in the profile's Deferred SEO fields register is fixed in the profile first. The section is SEO Inputs (template 3.6+); older profiles call it SearchAtlas / SEO Inputs, with the same fields. That register is for fields that do not apply to the business, never for values not yet gathered.
| Rank Math field | Profile section › field | Rule |
|---|---|---|
| Entity type | Industry Classification › NAICS, plus whether an address is public | Rule in Phase 3 step 1 |
| Name | Location Information › Location Name | Must match Google Business Profile exactly |
| Legal name (Organization) | General Business Details › business-name | Only if different from Location Name |
| URL | General Business Details › website-url | HTTPS, no trailing path |
| Logo | Brand Design System › Logos (primary) | Square version if one exists |
| Service Configuration › Website Contact Email (older profiles: Project Management) | Public address only, never a personal inbox | |
| Phone | General Business Details › business-phone | International format, e.g. +12035551234. Must match Google Business Profile. Older profiles: Auth Rep Phone, then LC Phone if the profile says it is the published number; never contact-phone |
| Address | General Business Details › address, city, state-province-region, postal-code, country | Only if published on Google Business Profile |
| Opening hours | SEO Inputs › operating-hours-per-location | Must match Google Business Profile |
| Map position | SEO Inputs › geo-latitude / geo-longitude | Only with a public address |
| Contact type | SEO Inputs › contact-type | Default customer support |
| Social profiles | Social & Directory Profiles › every URL not N/A | One per line |
| Facebook page / X handle | Social & Directory Profiles › facebook-url, twitter-url | Only live URLs |
| Services (Service schema) | Brand Voice & Positioning › What the Brand Does | One template per service |
| Description | SEO Inputs › brand-description | Trim to 160 characters for the homepage |
| Author (posts) | SEO Inputs › author-first-name / author-last-name | An existing WordPress author. Never create a WordPress user in this SOP; if the person has none, leave it, note it, and the ticket owner raises a separate ticket for the WordPress Author User Setup SOP |
| Default share image | Brand design kit (Drive brand-assets-master/) | 1200 × 630 |
Not carried over (they fed OTTO; Rank Math has no equivalent): serps-competitors-location, act-as-who, search-intent-mix, writing-toggles, iso-6523-code. Template 3.6 removed all but search-intent-mix, which stays for content work.
Revision History
| Date | Version | Change | Author |
|---|---|---|---|
| 2026-10-31 | 0.16 | Phase 3 step 8.4 states what a pass looks like on staging (WordPress's own Disallow: / while Discourage search engines is ticked; stored value allow-all). Appendix A follows the template's renamed SEO Inputs section. Related links repointed after the SearchAtlas docs were archived | Symphony Core Systems Team |
| 2026-10-09 | 0.15 | Restored two #336 safeguards that the v0.13 browser rewrite dropped, in browser form. Phase 1 step 4 purges the cache before the baseline crawl, so a stale cached page cannot pass as the live one. Phase 3 step 8 names a Disallow: / revealed in Rank Math's robots editor as the hidden block-all, and forbids deleting the live site's robots.txt before publish. | Symphony Core Systems Team |
| 2026-10-07 | 0.14 | Appendix A author row points to the new WordPress Author Identity Setup SOP for sites whose posts need a named author. | Symphony Core Systems Team |
| 2026-10-07 | 0.13 | Rewritten for a person working in the browser: every command-line step replaced by the screen that does the same job, and the agent quick reference removed. Eight phases became five, one per hand-off (record, swap, configure, publish, test). The sitemap transition became one step, since no remaining site runs Auctollo. Five STOP conditions became three; Verification went from fifteen rows to eight and is the Tester's checklist. The ticket owner now prepares the staging copy, content freeze and a field sheet from Appendix A. The pilot appendix was removed and the SOP made active, since the first client sites served as the pilot. The hosting auto-update detail moved to the Rank Math Configuration Standard. | Symphony Core Systems Team |
| 2026-10-06 | 0.12 | Lessons from the first client publish. Phase 5 step 7 now always turns search visibility back on, because publish carried staging's block to production. A conversion-element list (new Phase 1 step 8) feeds a regression click-through after publish and a new Verification row, after a homepage booking button went missing. Smoke tests require normal page content, not just a 200. The licence is judged only in Rank Math, since another plugin's activation notice caused confusion. Appendix A no longer asks for a WordPress user to be created for the author. Phase 6 adds removing the operator's own access and deleting the staging copy. A one-page site may reuse the homepage description. | Symphony Core Systems Team |
| 2026-10-06 | 0.11 | Phase 4b step 3 hands the Google connection to the new Rank Math Client Site Configuration SOP | Symphony Core Systems Team |
| 2026-10-05 | 0.10 | Staging and publish replace "repeat on production". Phases 0 to 4b change only a staging copy cloned that day; a new Phase 5 verifies staging, takes the approver's sign-off, backs up production, publishes with the host's push to live, and then fixes what the domain change can break (search visibility, Rank Math connection) and makes the external changes (GSC sitemaps, service-account revocation) that used to sit in Phases 0b and 2. Verify and close becomes Phase 6. Phase 0 now starts by hiding staging from search engines, since a public staging copy can be indexed as a duplicate. Content freeze added to Prerequisites, because publish overwrites production's database. | Symphony Core Systems Team |
| 2026-10-05 | 0.9 | Simplified: body down from 346 to 266 lines and from 5,550 to 3,670 words, with no rule dropped. Target configuration (module table, global meta, post-type schema, settled decisions, stack fit) now lives only in the Rank Math Configuration Standard, which Phase 4 reads back against. robots.txt neutralisation consolidated in Phase 0 step 4; sitemap and GSC submission in Phase 0b step 4. One agent-safe WP-CLI form per command. Pilot-only steps and open pilot checks moved to Appendix B. Fixed stale step references in Phase 5 and the rollback, and the Phase 0b skip rule, which relied on a check Phase 0 did not make. | Symphony Core Systems Team |
| 2026-10-05 | 0.8 | Phase 0b split into a short path and an Auctollo path, since no site remaining in the queue carries Auctollo. Phase 4 now starts from the exported SC baseline rather than eleven repeated decisions. Sitemap verification distinguishes Rank Math's children from WordPress core's wp-sitemap-* fallback, after a site was left on the core fallback with the module off. | Symphony Core Systems Team |
| 2026-09-30 | 0.7 | Sitemap ownership reversed: Rank Math owns the sitemap, Auctollo retired (decision D6). Phase 1 step 8, Phase 4 steps 9 and 11, the Verification plugins row and the Phase 5 clean-up (which now deletes the deactivated Auctollo plugin) follow the reversal. Phase 0b now moves a site off Auctollo and onto Rank Math's Sitemap module, in an order that never leaves the site without a sitemap - the previous direction had a brief gap. Added an explicit warning that Auctollo's Additional Pages URLs (GHL funnel routes such as /pricing/) leave the sitemap permanently, because Rank Math has no equivalent feature, and must be recorded in the out-of-scope register before deactivation. Settled decisions, Phase 1 step 3, the Phase 4 module table and the Verification sitemap and robots rows all follow. | Symphony Core Systems Team |
| 2026-09-30 | 0.6 | Tier 1 item 3 of issue #336. STOP condition 1 and the Prerequisites accept a field listed in the client profile's Deferred SEO fields register (template v3.5), so a field that does not apply to the business is recorded rather than escalated. The Appendix A phone row points to the new business-phone field. SC's own profile now supplies every Appendix A value or defers it | Symphony Core Systems Team |
| 2026-09-30 | 0.5 | Tiers 2 and 3 of issue #336. Phase 3 step 4 states that GHL's rocket-autoupdate must-use plugin forces auto-update on every plugin and suppresses the emails, so the WordPress toggle is inert; the step now records the host setting and the residual risk of an unannounced Rank Math update. Phase 1 step 6 enumerates Elementor Custom Code and WPCode with WP-CLI and looks for snippets that strip noindex. Added the edge-cache rule (unique query string, record cf-cache-status / Age, purge before baseline and Verification) and an out-of-scope URL register. Phase 4 step 8 detects a second schema emitter instead of naming one theme. Module table: catch-all Off rule, read-back command, confirmed slugs, and the modules it omitted. Rollback states what a restore does not undo. Appendix A email and phone rows corrected; agent-safe alternatives to wp db query in Phase 0 step 3 and Phase 1 steps 4 and 5. Closed two pilot checks: the pilot site runs MetaSync 2.7.0, above the 2.6.24 CVE threshold (no SOP change), and the redirect table name is confirmed from MetaSync's source, which also defines metasync_robots_txt_backups (covered by the Phase 5 metasync_* clean-up) | Symphony Core Systems Team |
| 2026-09-30 | 0.4 | Tier 1 of issue #336 (pilot blockers). Added Phase 0b, a sitemap transition that moves a site onto Auctollo before Phase 1 captures from it, ordered so the site is never left without a verified sitemap for more than a few seconds and every step reverts with one toggle; the pilot site ran Rank Math's sitemap with Auctollo inactive. A block-all in Rank Math's stored robots value is now STOP condition 3 even when a physical robots.txt hides it (previously it was carried to Phase 4 step 9, leaving it armed through Phases 1 to 3); Phase 4 step 9 still does the fix. Dropped price range from Phase 4 step 2: it has no Appendix A row, no client profile field and no canonical source, it is optional in schema, and requiring it would stop every site at STOP condition 1 | Symphony Core Systems Team |
| 2026-09-29 | 0.3 | Moved into the repo and brought to the SOP standard. Resolved the open items from research: Business license, Auctollo keeps the sitemap, CSV import replaces REST meta writes, known MetaSync keys and redirect table, GA4 tag off, entity-type rule, BlogPosting. Added Phase 0 state detection, the agent quick reference with STOP conditions, and an Appendix A mapped to the client profile template | Symphony Core Systems Team |
| 2026-09-29 | 0.2 | PRO features made explicit (Phase 4b) | Symphony Core Systems Team |
| 2026-09-29 | 0.1 | Skeleton | Symphony Core Systems Team |