Use an investor relations website checklist to verify outcomes, not simply to confirm that pages exist. A filings section can be present while its latest document is missing; an event page can look finished while its registration link fails.
For each check below, record a status, evidence, an owner, and any action needed. Use Pass, Fix, or Not applicable, and explain the last category. These are recommended acceptance checks for a website project or periodic review, not a substitute for the issuer's legal requirements register.
Confirm content and ownership
- Company identity matches approved materials, including the issuer name and relevant security identifiers.
- The latest results package contains the intended documents and accurate period labels.
- Current and historical presentations are clearly distinguished.
- Investor and transfer-agent contacts, where provided, have been verified by the responsible owner.
- Every recurring content category has an approver, publisher, and backup contact.
Begin with the content planning guide if the inventory itself is incomplete. Do not mark a category complete merely because its menu item exists.
Check filings and governance
- Filing links open the intended issuer and document, with amendments handled clearly.
- A reader can reach the official SEC record if the integrated archive is unavailable.
- Governance documents match the versions approved by the corporate secretary or legal team.
- Required posting dates, retention obligations, and disclosure channels have been confirmed for this issuer.
The SEC's search service provides a direct way to verify the original filing record. [1] Compare the website against that record during acceptance; a screenshot of the feed's configuration is not sufficient evidence that the public output is correct.
Walk through the investor experience
- Find current results and an older reporting period from the homepage.
- Reach and operate navigation, filters, and forms with a keyboard.
- Check visible focus, zoomed layouts, link descriptions, and form error messages.
- Review the accessibility of representative PDFs, presentations, and third-party tools.
- Test the event journey from announcement through registration and, where available, replay.
Include knowledgeable human evaluation. W3C says an automated tool alone cannot establish website accessibility. [2] Record the pages and processes tested, the method, and unresolved issues rather than relying on a single score.
Verify publishing and production controls
- Stage a realistic update and confirm that only approved content reaches the public site.
- Verify the launch configuration does not expose confidential drafts or test subscriber data.
- Confirm administrator access, offboarding, and recovery responsibilities.
- Obtain evidence of a backup restoration exercise appropriate to the service.
- Document who can roll back a release and who decides whether rollback is appropriate.
Use the hosting and security guide to define the evidence expected from the technical operator. A list of available platform features does not show which controls are actually enabled for the site.
Check discovery and ongoing support
- Important pages have distinct titles, useful headings, and appropriate internal links.
- Public pages intended for search have the intended indexing settings.
- Old URLs have been mapped where a move is involved, and linked documents have been checked.
- Analytics and webmaster-tool access belong to the company or are contractually transferable.
- Monitoring covers key investor tasks, with named contacts and an escalation process.
Google explains that a crawler must be able to access a page to read its noindex instruction. Review crawl rules and indexing rules together. [3]
Make the final decision explicit
Group findings by consequence: incorrect public information, blocked investor tasks, operational gaps, and presentation improvements. Name the person authorized to accept any remaining issue and its remediation date. A checklist should produce a decision and an action log.
For a first public launch, add the IPO checklist. For a platform change, add the migration checklist, which deals with exports, redirects, and cutover evidence.
Questions companies ask
Can this checklist certify compliance?
No. It supports website review. The applicable legal requirements and any conformance claim need their own documented assessment.
Should every check happen before launch?
Complete the launch-relevant checks before acceptance. Schedule recurring checks for content and services that continue changing afterward.
What counts as evidence?
Use tested URLs, dated approval records, completed user journeys, and restoration or monitoring records. Match the evidence to the check.
Who resolves a failed check?
Assign one accountable owner and a due date. If several providers are involved, name the person coordinating the resolution.
Bring the completed findings to VendorGroup when scoping improvements. Specific failures make the next website brief more useful than a general request for a refresh.
Related VendorGroup resources
- What Should an Investor Relations Website Include?
- Investor Relations Website Best Practices
- IPO Investor Relations Website Checklist
- Investor Relations Website Migration Checklist
