[Core Features & Tools] AI Processing Large Sites & Timeout Issues

[Core Features & Tools] AI Processing: Large Sites & Timeout Issues

Quick Answer

Large-site scans and AI-assisted fixes can take time because the amount of content and number of links vary by site. In V4, supported scans and fixes can continue in the background. Start the work from the Dashboard or the relevant report, then return to review progress and results.

Before Starting a Large Run

  1. Confirm that Link Whisper Premium is activated.
  2. Open Link Whisper → Settings → Content Scope and include only the post types and content that should be processed.
  3. Review Link Whisper → Settings → Linking Rules and Settings → AI so the workflow matches your goals.
  4. Run the initial scan from Link Whisper → Dashboard if report data is not ready.
  5. For AI work, open Link Whisper → AI Subscription and check the available credits.

Choose the Right Workflow

Use Run Scan on the Dashboard to refresh link and target-keyword data. During One Click Setup, choose Scan Site when you want to build initial reports. Choose Scan & Link Site only when you are ready to use the AI linking workflow and have enough credits.

How Background Processing Works

V4 moves supported long-running scans and AI fixes into background work so the browser does not need to hold one long request open. The Dashboard or relevant report shows the available status and results.

  • You can continue working in WordPress while supported background work runs.
  • Return to the Dashboard or report to see newer progress and results.
  • Do not start duplicate scans or fixes while an existing run is still active.
  • A page refresh only displays newer status; it does not restart the work.

AI Credits and Large Sites

AI credit usage depends on the task, the amount of content, and the links being processed. When a feature provides an estimate, review it before starting a large run. Check AI Credit History to review completed AI work.

If the account runs out of credits, Link Whisper stops the affected AI work and preserves work already completed. Add credits from Link Whisper → AI Subscription before continuing.

If Progress Appears Stuck

  1. Open the Dashboard or relevant report and check whether the run is still marked active.
  2. Wait for a meaningful status change, especially when a large group of posts or links is being processed.
  3. Confirm that the site remains accessible in WordPress and that the Link Whisper plugin is active.
  4. Check server error logs, available PHP resources, WordPress scheduled tasks, loopback requests, and firewall or rate-limit errors.
  5. If the status does not change after the site and server checks, contact support with the task name, site URL, plugin version, timestamp, status screenshot, and relevant error log.

Timeouts and Network Errors

A timeout, temporary rate limit, or remote-server error does not always mean that every link or task is permanently broken. Recheck uncertain results before changing content. Avoid repeatedly launching the same scan while the first run is active.

Reduce the Workload

  • Narrow Settings → Content Scope to the content that needs processing.
  • Run one focused workflow at a time and review its report before starting another large workflow.
  • Use the relevant report to review results instead of repeatedly rescanning the entire site.
  • Make sure the hosting plan has enough memory, execution time, database capacity, and outbound-request access for the site.

Important V4 Differences

  • V4 uses background processing for supported scans and fixes.
  • Do not choose an AI model based on old GPT-4o or GPT-4o Mini instructions.
  • Do not rely on fixed processing-time promises. Task duration varies by site and workload.
  • Do not keep the browser tab open as a requirement for background work.

Need Help?

Send support the site URL, Link Whisper version, task or report name, approximate start time, current status, exact error, and a screenshot. Never send a password or API key.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us