Beyond Launch Day: Keep Your Website Working
0:48 · Related video
Keep the pages that work. Plan the changes that matter. A practical before, during and after playbook for protecting search visibility and customer paths—with realistic expectations.
0:48 · Related video
0:25 · Related video
0:53 · Related video

A redesign should make your website more useful without casually throwing away the paths customers and search engines already know. The danger is rarely the new color palette itself. It is the useful service page that disappears, the old link that stops working, or the staging setting that quietly prevents the new website from being indexed.
This guide helps you ask better questions before, during and after launch. “Without losing your SEO” describes the goal—not a guarantee. SEO-safe planning means reducing and managing risk; Google still decides what to crawl, index and rank.
You can change layout, navigation and page design while keeping the same domain and page addresses. You can also rebuild on another platform without changing public URLs, if the platform and agreed implementation support it. A domain move and a URL-path change are separate decisions, not inevitable consequences of making a website look better.
Keeping useful URLs and strong content is generally less disruptive than changing both at once, but it does not remove the need to test. Rendering, internal links, headings, mobile usability, performance and indexing settings can change even when the address stays the same.
If your services are explained well and the customer path works, targeted improvements may be enough. If the structure no longer reflects your business, mobile contact paths fail or the platform cannot support the agreed needs, a larger rebuild may make sense. Neither option earns a guaranteed ranking advantage.
Improve unclear copy, visual consistency, navigation labels or a contact step while retaining useful pages and addresses. Confirm that the existing platform permits the needed changes.
Replan the page hierarchy, customer journey or platform around real requirements. Inventory the old site first so the new structure does not erase valuable service information.
Use Website Redesign vs. Website Refresh and Does My Website Need a Redesign? to separate a specific business problem from a desire for a different appearance.
Ask for an export or crawl of the current public URLs. Supplement it with the existing sitemap, navigation, Search Console pages and performance reports, analytics landing-page reports and important inbound links. None is a complete inventory alone: a sitemap can omit a useful page, and a crawl can miss an unlinked URL that still receives visitors.
Keep a secure project spreadsheet with one row per URL and a named reviewer. Do not place customer records, passwords or private form submissions in that inventory.
In Search Console, export clicks, impressions, queries and average positions for meaningful periods, segmented by landing page where possible. Average position is an aggregate, not a fixed rank for every searcher. In GA4, review organic landing-page activity and relevant key events, while documenting what the events actually measure.
A button click is not necessarily a completed form; a form submission is not necessarily a qualified lead. Compare with business-owned records of calls, inquiries and bookings without exporting sensitive personal details into a public report. Note consent, tagging and reporting limitations.
Make the decision based on customer purpose and the replacement content, not on whether a page looks old. This matrix is a planning aid; the correct implementation depends on the actual page and platform.
When: The purpose and useful page remain.
Check: Retain accurate content; test status, canonical, mobile and contact paths.
When: A path changes or pages genuinely consolidate.
Check: Use a direct permanent 301/308 to the relevant replacement; test for loops and chains.
When: Content is removed with no relevant replacement.
Check: Return the correct HTTP error; remove old internal links and sitemap entries.
A low-traffic page may still help a niche customer or receive an important link. Investigate before deleting it. Conversely, keeping obsolete or misleading content solely because it once ranked is not a good customer outcome.
When a path genuinely needs to change, map its old URL directly to the relevant new equivalent. For example, an illustrative roofing business might move /roof-repair to /roofing/roof-repair. The new page should still explain roof repair—not simply show a broad homepage.
Use a server-side permanent HTTP 301 or 308 redirect where appropriate. Several old pages may point to a genuinely consolidated equivalent, but do not mass-redirect unrelated pages to the homepage. Google may treat irrelevant redirects as soft 404s. A friendly error message returning HTTP 200 is also not a proper retirement response.
Google's site-move guidance (opens in a new tab) explains URL mapping, relevant destinations, temporary fluctuations and retaining redirects for at least one year. Prefer keeping useful redirects longer for people following old links. Confirm that whoever maintains the domain and hosting can keep them active.
Test the redirect itself, the final page and important old variants. Avoid loops and long chains: the old address should go directly to the final equivalent rather than through several past versions. For a removed page with no suitable replacement, a proper HTTP 404 or 410 is appropriate.
A visually cleaner page can become less useful if it removes the service details that brought visitors there. Keep accurate explanations of who the service fits, genuine coverage, process, limitations, customer questions and authorized proof. Improve repetition and outdated facts rather than deleting everything to make a short design fit.
Review titles, descriptions and headings intentionally. Retaining a helpful title may be sensible; copying a misleading one is not. Clear headings should describe the page, not repeat a phrase everywhere. Keep internal links that help customers understand related services.
Protect existing local landing pages when they answer distinct, truthful needs. Do not replace them with thin, interchangeable city pages or imply staffed locations that do not exist. Preserve rights for photos, testimonials and third-party material through any rebuild.
Staging should have appropriate controls to prevent accidental public indexing, but its restrictions must not leak into the live site. Blocking crawling with robots.txt is not the same thing as reliably removing a page from Google's index. Your developer should explain the specific staging protection and launch reversal.
Use the Website Launch Checklist as a companion. A technical test is not a promise that Google will immediately index every page.
An HTTP response sends visitors and crawlers from an old address to a replacement. It is the practical tool for a changed URL with an equivalent destination.
A canonical identifies the preferred URL among duplicate or very similar versions. It is a signal, not a visitor redirect or a substitute for fixing a broken old path.
A sitemap helps discovery of URLs you want crawled. It does not force indexing, replace redirects or override contradictory page settings.
Use Search Console's tool when the site moves to another domain or subdomain under its supported requirements—not for a visual redesign, internal path changes or an HTTP-to-HTTPS change.
Google's canonical guidance (opens in a new tab) describes consistent signals and Google's final canonical selection. Keep links, canonical tags and the sitemap aligned; do not accidentally canonicalize every service page to the homepage.
The Search Console Change of Address documentation (opens in a new tab) explains the domain-move process. Follow its current requirements when applicable, after the move and redirects are in place. It is not a general “we redesigned” notification.
Open the real live domain and complete the contact journey with authorized test data. Check call links, booking destinations, forms, acknowledgment messages and intended notification delivery. A receipt confirmation does not mean a person has followed up or an appointment is booked.
For multiple locations, test the specific location page and contact path rather than sending everyone to a generic page. Do not alter profile ownership, business identity or service-area settings casually during a website project.
These examples are illustrative, not A&E client results or forecasts.
A practice's new-patient page already explains appointment expectations and receives organic visits. The owner keeps its address, improves accessibility and updates verified information. Testing still checks the form, canonical and indexing settings; keeping the URL does not guarantee a stable rank.
A roofer reorganizes repair pages into a service hierarchy. The old roof-repair URL redirects directly to the new roof-repair page, with relevant copy retained. The developer tests old inbound links, internal navigation and the final HTTP status.
An HVAC company stops providing an unrelated legacy service. With no relevant replacement, the old page returns 404 or 410 and is removed from navigation and the sitemap. The owner checks demand and old links before retirement instead of directing visitors to an irrelevant homepage.
Use this as a launch conversation, not a score predicting your rankings. Record who owns each item and where the verification is saved.
These are useful review checkpoints, not Google's processing deadlines or a promised recovery schedule. High-risk launches may need more frequent checks; a small site with little activity may need longer to make meaningful comparisons.
Recheck live status codes, key old redirects, forms, calls, booking links, consent and tags. Investigate accidental noindex, domain or canonical mistakes immediately. Confirm who can correct a launch defect.
Inspect Search Console indexing and crawl signals as data becomes available. Compare important old/new pages, sitemap processing, broken links and redirect chains. Check whether leads are reaching the right person.
Compare organic landing pages and customer outcomes with the baseline. Separate tracking changes from demand changes. Review queries and indexing issues, prioritizing valuable service pages rather than reacting to one day's position.
Compare seasonality and other business changes, then refine from evidence. Keep relevant redirects active for at least a year and preferably longer. Maintain domain, billing and access records.
Google's redirect documentation (opens in a new tab) explains permanent redirect signals. If a page disappears from reporting, first examine status, redirect destination, indexability, canonical and tracking before assuming the design itself caused the change.
Continue with What Should Happen After Your Website Launches? for a broader care plan.
Keep the business's domain and recoverable access under documented control. Use role invitations and approved secure methods rather than emailing passwords. Website files, platform access, hosting and licensed assets are different ownership questions; export and migration options depend on the provider and contract. Read Website Ownership Explained before authorizing a platform switch.
The domain is the site's named home; a URL is a particular address, including its path. Changing a page path is not the same as moving to another domain.
Permanent HTTP redirect responses. They move a request to another address and signal that the new destination should be treated as the replacement.
404 means not found; 410 means gone. A soft 404 is a response Google interprets as an error or absent content despite an apparently successful response or unsuitable redirect.
The preferred version of duplicate or very similar content. Google considers your signal but chooses the indexed canonical itself.
Noindex asks search engines not to index a page when they can see the directive. Robots.txt controls crawling; blocking a crawl can prevent a crawler from seeing noindex.
Saved prelaunch activity, queries and outcomes used for comparison. It is context for investigation, not a promise of future traffic.
No. Careful planning reduces avoidable risk, but Google processing, competition, demand and content changes can affect visibility. Ask for a documented process and responsibilities—not a no-dip promise.
Not merely because the design changed. Confirm that important old URLs still work and that no paths, domain variants or content destinations changed unintentionally.
No. Redirect to a relevant equivalent when one exists. If there is no appropriate replacement, use a proper 404 or 410 and update links and the sitemap.
Google advises at least one year after a move. Prefer retaining useful redirects longer because customers, partners and old links may still use them. Agree who maintains them.
No. Hands-on website work, Website Growth Partnership and website SEO implementation are only for A&E-built sites. An external site can receive strategy audits and recommendations. A separately scoped new A&E website rebuild may be discussed with permissions; migration or third-party-site changes are not promised without an agreed scope.
Before choosing a new look, identify the pages that bring useful visitors and the contact paths that already work. Then ask for a page-by-page plan that keeps those strengths, fixes genuine problems and assigns launch responsibilities.
Explore Website Redesign and Website Design for separately scoped A&E website projects. If your existing site was built elsewhere, Website Audit can provide strategy and recommendations for you or your developer—not hands-on tweaks or SEO implementation on that external site. Any new A&E rebuild, migration needs and asset permissions must be agreed separately.
Talk through your goals, existing website and a realistic next step before committing to a larger project.
A&E Venture LLC — BUILD. GROW. CONVERT.