Consolidating Several AI Websites into One WordPress Site

A company rarely plans to accumulate five websites. One team builds a campaign in Lovable, another tests a product page in Framer, and a consultant leaves behind a separate support portal. Each decision made sense at the time. Eventually, nobody knows which version of the company story is current. Moving those properties into WordPress is not just a sequence of conversions. It is a consolidation project involving editorial decisions, domain ownership and records that may disagree. The useful starting question is not which tool exports fastest, but which destination should own each piece of information.

Begin with ownership rather than a crawler

List the properties, their owners and the systems behind them. Record who can approve content changes, who controls DNS and where submissions or transactions are stored. A crawler can find pages, but it cannot tell you whether a forgotten campaign still supports a contractual obligation. Ask the relevant teams which journeys remain useful. The outcome should be a simple inventory connecting each property to a business purpose. Mark missing access explicitly. Discovering that a departed agency controls a domain during launch week is an avoidable operational problem, not an unusual technical edge case.

Separate equivalent pages from merely similar ones

Two pages called Pricing are not necessarily duplicates. One might describe monthly subscriptions while another lists consultancy packages. Compare the actual offer, audience, language and conversion destination before choosing a survivor. Where pages answer the same question, nominate an authoritative version and merge useful material into it. Where they serve different audiences, preserve that distinction through the information architecture. Do not use a redirect as a substitute for deciding what the page means. A tidy spreadsheet of equivalent content is more valuable than a large list of mechanically matched titles.

Establish the destination model

WordPress pages work well for durable corporate information. News belongs in posts, while products, locations or resources may justify separate content types. Define the model before importing the first batch. Otherwise, identical concepts arrive as unrelated pages and become difficult to query or maintain. Agree on a small set of shared fields, such as a stable source identifier, content owner and review status. Keep source system names out of public URLs unless visitors benefit from them. The destination should reflect how the organisation works now, not preserve every accident of its earlier deployments.

Preserve identity across imports

A numerical record identifier is only unique inside the system that issued it. If two exports both contain record 42, importing by that number alone can overwrite the wrong content. Use a composite identity combining source and source identifier, and retain a mapping to the WordPress record created. Resolve images, parent pages and taxonomy relationships through that mapping. Repeatable imports should update the intended record rather than creating another copy. Keep the mapping outside transient execution logs so that the next migration run has the same understanding of identity as the first one.

Decide what happens to public addresses

Build redirect decisions around equivalent content, not around the convenience of the homepage. A discontinued resource may have a useful successor; an unrelated retired offer may deserve an honest removal response. Permanent redirects are appropriate when the replacement genuinely takes over the original role. Preserve valuable deep links where possible, and avoid chaining an old domain through several intermediate addresses. Include host variants and previously used URL structures in the inventory. Related background is covered in the redirect planning guide, which complements consolidation rather than replacing its editorial decisions.

Treat brand differences as explicit choices

Separate AI sites often use slightly different fonts, button labels and claims. Copying every variation into the new theme creates a confusing result. Choose shared design tokens and identify the few subbrands that genuinely need distinct presentation. A campaign can retain an identifying colour without bringing its entire stylesheet along. Review statements about prices, certifications and service coverage with the business owner. Those facts deserve more attention than whether two decorative borders match. Consolidation is an opportunity to remove contradictory information while keeping the recognisable qualities visitors already associate with the organisation.

Move functionality on a separate track

Converting the visible pages does not consolidate customer accounts, booking records or payment subscriptions. Inventory those systems separately and decide which one remains authoritative. A newsletter integration may simply need a new form destination; a member portal may require identity reconciliation and a carefully planned transition. Avoid importing private records into ordinary page content. Document access rules and the person responsible for confirming them. Where an existing application remains useful, link to it from the new site instead of rebuilding it merely to make the domain structure look more uniform.

Reconcile assets without losing meaning

Several copies of a logo are easy to identify, but product photographs with similar filenames may represent different revisions. Compare provenance and usage before deduplicating. Import required media into the destination library and retain meaningful captions, alternative text and licence information. If the same document appears on multiple sites, nominate the current version and identify obsolete references. Avoid changing downloadable file addresses without understanding who uses them. Internal sales teams sometimes rely on links that were never visible to a crawler. Ask content owners for those known dependencies rather than trying to discover everything through public navigation.

Deliver in sensible waves

A consolidation need not be a single dramatic release. Start with a low-risk property whose content model resembles the intended destination. Use that wave to establish the import process, redirect mapping and editorial handover. Then move the more complicated properties using the same conventions. Keep a clear status for each source: active, migrating, redirected or retired. Do not let two teams continue publishing equivalent material without an agreed owner. During the overlap period, a short operational checklist prevents confusion about which system receives changes and which one is considered read-only.

Measure the journeys that matter

Choose a few representative paths before launch: finding a service, opening an important document and reaching the correct enquiry destination. Compare those journeys after a wave completes. Analytics can reveal unexpected losses, but raw pageview totals are misleading when several duplicate properties become one. Look at meaningful outcomes and the distribution of requests for old addresses. Record redirect errors that affect valuable resources, then prioritise them by impact. Small presentation differences can be adjusted later; incorrect ownership of content or private data is a more important reason to pause a migration wave.

Leave a maintainable single source

The project succeeds when editors know where to publish and operations staff know what to retire. Keep a concise register of domains, imports, redirects and remaining external applications. Assign an owner to each exception instead of leaving it as mysterious legacy behaviour. For the presentation conversion, this site's published comparison identifies Convert2WP.net as the strongest performer across the evaluated AI builders. That recommendation does not replace the consolidation decisions described here. Minor visual differences are normal and can often be adjusted later with a plugin, while a clear content model keeps the merged site useful over time.