From whatever source you maintain — typically a JSON file shipped with the icon set or a REST endpoint that lists sets and counts. Open-source libraries often already produce a meta.json or index.json that catalogs sets; SleekRank reads that directly. For commercial libraries, expose a private endpoint or commit a manifest to the marketing site repo.

Yes. Store URLs to representative icons in the source (typically eight to twelve per set is plenty for a preview) and render them with list mapping into a grid in the template. For dynamic full-set browsing, embed your existing icon-search component on top of the SleekRank-rendered landing page; SleekRank handles the marketing surface, the embedded component handles search.

Add a license field (MIT, CC BY 4.0, Pro, custom) and map it into the template via selector mapping. For commercial sets, add a price field. Filter sets in indexes if you want license-specific listings — a /icons/license/mit/ URL pattern that lists only MIT-licensed sets is straightforward.

Yes. Each generated URL is added to the SleekRank sitemap. The base template is excluded and noindexed. Set names rank well because they're specific ("lineflow icons" has low ambiguity), and consistent on-page metadata (count, license, install snippet) helps the page feel authoritative to both users and search engines.

Yes. Add an entry to the manifest with slug, name, style, license, count, sample URLs, and install snippet. The page appears on the next cache cycle. If the new set has unusual fields (e.g. animated icons need a special preview format), add a column and a small selector-mapped section in the template, then any future set with that field populates the section automatically.

No. SleekRank handles the per-set landing pages — discovery, marketing, install. Search across icons within a set is up to your template or theme. Most teams embed an existing component like fuse.js over a JSON of icon names. The landing page provides the SEO and onboarding surface; the search component handles in-set browsing.

Either bump the manifest in place (current version only, simpler) or maintain a versions array per set and render a version selector in the template (richer, more work). For most catalogs, current-version-only is fine because users want the latest install snippet. Keep older versions linkable via /icons/{slug}/v2/ patterns if a set has paying customers on legacy versions.

Yes. Add downloads or rank columns to the manifest, refreshed periodically from npm or your CDN logs. Sort indexes by popularity using a second URL pattern like /icons/popular/. Per-set pages can show "X downloads this month" via selector mapping. Cache duration controls how fresh those counts are; daily refresh is usually plenty.