@rankveo/client

Framework-agnostic client for the rankveo headless blog API. Your site reads published articles and renders them under your own domain.

Every framework package — @rankveo/next, @rankveo/astro — is a thin layer over this. Use it directly for any other runtime: a plain Node server, Hono, Express, React Router, Hugo via a prebuild script.

npm install @rankveo/client

import { BlogClient } from '@rankveo/client';

const blog = new BlogClient(); // reads RANKVEO_BLOG_API_KEY
const { articles, total } = await blog.getArticles({ page: 0, limit: 10 });
const article = await blog.getArticle('how-to-rank-in-ai-answers');

Server-side only, and enforced: constructing it in a browser throws, because the key would already be in a bundle a visitor can read.

Beyond fetching

sitemapXml(entries, options) and rssXml(articles, options) produce complete documents, including the <image:image> entries Google indexes and no framework's built-in sitemap emits. articleJsonLd(article, options) builds BlogPosting structured data. verifyRevalidateSecret(header, secret) is the constant-time check for a revalidate endpoint.

Caching

The core sends no framework-specific fetch options — next: {…} and cache: 'no-store' are not understood by every runtime. Pass requestInit to add your own:

new BlogClient({ requestInit: { next: { revalidate: 3600 } } });
new BlogClient({ requestInit: (path) => ({ cache: path.includes('/site') ? 'force-cache' : 'no-store' }) });

Docs and setup guide · All integrations

MIT.