It reads source data on a configurable cacheDuration, which is fine for AUM, expense ratio, and category since those don't change second-by-second. For real-time AUM or NAV, use a separate widget on the base page powered by your fund data API. SleekRank handles structural content like name, ticker, holdings, and benchmark; the volatile fields update client-side.

Store holdings as an array per row with weight, ticker, and name in each element. Then use a list mapping in the page-group config to render them as repeated items inside a holdings table on each fund page. Quarterly N-PORT updates flow through the same source on cache flush, so SPY's top 10 always reflects the most recent disclosure.

Yes. Build separate page groups for Vanguard, iShares, State Street, Invesco, Schwab, and others from filtered views of the same dataset. Each group has its own urlPattern like /etf/issuer/vanguard/ and shares the underlying fund data, so expense ratio changes propagate to both the fund page and the issuer index.

Filter by status in the source feed or remove the row entirely. The page falls out of the sitemap on the next regeneration. If you want to keep historical URLs alive for SEO, leave the row, set a 'closed' flag, and adjust the template to render a wind-down notice with links to similar funds in the same category.

If your source includes a history array, map it into the page through a list mapping that repeats a row per change. Otherwise, link out to the prospectus and keep the page focused on the current expense ratio. Most ETF reference sites take the latter approach because expense changes are rare and easier to handle as one-off content updates.

Yes. Pair SleekRank with SleekPixel to generate per-fund OG images from a template that includes the ticker, issuer, and category. The OG URL maps into the meta tag through SleekRank's meta mapping, so social previews look branded and consistent across the entire ETF catalog.

Add a 'leverage' or 'fund_type' column to the source and use it in the template to render risk warnings or compliance language. Building a separate page group for leveraged products with its own template and URL pattern like /etf/leveraged/ is also a clean approach if you want different disclosure copy from vanilla index funds.

If your data source includes Morningstar-style ratings, ESG scores, or in-house analyst notes, add them as columns and map them in. Rating updates flow on cache flush, and the same column structure works whether you license third-party data or maintain ratings internally with your own methodology.