SEO Migration Checklist for FCA-Regulated Firms: A Practical UK Guide

A website migration is rarely just a technical project for an FCA-regulated business. It can change which claims are published, where risk information appears, how customer enquiries are recorded and whether important pages remain discoverable.

For mortgage brokers, insurance brokers, IFAs and wealth managers, that creates two connected risks. The first is familiar: lost rankings, broken links, crawling problems and unreliable conversion data. The second is governance risk. An apparently minor design or content change may alter the overall impression of a financial promotion, remove an important qualification or publish material that has not passed the firm’s approval process.

This SEO migration checklist for FCA-regulated firms treats the move as a controlled business change rather than a last-minute redirect exercise. It is practical guidance, not legal advice or a guarantee of regulatory compliance. Firms should interpret the relevant FCA Handbook requirements with their compliance advisers and consider the latest material published by the Financial Conduct Authority.

What counts as an SEO migration?

A migration does not have to involve a new domain. Any substantial change to URLs, templates, content, navigation or underlying technology can affect organic visibility.

Common examples include:

• moving to a new domain, subdomain or content management system;
• switching from HTTP to HTTPS or changing URL structures;
• combining several adviser, branch or acquired-company websites;
• redesigning templates and navigation;
• rewriting service pages or consolidating an article library;
• changing analytics, consent-management or lead-generation systems;
• rebranding an appointed representative or changing how its principal is presented.

A redesign that retains the same domain can be more disruptive than a domain change if it removes useful content, alters internal links and introduces client-side rendering problems. Scope the migration according to what is changing, not what the project has been called.

1. Establish ownership before technical work begins

The migration needs named owners across SEO, development, compliance, marketing and data protection. One person may cover several functions in a smaller brokerage, but the responsibilities should still be explicit.

Agree who can approve URL removals, content changes, disclosures, tracking tools and launch readiness. Also establish who has authority to stop the launch. Without that decision structure, unresolved issues are often accepted because a supplier, board announcement or campaign has fixed the date.

I recommend maintaining one risk and decision log. Record the issue, owner, proposed treatment, evidence reviewed, approval status and deadline. This is more useful than decisions dispersed across email threads.

Define measurable migration objectives

“Launch the new website” is not an adequate objective. Define what must be preserved or improved, such as:

• retention of valuable organic landing pages and backlinks;
• continued visibility of regulatory and company information;
• accurate tracking of calls, forms and booked appointments;
• no unintended expansion of product or geographic claims;
• acceptable crawlability, indexability and page performance;
• a documented approval trail for migrated and rewritten content.

Rankings and traffic can fluctuate after significant changes, so avoid promises that a migration will be lossless. The defensible goal is to reduce avoidable risk and identify material problems quickly.

2. Create a complete pre-migration inventory

Crawl the live site before development is finalised. Export every indexable URL, page title, canonical, status code, meta robots directive, heading and internal link. Supplement the crawl with XML sitemaps, analytics landing-page data, Google Search Console exports, backlink information and any URLs held in the CMS.

Do not rely on traffic alone when deciding what survives. A low-traffic page may contain mandatory information, support an important customer journey or attract a small number of commercially valuable enquiries. Conversely, an old article may receive visits while describing products, rates or tax treatment that are no longer current.

Classify each URL as:

• retain: keep its purpose, content and URL where possible;
• update: preserve the page but review claims, evidence and presentation;
• merge: combine genuinely overlapping pages into a stronger destination;
• remove: retire content with no continuing user, compliance or search value;
• restricted or archived: retain for internal records rather than public search access.

Record the reason for each decision. This reduces the chance that useful content disappears simply because it was absent from the new navigation mock-up.

A broader crawl and indexation review can follow the process in this technical SEO audit framework for mortgage broker websites.

3. Build and test a one-to-one redirect map

Every changing URL needs an intentional outcome. Map an old page to the closest relevant new page, not automatically to the homepage or a generic service category.

