Continue a stored-content link scan

Choose the request scope

Open Site diagnostics and explicitly authorize checking public URLs found in stored public, password-free posts and pages. External destinations require a separate choice. Sensitive, query-bearing and action URLs remain excluded. Checks observe HTTP responses, not content quality or search rankings.

Review a scope before continuing

Each scope retains up to 1,000 posts, 500 distinct targets and five source examples per target within 2 MB; it may stop earlier for storage. Export the current-scope CSV for full retained detail before continuing. The next scope resumes the saved post and anchor position. A traversal fixes its highest post ID; newly added posts and edits behind the cursor are covered by a later traversal. A changed resumed post is reread from its first anchor.

The observations have different dates and are not a simultaneous whole-site check. A successful result resolves a retained failed observation only after the same target is actually checked successfully under the same external-target scope. Missing or evicted observations do not establish resolution.

Enable recurring content scans only when wanted

Recurring content scans start off. An administrator can authorize daily or weekly work, which continues through bounded scopes. WordPress cron can be late. Stopping discards in-flight results. This feature adds no email alerts; recurring rule monitoring and its optional alerts remain separate.

Keep the evidence you need

Up to ten scope summaries are retained for 30 days, with 50 dated target observations per scope and a 2 MB total archive. Issues receive priority. Old or excess records can be removed, so export needed evidence. Rolling 7, 30 and 90-day care reports show actual observation dates and incomplete coverage; they do not estimate revenue or promise complete site health.