The new Product Marketing Specialist is hired to write landing pages, SEO content and activation flows. But the pages that matter most for that job are empty to anything that does not run JavaScript: the homepage, /pricing, /signup and every symbol page in the catalog return the same 17.9 KB shell titled just "Databento" with the text "You need to enable JavaScript to run this app". The sitemap hands search engines 1,564 of those catalog pages, and AI assistants' crawlers and link previews (Slack, LinkedIn, X) mostly read the raw HTML, so they see the shell, not the data coverage. The futures, options, tick-data and docs pages are already full HTML, so the team has a working pattern to copy.
First action
Prerender the NVDA, ES and SPY catalog pages and compare what a plain request returns before and after.
How to measure it
Organic sessions to catalog pages
- Now
- –
- Target
- 5x
- By
- 2 quarters
Steps
Confirm the gap
Fetch ten catalog pages, the homepage and pricing with JavaScript off and log what search and AI crawlers receive.
Product Marketing Specialist 1 day
Pick the method
Prerender at build time or server-render the React routes, reusing the stack behind /futures and /docs.
Software Engineer (TypeScript/JavaScript) 3 days
Template the metadata
Title, description, H1 and Dataset schema per symbol from the catalog data.
Product Marketing Specialist 3 days
Add page content
Schemas available, history start date, venue, a code sample and links to the dataset page.
Software Engineer (TypeScript/JavaScript) 1 week
Fix soft 404s
Unknown symbols return 404 instead of 200.
Software Engineer (TypeScript/JavaScript) 1 day
Static pricing table
Plans and per-GB historical rates in HTML on /pricing.
Product Marketing Specialist 2 days
Resubmit and watch
Submit the sitemaps in Search Console and track indexed pages and clicks weekly.
Product Marketing Specialist weekly
Why it works
Prerender (or server-render) the homepage, pricing and catalog templates the same way the marketing pages are built. Give every catalog page its own title and description from data Databento already has, e.g. "NVDA tick data: Nasdaq TotalView-ITCH order book, trades and OHLCV, history from 2018 | Databento", a short HTML summary of schemas, history start and a sample query, and Dataset structured data. Return a real 404 for symbols that do not exist. Then rewrite pricing as a static table of the plans and per-GB historical pricing so it can be quoted and linked.
Searches for "<ticker> tick data", "<futures root> historical data" and "<venue> order book API" are exactly what quants and developers type, and each of the 1,564 pages already exists as a target. Readable pages can rank, be cited by AI assistants and unfurl properly when a quant shares a link in a team chat, without new content being written.
Ready to use
ChecklistCatalog page launch list
[ ] Plain HTTP request returns the symbol name, venue and history range [ ] Unique <title> and meta description per symbol [ ] Dataset structured data [ ] Code sample in Python visible in HTML [ ] Unknown symbols return 404 [ ] /pricing table readable without JavaScript [ ] Link previews tested in Slack and LinkedIn [ ] Search Console: indexed count tracked weekly
Risks and how to handle them
Prices or coverage go stale in HTML
Rebuild pages nightly from the same source the app uses.
Thin pages across thousands of symbols
Lead with the unique data (history range, schemas, sample) and keep pages that have real coverage only.
Evidence
- HiringProduct Marketing Specialist (remote, open on Greenhouse, updated November 2, 2026): "Write and review landing pages, activation flows, and sales copy to drive engagement and conversion"; "Drive product marketing initiatives, including positioning, messaging, and launch campaigns"; "Plan and execute content and social distribution (blogs, LinkedIn, X/Twitter, founder amplification)"; work "with product, sales, and growth teams on experiments, campaigns, and activation strategies"; writing samples should include "landing pages, blog articles, SEO content". The role will "help shape the marketing function at Databento".Source
- Your websiteChecked November 4, 2026 with a plain HTTP request: the homepage, /pricing, /signup and the symbol catalog pages (for example /catalog/us-equities/XNAS.ITCH/stocks/NVDA) all return the same 17.9 KB page whose only title is "Databento" and whose only text is "You need to enable JavaScript to run this app", with the same generic description on every one. A made-up symbol (/catalog/us-equities/XNAS.ITCH/stocks/ZZZZZ) also answers 200 with that page. Nothing on these pages is readable without running JavaScript.Source
- Your websiteBy contrast the marketing and docs pages are full HTML with their own titles: /futures ("Futures Market Data - Live and historical futures data API", 430 KB), /options, /tick-data, /venues, /datasets/GLBX.MDP3 ("CME Globex MDP 3.0 | CME futures historical & live data API"), /docs and every blog post.Source
- Your websiteSitemap index (14 sitemaps, 2,495 URLs, checked November 4, 2026): 1,564 catalog symbol pages (exactly 500 US equities and ETFs, 200 OPRA options roots, 190 index, 178 CME, 186 Eurex, 100 ICE Europe and 95 ICE US, among others), 381 docs pages, 185 blog posts, 181 trading-compliance pages, 115 market microstructure pages, 31 dataset pages, 10 customer pages and a /startups page. No page compares Databento with a named vendor except one migration guide for IEX Cloud users; no integrations page; no /llms.txt.Source
- HiringSoftware Engineer (TypeScript/JavaScript): "Own, build, and maintain our JavaScript client library, ensuring it is robust, well-tested, and easy for external users to integrate with", including "publishing to npm"; also front-end work in React, Redux and Vite and translating Figma designs into "production-ready components and design systems". Today the official client libraries are Python, C++ and Rust, and no Databento package is listed on npm.Source