The technical change impact checklist: make site changes without losing your rankings

This is a pre-flight check for making changes to a website without harming its search rankings. It is for the owner of a site that finished an SEO engagement, who is not technical, and who now needs to change something. The reassuring truth: most catastrophic "our traffic vanished after the relaunch" stories are not Google penalties, they are avoidable mistakes: a noindex carried over from the test site, a robots.txt blocking the whole site, redirects pointing to dead pages, or URLs that changed with no redirect. Get these right and you keep what you built. The one rule that prevents most disasters: change one thing at a time.

Rule of thumb: green you can do, amber do carefully and watch, red goes through your SEO partner first.

1. Screenshot or export the current numbers from Search Console so you have a "before."
2. Write down the current URL and title.
3. Confirm you are not changing the URL; if it is changing with no planned redirect, stop and talk to your SEO partner.
4. Make sure you can undo it (a backup or a saved version).

For anything bigger than a single page, also take a full backup and make the change on a private copy first.

Send this section to whoever makes the change.

URLs changing with no redirect: every old URL must 301-redirect to the matching new one, to its true equivalent not all to the homepage, with no redirect chains; done this way 301s keep ranking power; keep redirects at least a year.

The staging noindex reaching the live site: the number one launch-day disaster, so make removing it a launch step.

robots.txt blocking the site: remove any leftover Disallow: / and never block CSS or JavaScript.

Accidental noindex from a template or plugin: check the live site after launch.

Canonicals pointing at old or test URLs: each new page should point to itself.

Lost titles, headings, and content: preserve the content, not just the address.

Stripped internal links: a new template that removes them can drop the pages they fed.

Speed regressions: compare before and after.

Deleting pages carelessly: return a proper 404 or 410 for removed pages, 301 for merged ones, and do not delete a page with backlinks without asking your SEO partner.

After a clean, simple change, expect little or no impact. After a correct redirect or migration, expect some temporary wobble while Google recrawls, often a couple of weeks to a couple of months, so do not panic-revert on day three. A botched change shows up fast: pages dropping out of the index, 404 errors in Search Console, or a sharp sitewide fall right after launch. Honest expectation: a clean change recovers in days to a few weeks; a badly handled migration can take many months, and a minority never fully recover.

Because you took a backup, a bad robots.txt, template, or setting can usually be rolled back quickly. First tell a true error (deindexed pages, 404 spikes, a sitewide drop) apart from normal post-change wobble. If you roll back, test it on the copy first where possible.

Before the change if it is anything red: a URL or domain change, HTTP to HTTPS, a redesign or platform migration, or editing robots.txt, canonicals, or noindex. Promptly after if pages drop out of the index, 404s spike, or traffic falls sharply right after launch.