Website Redesign SEO Migration for Small Business: Softix Inventory–Redirect–Monitor

Published (planned): September 11, 2026 · Last updated: September 11, 2026 · Author: Softix
Category: web design and development

A redesign that looks better in the browser can still erase years of organic traffic if URLs change without a plan. Softix’s website redesign SEO migration checklist for U.S. small businesses is not a 200-row agency spreadsheet. It is Inventory–Redirect–Monitor: inventory every URL that earns impressions, build a 1:1 permanent redirect map, launch with staging hygiene and preserved titles/H1s on ranking pages, then monitor Search Console for 30–90 days.

Facts below come primarily from Google Search Central’s Site Moves and Migrations documentation (last updated August 20, 2026 in Softix’s fetch) and Google’s Change of Address guidance. Softix’s sequencing and SMB launch QA are analysis—not a Google ranking guarantee. Softix sells web app development, mobile application development, and broader services; this post is how we protect organic demand when we redesign or replatform.

When this framework applies

Google’s site-move guide covers URL changes such as HTTP→HTTPS, domain changes, merging hostnames, and path changes (for example, query-string URLs to clean paths, or .html to extensionless URLs). Softix Inventory–Redirect–Monitor is for those moves and same-domain redesigns that still rewrite slugs, drop service pages, or change CMS permalinks.

Fact (Google). Google advises: know what to expect; prepare and test the new site thoroughly; prepare a URL mapping; start the move with server redirects; monitor traffic on old and new URLs. Google also recommends changing one major thing at a time when possible (for example, do not simultaneously move domains, change CMS, and rewrite the entire information architecture unless you must), timing moves for lower traffic when feasible, and expecting temporary ranking fluctuation while Google recrawls and reindexes.

Softix analysis. SMBs often redesign and replatform in one project because budget only opens once. If you must combine changes, Softix’s Inventory step becomes non-negotiable: you need a complete old→new map before launch night, not a “we’ll fix 404s later” hope.

Softix Inventory–Redirect–Monitor at a glance

Pair launch QA with Softix’s parallel posts on Core Web Vitals for small business websites and WCAG 2.2 AA Audit–Fix–Prove—performance and accessibility are launch gates, not “phase two.”

Step 1 — Inventory: sitemap + GSC + analytics, not vibes

Fact (Google — determine old URLs). Google suggests starting with important URLs from sitemaps submitted in Search Console, server logs or analytics for high-traffic URLs, Links to your site in Search Console, CMS URL listings, and recently visited URLs in logs. Include images, videos, JavaScript, and CSS URLs that earn search or link traffic.

Softix Inventory sources (analysis)

1. XML sitemaps (current production).
2. Google Search Console — pages with impressions/clicks over a representative window (Softix prefers 90 days when seasonality matters).
3. Analytics landing pages — organic and direct.
4. CMS export / crawl — full path list including pagination, tag, and filter URLs you may choose to noindex or 404 intentionally.
5. Backlink / “Links to your site” — high-value inbound URLs that must not soft-404 to the homepage.

For each row capture: old URL, traffic/impressions note (your numbers—Softix invents none), proposed new URL, disposition (1:1 redirect / consolidate / intentional 404 or 410), title, H1, primary intent, and owner.

Softix judgment. Inventory is a product decision as much as an SEO task. Killing a ranking service page because the new design “doesn’t have room” is a revenue decision—record it.

Step 2 — Redirect: 1:1 permanent map and staging hygiene

Fact (Google — redirects). Google recommends server-side permanent redirects from old URLs to new URLs as indicated in your mapping. Prefer HTTP permanent redirects such as 301 and 308. Avoid long redirect chains; Googlebot can follow up to 10 hops, but Google advises redirecting to the final destination directly and keeping chains ideally to no more than 3 and fewer than 5. Google states that 301 and other permanent redirects do not cause a loss in PageRank.

Fact (Google — irrelevant redirects). Do not redirect many old URLs to one irrelevant single destination such as the homepage; that can confuse users and might be treated as a soft 404. Consolidation to a new single relevant page is acceptable when content truly merged.

Fact (Google — prepare new site). Set up robots.txt correctly for what should remain blocked after launch. If you used noindex during development, prepare the list of URLs from which you will remove noindex at cutover. Provide proper 404/410 for deleted content. Verify old and new properties (and variants) in Search Console. Ensure server capacity for temporarily heavier crawling after migration.

