Stop SiteGround CPU Limits & Downtime Instantly!

This is due to plugins triggering too many server requests. We analyze which specific process is consuming resources using Site Tools metrics and disable it.

We identify the script causing the overload (often cron, backup plugins, or bots) and implement WAF rules or optimize the script to reduce execution count.

CPU Seconds measure processing power used. Script Executions count how many times PHP runs. Both have limits; we optimize both.

We use Query Monitor and Site Tools logs to trace high-load queries back to specific plugins.

By limiting the WordPress Heartbeat API and disabling AJAX-heavy features in plugins like page builders.

Disable other caching plugins and let SG Optimizer handle server-side. We configure exclusions for problematic CSS/JS.

Ultrafast PHP is only available on GoGeek plans. We enable it via Site Tools > Devs > PHP Manager.

Dynamic Caching stores rendered HTML. Flush it via SG Optimizer plugin in wp-admin or Site Tools > Speed.

We check if Memcached is enabled in Site Tools and reinstall the object cache drop-in file.

We identify the breaking script using browser DevTools, then add it to SG Optimizer's exclusion list.

A DNS or .htaccess rule is blocking Let's Encrypt validation. We fix the rule and manually re-issue the certificate.

This means your SSL is expired or misconfigured. We reinstall it via Site Tools > Security > SSL Manager.

We perform a database search-replace to update all http:// links to https://.

This is often a TLS version mismatch. We update your server's PHP TLS settings.

Yes. We upload your custom SSL certificate via Site Tools > Security > SSL Manager > Import SSL.

The permalinks in the staging subdirectory need to be reset. We fix this by re-saving permalinks within the staging environment.

We manually merge database changes and rsync files to ensure a clean deployment.

No, staging is available only on GrowBig and GoGeek. We can help you set up an alternative staging solution.

We destroy the old staging and create a fresh copy from the live site via Site Tools.

Go to Site Tools > WordPress > Staging > Manage, then delete the old staging copy.

SiteGround's shared IP is often blacklisted. We set up SMTP to bypass local mail and use a trusted sender.

We add TXT records for SPF and DKIM provided by your email service to authenticate your domain.

SiteGround uses port 465 (SSL) or 587 (TLS). We configure the correct port in WP Mail SMTP.

We verify the SMTP connection, often switching from PHPMailer to direct SMTP with correct authentication.

The default PHP mail is blocked. We install and configure an SMTP plugin to route emails properly.

We reset permissions via SSH: folders to 755, files to 644.

Navigate to Site Tools > Statistics > Error Log or view the file directly at public_html/error_log.

We edit the php.ini via Site Tools > Devs > PHP Manager to increase upload_max_filesize and post_max_size.

We clear cache folders, email logs, and session files that accumulate thousands of small files.

Via Site Tools > Database > phpMyAdmin. We can access it directly to repair tables.

We access Site Tools > Security > Backups, download the archive, and extract only the specific file needed.

Often due to disk space limits. We clear old backups and cache to free up space first.

SiteGround retains 30 daily backups for GrowBig and GoGeek, 7 days for StartUp.

We manually import the database via phpMyAdmin and rsync files from the backup archive.

We identify the infection date, restore a clean backup from before that date, then apply security hardening.

Dynamic pages are being cached or the wc_ajax call is unoptimized. We configure exclusions and optimize queries.

We exclude WooCommerce session-related pages from all caching layers.

Add /my-account/* to the SG Optimizer "Exclude URLs From Caching" settings.

We pre-warm cache, optimize database tables, and limit background processes during peak hours.

Enable Ultrafast PHP, Memcached, and configure a full-page CDN like Cloudflare.

We manually scan files, remove the malicious code, and submit your site to Google for a security review.

After cleaning, we request a review via Google Search Console to get the warning removed.

We use the SiteGround Smart WAF or Cloudflare Firewall rules to geo-block traffic.

We limit login attempts with Wordfence and enable SiteGround's built-in Two-Factor Authentication.

We add a rule to .htaccess to block access to xmlrpc.php, closing a common attack vector.

The AI Agent suggests fixes for common errors. However, we recommend manual review before applying AI suggestions to avoid conflicts.

It can attempt fixes, but complex 500 errors require human analysis of error logs. We provide that expert layer.

We add rules to robots.txt and .htaccess to block known AI training bots like OpenAI's GPTBot.

The Smart WAF uses AI to detect new attack patterns. We configure custom rules for your specific traffic profile.

If SiteGround support is slow, WP Fix Now acts as your dedicated human expert, bypassing queues for immediate resolution.