Where Do Your SEO Changes Live? CMS, Script, Edge

Every SEO tool that changes your site has to put the change somewhere. There are three places it can go: into your CMS, into a JavaScript layer that rewrites the page in the visitor's browser, or into the CDN that sits between your server and everyone who requests a page.

Most buyers never ask which one a tool uses. It decides what crawlers see, how you undo a change, and what is left on your site the day you stop paying.

This guide explains each approach and what it means for crawlers, cancelling, undo, speed, multi-CMS support and lock-in. Disclosure: we make RankHive, which writes changes into WordPress. We've tried to describe the other two approaches fairly, including where they're the better choice.

Details about other tools come from their own websites and help pages as published in October 2026, linked where we cite them. Plans and features change, so check with the vendor before you decide.

The short version

1. Written into the CMS

The tool connects to your CMS with write access, usually through a plugin, and saves each change where you would have saved it yourself. On WordPress that means the post body, the title and description fields of your SEO plugin, and the alt text field in the media library. Site-level changes such as redirects or robots.txt rules are stored wherever the tool or your SEO plugin keeps them.

Crawlers. The change is in the HTML your server sends. Googlebot sees it on the first fetch, and so does every crawler that never runs JavaScript, including many AI crawlers and most link-preview bots.

Cancelling. A change written into your database is your data. Cancel the tool and the title is still in your SEO plugin and the new paragraph is still in the post. One caveat: if the tool's own plugin prints something at runtime, such as schema it stores or redirects it keeps in its own table, that works only while the plugin stays installed and active. Ask the vendor which changes those are.

Undo. Harder than with a script, because the old value is overwritten. WordPress keeps revisions of post content, but not of your SEO plugin's fields or of alt text. Before you give a tool write access, check that it records each change's before and after and can put the old value back.

Speed. Nothing extra loads in the browser: the change is part of the page. If you run a page cache, the change appears when the cache refreshes.

Multi-CMS. This is the weak spot. Each CMS needs its own integration, so tools that write into the CMS usually support one or two platforms.

Lock-in. Low for the changes themselves. They stay in your database whatever you do with the tool.

The trade-off. Write access is real power: a bad change is a real change on your live site. An approval step before each write, and a revert after it, matter more here than anywhere else.

2. A JavaScript snippet or pixel

You add one script tag to your site's template. When a page loads, the script fetches the vendor's changes for that URL and rewrites the page in the browser: the title, the meta description, schema, links, alt text. Your CMS still holds the original.

According to their own sites, Search Atlas OTTO (through the OTTO Pixel), Alli AI and SEOJuice apply changes this way.

Where it's the better choice. A script works on almost any site you can add a tag to: WordPress, Shopify, Webflow or a custom build. Nobody needs database access, there's no plugin to keep updated, one person can roll a change out across thousands of pages, and undoing it is a switch. For an agency with clients on five platforms, or a site whose CMS has no plugin system, those are real advantages.

Googlebot. Google renders JavaScript, so Googlebot can see a change a script makes, after the page goes through rendering. Google's own documentation sets some limits. If the HTML Google first receives contains noindex, it may not render the page at all, so a script can't reliably lift a noindex. A script can't send a 301 status code, and Google recommends server-side redirects, with JavaScript redirects as a fallback for when nothing else is possible. And robots.txt is a file the crawler requests on its own, so no script on a page can change it.

Crawlers that don't run JavaScript. They see the page as your server sent it, before the script ran. That includes many AI crawlers: Vercel's study of AI crawler traffic (December 2024) found that the major AI crawlers it measured didn't render JavaScript. Vendors know this. Alli AI says on its own site that AI crawlers can't run JavaScript, and it offers an AI Search Visibility Engine that pre-renders pages for them.

Cancelling. Changes made by a script exist only while the script runs and the vendor serves them. Search Atlas's OTTO Pixel page says pixel fixes stay live only while the pixel stays connected. Alli AI's Live Editor page says its changes revert when you cancel, and its help centre asks you to remove its code snippets before you cancel. To keep a change after you leave, you'd need to make it again in your CMS, so ask the vendor whether you can export what it changed.

Undo. The easiest of the three. Switch a change off and the original, which never left your CMS, is what loads again.

Speed. One more script to download and run, and the changes arrive after the page rather than in it. How much that costs depends on the implementation, so measure your Core Web Vitals before and after.

Multi-CMS. As broad as the edge, and easier to set up: it works on any site you can add a tag to.

Lock-in. High for the changes themselves, because they live in the vendor's system rather than yours.

3. The edge or CDN layer