Use permanent server-side redirects for content that has permanently moved. Avoid redirect chains, loops and blanket rules that send unrelated pages to one destination. If there is no useful replacement, an honest 404 or 410 response can be preferable to an irrelevant redirect that confuses users.

The redirect map should include the old URL, new URL, decision rationale, redirect status, content owner and test result. Include PDFs, campaign landing pages, adviser biographies, branch pages and URLs with historic naming conventions.

Preserve URL paths where there is no good reason to change them. A new CMS is not, by itself, a user benefit. Unnecessary URL changes increase testing effort and create more failure points.

Review internal links separately

Redirects are a safety mechanism, not a replacement for updating links. Change navigation, breadcrumbs, contextual links, canonical tags and XML sitemaps so they point directly to final URLs.

Pay particular attention to links connecting educational content with service, location and adviser pages. A migration can preserve every page while weakening the relationships between them. For a structured approach, see this UK internal-linking framework for financial services websites.

4. Conduct a compliance-aware content review

A migration often changes presentation as much as wording. Review the complete customer impression on desktop and mobile, including headings, buttons, calculators, comparison tables, testimonials, imagery, footnotes and risk information.

Regulated firms should verify whether published material constitutes a financial promotion and which approval requirements apply. As a practical editorial principle, prominent benefits should not be separated from material limitations in a way that leaves the page unbalanced. The applicable rule depends on the product, audience and firm, so compliance sign-off cannot be replaced by a generic SEO checklist.

Check at least the following:

• the firm’s legal name, trading names and regulatory status;
• FCA reference details and the accuracy of register-related wording;
• appointed representative and principal disclosures, where applicable;
• scope-of-service statements, including whole-of-market or panel claims;
• fees, commissions and eligibility descriptions;
• risk warnings and product-specific qualifications;
• claims about experience, awards, performance, savings or approval speed;
• references to rates, allowances, tax treatment or market conditions;
• complaints, privacy, cookie and accessibility information;
• dates, authors, reviewers and review cycles where these help users assess the content.

Do not assume that text approved on the old site remains acceptable in a new layout. A warning that was visible beside a call to action may become collapsed, truncated or pushed far below it. For more detail on the relationship between organic content and promotions, review how FCA financial promotions rules affect SEO content.

Preserve evidence and accountability signals

Author biographies, reviewer information, sources, update dates and clearly stated editorial responsibility can help readers evaluate sensitive financial content. Preserve them when they are genuine and useful; do not add nominal reviewers who did not review the material.

Structured data should match visible content and actual business arrangements. Avoid unsupported ratings, invented credentials or schema implying that a page was reviewed by someone who had no involvement. Google’s current technical documentation should be checked through Google Search Central rather than relying on old implementation guides.

5. Complete technical SEO quality assurance

Test the staging environment while it is protected from public indexation. Before launch, prepare a controlled process for removing staging restrictions from production. A copied noindex directive or blocked robots.txt file can suppress an otherwise successful website.

Also test pagination, filters, search results, downloadable documents, hreflang if relevant, structured data, image handling and custom error pages. Check that enquiry forms fail safely and provide understandable validation messages.

Performance matters, but it should not be improved by stripping out substantive qualifications or making them difficult to access. Compressing images and reducing unused scripts are sensible; hiding important information behind interaction purely to simplify the design is a different trade-off.

6. Protect analytics, consent and lead attribution

A visually successful migration can still damage decision-making if tracking breaks. Catalogue each analytics tag, advertising pixel, call-tracking number, CRM integration, appointment tool and form event before launch.

Define what counts as a meaningful conversion. A form start, successful submission, click-to-call and completed booking are different actions. Test them separately, including duplicate-event prevention and hand-off to the CRM.

Consent implementation should be reviewed with the organisation’s data-protection specialists. The migration may introduce new vendors, cookies or data flows. Consult current guidance from the Information Commissioner’s Office; an old cookie banner should not be assumed adequate because it still appears.

Use test leads that are clearly labelled and remove them according to internal procedures. Confirm where form data is stored, who receives notifications and whether sensitive information is being requested unnecessarily. SEO teams need visibility of measurement, but not unrestricted access to personal customer data.

