Why Your Organization Needs a /open Page
Your site already has /about and /contact. Add /open.
Most organizations treat their website as a storefront with three fixed stops: who we are, what we sell, and how to reach us. Visitors learn the story, scan the services, and fill out a form. That structure worked when data lived behind a request desk. It does not work when researchers, journalists, civic technologists, and partner teams arrive looking for your datasets first.

A dedicated /open page gives those visitors one obvious destination. It sits beside /about and /contact as a peer, not as a buried subpage of either one. The URL itself signals intent: here is what we share, here is how to use it, here is where to ask questions.
Visitors arrive with dataset questions, not marketing questions
Someone hunting for your open data is not interested in your mission statement. They want to know what files exist, what formats they come in, how often they refresh, and what license governs reuse. If that information is scattered across blog posts, PDFs, and a legacy portal, most visitors leave before they find it.
A /open page answers those questions in one scroll. It names the collections, links to the download or API endpoints, and states the terms in plain language. The page becomes the front door for a audience your /about page was never designed to serve.
If a visitor cannot find your datasets in two clicks, they will assume you do not publish any.
What belongs on a /open page
The page does not need to be long, but it does need to be complete. Treat it as a directory with context, not a press release. Every item should help a stranger decide whether your data is useful to them.
- A short statement of what your organization publishes and why.
- Direct links to datasets, APIs, and bulk downloads.
- Update frequency and the date of the last refresh.
- License terms and attribution requirements.
- A contact route for data questions, separate from general inquiries.
Keep the language concrete. "Monthly air quality readings since 2015, CSV and JSON, CC BY 4.0" tells a visitor more than three paragraphs of policy prose.
Why the page earns its own URL
Search engines and institutional directories treat distinct URLs as distinct resources. A /open page can rank for queries like "your organization open data" and "your organization datasets" that an /about page will never win. It also gives partners a stable link to cite in reports, papers, and internal wikis.
Internally, the page creates accountability. Once the URL exists, someone owns it. Datasets get reviewed, licenses get checked, and stale links get fixed because the page makes the gaps visible.
Make /open a permanent stop on your site
Add the link to your main navigation and your footer. Reference it from /about and /contact so visitors can move between the three stops naturally. Then keep it current, because an open page that lists dead endpoints is worse than no page at all.
Your organization already explains who it is and how to reach it. Now explain what it shares. A /open page turns scattered files into a public resource and turns curious visitors into actual users of your data.
