An investor relations website can contain every document a visitor needs and still be difficult to use.
The problem is often not missing information. It is navigation.
A company may have current financial reports, detailed project pages, recent announcements, management biographies, and a strong corporate presentation. Yet if those materials are spread across vague menu categories, buried several levels deep, or labeled in language that only makes sense internally, the website becomes harder to trust.
Visitors do not experience the website as a collection of content-management decisions. They experience it as a single question: can I find what I came here for? When the answer is yes, the navigation disappears into the background. When the answer is no, the visitor starts guessing.
Good IR website navigation has less to do with keeping the menu short and more to do with organizing the company the way external visitors actually think about it.
Navigation should reflect investor questions
The first mistake companies make is organizing the website around departments. Internally, it may feel natural to divide information into corporate affairs, operations, finance, governance, and communications — those categories reflect who owns the content.
Investors do not care who owns it. They care where to find it.
A visitor arrives with questions: What does the company do? What assets or products does it own? What has happened recently? Where are the latest financial statements? Who runs the company? Where is the current corporate presentation? The navigation structure should answer those questions directly.
This is why labels such as “Corporate,” “Resources,” “Information,” and “Media” cause trouble — they can mean almost anything. “Investors,” “Projects,” “Financial Reports,” “Governance,” “News,” and “Contact” tell visitors what they are likely to find before they click. Clear labels reduce interpretation.
Start with the company’s real information hierarchy
Navigation design should not begin with menu labels. It should begin with the company’s information hierarchy: the main parts of the business, the most important investor materials, and the relationships between them.
A mining company may have one flagship development project, two earlier-stage properties, a corporate presentation, technical reports, financial statements, news releases, governance documents, and management information. The navigation should show which of those elements are central and which are supporting. If the flagship project is the primary reason investors visit the website, it may deserve direct visibility in the main navigation, while smaller properties sit under a broader “Projects” section.
The same principle applies outside mining. A biotechnology company may organize around a pipeline, a technology issuer around products, markets, or solutions, an operating company around divisions, facilities, or regions.
Navigation is a form of prioritization. What appears at the top tells the visitor what matters most.
The homepage is not a substitute for navigation
Some websites try to solve structural problems by loading more content onto the homepage. The menu stays vague, but large sections direct visitors to projects, reports, governance, news, and presentations.
That may help temporarily, but it does not fix the underlying issue, because not every visitor enters through the homepage. An investor may land on a news release from an email. An analyst may arrive directly on a project page through search. The website still needs to make sense from those entry points.
The homepage can introduce and prioritize. The menu should orient. Internal links should guide. Those are related but different jobs.
Keep the top-level menu focused
A crowded top-level menu makes everything feel equally important. When visitors see ten or twelve primary items, they have to weigh too many options before making a decision. The top level should represent the company’s main content groups rather than every individual page.
A public-company structure might include:
- About
- Projects or Business
- Investors
- News
- Governance
- Contact
This is only a starting point. The right number is not fixed; the goal is a small set of distinct choices. Each top-level item should have a clear purpose — if two menu items routinely contain similar content, the distinction is probably weak.
Structure should follow content volume and visitor behavior rather than copying another company’s menu.
Make the investor section practical
The investor section is often treated as a container for everything that does not fit elsewhere, which leads to long dropdowns holding overview, presentation, financials, filings, stock information, share structure, events, governance, news, analyst coverage, FAQs, email alerts, and contact information.
There is nothing inherently wrong with including these items. The trouble starts when they are presented as a flat list without hierarchy.
The investor section should reflect the most common research paths. A useful structure may separate current materials, financial information, and shareholder resources, so that the current presentation and latest results are easier to reach than an old event replay or an archived filing.
Good navigation requires editorial judgment.
Separate current information from archives
One of the most important structural decisions is the separation between current and historical content. Investors may need access to old reports, presentations, and announcements — that does not mean historical materials should compete with the latest version.
A presentation page should feature the current deck clearly, then provide access to an archive. A financial section should make the latest reporting period obvious before displaying previous years. An events section should distinguish upcoming events from past replays.
This separation improves both speed and credibility. When current and historical materials look identical, visitors have to verify dates manually; the navigation should tell them the status before they click.
Build project navigation around importance and scale
Project-heavy companies face a particular challenge. A business may begin with one main asset and add several more over time, and the menu grows with each acquisition until the project dropdown becomes a list of names that means little to anyone unfamiliar with the portfolio.
A stronger structure introduces hierarchy. If the company has one clear flagship asset, that project may be highlighted separately, with other projects grouped by region, commodity, development stage, or strategic role. The grouping should help investors understand the portfolio, not simply reduce the number of menu items.
The project landing page can carry far more context than the menu ever could. The navigation’s job is to get the visitor there.
Do not hide essential pages inside dropdowns
Dropdown menus are useful, but they can also hide the website’s most important pages. On desktop, visitors may need to hover before discovering a section; on mobile, they may need to tap several times and expand nested levels. Important pages should not depend entirely on a hidden interaction.
The top-level label itself should usually lead to a useful landing page. Clicking “Investors” should open an investor overview rather than doing nothing. Clicking “Projects” should open a portfolio summary rather than forcing the visitor to choose an unfamiliar project name immediately.
Landing pages provide orientation.
Limit navigation depth
Every additional level adds friction. A visitor should not need to move through Investors → Reports → Financial Results → 2026 → Third Quarter before reaching a document list.
Most public-company content fits comfortably within two meaningful levels. The menu should get visitors to the right area; the page should help them find the specific item. Trying to place the full content hierarchy inside the navigation produces oversized dropdowns and poor mobile behavior.
Use labels investors recognize
Creative menu labels may suit a consumer brand, but on an IR website they mostly create ambiguity. “Discover,” “Our Journey,” “Value Creation,” and “Knowledge Center” may sound distinctive; they also force the visitor to guess what is inside.
Investors recognize labels such as About, Projects, Operations, Investors, Financial Reports, Governance, News, Sustainability, and Contact. Familiar language is not boring when it helps people move efficiently.
The same applies to buttons and document links. “View Q2 2026 Financial Statements” is more useful than “Learn More.” Specific labels reduce uncertainty and improve accessibility.
Design navigation for mobile from the beginning
Desktop navigation can hide structural weaknesses. Mobile exposes everything: nested menus require repeated taps, large dropdowns become long vertical lists, parent pages become hard to reach, and important links sink below secondary content.
Mobile navigation deserves its own design attention rather than being treated as a compressed version of the desktop menu. Each section should open clearly, expanded states should be obvious, and the visitor should be able to move back without losing their place.
Testing should involve real tasks. Can someone find the latest financial report with one hand, standing on a train platform? Can they open the project page from a news release? A navigation system that technically fits on mobile may still be frustrating to use.
Use internal links to support the menu
The main navigation should not carry the entire user journey; internal links matter just as much. A news release about a drilling program should link to the relevant project page. A project page should link to the technical report and current presentation. A financing announcement may link to the investor overview and share structure.
These connections help investors move through the company story naturally. When internal linking is weak, every page becomes a dead end. Thoughtful internal links answer the likely next question.
Provide orientation on every major section page
Section landing pages should explain where the visitor is and what the section contains. An investor overview may feature the current investment proposition, latest presentation, recent financial results, stock information, upcoming events, and investor contact. A project landing page may show the portfolio map, flagship asset, development stages, relevant reports, and recent project announcements.
These pages reduce the need to overload dropdown menus with every destination, and they create a better experience for visitors arriving through search.
Search should support navigation, not replace it
A search function is useful on a large IR website, especially when years of news releases, reports, and technical documents are available. It should not have to compensate for a confusing structure — nobody should be forced to search for basic items such as financial statements, corporate presentations, or management biographies.
Search earns its keep in specific research. The results should include meaningful titles, dates, and content types, and should help visitors reach detailed or historical content quickly.
Navigation should survive future growth
A navigation structure should fit the company today and accommodate what is likely coming. What happens if another project is acquired? When the company begins reporting production? If a second exchange listing is added?
The answer should not be “add another top-level menu item” every time. A strong structure has room to grow because related content already has a logical home. Navigation should reflect the current story while leaving space for the next chapter.
Test the structure with real tasks
Internal teams are usually too familiar with the website to judge its navigation accurately. They know where everything is. New visitors do not.
Ask someone unfamiliar with the site to find the latest corporate presentation, the most recent financial report, the flagship project overview, the investor contact, a specific announcement, and the board of directors. Do not explain where anything is. Watch the path they take, where they hesitate, and which labels they misread.
If several people pause at the same place, the problem is probably the structure rather than the user.
Do not copy a competitor’s menu without understanding it
Reviewing other public-company websites can be instructive. Copying their navigation rarely is. Another company may have a different business model, reporting volume, regulatory environment, internal team, and investor audience — and its structure may simply be poor.
The structure should be proportional to the business. A company with one project and a modest number of documents can still present itself credibly with a focused navigation system. Clarity feels more established than unnecessary scale.
Governance placement requires judgment
Governance content can sit either as a top-level section or within the investor section, and both approaches can work.
A separate governance item may be appropriate when the company has substantial content, several committees, and a broad policy library. Placing governance under investors may suit a smaller issuer where the content is important but limited.
Either way, the navigation should represent the actual content honestly.
Use visual hierarchy inside large menus
Some companies genuinely need larger menus. When a dropdown contains many items, visual hierarchy makes it easier to scan: group related links under clear headings, separate current investor materials from shareholder services, and highlight the flagship project without making every project compete equally.
Mega menus can serve complex organizations well, but they should not become miniature homepages. Their role is still navigation.
The footer should reinforce the structure
The footer cannot replace the main menu, but it provides a dependable secondary route. It may include links to the investor overview, financial reports, news releases, governance, contact details, privacy policy, legal notices, and email alerts.
Rather than duplicating every page on the site, the footer should reinforce the most important destinations and the required legal information.
Navigation and content ownership are connected
A clean structure is difficult to maintain when nobody owns the sections. Each major content area should have a responsible person or team.
Without ownership, navigation gradually breaks down: new pages are added wherever convenient, duplicate document sections appear, and old items remain visible because nobody is sure whether they can be removed.
Information architecture needs an operating model, not just a design deliverable.
A clear structure makes the company easier to understand
The best IR website navigation does not draw attention to itself. It makes the company feel organized.
The visitor can understand the business, move into the relevant project or product, review the latest documents, and verify the people and governance behind it — without having to learn the website before they can learn about the company.
A public company may be complex. Its website does not need to feel that way.
