Serve distinct audiences clearly
A buyer needs service scope, a partner needs documents and a candidate needs a vacancy and application path. Putting everything into one long page makes each task harder. We organise the site around these journeys, connecting business directions, services and supporting projects.
For a company group, agree which brands, legal entities and details can be published. Each enquiry needs an owner, and each business claim needs someone responsible for confirming it.
Content types and editorial ownership
The agreed scope may include services, projects, news, staff, vacancies, documents, search and departmental contacts. Each service explains its own task and boundaries. Photographs and certificates require publication rights and a factual basis.
The CMS separates drafting, fact checking and publication where required. Frequently changing information needs a named owner: contact details and vacancies should not remain stale indefinitely. Approval workflows are specified rather than assumed.
Languages, search and migration
RU, KK and EN need equivalent pages and descriptions. A document available in one language should be labelled honestly. Internal search is tested against actual service names and company abbreviations. Files need meaningful names and access rules.
Map important old addresses to corresponding content before replacement. Do not redirect every deleted page to the homepage. Canonicals and sitemaps should describe the real structure, without artificial keyword pages.
Documents need purpose, language and version information. Agree what happens to old links when a presentation or instruction changes. Partner-only files may require separate controlled access; sharing a CMS does not make public pages and private storage the same product.
Delivery and acceptance
Inventory the content, agree the page map and prototype representative templates. Staff then try publishing a service, news item and document in a test environment. Check translations and migration before switching the domain.
- Visitors find the correct service and department.
- Editors publish only within their permissions.
- Search and documents work on mobile.
- Business details and image rights are approved.
- Important old URLs reach equivalent new content.
Project questions
How is this different from a brochure site?
A corporate site serves more audiences and business directions, with additional content types and editorial roles.
Can an internal catalogue supply website data?
Where access and publication rights exist. We first check its structure, update frequency and private-data boundaries.
Can news require approval?
Yes, when included in scope. Roles, statuses, publication rights and revision handling are agreed explicitly.
Illustrative image