SEO during a code freeze or replatform: what to keep moving (2026)

SEO during a replatform should keep moving wherever changes are permitted, while protecting the pages already bringing customers. A code freeze stops specified production changes, but it needn't stop content research, approved CMS edits, internal linking or preparation for the new site. Keep measuring throughout. The crucial detail: every live improvement must survive the migration, rather than disappear when an older content export replaces it.

I'm Brenden House, founder of Searchmaxxed, where we do SEO and AI SEO, including the technical fixes, content and measurement a rebuild needs. For marketing leaders facing a long rebuild, the question is practical. What can improve now without making launch harder?

In summary

• Confirm what's frozen. Application code, CMS content, redirects and tag-manager releases can have different restrictions.
• Keep approved content improvements moving, with a named owner carrying each change into the replacement site.
• Prepare redirects and test new templates before launch week. Preserve useful URLs wherever possible.
• Treat Google Tag Manager as a production change, not a secret route around engineering.
• Separate search performance from tracking faults. A missing enquiry event can look like a missing customer.

What does an SEO code freeze actually stop?

An SEO code freeze restricts changes to the live website; its boundaries depend on the organisation's release policy. Get those boundaries in writing.

A code freeze might lock application deployments while leaving editorial fields open, whereas a content freeze stops the publishing or editing of content. A replatform changes the system serving the website, such as its CMS or front end, and can involve either restriction.

They're different constraints.

Ask the engineering lead which systems are frozen, who can approve exceptions, and when the restrictions will be reviewed. Include the CMS and tag manager, plus the CDN, redirect configuration and third-party integrations, because those can affect production without touching the main repository.

For Searchmaxxed's technical SEO work, this determines which crawl, rendering and indexing fixes can ship now. Other fixes must wait.

Your release policy controls the answer; this table helps you discuss its boundaries with engineering rather than providing permission to publish around them.

Should SEO continue during a months-long website rebuild?

Yes. SEO during a website rebuild should protect current acquisition and prepare improvements that the new platform can actually deliver. Waiting for launch leaves both jobs unfinished.

The useful distinction is between work that survives the rebuild and work you'll immediately throw away. Rewrite a valuable integration page if its content will transfer. Avoid rebuilding a temporary component solely to remove it at launch, unless the current fault warrants the effort.

Consider a hypothetical B2B SaaS company moving its marketing site to a headless CMS. Demo requests still arrive through its integration pages, and although engineering has frozen templates during the rebuild, the team still permits approved editorial changes.

The integration page can answer a missing compatibility question now, while the new interactive comparison component waits for the engineering team to finish its work. Both belong in the new site's plan, but only one requires a production code deployment.

That distinction matters commercially.

Searchmaxxed combines page production with technical implementation, so the content decision and the template requirement can sit in the same scope. An article backlog alone won't resolve a broken demo form.

If everything is frozen, change the deliverable. Research and approved drafts are useful preparation, alongside redirect decisions and tested templates, but none should be reported as improvements already helping the live website.

Which content and internal-link changes are worth shipping now?

Prioritise permitted edits to pages already serving commercially useful searches, especially where an answer is missing or an important link is broken. Preserve what works.

Use Search Console to find the queries behind those pages, then compare the page with current search results and the buying question behind them. A manufacturing specification page needs different detail from a SaaS integration page, even when both attract substantial impressions.

For the SaaS example, explain supported workflows, implementation requirements and relevant limitations on the integration page, then link from documentation already discussing those workflows.

No new template required.

A practical order for approved editorial work:

1. Correct inaccurate product or service information that affects a buying decision.
2. Repair broken contextual links and connect relevant articles to the commercial page they support.
3. Answer a missing question with a useful table, example or explanation inside an existing component.
4. Improve a title or description where it misrepresents the page, preserving terms that already bring relevant searches.
5. Publish a genuinely missing page only after confirming its permanent URL and migration treatment.

Changing content, URLs and templates together makes later performance changes harder to diagnose, so don't turn the freeze into a mass rewrite of working pages. Google recommends changing one thing at a time during site moves.

Searchmaxxed's SEO content work covers research, page copy and internal links, with a destination needed for each deliverable in the new site's content model.

How do you stop live SEO improvements disappearing at launch?

Record every approved live edit after the migration export, then reconcile it with the new platform before cutover. Otherwise, the rebuild can restore yesterday's problems.

This is content reconciliation: checking that the new site contains the latest approved version of each page. Assign an owner who can verify that the latest title, table and internal links made it across, rather than simply marking a spreadsheet “content migrated”.

Return to the SaaS integration page, where the migration team imported the content before marketing added the compatibility table that answers the missing customer question. The answer has vanished.

Use a record like this:

Check the rendered page rather than just the import file, because even a correctly imported field can disappear through a template condition or failed component.

Searchmaxxed's delivery includes content, technical work and live verification. For this kind of rebuild, agree that verification also covers the transfer of approved changes. Scope it explicitly.

Can you implement schema through Google Tag Manager during a freeze?

Google Tag Manager can add structured data, but only if tag changes are permitted and the implementation passes testing. It isn't a bypass for a freeze.

Structured data is machine-readable markup describing the content of a page, commonly written in JSON-LD and inserted either by the platform or through JavaScript. Google's JavaScript structured-data guidance documents both GTM and custom JavaScript implementations.

