In this guide
Define what must keep working
A new design may be approved while an old link returns an error or the form no longer delivers enquiries. The technical acceptance testing means checking the delivered site against expected results, on the pages and journeys that matter to your activity.
Start by naming the person who decides when to publish, someone able to restore the previous version, and the people responsible for fixes. List the essential journeys: finding a service, sending an enquiry, signing in, or placing an order, depending on the site.
A visual redesign, CMS change and domain migration have different scopes. Identify the changes explicitly. Google’s migration procedures concern URLs or hosting; they do not replace acceptance tests for your features.
Before publication: keep a baseline and test the target version
- Inventory important URLs. Cross-check the sitemap, known links, Search Console and available analytics. Include pages that receive enquiries, PDFs and campaigns that are still active.
- Keep a baseline before redesigning. Record the HTTP status, main content, headings, indexing directives and measurements for a few representative pages. Keep the date and conditions for each observation.
- Prepare a protected staging environment. Use test data. A
robots.txtor anoindexis not access control. Document which restrictions to keep on staging and which to remove only in production. - Repeat the journeys. Test mobile and desktop, keyboard navigation, error messages and confirmations. For a form, verify actual message delivery; for a payment, use the provider’s test mode.
- Prepare the rollback. Retain the necessary version, configuration and backup. Check restoration and define how to handle data created after the switch: restoring old code does not automatically restore a compatible database.
If hosting changes, prepare certificates, configuration and access before changing DNS. Check the new infrastructure, then monitor both environments during the transition. Keep the old hosting until the switch is confirmed. Google procedure for changing hosting.
If addresses change: map each URL individually
For each important old address, choose an equivalent destination or record its removal. Avoid redirecting every removed page to the homepage. A permanent server redirect, usually 301 or 308, should reach the correct content directly, without a chain or loop. Choose the redirect type.
On a small screen, scroll the table horizontally.
| Old URL | Decision | Expected result |
|---|---|---|
/nos-services/audit | Moved to /services/audit-web | A permanent redirect, followed by the equivalent page returning 200. |
/contact | Address retained | 200 and a working form. |
/promotion-ancienne | Removed without an equivalent | 404 or 410, with a useful error page. |
Update internal links, canonicals, sitemaps and language variants to point to the new URLs. When changing domains, check Search Console properties and use the change-of-address procedure where applicable. Google recommends keeping redirects for at least a year, and longer if they remain useful to visitors. Prepare and monitor a URL migration.
At publication: repeat checks on the real domain
A staging result is not enough: the CDN, service keys, cache or protections may differ. Open the published version without an administrator session, then check each page type.
- Access: domain, certificate, HTTP/HTTPS variants, old URLs, 404 page and essential resources.
- Indexing: absence of
noindexunintentionally present in HTML or headers; appropriate crawl rules; canonicals and sitemap using the final domain. Keep intentional exclusions. Read the robots directives actually served. - Journeys: form delivery, contact links, authentication and payments within your scope. Also check errors and confirmations.
- Display and accessibility: keyboard navigation, visible focus, named fields, enlarged text and no hidden content. These tests remain an initial review. W3C first checks.
- Performance: the same page, viewport, network and cache state for comparison. Replay late-loading content using the CLS guide.
For each failure, record the URL, steps, evidence, owner and decision. An unusable essential journey may justify delaying publication or rolling back. A cosmetic change that does not affect tasks can be scheduled; the publication owner makes the decision.
After publication: monitor what a one-off test cannot show
Quickly check server errors, requests to old URLs and delivery of enquiries. Then continue monitoring indexing, impressions, clicks and essential journeys. Adjust the frequency to the site’s traffic and importance.
A decline observed after a redesign does not automatically identify its cause. Compare affected pages, dates and changes. Ranking variations during a migration are possible; a forgotten page or a blocking directive should be investigated promptly.
Argos can help you collect public signals from several URLs, one at a time, before and after. It does not check your complete redirect plan, email delivery, orders or signed-in areas. Keep the manual tests alongside the reports and their measurement coverage.
A worksheet for evidence-based decisions
Download the redesign acceptance worksheet (CSV, semicolon separator). Elle comprend les phases avant, publication et suivi ; complétez une ligne par URL ou parcours. Aucun contrôle n’est prévalidé.
Record the expected result, observation, evidence, owner and decision. Duplicate rows for your scope and justify removing any that do not apply. This worksheet documents a decision; it is not a certification.
To broaden preparation to accounts, emails and other website or SaaS needs, the launch checklist by Antoine Le Louët, creator of Argos, provides an interactive supplement.
Official references
Sources consulted on 2 November 2026. Service interfaces and rules may change.
Check your page with Argos
Run a free audit of a public URL and examine the available evidence. Automated checks complement the checks in this guide.
Analyse a page for free