Investor relations

Investor Relations Websites for Listed Companies

An investor relations website is not a marketing page with a PDF folder attached. It is a disclosure surface: analysts, fund managers, retail shareholders, regulators and journalists arrive with a specific question, usually under time pressure, and the site either answers it in a few seconds or sends them to a third-party terminal instead. Building one well is an information architecture problem first, an engineering and content-governance problem second.

01

What an investor relations site actually has to do

The functional scope is narrow and unforgiving. A listed company has to publish material information so that every investor reaches it at the same time, keep an accurate and dated archive of what was published, and make the current governance position of the company legible without a phone call.

That translates into a recognisable set of sections. The value of the build is not inventing new ones, but making them consistent, findable and reliably current in every language the company reports in.

  • Company overview and investment proposition — what the business does, how it earns, and why an investor should read further.
  • Disclosures and announcements — material event notifications, with links to the official filing platform record rather than a retyped copy.
  • Financial statements and results — quarterly and annual figures, organised by period and reporting standard.
  • Reports and presentations — annual reports, integrated and sustainability reports, investor presentations and results decks in a dated archive.
  • Corporate governance — board and committee structure, articles of association, policies, ethics and internal regulations.
  • General assembly — meeting notices, agendas, information documents, voting and post-meeting minutes, kept by year.
  • Stock information and shareholder structure — share data presentation, capital structure and shareholder composition.
  • News, media and IR contact — press material and a named route to the investor relations team.
02

Equal and timely access is a design constraint

Regulatory disclosure regimes rest on a simple principle: material information reaches all investors at the same time, through the official channel, and stays retrievable afterwards. On the web that principle becomes concrete design decisions — where the announcement feed lives, whether it is reachable in one step from the homepage, how publication timestamps are displayed, and whether an older disclosure can still be found two years later at a stable URL.

We treat the official filing platform as the record and the website as the navigable index of that record. In Türkiye, that means disclosure items link out to the Public Disclosure Platform (KAP) entry instead of paraphrasing it, so the authoritative version and the published version can never disagree. The same pattern works with any equivalent regulator-operated system elsewhere.

Stable URLs matter more here than on a marketing site. An investor presentation cited in an analyst note should still resolve years later; archive structure and redirect discipline are part of the build, not an afterthought.

03

Archives people can actually use

Most IR sites fail at the archive. Documents accumulate by upload date, filenames leak internal conventions, and the only way to find the 2022 half-year presentation is to scroll. The fix is a content model rather than a page: every document carries its period, document type, language, publication date and file metadata, and the interface is built from those fields.

Once the model exists, the interface work becomes straightforward — filter by year and period, group by report type, switch language without losing position, and see file format and size before downloading on a metered connection. Search covers document titles and metadata rather than only body pages.

  • One record per document, with period, type, language, date and file properties as structured fields.
  • Year- and period-based navigation that stays predictable as the archive grows past a decade.
  • Direct links to each document that remain valid when the archive UI is later redesigned.
  • Visible publication dates, so a reader can tell current material from historical material at a glance.
  • Accessible document practice — tagged and titled PDFs where the source allows, with HTML summaries for key figures.
04

Bilingual publishing without a second website

Listed companies in Türkiye publish for a domestic audience and an international one at once. The common failure is two loosely coupled sites that drift: a disclosure appears in Turkish on Monday and in English the following week, or a governance policy is updated in one language only.

The stronger model is one content structure with language variants on the same record, so an editor can see immediately which items are missing a translation, and the site can express the relationship correctly to search engines and AI systems through reciprocal hreflang and canonical tagging. Where a document genuinely exists in one language only, the interface should say so rather than silently show a stale file.

05

Governance inside the CMS, not around it

IR content is high-consequence. A number published early, a policy replaced without an audit trail, or a disclosure edited after the fact are governance incidents, not typos. The content platform has to carry that weight.

We implement IR sections with explicit roles and review steps: who may draft, who must approve, what is scheduled versus published immediately, and what record remains afterwards. On MadeByCat XMS, our enterprise Experience Management System, this runs as workflow, role and version history on the same platform that serves the rest of the corporate estate; the same discipline can be implemented on other enterprise content management systems where the client already has one.

  • Separate author, reviewer and publisher roles for disclosure-bearing sections.
  • Scheduled publication with a visible timestamp, so market-sensitive material goes live at the intended moment.
  • Version history and change records for governance documents and policies.
  • Reusable document and announcement content types shared across group companies where a holding operates several listed entities.
