# AI Visibility During a Website Redesign By AI Visibility editorial team AI-assisted article. Before redesigning your website, identify the pages that let a customer decide what to buy, where to go or whom to contact. Save the public facts and routes that support those decisions. Then ask the launch team to prove that a customer can still make the same decisions after the release. Include both the pages whose URLs move and the pages that keep their addresses but change templates. A redesign can leave the business name and web addresses intact while moving a price qualifier, dropping a location link or changing how the page loads. It can also improve a page without immediately changing how search systems describe it. Keep the release evidence and the discovery observations separate. The first tells you what the team shipped. The second tells you what someone saw on a particular surface at a particular time. Disclosure. AI Visibility is published by Lunasol, which offers GEO and AEO services. The release exercise is fictional. The public furniture example illustrates a customer path. It supplies no evidence that the named business redesigned its site, and no live assistant tests were conducted for this guide. About AI Visibility (https://aivisibility.ae/about/) Save what a buyer needs to know before you change the page Select a short list of customer paths with real consequences. Include a page that explains an important service, a location or contact page, and a page customers may reach through a link outside your site. If Arabic and English users have separate public pages, cover both where the business depends on them. For each path, record the entry URL, the customer question, the essential answer and the expected next step. The inventory should help the team tell the difference between content that moved and content that disappeared. Save the relevant wording and date. Include the approved source for facts that might change, such as service coverage, a booking condition or visit instructions. Save an image of the layout where position matters, and retain a text excerpt or page export for details the image may cut off. If the current page already contains a wrong fact, mark it for correction. The goal is to preserve the evidence and the customer decision, with changes approved where needed. The Klekktic website illustrates a useful split. Its showroom page publishes a visit action and a written Dubai location, alongside a 360-degree experience and a map. Its lighting collection also explains that customers can see finishes in the showroom. These are distinct entry points for a person exploring products or planning a visit. In a hypothetical redesign of a similar site, test whether both routes still expose the essential visit information and reach the right destination. The example describes the published pages and does not assess the booking process. Klekktic showroom page (https://klekktic.com/en-ae/pages/visit-showroom) · Klekktic lighting collection (https://klekktic.com/en-ae/collections/lighting) An official Klekktic Instagram reel from 25 March 2026 illustrates a different role. It presents home inspiration, while the site carries the practical showroom information. A redesign team can keep a social example as part of the brand experience and preserve a clear path to the visit details on the site. Record the post as dated context. Where a current bio link, ad or partner link actually directs people to a page being changed, add that link to the route inventory and check it separately. No outbound link from this particular reel was assumed. Official Klekktic Instagram reel (https://www.instagram.com/klekktic/reel/DWTGC9nDInD/) View the selected official Instagram post (https://www.instagram.com/klekktic/reel/DWTGC9nDInD/) Klekktic’s 25 March 2026 reel presents home inspiration. Use the showroom page for practical visit information. Check the new template even when the URL stays put Open the proposed page on a phone and follow the task in the inventory. Can you find the condition that affects the decision? Can you get to the correct form, directions or contact action? Check what happens when the page loads in an ordinary browser with no prior visit, particularly if an earlier choice or cookie changes what you see. Where a third-party widget is involved, identify which essential information the site can present directly and what requires the widget. Check how the content gets onto the page. An accordion may hold text already present in the document, or it may fetch the text only after a click. Those implementations deserve different checks. Google's JavaScript guidance says Google can use rendered HTML, and its lazy-loading documentation explains that Google Search does not interact with a page to trigger loading. For important text, inspect the rendered output and verify that it is available without requiring someone to reveal it through an interaction that Google won't perform. Treat this as evidence about Google Search. Other surfaces may fetch or render differently. Google JavaScript SEO guidance (https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics) · Google guidance on lazy-loaded content (https://developers.google.com/search/docs/crawling-indexing/javascript/lazy-loading) Check the links that bring someone to the page, too. The address may still work while a category page loses its link to it. A new navigation menu might direct English and Arabic users to different places. Test from a realistic starting point and record the destination you actually reached. A screenshot of the final page cannot establish that a person can get there from the earlier step. Add a URL map when routes change For a redesign that moves URLs, map the old routes to their useful replacements before launch. Include high-value pages, relevant files and any URLs linked from current campaigns or partners. Record intentional removals and the business reason for them. If several old pages are merged, check that the replacement still answers each retained customer question. A link that resolves can still be a poor handoff if the new page has no relevant content. Google's site-move guidance covers mapping old URLs, redirects, updated internal links and sitemaps, and removal of indexing restrictions that were needed only during development. It also cautions against sending many unrelated pages to the same irrelevant destination. Give the release owner a checklist that verifies final destinations and public indexing settings on the live site. Check them after deployment even if the staged mappings passed. A live route can behave differently because of hosting rules or a setting that only applies in production. Google guidance on moving a site with URL changes (https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) Keep restricted staging separate from public verification. A staging review can confirm approved wording and expected behaviour using the team's own access. After launch, check the public page as a visitor, then use the appropriate platform's own tools if available. Google distinguishes the indexed snapshot in URL Inspection from the live test. The live test checks the current page for certain conditions and does not guarantee indexing. Record which view you used. Seeing an older indexed snapshot after a successful live check is a different observation from finding a current public page with a blocking directive. Google Search Console URL Inspection documentation (https://support.google.com/webmasters/answer/9012289?hl=en) Agree on what can hold the launch Imagine a fictional UAE furniture retailer redesigning three important paths. Its product template stays at the same URL, its showroom page moves, and a trade enquiry form changes provider. The following table shows a release plan and acceptance conditions. It contains no observations from an actual deployment. Path Preserve before release Verify after release Decision if it fails Product page on the same URL Approved product qualifiers and link to the relevant showroom information The qualifiers appear on mobile and in the rendered content, and the link reaches the intended page Stop rollout of the affected template and restore the approved version if a material qualifier disappears Showroom page with a new URL Former route, current visit facts and important sources linking to it The old URL reaches the intended replacement, which supplies the confirmed directions and visit action Fix the mapping or content before approving the route Trade enquiry Published eligibility and expected destination for a prospect The live form opens correctly, and a separately authorised test reaches the team that owns enquiries Restore the approved contact path or delay that part of the release Arabic customer path Approved service conditions and locale-specific links The Arabic entry route reaches the Arabic answer and a usable contact action Assign to the locale owner and recheck the affected routes Assign someone who can clear each condition. The web owner can verify a redirect. The showroom team confirms the directions and whether the visit action matches operations. The trade team can confirm receipt of a labelled test enquiry if the business has authorised one. A release manager can record an exception only after understanding the affected path and agreeing on the fallback. Document how to disable or restore a specific component so that a failed form need not turn into an improvised rollback. Include a time and a link to the evidence with each release check. If the team decides that a question can wait until after launch, record the reason and who will recheck it. Some issues can be corrected without delaying unrelated work. For example, a low-priority change to a decorative gallery may be separate from a failure that prevents customers from finding a public service. The customer task and approved fallback should drive that decision. Repeat the discovery checks under comparable conditions If you already run an AI visibility panel, preserve its exact questions and the conditions used before launch. Keep the outputs, dates, product or surface, location and relevant settings. Mark the redesign release in the log. For the first follow-up, repeat the same questions under comparable conditions and record whether a named business, a cited URL or a service fact changed. If you add new questions about features introduced by the redesign, report them as a new group. Keep unavailable baseline observations visible instead of treating them as negative results. AI Visibility monthly reporting guide (/article/what-should-a-monthly-ai-visibility-report-contain/) Treat a change in an answer as something to investigate. Suppose a future observation cites an old showroom address after the new site is live. Open the cited source, verify the public redirect if it is an old route and compare the answer with the current operations-approved facts. The issue could be stale copy, an old external source or an answer whose source you cannot establish. Record the evidence that distinguishes those cases. If the answer cites the new page but leaves out the expected qualifier, check whether the new page actually carries it before asking for another observation. Keep separate decisions for the first launch checks and for later interpretation. A missing public phone link is actionable as soon as you reproduce it. A handful of changed AI answers after deployment does not isolate the redesign as a cause. Preserve the changed template, release date and any other relevant changes in the period. A follow-up report can then distinguish a confirmed deployment defect, a fixed customer path and an observed answer change. If a broader inventory is needed, the existing audit guide gives context for the evidence and fix list. AI Visibility audit guide (/article/what-an-ai-search-audit-should-include-a-guide-for-uae-businesses/) Close the release review when the priority routes and facts have been checked, the remaining issues have owners, and the next discovery observation has a date. Keep the baseline and the public checks linked to the release. When an older answer appears later, the next reviewer should be able to tell whether it points to a retired URL, describes information that was removed or reflects a separate source that still needs investigation.