Some CiteTrack features need to fetch public resources: official crawler network ranges, your robots.txt, your sitemap, or a rendered page for a page check. Newer versions use WordPress’s SSRF-safe HTTP client and practical response-size limits for these requests.
What is bounded
- Official crawler network range refreshes.
- Local robots.txt checks.
- Sitemap and child-sitemap inspection.
- Rendered-page checks used by Optimize tasks.
- Webhook and update metadata responses.
What happens when a page cannot be fetched
Page checks that cannot safely verify a rendered page should show Couldn’t verify rather than incorrectly lowering the score. That keeps “unknown” separate from “failed.”
A safe fetch limit can mean less detail from an abnormal response, but it protects WordPress memory and keeps the admin responsive.