An investor relations website is the place where shareholders, analysts, journalists and potential investors go to check a listed company's facts. If the financial results are hard to find, the annual report is a scanned PDF, or the Arabic and English versions do not match, the company loses credibility before anyone speaks to the management team. This checklist covers what a listed company in the Middle East should publish, how to organise it, and what to build so the site stays accurate over time.
What investors expect to find on your site
Most visitors arrive with a specific question. They want the latest share information, the most recent results, the governance structure or the reason behind a recent announcement. A good investor relations website answers those questions in two or three clicks. It does not try to sell the company's products on the same pages.
Use this list as your starting point:
- Company overview: a short, factual description of the business, its segments, its main markets and its leadership team with roles and biographies.
- Financial results: quarterly and annual results, with the full statements available as downloads and key figures summarised on the page.
- Annual and interim reports: archived by year, so a researcher can compare figures across periods.
- Shareholder information: share capital, listing details, major shareholders where disclosure rules require them, and dividend history.
- Governance: board members, board committees, the company's articles or bylaws, and the code of conduct.
- Financial calendar: dates for results releases, general assembly meetings and investor briefings.
- Press releases and announcements: every official release, dated and filed in the same place as the regulatory notices.
- Contact details for the IR team: a named function or mailbox, not only a general contact form.
Plan the document library before the design
Most delays in investor relations projects come from documents, not code. Before anyone designs a page, agree on a document register: every filing, its type, its period, its language, who approves it and where the official copy is stored. The website should pull from that register, so a result published on the regulator's portal and on your site is the same file with the same date.
A simple structure works well. Each document needs a title, a category such as results or governance, a reporting period, a publication date, a language flag and a file. Store the original file once and generate the web listing from the metadata. This avoids the common problem where the Arabic annual report on the site is a different version from the one filed.
Bilingual content is a publishing workflow, not a translation task
Many listed companies in the region publish in both Arabic and English. The mistake is to treat the second language as a copy written later. Financial terms, company names and dates must match exactly across both versions, and both need approval before going live.
Build the site with a proper localisation structure from the start. Arabic needs right-to-left layout, correctly mirrored navigation and number formatting that matches the local convention your finance team uses. Our approach to bilingual sites is described in our article on building bilingual Arabic and English websites with Laravel, and the same principles apply to investor pages.
Recommended page inventory
| Section | What to include | Typical update frequency |
|---|---|---|
| Home | Latest announcement, key share facts, next event date | Weekly or when news is released |
| Results and reports | Quarterly and annual results, reports archive | Each reporting period |
| Shareholders | Capital structure, listing details, dividends | When corporate actions occur |
| Governance | Board, committees, bylaws, code of conduct | When appointments change |
| News and announcements | Press releases with dates and categories | As issued |
| Financial calendar | Results dates, general assemblies, briefings | Quarterly review |
| IR contact | Named team contact, request form | Yearly check |
Features that save the IR team time
A static set of pages is enough on launch day. Within a year, the IR team will want a few features that reduce manual work:
- A content management panel for news, documents and calendar entries, with approval steps so a draft is never published by accident.
- Email alerts so subscribers receive a notice when a new result or announcement is published.
- Document search that filters by year, category and language.
- Versioned documents so a corrected filing replaces the old file while the history remains visible.
- Audit logs that record who uploaded or changed each item and when.
- Accessible downloads with clear file sizes and formats, so users on slower connections can still get what they need.
Security, performance and access
An investor site is a target for impersonation. Anyone can create a convincing copy of a results announcement. Protect the platform with role-based access, two-factor authentication for publishers, and a clear rule that official announcements are published only from the controlled panel. Keep the site on HTTPS, monitor uptime, and test the site under load before results day, when traffic spikes sharply.
Performance matters more than designers expect. Journalists and analysts often open many large PDFs in quick succession. Serve files through a content delivery network, keep page weight low, and make sure the results page loads in a few seconds on a mobile connection.
How to build it in practice
Phase 1: Content and register (two to three weeks)
Map the existing documents, agree the register, approve the page inventory and confirm the bilingual terminology.
Phase 2: Design and build (four to eight weeks)
Build the public pages, the document library, the calendar and the publishing panel. Test right-to-left layout and both language versions on desktop and mobile.
Phase 3: Migration and go-live
Import historical filings with their metadata, check every link and file, then launch outside the results window. Set up monitoring and alerts before the first live announcement.
Phase 4: Maintenance
Agree a support plan with response times for urgent fixes, and review the content register after every reporting cycle.
Our work on the Enseval corporate and investor relations website shows how a bilingual group site can present operating businesses and investor information side by side without making either hard to find. For the broader approach to building and running a corporate site, see our web systems engineering services.
Common mistakes to avoid
- Publishing a PDF that differs from the filed version, with no version history to explain the change.
- Leaving the Arabic site as a partial translation of the English one.
- Hiding the financial calendar, which is one of the first things analysts check.
- Giving no one clear ownership of the content, so updates wait for a developer.
- Launching the site a week before results, with no time to test under real traffic.
If you are planning a new investor relations website or redesigning an existing one, contact us with your current document list and your target languages. We will map the register, the page structure and a realistic timeline before you commit to a build.
Frequently asked questions
What should an investor relations website include?
At minimum it should include a company overview, financial results and reports, shareholder and listing information, governance details, press releases, a financial calendar and an IR contact. Requirements vary by market, so confirm the disclosure rules that apply to your listing with your legal or compliance advisers.
Should an investor relations website be bilingual?
If your shareholders, analysts or regulators use both Arabic and English, yes. Both versions should carry the same figures and dates, and both should go through the same approval process before publication.
How long does it take to build an investor relations website?
A focused corporate IR site with a document library and a publishing panel typically takes a few months, depending on the volume of historical documents and the number of languages. Most of the time is spent on content and document migration rather than on the code.
Who should maintain the investor relations website?
The IR or finance team should own the content, with a named approver for each category. A technical partner should maintain the platform, apply security updates and handle urgent fixes under an agreed support plan.
Can a standard corporate website serve as an investor relations site?
A standard site can present the basics, but it usually struggles with document versioning, calendar management, alerts and audit trails. If your filings are frequent and your audience is wide, a dedicated IR module or a custom section is usually worth the investment.
