This release of HeadstartWP introduces optimizeYoastPayload, a new option that trims down the payload delivered by the Yoast integration. If you’re pulling Yoast SEO metadata through the headless API, this reduces the amount of data shipped on each request, keeping responses lighter and your frontend faster.
What’s new
- optimizeYoastPayload — Reduce the size of the Yoast integration payload to cut down on transferred data for SEO metadata.
The optimization is opt-in, so existing behaviour is unchanged unless you enable it. Turning it on is a straightforward win for sites that rely on the Yoast integration and want to keep API responses lean, particularly on content-heavy setups where metadata payloads add up.
Bug fixes
- Post path matching — Corrected the path matching logic when
params.fullPathis set, ensuring routes resolve as expected.
This patch addresses cases where post path resolution behaved incorrectly with params.fullPath configured, so routing now matches the intended path reliably.