Code runs on your CDN, for example in Cloudflare Workers, between your server and every visitor. It can rewrite the HTML as it passes through, answer a URL with a redirect, or serve a robots.txt, before any crawler or browser sees the response. A developer with access to your CDN can set this up, and some vendors offer it as a service.

Crawlers. The rewritten HTML is what every crawler receives, whether or not it runs JavaScript. Redirects are real HTTP redirects.

Cancelling. It depends on who owns the rules. If they run in a vendor's worker, they stop when the worker is removed. If they live in your own CDN account, they stay as long as you keep them, but they still aren't in your CMS.

Undo. Remove or change the rule. The CMS was never touched.

Speed. The code runs close to the visitor and adds no work in the browser. But every request passes through it, so a slow or broken rule affects the whole site at once.

Multi-CMS. Any CMS behind the CDN.

Lock-in. Moderate. Because the changes sit outside your CMS, the CMS and the live page disagree: an editor who opens the post sees the old title, and the next person to edit it may not know the edge is rewriting it. Two sources of truth is the real cost.

Where seven tools put your changes

The first five are agents that change pages for you. ThinkRank and Rank Math are WordPress SEO plugins: ThinkRank's AI drafts metadata in the editor, and in Rank Math you make each change yourself. "Not stated" means we couldn't find it in the vendor's material as of October 2026, not that the feature doesn't exist.

Sources, as of October 2026: Search Atlas's OTTO Pixel page and pricing; Alli AI's Live Editor page, help centre, FAQ, AI SEO software page and pricing; SEOJuice's docs, WordPress.org listing, internal links page, API docs, cancellation guide, stop-using FAQ and pricing; RightBlogger's Site Agent page and pricing; ThinkRank's WordPress.org listing and pricing; Rank Math's free vs PRO page.

For a scored version of this list, with a "best for" pick in each category, see the best SEO automation software for WordPress.

For one agent at a time next to RankHive, read RankHive vs OTTO SEO, RankHive vs Alli AI, RankHive vs SEOJuice or RankHive vs RightBlogger.

Many tools mix approaches

The categories aren't sealed. Search Atlas also lists a WordPress plugin, metasync, on WordPress.org, and Alli AI announced a WordPress plugin in June 2026. If your site runs WordPress, ask a script-based vendor which changes its plugin writes into WordPress and which still depend on the script.

Questions to ask before you connect any SEO tool

1. Where does each type of change live: in my CMS, in your script, or at the edge?
2. What is on my site the day after I cancel, for each type of change?
3. Can a crawler that doesn't run JavaScript see the change?
4. Who approves a change before it goes live, and is that the default or a setting?
5. How do I undo one change, and for how long can I?
6. Can I export everything you changed if I leave?

A vendor that answers all six plainly is one you can plan around, whichever approach it uses.

Which approach fits which site

Sites on several platforms, or a CMS with no plugins. A script is often the practical choice. Accept that crawlers which don't run JavaScript will miss the changes, and keep a list of what you'd need to re-make if you leave.

A developer controls the CDN. Edge rules give you real redirects and changes every crawler sees, on any CMS. Write down every rule somewhere your editors will look, so the CMS and the live page don't drift apart unnoticed.

WordPress, and you want to keep what you approve. Write into WordPress. Changes are in the HTML every crawler gets, and they stay if you cancel. Insist on an approval step and a change log, because the changes are real.

Where RankHive fits

RankHive is an SEO agent for WordPress, and it writes into WordPress. It reads your Google Search Console data (read-only), drafts fixes, and waits. Each change is written only after you approve it, through the free RankHive plugin:

• Titles and meta descriptions go into the fields of the SEO plugin you already run: Yoast SEO, Rank Math or SEOPress. All in One SEO isn't supported.
• Content edits and internal links go into the post itself, so they also appear in WordPress's revision history if your site keeps revisions.
• Image alt text goes into the media library.
• Schema, redirects and robots.txt rules are stored in WordPress and output by the RankHive plugin. They keep working after you cancel for as long as the plugin stays active. Deactivating the plugin stops them, and deleting it removes its redirects table and robots.txt rules.

If you cancel, the changes you approved stay on your site. You can revert edits from the Change Log however long ago they were made. A paragraph, link, redirect or robots.txt revert stops if that item was edited in WordPress since; a title, description or other field revert puts the old value back. New articles RankHive drafted can't be reverted from there. RankHive works on posts and pages, not WooCommerce products, and costs $49.99 a month or $499.99 a year, with no free trial.

How RankHive works walks through each step, and the approval workflow shows what you see before anything is written.