For a fuller measurement model, see this guide to conversion tracking for mortgage broker SEO.

7. Run a controlled launch

A launch checklist should specify the sequence, owner and expected result for every critical action. Take final backups and exports of the old site, redirect file, crawl data, analytics configuration and approved content.

Immediately after deployment:

1. confirm that the correct production version is live;
2. remove unintended noindex rules and crawling blocks;
3. test representative redirects across every content type;
4. check canonical tags, sitemaps and robots.txt;
5. submit or refresh relevant Search Console properties and sitemaps;
6. test high-value pages and forms on mobile and desktop;
7. verify consent choices and analytics events;
8. inspect regulatory details, disclaimers and contact information;
9. crawl the live site and compare it with the approved URL map.

Do not combine several avoidable changes on launch day. If possible, defer experimental copy, broad navigation revisions and non-essential integrations. Fewer simultaneous variables make faults easier to isolate.

8. Monitor the migration beyond launch week

Migration QA is a period, not a moment. Monitor daily at first, then reduce frequency as the site stabilises.

Track organic landing-page clicks and impressions, indexed-page patterns, crawl errors, redirect failures, server errors, conversion completion and CRM receipt. Segment reporting by page type, service and location. Site-wide totals can conceal the loss of one commercially important section.

Compare performance with several relevant pre-migration periods, while accounting for seasonality, campaigns and known market changes. A simple week-on-week comparison can misattribute normal demand variation to the migration.

Keep redirects in place for the long term where old URLs continue to receive visits or links. Update important third-party profiles and campaign destinations directly, but do not remove redirects merely because those updates are complete.

Common migration mistakes in regulated financial services

• Compliance is invited too late. Review then becomes a launch blocker rather than part of content design.
• Traffic decides every content outcome. Necessary disclosures and valuable low-volume pages are removed.
• All old URLs go to the homepage. Users lose context and search engines receive weak destination signals.
• Approved copy is altered during build. Shortened headings or buttons introduce claims that were never reviewed.
• Mobile presentation is overlooked. Qualifications become less prominent than benefits.
• Tracking is tested only in preview mode. Consent choices, live domains or CRM integrations produce different results.
• No baseline is retained. The team cannot distinguish a migration issue from an existing technical problem.

Concise FAQ

Should every old URL be redirected?

No. Redirect URLs with a relevant successor. If content has been intentionally removed and no equivalent exists, a proper 404 or 410 response may be clearer than sending users to an unrelated page.

Can a migration guarantee retention of rankings?

No. Search visibility is not fully controllable, and substantial changes can cause fluctuations. Careful mapping, content preservation, technical testing and monitoring reduce avoidable risk but do not guarantee outcomes.

Does compliance need to approve redirects?

Not necessarily every technical rule. Compliance should, however, be involved where a redirect changes the destination, customer journey, product context or presentation of approved material. Agree the threshold before mapping begins.

How long should post-launch monitoring continue?

Intensive checks are appropriate immediately after launch, followed by regular monitoring over the following weeks and months. The exact period depends on site size, crawl frequency and the scale of change.

Should an old site remain publicly available as an archive?

Usually not without a clear reason and controls. A public archive can create duplicate, outdated or conflicting information. Preserve records internally in line with applicable retention requirements and professional advice.

Conclusion: treat migration as governed change

The safest approach is not to bolt an FCA review onto a standard SEO migration. Build regulatory ownership, content evidence, technical controls and measurement into the project from the beginning.

Start with a complete inventory. Make explicit keep, merge and remove decisions. Map redirects to genuinely relevant destinations, review the presentation as well as the wording, and test production as a customer would experience it. Then monitor by page type and conversion journey rather than relying on a single traffic number.

In my professional judgment, the strongest migration plan is usually the least theatrical one: preserve what already works, change only what has a defensible purpose, document approvals and make failures easy to detect. That does not eliminate search or regulatory risk, but it gives an FCA-regulated firm a far more controlled basis for managing both.