Live engine migration
The public estate moved from the legacy builder to the new Astro platform.
Creative direction, migration and search architecture
XO3D website: a premium CGI studio platform. Rebuilt as an authority system.
What does XO3D website transformation do, and who is it for?
XO3D's main website was rebuilt from a legacy WordPress and Elementor estate into a fast, structured Astro platform. The transformation combined premium creative direction, large-scale content architecture, migration controls, technical SEO, GEO and AI-search foundations, consent-aware analytics and clearer journeys from expertise to enquiry. The intended operating context is Large public route estate across services, proof, research and conversion. Thomas's role was Founder, creative director and digital-system lead. The case follows the product from its main operating problem through Live engine migration, Premium creative direction, Large-estate cleanup, then connects each interface to a working feature and control. The evidence comes from live migration, builds, route qa, analytics and search checks. It also records what failed, what changed and how privacy, evidence or approval boundaries are handled. The limit is explicit: no attributed ranking, traffic or lead-lift claim yet.
StatusLive public website
RoleFounder, creative director and digital-system lead
ScopeLarge public route estate across services, proof, research and conversion
EvidenceLive migration, builds, route QA, analytics and search checks
Known limitNo attributed ranking, traffic or lead-lift claim yet
Public proof / Last verified 4 September 2026View the live XO3D website
01 / The operating problem
Replacing the website engine could not mean throwing away the studio's accumulated authority.
A direct account of the operating constraint, the product decision and the limits of the evidence.
The legacy estate held useful history but also route sprawl, duplicate copy, inconsistent entity facts and weak separation between commercial pages and informational content. The visual work needed full-frame space, while the written estate needed enough structure for buyers, search systems and AI answers.
A migration at this scale can create quiet damage: old URLs disappear, middleware changes redirect behaviour, analytics continuity breaks, video slows first paint and internal links point at the wrong version of the offer. A clean new home page would not solve those estate-level risks.
The rebuild treated the site as an authority system. Content collections define reusable page types. Redirect and canonical rules preserve intended routes. Commercial, research and proof journeys have distinct jobs. Media, consent, analytics and cross-property links are part of the architecture rather than finishing tasks.
| Primary job | Make a director-led product CGI studio understandable, credible and easy to contact. |
|---|---|
| Core estate | Services, industries, use cases, case studies, guides, research, team, reviews and contact. |
| Experience | Full-frame work, autoplay hero film, showreel, clear commercial spines and restrained editorial copy. |
| Search layer | Structured content, redirects, canonicals, schema, sitemaps, feeds and AI-crawler guidance. |
| Ecosystem | Main studio journeys connect to Labs tools and related products without confusing their roles. |
02 / What changed
What shipped across XO3D website transformation.
These are observed properties of the working system. They are not claimed percentages, revenue attribution or a guarantee of future performance.
Premium creative direction
Self-hosted type, full-frame work, restrained motion and a coherent showreel experience now carry the studio identity.
Large-estate cleanup
Legacy routes, stale copy, duplicate intent and entity inconsistencies were consolidated through the migration.
Search and AI foundations
Structured pages, schema, sitemaps, feeds, LLM context and crawler controls are live.
Connected product ecosystem
Main and Labs now link in both directions through relevant buyer and tool journeys.
Measured limit
The platform and migration are proven; ranking and lead improvement have not been attributed yet.
03 / Interface tour
Pages, journeys and conversion surfaces in XO3D website transformation.
Every image preserves the interface purpose and control logic while replacing live people, projects, records and values with staged data.
04 / Feature evidence
Explore the evidence for XO3D website transformation.
Each entry links to the exact view it describes. Product captures and explanatory diagrams retain their own evidence labels.
Direct public product capture
Studio home
What this evidence shows
A released-style product frame demonstrates the premium public direction without using private work.
Direct public product capture
Service architecture
What this evidence shows
A public-safe page connects service, process, proof and a clear next action.
Direct public product capture
Sony case study
What this evidence shows
The direct public case-study route shows the real evidence structure and released work.
Direct public product capture
Thinking
What this evidence shows
The public editorial hub extends the studio's authority beyond the work gallery.
Direct public product capture
Case studies
What this evidence shows
The public case-study index connects the studio's released work and evidence routes.
Explanatory system diagram
Feature map
What this evidence shows
A visual summary connects the main product capabilities to the decisions, controls and user outcomes they support.
Explanatory system diagram
End-to-end workflow
What this evidence shows
The complete working sequence shows how information moves from the first input to a checked and reviewable outcome.
05 / System design
Brand, content, search and technical architecture.
The visible dashboard is only the decision surface. Context, data, permissions, review and learning determine whether it can be trusted.
Brand and creative system
Typography, framing, motion and image rules keep the product work primary.
Content architecture
Services, industries, use cases, proof, guides and research use clear page contracts.
Migration layer
Redirects, canonicals, route ownership and middleware tests preserve intended public destinations.
Discovery layer
Metadata, schema, internal links, feeds, sitemaps and answer-first content make expertise extractable.
Conversion and learning
Relevant proof, contact flow, attribution and consent-aware measurement connect page intent to enquiry.
06 / Working flow
From visitor intent to a controlled enquiry.
A useful workflow names the input, owner, check, approval boundary and proof that closes the loop.
Orient
A buyer recognises the studio, the product-CGI category and the available service path.
Inspect
Full-frame work, case studies and process evidence build confidence without decorative interruption.
Understand
Industry, use-case, guide and research pages answer the practical questions around commissioning.
Explore
Relevant Labs tools support planning and evaluation without replacing the studio service.
Enquire
A consent-aware contact path preserves source context and routes the opportunity correctly.
07 / Working features
Working website and measurement features.
Each feature exists because it changes a decision, reduces unsafe ambiguity or makes a failure easier to see.
Service and sector architecture
Product films, stills, interactive work, industries and use cases have distinct decision paths.
Proof estate
Case studies, reviews, team context and process pages show how the work is directed and delivered.
Research and guides
Long-form useful pages answer planning, production and commissioning questions.
Showreel experience
Autoplay hero and an intentional showreel view keep released work full-frame.
Conversion and attribution
HubSpot, first-touch context and consent-aware analytics connect enquiry to the page journey.
Machine-readable estate
Schema, RSS and Atom feeds, sitemap, LLM summary and crawler controls reinforce the visible site.
08 / Issues and changes
Migration, form and measurement failures in XO3D website transformation.
The strongest evidence in an operating system is often the failure behaviour. These issues became design constraints and regression checks.
Legacy route sprawl
What failed
Years of builder pages created overlapping and inconsistent destinations.
What changed
Map route intent, consolidate duplication and preserve important legacy URLs through explicit redirects.
Weak commercial separation
What failed
Informational and buyer pages could compete or repeat the same broad message.
What changed
Give each template a primary job and build a clear internal commercial spine.
Video performance
What failed
Premium motion and showreel media could slow or destabilise the first experience.
What changed
Control loading, modal playback, responsive media and metadata as product requirements.
Middleware surprises
What failed
A redirect could behave differently at production boundaries than in a local build.
What changed
Test the final host behaviour and treat redirects as observable routes, not configuration assumptions.
Entity inconsistency
What failed
Old copy disagreed about facts or described the studio in several ways.
What changed
Create canonical entity language and propagate it through visible copy and structured data.
09 / Controls and limits
What XO3D website transformation proves, and what it does not.
A public case study should make it easy to see what is working, what remains internal and what has not been proven.
Known limit
No attributed ranking, traffic or lead-lift claim yet.
Every visual is labelled as a direct public product capture or an actual product capture with generic data. This is evidence of design and operating capability, not a promise of rankings, revenue, leads, productivity or a client outcome.
10 / Capabilities demonstrated
Capabilities demonstrated by XO3D website transformation.
Strategy, interface, governance and implementation are treated as one operating problem rather than separate deliverables.
11 / Follow the evidence
Evidence connected to XO3D website transformation.
Each link adds a different layer of first-hand evidence rather than repeating the same page under another keyword.
12 / Clear answers
XO3D website transformation: practical questions and answers.
Practical answers about the build, its use and its limits.
What changed in the XO3D website rebuild?
The public estate moved from a legacy WordPress and Elementor engine to a structured Astro platform.
How large is the estate?
At the 22 July 2026 verification, it contained hundreds of crawlable routes across services, proof, guides, research and conversion.
Does the case claim search or lead growth?
No. It proves the platform, migration and discovery foundations, not attributed commercial lift.
Are private client projects shown?
No. Public-safe or staged visual material is used in this case study.
Need to turn a legacy site into an authority platform?
Creative direction, Website architecture, Astro development, Technical SEO
A buyer-journey, search and measurement audit followed by a prioritised build brief. Handover: the findings, a prioritised plan and the evidence needed to decide the next step. Scope and schedule are agreed after the fit conversation.
Live migration, builds, route QA, analytics and search checks
Creative direction / Website architecture / Astro development
Need to turn a legacy site into an authority platform?
Thomas can connect creative direction, information architecture, migration, search and conversion without losing the evidence already earned.