Technical support isn't permission.

Before publishing an approved implementation, work through the following checks with whoever owns the existing markup, the consent settings and the replacement platform:

• The markup describes content users can actually read on that URL.
• Existing CMS or template markup won't conflict with the new tag.
• Page-specific triggers prevent the same claims appearing across unrelated pages.
• The tag works on direct entry and client-side navigation, without relying on a visitor clicking a button.
• Consent controls remain intact, and the implementation doesn't require bypassing them.
• Google's Rich Results Test can fetch the live URL and inspect its rendered output.
• The new platform has an owner for replacing or removing the temporary implementation.

Google recommends extracting values from the page rather than maintaining duplicate facts inside GTM. That reduces mismatches when editors update the visible content.

Don't use tag manager to pretend you've fixed server behaviour. It cannot turn a server error into a correct HTTP response or replace a server-side redirect.

There's another limit. Google says JavaScript may not remove an initial noindex effectively because Google can skip rendering after seeing that directive. Fix the source through engineering.

Our schema work sits alongside crawl and rendering checks. If the temporary tag introduces another dependency that nobody will own at launch, prepare the template fix instead.

Can links and AI-search work continue while the platform is frozen?

Yes, where that work doesn't require prohibited site changes. Keep external link destinations stable while researching the questions that Google and AI tools answer, so the work supports pages that will survive the rebuild.

For the SaaS company, an existing integration guide could support relevant editorial coverage, whereas a new report is no use with its landing page unpublished.

Check the destination first.

Link building and digital PR can form part of Searchmaxxed's plans. During a rebuild, the URL map should inform that work, so new coverage doesn't point at pages scheduled for removal.

AI SEO, GEO and AEO also depend on accessible, useful pages. Google's AI features guidance says existing SEO fundamentals still apply, with no additional technical requirements for AI Overviews or AI Mode.

Keep improving the answers where publishing is allowed, or prepare them with evidence and specialist review for the new site when publishing is blocked. The answer must exist first.

What should the new site's developers receive before launch?

Give developers testable SEO requirements while templates and routing are still being built, rather than waiting until a late audit reveals what was missed.

Searchmaxxed's technical scope includes rendering, canonicals, redirects, XML sitemaps and site structure; for a rebuild, translate each requirement into something the team can inspect.

Keep useful URLs intact. For necessary moves, prepare server-side permanent redirects to the most relevant replacement, not a blanket homepage redirect.

Google's site-move guidance recommends server-side 301 or 308 redirects pointing directly to final destinations, and advises keeping those redirects for at least a year.

Keep staging access-controlled. Prepare the production robots rules separately, so a development restriction doesn't become a launch setting by accident.

This article covers the work before cutover. Our site migration SEO checklist covers the full inventory, redirect testing, launch checks and recovery decisions.

How do you preserve measurement during a replatform?

Keep comparable search and conversion measurements before, during and after the rebuild, testing the events themselves rather than simply checking whether the analytics tag loads.

An apparently tidy migration can mislead a marketing team when search traffic holds steady but the new form stops recording completed enquiries in analytics.

Our October 2026 measurement review found this:

A client's four enquiry types never counted as conversions. Their event names ran 41 to 50 characters; GA4 cuts at 40. The 40-character "career" event counted every time. Nobody had noticed, because the events still showed up.

That finding wasn't a migration result; it shows why you should test the measurement you're carrying across rather than assume the old implementation was correct.

Searchmaxxed includes Search Console and GA4 setup and checks in its managed work. For a rebuild, agree these continuity checks:

• Preserve the existing GA4 property and event meanings unless there's a documented reason to change them.
• Test completed enquiries, not only button clicks, and reconcile test submissions with the receiving CRM or form system.
• Check duplicate page views, consent behaviour, referral handling and any cross-domain booking flow.
• Preserve Search Console verification and record which URL groups are changing.
• Record releases, tracking changes and content migrations alongside performance reports.

Compare like with like. Separate brand from non-brand searches, Australia from the US, and important page families from the sitewide total.

If integration-page clicks hold steady but recorded demos disappear, inspect forms and analytics before rewriting the content. If clicks also drop, examine indexing and the affected URLs.

Is Searchmaxxed right for your rebuild?

Searchmaxxed fits teams that want technical SEO, content and AI-search work connected to implementation, with clear permission to ship the agreed changes. The operating constraints matter.

Our Growth System covers ongoing pages, technical work, schema and internal links. Agentic Search Engineering adds comparison, industry and integration page families alongside deeper digital PR and AI-answer tracking.

Custom & Enterprise can include multiple markets, dedicated engineering, custom reporting and first-party research. That is the relevant conversation when procurement, security or a separate platform team controls releases.

You retain ownership of the site, repository, content and data, and speak directly with the people doing the work, without an account-manager relay.

If nobody can publish and the launch date keeps slipping, agree a bounded preparation scope first, because a total production lock changes the fit. Don't describe unshipped drafts as live growth.

We also won't replace your release policy with a tag-manager workaround. The engagement needs engineering access, content owners and an agreed route from a tested change to production.

Frequently asked questions

What should you do next?

Bring the freeze policy, proposed launch date and current website, so we can scope what can ship now and what belongs in the rebuild.

Let's talk pricing.