Yes. The rest_api source handles authenticated JSON endpoints, so a nightly factsheet feed from a fund admin like SEI, BNY, or State Street maps cleanly into per-fund pages. Configure the auth header in the page-group config and SleekRank fetches on each cache miss. Many teams trigger a manual flush after the EOD feed run rather than waiting for cacheDuration to expire.

Each data source has its own cacheDuration setting. Set it to a few hours during market days, align it with your nightly EOD feed, or flush the cache after a feed run to refresh on demand. NAV updates only matter end-of-day for mutual funds, so a longer cache like 4-12 hours is usually fine and keeps origin requests low during peak traffic.

Top holdings stored as an array per fund row work directly with the list mapping. The list mapping repeats a row template inside the base page for each holding, so you can render a clean table with weight, ticker, and name columns. The same pattern handles country allocation, sector breakdown, or maturity buckets if those live as arrays in the source.

Footers live on the base WordPress page itself, not in the per-fund render, so a single edit to the disclosure language propagates to every fund page on the next render. This is much easier to defend in an audit than tracking edits across dozens of separately built pages, and your compliance team can review and approve a single source of truth rather than a backlog.

SleekRank does not draw charts. Embed your existing chart widget — Highcharts, FusionCharts, or a vendor library from your fund data provider — on the base page and feed it the ticker via a selector or meta mapping. The chart loads client-side with the right symbol on every fund page.

Each generated /funds/{slug}/ URL is a real WordPress page in the sitemap. The base template page is auto-excluded and noindex'd so only fund pages compete in search. This means NSLGX, ATCBX, and the rest each get their own indexable URL targeting the branded ticker query, while the template stays out of the index.

When two funds merge, update the master to point one ticker to the surviving fund and add a redirect_to column the template can use to issue a 301. The page-group config can also handle slug aliases so old URLs continue to resolve. For reorganizations like share class consolidations, the same approach keeps historical SEO equity while the new structure renders correctly.

Yes. Render a public summary on the SleekRank page and link to a gated PDF download for the full factsheet, prospectus, and SAI. The download URL maps in from a column in the source, so when a new prospectus posts to your CDN the link updates on cache flush. This keeps the page indexable while preserving the gated form for advisor-facing material.