A redirect save can purge HyperCache so visitors do not keep the old Location.
Speed
HyperCache SEO
The missing hinge between a cache that must be hot and an SEO graph that must stay true.
- Preload from sitemaps
- Purge on SEO edits
- Pairs with HyperCache
Requires: HyperCache
What it is
Built for a job, not a feature list.
HyperCache SEO is not an SEO plugin. It is the hinge: when Nexora SEO saves redirects or settings, the cache purges; when the sitemap changes, those URLs enter HyperCache’s preload queue. Buy it if you already run HyperCache and Nexora SEO and you are tired of stale HTML pointing at last week’s canonical.
Results
What changes on the site.
SEO sitemap URLs are merged into preload — first organic hit is more often a cache HIT.
You do not maintain a second crawler config beside the SEO sitemap.
Capabilities
What the package actually does.
- Purge HyperCache when SEO redirects are saved
- Invalidate sitemap preload cache when SEO settings save
- Merge SEO sitemap URLs into the HyperCache preload worker
- Admin status: sitemap on, redirect count, flags
- Requires HyperCache (Core or AI) and Nexora SEO
Versus
Against the category leaders.
Honest deltas — not a fake scorecard. If a rival is better at a narrow job, the row says so.
| Leader | Where NexoraPlug differs |
|---|---|
| WP Rocket sitemap preload | Rocket crawls Yoast or Rank Math sitemaps itself. This hinge only speaks Nexora SEO + HyperCache — thinner, and honest about the dependency. |
| LiteSpeed Cache crawler | LSCache crawls the site. HyperCache SEO injects the SEO sitemap into a worker you already run. |
| Rank Math Instant Indexing | Instant Indexing talks to Google. This talks to the cache. Different job; we do not pretend otherwise. |
Seat
The zip is not on the internet.
Packages live in a vault outside the web root. A key is HMAC-bound to your hostname. Verify and download are rate-limited. Updates stop when the seat is cold. We do not remote-wipe content you already have — PHP that WordPress requires to be GPL can be copied; stolen copies simply do not get the next build.
How a key behaves