WordPress Site Not Loading Fix — Emergency Guide | WebFixHQ

Confirm Server Status & Hosting Account

Before diving into WordPress, rule out the hosting provider. Log into your hosting control panel (cPanel, Plesk, custom dashboard) and check for server status notifications or resource usage alerts. If your hosting provider has an outage, there’s nothing you can do on your end until they resolve it. Also, verify your account isn't suspended for billing or resource overages. Ping your domain from your local machine to see if it resolves to an IP address.

ping yourdomain.com

✓ 5-10 minutes. Essential first check.

Disable Plugins & Themes via FTP/File Manager

A common culprit for a completely down WordPress site is a recently updated or incompatible plugin or theme. Access your site via FTP or your hosting's file manager. Navigate to /wp-content/. Rename the plugins folder to plugins_old. Try loading your site. If it comes back, a plugin was the issue. Rename it back to plugins, then rename individual plugin folders inside it until you find the culprit. Do the same for the themes folder if plugins don't resolve it, ensuring you have a default theme like Twenty Twenty-Four active. This is a critical step if your WordPress site went down after a plugin, theme, or core update.

/wp-content/plugins/  -->  /wp-content/plugins_old/

✓ 10-20 minutes. Often the quickest fix.

Check wp-config.php for Database & Debug Issues

Your wp-config.php file, located in your WordPress root directory, contains vital database connection details. Open it via FTP/File Manager. Look for DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST. Ensure these credentials are correct. Incorrect details will result in a database connection error. Also, temporarily enable debug mode by adding define( 'WP_DEBUG', true ); and define( 'WP_DEBUG_LOG', true ); to surface specific errors. Remember to remove or set to false once debugging is complete.

define( 'DB_NAME', 'your_database_name' );
define( 'DB_USER', 'your_database_user' );
define( 'DB_PASSWORD', 'your_database_password' );
define( 'DB_HOST', 'localhost' );

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

✓ 5-15 minutes. Crucial for database-related outages.

Inspect .htaccess File for Corruption

The .htaccess file, also in your WordPress root, controls permalinks and server directives. A corrupted or misconfigured .htaccess can cause a 500 Internal Server Error or prevent your site from loading entirely. Via FTP/File Manager, rename .htaccess to .htaccess_old. Then, try accessing your site. If it loads, log into your WordPress admin (if possible), go to Settings > Permalinks, and simply click Save Changes without making any modifications. This will regenerate a fresh .htaccess file. If you can't access the admin, you'll need to manually create a new .htaccess with the default WordPress rules.

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

✓ 5-10 minutes. A common fix for blank pages or 500 errors.

Check File Permissions & Ownership

Incorrect file and folder permissions can make your WordPress site inaccessible, leading to a "wordpress site not loading" scenario. Via FTP/SSH, ensure directories are 755 and files are 644. The wp-config.php file can sometimes be 640 or 600 for extra security. Incorrect ownership (e.g., files owned by root instead of the web server user) can also cause issues. If you have SSH access, you can use commands like find . -type d -exec chmod 755 {} \; and find . -type f -exec chmod 644 {} \; from your WordPress root directory.

find /path/to/your/wordpress/ -type d -exec chmod 755 {} \;
find /path/to/your/wordpress/ -type f -exec chmod 644 {} \;

✓ 10-15 minutes. Essential for server-level access issues.

Review Server Error Logs & PHP Version

If your WordPress site is completely down, server error logs (Apache error_log, Nginx error.log, PHP php_error.log) are invaluable. These are usually found in your hosting control panel or via SSH in directories like /var/log/apache2/ or /var/log/nginx/. Look for fatal errors, memory limits exceeded, or parse errors. Also, ensure your PHP version is compatible with your WordPress installation; older PHP versions can cause a "wordpress site not responding" error. You can often change PHP versions in your hosting panel.

tail -f /var/log/apache2/error.log

✓ 10-30 minutes. Provides critical diagnostic information.