SleekRank consumes whatever source you point it at: REST endpoint, JSON file, Google Sheet, CSV. Many sites point it at a sheet that an external script refreshes from an FX API on a cron. That way, the API call lives outside WordPress and SleekRank just reads the latest sheet.

As fresh as your source and cacheDuration allow. If the source refreshes hourly and cacheDuration is one hour, pages stay within an hour of the source. The page also renders the updated_at timestamp from the source, so readers see exactly how recent the rate is.

Add a historical_rates array column with date and rate per row from a separate feed, then render via a list mapping. The dataset carries the records, the template carries the formatting, so historical context stays consistent across every pair.

Same pattern, different source. Use a crypto rate API and the same mappings. The slug for crypto pairs can follow the same kebab-case convention (btc-to-usd, eth-to-eur) under a separate URL prefix or in the same /currency/ tree.

SleekRank caches the source per cacheDuration set in seconds. Set it to match your rate refresh cadence (3600 for hourly). On expiry, the next request fetches fresh rates and rebuilds every pair page in one pass.

Yes. Each generated URL is a real WordPress page included in the sitemap. The base template is excluded automatically so the scaffolding does not compete with real currency pages. Run a rewrite flush after adding new pairs so the routes resolve immediately on production.

Yes, via the calculator widget embedded in the base template. SleekRank renders the static content (rate, common amounts, timestamp); the calculator is a small interactive component that uses the same rate value. Both read from the dataset.

Add a source column (ECB, exchangerate.host, OXR) and render it via a selector mapping. Include a standard disclaimer in the base template explaining that rates are reference values, not guaranteed transaction rates. The dataset carries the source; the template carries the disclaimer.