Changing your optical website provider requires careful planning. You want a better site, but you also need patients to keep finding your practice and booking appointments throughout the transition.
It is easy to miss things when you are focused on the new design. Useful pages can be left out, old links can stop working and booking buttons can lead to the wrong place. These problems can affect both your search visibility and patient enquiries.
This checklist explains what to check with your provider before the move, what to test before launch and what to keep an eye on afterwards.
First, Confirm What Is Actually Changing
A provider change does not always require a new domain or different page addresses. Establish the scope before approving the work.
| What is changing? | What needs particular attention? |
|---|---|
| Hosting provider, with the same website addresses | Reliable access, secure connections and a tested switchover |
| Website platform or design | Content, page settings, navigation, forms and booking integrations |
| Individual page addresses | Redirects connecting old addresses to their relevant replacements |
| Domain name | Redirects, domain ownership, Search Console and external website links |
For a hosting change that keeps the same URLs, Google’s guidance focuses on testing the new infrastructure and monitoring access for both visitors and search engines during the switch.
Ask your incoming provider to document which changes are necessary. Keeping working page addresses can reduce the number of things that need managing.
Before the Build: Record What You Need to Protect
Your current website provides the starting point for the migration. Give the new provider an inventory of its pages, performance and connected services before decisions are made about what to replace.
1. Confirm Ownership and Account Access
Your practice should have control of the accounts needed to run and measure its website.
Check access to the domain registration, hosting, website administration, Google Analytics, Google Search Console and Google Business Profile. Confirm who manages the hosting and how it will be transferred or replaced. Include booking services, payment providers and product feeds where relevant.
Agree what the outgoing provider will supply, the notice period and which services will stop when the contract ends. Confirm ownership or transfer rights for copy, photography and other website assets.
Email needs attention too. If the provider manages your domain settings, establish who will preserve the records that keep practice email working.
⇒ Checklist: Account access confirmed, assets available and handover responsibilities documented. |
2. Save a Performance Baseline
Record how the website performs before making changes. Otherwise, it will be difficult to distinguish a migration problem from an existing issue.
Use the Search Console performance report to identify the pages and search queries generating clicks and impressions. Separate searches for your practice name from searches for services, such as contact lens appointments or children’s eye tests.
Alongside search data, record the actions that matter commercially: completed bookings, enquiries and online purchases, where tracking is available. A booking-button click should be recorded separately from a confirmed appointment.
Save data for a recent period to use as your baseline and, where possible, the equivalent period last year to account for seasonal differences.
Checklist: Search performance and key patient actions recorded before launch. |
3. Agree Which Pages Will Stay
Review service pages, branch pages, practitioner profiles, patient information, articles and any product categories.
Pay particular attention to pages that attract relevant visitors, generate enquiries or have links from other websites. A page does not need to appear in the main menu to have value.
For an optical practice, separate pages about myopia management, dry eye appointments or contact lenses may explain services in more useful detail than a single general “Eyecare” page. Assess their performance and purpose before combining them.
Review photography as part of this process. Replace outdated images and prioritise original photographs of your practice, team and equipment over generic stock imagery, which tells patients little about your actual practice. Consider adding short videos to introduce practitioners, show the premises or explain what to expect during an appointment.
Check usage rights for all images and videos, including licences for stock photography and consent from anyone featured. AI-generated images may raise copyright concerns and should be reviewed carefully before publication. They should not be presented as photographs of your actual team, premises or services.
Record a decision for each page: keep, update, merge or remove. Save existing titles, meta descriptions and important content so they can be reviewed during the build.
⇒ Checklist: Every existing page has a documented decision to keep, update, merge or remove it, with a reason for any removal. Photography reviewed, relevant videos considered and usage rights and permissions confirmed. |
Before Launch: Check the Details Behind the Design
The preview should demonstrate that the website works as well as it looks. Ask your provider to show the results of these checks before agreeing on a launch date.
4. Map and Test Changed Page Addresses
Where an address changes, record the old URL and its relevant replacement in a redirect map.
A permanent server-side redirect, commonly a 301, directs visitors to the new address and signals the move to search engines. Google recommends permanent redirects for pages that have moved.
Send each old page to the closest appropriate destination. Redirecting every removed service page to the homepage leaves visitors searching again and may be treated as an error by Google.
Update links within the new site to point directly to the final addresses. Test the redirects, including any retained from earlier website changes. Where content has genuinely been removed without a replacement, an appropriate not-found response is preferable to an unrelated destination.
⇒ Checklist: Changed URLs mapped, redirects tested and internal links updated. |
5. Check What Search Engines Can Access
Development websites are often kept out of search results while work is in progress. Those protections need checking carefully at launch.
Ask your provider to confirm that public pages are accessible to search engines and that development-only restrictions have been removed from the live website. A leftover noindex instruction can prevent a page from appearing in Google even when patients can open it normally.
Check canonical tags too. These identify the preferred address for a page; they should point to the intended live URLs, with no references to the development website. Google recommends keeping canonical signals consistent.
The new XML sitemap should list the live pages you want discovered. Your provider can submit the sitemap through Search Console, although submission does not guarantee indexing.
⇒ Checklist: Public pages accessible to search engines, indexing settings checked and the live sitemap ready. |
6. Test Booking, Enquiries and Online Purchases
Protecting search traffic is only useful if visitors can still complete their next step.
Check the route from your website to an appointment on mobile and desktop. Test booking buttons across service and branch pages, appointment selection and confirmations. Make sure each branch sends patients to the correct booking service and, where integrated, the correct practice diary.
Submit enquiry forms and confirm that the messages arrive with the right team. Check telephone links, maps and opening hours.
For an eCommerce website, test product options, stock information, checkout, delivery charges and order confirmations using the payment provider’s approved testing process.
Verify that analytics records the intended actions without counting them twice.
⇒ Checklist: Bookings, forms, purchases and tracking tested through to completion. |
7. Review Website Responsiveness and Practice Information
Check more than the homepage. Review a service page, branch page, article and product page, where applicable.
The website should be responsive, adapting to different screen sizes. Text should be readable, navigation usable and booking controls easy to reach. Check for missing images, broken layouts and unnecessarily large files that slow loading.
Confirm that addresses, telephone numbers, opening hours and service descriptions are accurate. If website or booking URLs change, update the relevant links in Google Business Profile, directories, social profiles and advertising campaigns.
⇒ Checklist: Key page types checked for responsiveness reviewed on mobile, with accurate practice details and working external links. |
Launch Day: Give Each Check an Owner
Agree who authorises the launch, who handles technical problems and who checks patient-facing functions. Schedule the switch when support is available.
Keep a backup and a documented recovery plan. Avoid cancelling the old hosting until the incoming provider has confirmed that the move is working and the old service is no longer needed.
Use a shared sign-off list so unfinished tasks remain visible.
| Launch check | Suggested owner |
|---|---|
| Domain settings, secure connection and website access | Website provider |
| Redirects and indexing settings | Website provider or SEO specialist |
| Branch details, booking and enquiries | Practice team |
| Analytics and conversion tracking | Marketing team or provider |
| Fault reporting and recovery decision | Named migration lead |
After Launch: Monitor Search Visibility and Patient Actions
Check access, forms and booking immediately after launch. Review search performance regularly over the following weeks.
Google notes that rankings can fluctuate during a site move while pages are recrawled and reprocessed. That makes monitoring important; it does not mean every decline should be dismissed as temporary.
Compare important service and branch pages with your baseline. Investigate missing pages, incorrect redirects and indexing restrictions. Check tracking separately: an apparent fall in bookings may reflect a measurement fault, while stable traffic with fewer confirmed appointments may point to a booking problem.
Keep migration redirects in place for at least a year, as Google recommends, and longer where old links still serve patients.
Once the migration is stable, use ongoing marketing support for your optical practice to assess further improvements against a reliable baseline.
Choosing a Provider Who Understands Optical Websites
An optical website needs to explain services clearly, represent each practice location accurately and help patients book. Online retail adds product information, payments and fulfilment requirements.
Those needs should shape the brief and the testing plan.
OptiCommerce provides websites and online stores built for independent optical businesses. Its team specialises in the eyecare industry, helping practices create an online presence that supports browsing, purchases and appointments.
When discussing a move, ask for a written scope covering content, changed URLs, booking connections, tracking and support after launch. Agree which migration tasks are included and who is responsible for each one.
A review of your current digital presence can help identify priorities before you commit to the rebuild.
You can book a demo to get a clearer understanding of what needs improving and what needs protecting.
