Yoast · Rate Limits

Yoast Rate Limits

Yoast publishes NO rate limits for any of its APIs, and emits no rate-limit response headers anywhere. This is an honest zero, not a gap in the search: developer.yoast.com documents no limits on the REST API, the Schema Aggregator or the Abilities API, and the MyYoast Provisioning API's own generated client declares none. The structural reason is that most of the surface is not Yoast's to throttle. The Yoast REST, Schema Aggregator and Abilities endpoints are WordPress REST routes running inside the customer's own install, so throttling is whatever that host enforces (nginx, Apache, a WAF, WP Engine, Cloudflare). Yoast ships plugin code, not a gateway. Throttling on Yoast's OWN hosts is real and was observed live during this pass, but it is edge protection rather than a published API budget, and it carries no machine-readable signal a client could plan against.

Yoast Rate Limits is the machine-readable rate-limit profile for Yoast on the APIs.io network, conforming to the API Commons Rate Limits specification.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include SEO, WordPress, Plugin, and Rate Limiting.

0 Limits Throttle: 429
SEOWordPressPluginRate Limiting

Policies

No Yoast gateway
Yoast is delivered as plugin code, not as a managed API; limits on the site-side APIs are whatever the host WordPress or hosting platform enforces.
Edge protection on Yoast-owned hosts
yoast.com and my.yoast.com apply bot/rate protection at the edge with no documented threshold and no rate-limit headers.
Backoff
On 429 or 5xx, back off exponentially with jitter. Do not blind-retry write operations on the MyYoast Provisioning API — it has no idempotency key, so a retried create can bill a customer twice. See conventions/yoast-conventions.yml.

Sources