Most VC directories combine three sources: a maintained editorial sheet of funds the team has researched, a partner data feed from a provider like Pitchbook or Crunchbase for AUM and recent investments, and public sources like fund websites and partner bios. SleekRank reads whichever combination you produce as the unified dataset, then publishes per-fund pages from that single source of truth.

Use a partners column that's either a comma-separated list or a JSON array of partner objects with name, title, and focus. Update the source dataset when partners join, leave, or change focus. The per-fund page renders the current partner list, and a per-partner page group can run alongside to build /vc/partner/{slug}/ pages for high-profile partners with their own SEO surface.

Emerging manager funds, often Fund I or Fund II from a new GP team, can have their own page group at /vc/emerging-manager/{slug}/ or be flagged within the main directory via a vintage column. Emerging managers are a meaningful subset of VC search traffic because LPs actively hunt for first-time or second-time fund opportunities, so giving them their own surface makes sense.

Add a portfolio column with company names or use a separate portfolio dataset keyed by fund slug. Render the portfolio via list mapping with optional links to a portfolio-company page group. Most VC directories cap the rendered portfolio at the top 10-20 named investments to avoid overwhelming the page; the rest are accessible via a See full portfolio expandable section.

Yes. The warm-intro CTA on each fund page can deep-link to your platform's intro request flow, a third-party intro service like Lunchclub, or a portfolio-founder routing where the system identifies a portfolio founder who can make the intro. SleekRank renders the link; the intro flow runs elsewhere.

VC AUM changes when a fund closes a new vintage, typically every 2-4 years per fund. The dataset should update within days of a fund closing announcement to keep AUM current. Some funds also rebalance reported AUM annually as portfolio companies mark up or down; if you want that fidelity, integrate with a paid data provider that tracks fund-level NAV updates.

Set a status flag to wound-down once a fund stops new investments and has fully distributed back to LPs. These funds move to /vc/archive/{slug}/ which preserves the historical record of portfolio outcomes, useful for LP due diligence on follow-on funds from the same GPs.

Add a thesis or focus_area column with short tags like dev tools, fintech infrastructure, climate, vertical SaaS. Run a per-thesis page group at /vc/thesis/{slug}/ that filters to funds with that thesis. This catches narrower searches than per-sector pages, like founders looking specifically for fintech-infrastructure investors rather than generic fintech investors.