An AI-assisted website redesign should preserve what the business needs while improving the user task. Compare tools through 5 checks: source inventory, proposed composition, information preservation, working journeys and controlled release. A new screenshot is not evidence that links, content, forms or ownership survived the redesign.
Which AI redesign route fits the existing site?
Begin with the current site as evidence. List public pages, important files, contact routes, forms and connected workflows before asking a tool to redesign anything. Record which content is approved and which defects need correction. Do not let an attractive generated concept become the authority for facts that already have authentic source material.
Shuffle’s redesign page presents AI-assisted design and editing routes with example compositions and prompt guidance. Use it to investigate how a proposed visual direction becomes editable output. The page’s examples are not evidence that a tool has preserved your site’s content, integrations or accessibility. Compare the actual output contract and the work still required after generation.
Macaly’s redesign page describes starting from a website URL, collecting content and screenshots and producing a new design. It also makes broad preservation claims. Treat those as vendor statements to test, not completed assurance. A tool saying that headings or metadata are retained should lead to a source-to-output comparison on the actual pages.
Compare URL-led recreation with a structured redesign brief. A URL can supply visible source material, while a brief can identify the information and behaviour that must remain. Neither alone necessarily captures private workflows, hidden states or business decisions behind the current site. Provide an explicit preservation list and keep unresolved source gaps visible rather than allowing the tool to invent missing sections.
Define the visual direction through the task and existing identity. Preserve approved logos and factual representation. A generated image should not imply real staff, premises or completed work without evidence. Compare the proposed composition at the intended screen sizes using actual visual review. A text description of a concept cannot establish that the resulting interface looks coherent or uses the brand correctly.
How do you preserve information and verify the result?
Build a page-and-link map before changing addresses. Identify each current URL, its intended destination and any approved change. Keep internal links and important external entry points in the review. A redesign that preserves paragraph text can still break the visitor journey by dropping a useful page or changing a link destination. Do not assume a crawl-based import captures everything the business needs.
Test the actual customer tasks. Use fictional submissions to inspect contact forms, bookings or other permitted test routes. Distinguish a simulated confirmation from a request accepted by the intended service. A generated page can look complete while its actions remain placeholders. Keep those placeholders out of a final candidate until their behaviour is implemented or truthfully removed.
Include accessibility throughout the work. W3C’s planning guidance treats it as an ongoing production responsibility rather than a final decorative pass. Assign content, design, development and evaluation tasks. Compare the new interface with the required journeys, not only with the previous appearance. A visually modern page can introduce new keyboard, structure or error-recovery barriers.
Check data and account boundaries before connecting or publishing. The redesign tool may have hosting, database or integration features, but the business still needs authorised ownership and a clear data-handling basis. Do not grant access merely because a prompt requests it. Keep generation, integration setup and production release as separate actions under the organisation’s authority.
Plan rollback and maintenance. Retain the current approved source and the proposed candidate with clear versions. Identify what would be restored if the release failed and who maintains the resulting site. Export or source-code availability needs current product documentation and a practical handover check. A conversation that produced the page is not necessarily a complete operating record.
Worked preservation example: REDESIGN-A
REDESIGN-A is a fictional service site with an About page, a service explanation and an enquiry form. The approved service page contains an important scope exclusion. For a URL-led Macaly brief, include the public URL and explicitly name that exclusion in the preservation ledger; compare the candidate text with the authentic source. For a Shuffle design/editing brief, supply the same content and ask where it will live in the editable composition. These routes differ in their documented starting material; neither has been trialled here.
The ledger is populated before generation: About biography — preserve authorised text and image attribution; service exclusion — keep beside the relevant claim; enquiry destination — retain as an implementation dependency until tested; existing service URL — preserve or document the authorised destination. If a candidate shortens away the exclusion, that is a failed preservation check even if the page looks cleaner. If the form shows a simulated confirmation, record the journey as incomplete. This example defines acceptance conditions; it is not a generated design, a tool benchmark or evidence that either vendor has passed them.
Decision worksheet
Original contribution: an AI-redesign preservation ledger. Compare Shuffle and Macaly against the same fictional source site. For every page, record the authentic text, important asset, incoming route, outgoing action and intended candidate destination. Add an evidence column for actual preservation rather than accepting the vendor’s claim. Then test the fictional enquiry journey and the page’s accessible structure. The ledger makes visual improvement and information continuity separate findings.
| Checkpoint | Evidence to retain | Decision or corrective action |
|---|---|---|
| Source inventory | Pages, assets and authentic content | Prevent invented replacement material |
| Composition | Actual wide and narrow visual review | Preserve approved identity |
| Information | Source-to-output page and link map | Do not infer preservation from appearance |
| Journeys | Real test routes and accepted results | Remove simulated functionality |
| Release | Authority, candidate and rollback evidence | Keep generation separate from publication |
Add a missing-source exercise before generation. Remove a fictional team biography from the supplied material and instruct the process to keep the gap unresolved. Inspect whether the candidate invents a person, credential or history to fill the layout. Then change an approved contact destination and identify every page or component affected. These tests evaluate fidelity and maintenance, not just the first generated screen.
No tool account has been connected, no redesign generated and no site published for this article. Actual visual examples, exports and user journeys remain to be reviewed. See web development and logo and brand design. To discuss a redesign, get started with existing source material and the preservation ledger.
By Spout Team. AI-assisted drafting by Codex using the linked primary sources.