API overview
Two ways to get Rankfender articles into a site that is not WordPress: the read-only content API and the push webhook.
Rankfender gives you two ways to get your articles into a site that does not run WordPress. Both are set up in the project's Settings › Integrations, on the "Modern Web Integration" card, and both are on every plan.
| Content API (PULL) | Webhook (PUSH) | |
|---|---|---|
| Who starts it | Your site asks Rankfender | Rankfender calls your site |
| When | Whenever your site requests it | Each time an article is published |
| What you get | Your published articles: a list, or one article with its HTML | The full article in a JSON POST |
| Security | Your project's API key in the X-Rankfender-Key header | Optional API key, bearer token, basic auth or secret header |
| Good for | Static sites, headless front ends, server-rendered pages | A CMS or back end that stores articles itself |
In this section
- Your API key: create it, send it, replace it.
- Content API reference: the endpoint, its parameters and its responses.
- Push webhook: headers, payload and what your endpoint must answer.
What the API does not do
- It is read-only: you cannot create or edit articles, keywords or projects through it.
- It returns articles only, not AI visibility, keyword or audit data.
- Account Settings › "API Keys" says "API key management coming soon". Keys live on each project's Modern Web card.
Tip
On WordPress, use the plugin instead: one click fills the SEO fields of your SEO plugin. See WordPress. Card-by-card setup of Modern Web: Modern Web.