Content, localisation and search presentation

Site Content collections

Site Content is God-only and manages database-backed testimonials, FAQs, client logos, homepage statistics and section or page settings. The list shows stable keys, order and published/hidden state. Create or edit the appropriate type rather than changing translation source files through this screen. Collection records support reordering; settings do not. Create and update actions record a reason and before/after audit data. Keep content factual and use only claims approved by the owner.

1. Choose the collection that owns the public content and locate the record by its key.
2. Edit or create the item with the required locale values and type-specific fields.
3. Save, then check its audit event and public placement before considering the change complete.

Localised copy

The content editor requires payloads for ten configured locales: English, French, Spanish, German, Portuguese, Russian, Chinese, Japanese, Hindi and Arabic. Every locale structure is validated as an array; an omitted locale can block the save. Write idiomatic copy rather than literal word-for-word translations, preserve the same approved meaning, and keep executable identifiers unchanged. Arabic is right-to-left on the site; review direction and punctuation in context. This database content is distinct from the application translation catalogue.

1. Prepare the full set of locale values for the selected item before opening Save.
2. Check terminology, placeholders, punctuation and Arabic right-to-left presentation for each translation.
3. If validation fails, fill the missing locale structure and resubmit; do not replace translations with empty strings.

Type-specific fields and ordering

Testimonials and client logos use image references; a client logo also requires width and height. Homepage statistics require a display value and may include an icon. All collection records can carry a sort order and publication state. Reorder by setting positions on the collection list and providing a reason; the page stores the new sequence. A settings entry uses an area, key and per-locale values, and its key must be unique within that area. Use concise stable keys, not customer names or secrets.

1. Check required media, dimensions, display value, area and unique key fields for the selected type.
2. Enter positions in the collection list and provide a meaningful reason before saving the order.
3. Refresh the list and public page to confirm both the saved order and expected content.

Publishing and review

Saving an item and publishing it are separate steps. The list marks each record Published or Hidden, and the publish action requires a reason. Use Hidden while copy is incomplete or awaiting review; publish only when all locale versions and media have been checked. If a page still shows old content after publication, confirm that you edited the intended key and locale and that the public page uses that data-backed section. Do not create duplicates to work around a stale display.

1. Save the complete draft and inspect the list for its key and hidden/published state.
2. Use the publication control with a clear reason once all locale and media checks pass.
3. Open the public page in the affected locale and verify that the correct item appears in the intended position.

SEO and public metadata

Some content areas have dedicated SEO title and description fields, including knowledge-base articles and AI hosting catalogue records. These fields are not a global SEO editor, and the Site Content page does not expose every page’s metadata. Enter a concise title and accurate description in the record that owns the page, then inspect the rendered page metadata through the relevant view. Avoid unsupported claims, repeated keyword lists and private infrastructure details.

1. Open the specific article or catalogue record and locate its SEO title and description fields.
2. Write a clear, accurate title and description within the field limits and save the record.
3. Inspect the resulting page title and snippet metadata; correct truncation or mismatch at the source.

Offices and careers content

Office locations are presented by the public Offices page; maintain their approved source data through the relevant owned content process and verify the localised page after an update. Recruitment administration has its own categories, job positions, application questions and referral codes. Job copy and referral biographies can appear publicly, so keep dates, locations, salary currency and referral text accurate. Applications contain personal data and belong in the restricted Recruitment workflow, not in public content fields or documentation.

1. Identify whether the change belongs to a public office listing, a job position or a referral record.
2. Update only the relevant content through its authorised editor and retain required locale or salary fields.
3. Check the public office or careers page and confirm sensitive application details remain in the protected staff workflow.

Frequently asked questions

Related pages

• Administration and access control
• Encrypted backups and recovery
• Commercial and finance administration
• AI, hosting and service catalogues
• People, teams and recruitment
• Service operations and monitoring
• Support desk and knowledge operations