Softix Redirect launch packet (analysis)

• 1:1 map for every Inventory keep/merge row; no wildcard-to-homepage shortcuts for money pages.
• Staging noindex (and/or auth) until cutover; then remove blocks the same hour redirects go live.
• Self-referencing canonicals on new URLs; update hreflang if you use it.
• Preserve titles and H1s on pages that already rank for commercial queries unless you have a measured reason to rewrite—Softix analysis, not a Google rule.
• Update internal links to new URLs (Google asks for this explicitly) so users and crawlers are not forced through chains.
• Test redirects with Search Console URL Inspection for samples and a crawl/script for bulk checks.

Fact (Change of Address). Google’s Change of Address tool is for moves from one domain or subdomain to another after redirects are live. You do not need it for HTTP→HTTPS alone, www↔non-www on the same domain, or path-only moves on the same domain. Softix analysis: still do Inventory–Redirect–Monitor for same-domain redesigns; skip Change of Address when Google says it does not apply.

Fact (how long to keep redirects). Google’s site-move documentation advises keeping redirects as long as possible, generally at least one year, so signals can transfer and inbound links can be updated. Softix Monitor assumes at least that horizon for high-traffic paths.

Step 3 — Monitor: sitemap, indexing, 30–90 day triage

Fact (Google — after start). Once redirects are active, check canonicals and remove temporary noindex rules. Submit the new sitemap in Search Console; you can remove the old sitemap thereafter. Expect temporary visibility fluctuation. Use Index Coverage / indexing reports, Sitemaps reports, and Search queries reports to watch old URLs decline and new URLs rise. Google notes medium-sized sites can take a few weeks or more for new URLs to gradually replace old ones in results; larger sites take longer. There is no fixed crawl frequency Softix can honestly promise.

Softix Monitor cadence (analysis)

Request indexing for top commercial pages after cutover when appropriate in Search Console—Softix uses this as a discovery aid, not a ranking switch. Parallel Softix launch QA: re-run Core Web Vitals field/lab checks and WCAG remediation evidence so the new design does not trade SEO survival for inaccessible or sluggish templates.

Common SMB failure modes Softix sees

• Staging noindex left on production — Google’s troubleshooting table explicitly calls out forgotten noindex/robots blocks.
• Incorrect redirects — mapping to non-existent new URLs; Softix Inventory prevents this only if QA crawl happens before DNS cutover.
• Insufficient server capacity — Google warns of heavier crawl after migration.
• Sitemap not updated — new URLs never submitted.
• Design-driven slug chaos — pretty URLs shipped without a map.

30-day Inventory–Redirect–Monitor plan

Extend Monitor through day 90 for commercial sites. Softix custom software and redesign engagements treat the redirect map as a deliverable equal to the Figma file.

Limits and honesty checks

• No ranking guarantees. Google describes temporary fluctuation; Softix cannot promise recovery timelines or traffic percentages.
• No invented volumes. Use your Search Console and analytics numbers—Softix will not fabricate keyword volumes or “average SMB traffic loss” stats.
• Change of Address is situational. Domain/subdomain moves only, after redirects.
• Not legal advice. Accessibility obligations (see Softix WCAG post) may be regulatory, not optional QA.

FAQ

Do we need Change of Address for a same-domain WordPress redesign?

Usually no. Google says the tool is for domain or subdomain changes, not path-only moves on the same domain. You still need Inventory–Redirect–Monitor if URLs change.

Are 301s enough if we change titles and H1s on every page?

Redirects preserve URL relationship; Softix still recommends preserving proven titles/H1s on ranking commercial pages unless you have a measured rewrite plan. Treat copy rewrites as a separate experiment from the migration event when you can.

Can Softix redesign without an SEO migration plan?

We will not recommend it. If Softix builds your new site, Inventory–Redirect–Monitor is part of delivery—alongside Core Web Vitals and WCAG launch gates.

Next step

If you are replatforming or redesigning and want Softix to own Inventory–Redirect–Monitor end to end—including web and mobile delivery—talk to Softix. Bring Search Console access and your current sitemap; we will not launch on vibes.