Audience, purpose and journeys
Each important page needs a defined audience, buying moment, purpose and next action.
Build the owned foundation your digital authority depends on.
Orionis plans new websites, redesigns, migrations and replatforming around information architecture, semantic structure, content requirements, search foundations and implementation controls—before production decisions become expensive to reverse.
A polished interface can preserve a structural problem.
Your website is the main source you control. It is where audiences, search engines, AI systems, journalists and partners look for a coherent account of the organisation, its services, expertise and evidence. That owned foundation directly supports Search & AI Visibility.
A redesign can improve appearance while leaving the underlying problem intact. If page purposes overlap, expertise has no clear home or the CMS cannot support the intended publishing model, the new interface may reproduce the old constraints in a more polished form.
Four decisions the foundation must establish.
Settle the meaning before designing the surface. Copy, design and technology can then express an agreed system instead of resolving structural questions independently.
Information architecture and semantic relationships
The taxonomy, hierarchy and URL system give every service, topic, audience and evidence type a clear home.
Content and publishing system
Page types, components and CMS fields should support the meaning the site must maintain: entity, audience, intent, evidence, relationships and review state.
Technical and measurement requirements
Crawlability, rendering, indexation, canonicals, metadata, structured data, accessibility, performance, analytics and consent must be specified and verified.
What the engagement creates.
Website strategy and architecture; a content and component system; an implementation and migration map; and a design-ready prototype with a production brief. The result gives design and development teams an agreed structure to implement—not a polished surface with unresolved foundations underneath.
From current state to verified launch.
Establish the current state — inventory the existing record, technology, content and constraints.
Define the architecture — settle page ownership, navigation, URL structure, journeys and topical hierarchy.
Build the content and component system — give each page and reusable module a defined responsibility.
Prototype the experience — demonstrate the approved hierarchy, content and behaviour before production.
Engineer and validate the live build — verify accessibility, performance, analytics, consent and technical behaviour.
Implementation without ambiguity.
Strategy and architecture
Defined audiences and journeys, page ownership, navigation, URL structure, topical hierarchy and a controlled expansion model.
Production reference
Representative copy, page requirements, reusable modules and editorial rules give the implementation team real content to build.
Engineering responsibility
HTML prototypes guide implementation. The developer remains responsible for maintainable integration, security, accessibility, performance and production behaviour.
Make the important decisions before production makes them expensive to change.
Plan the owned foundation that audiences, search engines, AI systems, journalists and partners can understand and use.
Plan your website foundation