Yoast SEO hosting for archives too big to rebuild in a request.
Yoast keeps its own table describing every URL on your site. On a small blog you never see it. At forty thousand posts it is the thing that times out.
A second index of your whole site.
Everything below follows from Yoast maintaining a derived table that has to stay accurate as content changes.
Indexable rebuilds that reach the end
Rebuilding after an upgrade or a bulk edit means writing a row for every post, term and author on the site. It runs as a resumable batch, so a large archive finishes rather than stopping at whatever the timeout allowed.
Sitemaps that generate without stalling
An XML sitemap index over tens of thousands of URLs is a real query every time a crawler asks. Generation is given room and the output cached, so Googlebot is not the thing making the site slow.
Bulk edits that do not lock the site
Changing a category across five thousand posts triggers five thousand indexable updates. Those are queued behind the front end rather than run inline while an editor waits.
A table that is actually indexed
Yoast's own tables are queried on every page render for the title, description and canonical. Those lookups get indexes rather than being left to scan.
Recover from a bad bulk change
A find-and-replace across meta descriptions is fast to run and slow to undo by hand. Daily backups make it a restore.
Where SEO plugins meet their limit.
Nothing about Yoast is slow on a normal site. The problems all start at the point where a maintenance task can no longer complete inside one request.
- Reindexing runs as resumable batches
- Sitemap generation cached and given headroom
- Bulk edits queued off the request path
- Indexable lookups indexed
Every page asks Yoast a question.
Title, description and canonical come from the indexable table on every single render, so a slow lookup there is a slow lookup everywhere.
What we change for Yoast SEO
The plugin maintains a derived index of your site, and every row here is about keeping that index correct without blocking anything.
| Setting | What we do | Why |
|---|---|---|
| Indexable rebuilds | Resumable batches rather than one long run | A rebuild writes a row for every post, term and author, which on a large archive cannot complete inside any request timeout and silently stops part way. |
| Sitemap generation | Cached output with headroom for the first build | A sitemap index over tens of thousands of URLs is a genuine query, and crawlers request it often enough to become a load source of their own. |
| Bulk edit handling | Indexable updates queued off the request | Reassigning a category across thousands of posts triggers an update per post, and doing that inline leaves an editor watching a spinner for minutes. |
| Indexable table | Indexed for the per-render lookups | Title, description and canonical are read from that table on every page view, so an unindexed lookup there is a cost paid site-wide. |
| Orphaned indexables | Cleaned on a schedule, not on request | Deleted content leaves rows behind, and the cleanup task is large enough that it belongs on a schedule rather than in front of a visitor. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Why does Yoast's reindex never finish?
Does the XML sitemap slow my site down?
Is Yoast bad for performance on big sites?
Can I use Rank Math or SEOPress instead?
Keep the index in step with the content.
Move the archive across. Migration is free, indexables included.