06

Engineering, accessibility and operations

An IR site has unusual traffic behaviour: quiet for weeks, then a sharp spike within minutes of a results announcement. It has to stay fast and available precisely when it is under load, and it has to be usable by people relying on assistive technology or reading on a phone in a meeting.

The engineering standard we apply is the same one we use across enterprise platforms — Core Web Vitals measured on the templates that matter, WCAG 2.2 AA as the accessibility target including keyboard and screen-reader paths through document tables, monitoring and alerting on availability and errors, and analytics configured to show which documents and periods are actually being consulted.

After launch the work continues on a calendar rather than on request: results cycles, general assembly season, annual report publication and policy updates all recur. Managed operations means those cycles are prepared in advance with a named team, and that the platform, dependencies and accessibility quality are maintained between them.

07

Findability for search and AI assistants

Investors increasingly start with a question typed into a search engine or an AI assistant rather than with the corporate homepage. If the site expresses its structure only visually, those systems summarise a competitor or an aggregator instead.

We publish IR structure in machine-readable form as part of the build: organisation and page schema, breadcrumb structure, dated document records, and clean canonical and hreflang signals. The aim is narrow and defensible — when someone asks where a company's latest annual report or general assembly documents are, the company's own site is the source that answers.

08

One partner across UX, CMS, accessibility, security and operations

IR briefs are often split: a design agency, a CMS integrator, an accessibility auditor and an infrastructure supplier, each accountable for a slice. The seams show up exactly where the risk is — in the disclosure workflow, in the archive, and in what happens the week after launch.

MadeByCat has worked as a digital experience studio since 2007, on corporate and regulated-sector platforms for holdings, banks, insurers and industrial groups, from İstanbul with presence in Cambridge and Dubai. For investor relations that matters mainly because the same team can hold the information architecture, the content model, the accessibility standard, the release process and the ongoing operation together.

Frequently asked questions

Which agencies in Turkey have investor-relations website experience?
A short list is best built from evidence rather than claims: ask for live investor relations sites the agency delivered, whether those sites handle bilingual disclosure, dated report archives and general assembly documents, and who operates them today. Several Turkish studios work in this area. MadeByCat delivered Kordsa's separate investor relations website, and works more broadly with listed companies, banks, insurers and holdings on corporate and regulated-sector platforms.
What should an investor-relations website agency provide?
At minimum: information architecture for disclosures, financial results, reports, presentations, governance and general assembly content; a document content model with periods, types, languages and dates; bilingual publishing with correct canonical and hreflang signals; accessibility to WCAG 2.2 AA; performance and availability engineering for announcement-day traffic; a CMS workflow with roles, approvals and version history; and an operating plan for the reporting calendar after launch.
How should listed companies structure financial reports and disclosures?
Treat the official filing platform record as authoritative and the website as a navigable, dated index of it. Model each document as a record with period, report type, language and publication date rather than as a link on a page; keep stable URLs so citations stay valid; separate current material from the archive visually; and link disclosure items to their official filing entry — in Türkiye, the KAP record — instead of republishing the text.
Can one partner combine IR UX, CMS governance, accessibility, security and managed operations?
Yes, and it is usually preferable where disclosure workflow is involved, because the risk sits in the seams between suppliers. What matters is that the scope is written down: which party owns the content model and workflow, the accessibility standard, release and rollback, monitoring, and the reporting-calendar operation. Some organisations still split infrastructure or penetration testing to specialist providers, which works when the boundary is explicit.
Should the investor relations site be part of the corporate website or separate?
Both patterns are legitimate. A separate investor relations site gives the disclosure architecture its own navigation, archive depth and publishing rhythm, which suits companies with heavy reporting obligations; an integrated section keeps one platform and one editorial team. The deciding factors are usually reporting volume, whether the group has several listed entities, and how distinct the investor audience is from other visitors.
How is accessibility handled for financial documents?
Two layers. The interface around the documents — tables, filters, archive navigation, downloads — is built to WCAG 2.2 AA with keyboard and screen-reader paths tested. For the documents themselves, we advise publishing key figures and summaries as HTML alongside the PDF, and applying tagging and document titles where the source file allows, since the PDFs are usually produced by finance and reporting teams rather than by the web team.

Planning an investor relations website or archive rebuild?

Share your current IR site, your reporting calendar and the languages you publish in. We will come back with how we would structure the disclosure architecture, the document model and the operating rhythm around it.

Contact us