15 WordPress Quick Fixes Every Beginner Should Bookmark

Every WordPress beginner hits the same wall eventually: the site breaks, a scary message appears, and you have no idea what to do. The good news is that the most common WordPress problems have simple, well-known fixes. You do not need to be a developer to handle them. You just need to know which lever to pull.

This is a bookmark-it list of 15 problems beginners run into most, each with the symptom you will see, the usual cause, and the exact fix. Work top to bottom when you are not sure what is wrong, because the early items are the ones that cause the most panic for the least real damage.

One rule before you start: back up your site before changing anything, especially the files mentioned below. A backup turns every fix on this list from risky into reversible.

First, turn on debug mode to see the real error

Many of the fixes below are faster if you can see the actual error instead of a blank page. WordPress can show you, you just have to ask. Open wp-config.php, find the line that says to stop editing, and just above it add:

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

With this on, WordPress writes errors to wp-content/debug.log instead of breaking the page for visitors. Reproduce the problem, open that log, and the last few lines usually name the exact plugin or file causing it. When you are done, set WP_DEBUG back to false so the log does not grow forever.

How to safely edit WordPress files

Several fixes ask you to rename a folder or edit a file. There are two beginner-friendly ways to do that. The first is your host’s File Manager, found in your hosting control panel, which lets you browse and rename files in your browser. The second is an FTP client like FileZilla, which connects using the FTP details your host provides and shows your files in a drag-and-drop window.

Either way, the golden rule is the same: before you change or delete a file, copy it first. Renaming .htaccess to .htaccess-old instead of deleting it means you can undo the change in one click. Treat every file edit as reversible and you can work through this whole list without fear.

1. The white screen of death

Symptom: a completely blank white page, no error, nothing.
Cause: usually a plugin or theme conflict, or PHP running out of memory.
Fix: connect to your site with FTP or your host’s file manager, go to wp-content/plugins, and rename the plugins folder to plugins-off. If the site comes back, a plugin was the culprit. Rename it back, then deactivate plugins one at a time until you find the bad one. If that does not help, switch to a default theme by renaming your active theme’s folder.

2. Locked out of wp-admin

Symptom: you cannot log in, even though the password is right.
Cause: a corrupted session, a security plugin, or a wrong site URL.
Fix: clear your browser cookies for the site first. If that fails, reset your password from your host’s database tool, or temporarily set a new one by adding this to your theme’s functions.php, loading the site once, then removing it:

wp_set_password( 'YourNewPassword123', 1 ); // 1 is the admin user ID

3. Error establishing a database connection

Symptom: a page that just says “Error establishing a database connection.”
Cause: wrong database details in wp-config.php, or your host’s database server is down.
Fix: open wp-config.php and confirm DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST match what your host gave you. If they look right, the database server may be overloaded, so contact your host. This is one of the few problems that is often not your fault.

4. The 500 internal server error

Symptom: a generic “500” or “internal server error” page.
Cause: a broken .htaccess file or a plugin error.
Fix: rename .htaccess to .htaccess-old via FTP, then visit Settings then Permalinks in your dashboard and click Save to generate a fresh one. If that does not work, try the plugin-folder rename from fix #1.

5. Briefly unavailable for scheduled maintenance

Symptom: the site is stuck saying it is in maintenance mode.
Cause: an update was interrupted and left behind a lock file.
Fix: connect via FTP, look in your site’s root folder for a file named .maintenance, and delete it. The site returns instantly. Then re-run the update that got interrupted.

6. The login redirect loop

Symptom: logging in just bounces you back to the login page forever.
Cause: a mismatch between your site address settings and the real URL, or stale cookies.
Fix: clear cookies, then pin your URLs in wp-config.php so nothing can drift:

define( 'WP_HOME', 'https://yoursite.com' );
define( 'WP_SITEURL', 'https://yoursite.com' );

7. Changes not showing up

Symptom: you edit a page, but the live site looks the same.
Cause: caching, either in your browser, a caching plugin, or your host’s server cache.
Fix: hard-refresh your browser (Cmd-Shift-R or Ctrl-Shift-R). Then clear your caching plugin’s cache, and if your host has its own cache, clear that too. Nine times out of ten, the change was saved all along.

8. Memory exhausted errors

Symptom: a message about “allowed memory size exhausted.”
Cause: a heavy plugin or theme needs more PHP memory than the default.
Fix: raise the limit in wp-config.php, above the line that says to stop editing:

define( 'WP_MEMORY_LIMIT', '256M' );

If the error continues even at 256M, the real cause is usually one badly behaved plugin, so investigate which page triggers it.

9. Mixed content warnings after adding SSL

Symptom: the padlock is missing, or the browser warns the page is “not fully secure.”
Cause: some images or scripts still load over the old http address.
Fix: make sure both URLs in Settings then General use https. Then install a free plugin like Really Simple SSL, which rewrites the insecure links for you. For a deeper clean, a search-and-replace of http://yoursite to https://yoursite in the database fixes the stubborn ones.

10. Your emails are not sending

Symptom: contact form messages, password resets, and order emails never arrive.
Cause: most hosts do not reliably send mail through PHP’s default function.
Fix: install an SMTP plugin and connect it to a real mail service. This single change fixes the most common “my contact form is broken” complaint, which is almost never the form and almost always the email.

11. 404 errors on every page except the home page

Symptom: the home page loads, but every other page returns “404 Not Found.”
Cause: your permalink rules got flushed or corrupted.
Fix: go to Settings then Permalinks and click Save Changes without changing anything. That single click rebuilds the rules and almost always brings every page back.

12. The site is suddenly very slow

Symptom: pages that used to load fast now crawl.
Cause: no caching, oversized images, or a bloated database.
Fix: install a caching plugin, compress your images with an optimization plugin, and clean out old data. If the slowness is specifically in the dashboard rather than the public site, the cause is often a plugin making slow background calls, and tidying your wp_options table helps. Our guide to WordPress database optimization walks through that cleanup.

13. You think your site was hacked

Symptom: strange pop-ups, content you did not write, or visitors redirected to spam sites.
Cause: a compromised plugin, a weak password, or an out-of-date site.
Fix: do not panic and do not just delete things at random. Change every password, scan with a security plugin, and remove any admin users you do not recognize. We have full step-by-step guides for cleaning a hacked WordPress site and for the specific redirect hack that sends visitors elsewhere.

14. The visual editor stopped working

Symptom: the editor is blank, buttons are missing, or formatting will not apply.
Cause: a browser cache issue or a plugin loading broken JavaScript.
Fix: clear your browser cache and disable browser extensions first, since ad blockers sometimes break the editor. If it persists, deactivate plugins one by one. As a last resort, add define( 'CONCATENATE_SCRIPTS', false ); to wp-config.php, which fixes a common script-loading conflict.

15. A flood of spam comments

Symptom: dozens or hundreds of junk comments appear overnight.
Cause: automated bots targeting open comment forms.
Fix: turn on the Akismet anti-spam plugin that ships with WordPress, and under Settings then Discussion, require comments to be manually approved and hold any comment with links. Those two settings stop the vast majority of comment spam without blocking real readers.

How to avoid most of these in the first place

Almost every fix above traces back to one of three habits. Build them and you will rarely need this list:

• Back up automatically. A scheduled backup means any broken change is a five-minute restore instead of an afternoon of stress.
• Keep WordPress, plugins, and your theme updated. Most hacks and many errors target out-of-date software. Updating is the single highest-value habit you can build.
• Change one thing at a time. When you install or edit, do it in small steps. If something breaks, you know exactly what caused it, which makes every fix on this list faster.

Frequently asked questions

Will these fixes delete my content?

No. None of the fixes on this list remove your posts, pages, or images. They reset settings, rename files, or toggle plugins. As long as you back up first, everything is reversible.

I do not know how to use FTP. Is there another way?

Yes. Almost every host includes a File Manager in its control panel that does the same job in your browser, with no software to install. If you are unsure where it is, your host’s support team will point you to it in a minute.

How do I find which plugin is causing the problem?

Deactivate all of them, confirm the site works, then reactivate them one at a time, checking the site after each. The plugin that brings the problem back is your culprit. It is slow, but it always works.

Should I edit theme files directly?

For the small functions.php changes here it is fine as a temporary fix, but remove them once the problem is solved. For lasting changes, use a child theme so a theme update does not erase your edits.

The fix worked, but the problem came back. Why?

A returning problem usually means the root cause is still there, such as an outdated plugin or a weak password an attacker keeps using. Fixing the symptom buys time; updating everything and tightening passwords fixes the cause.

How often should I back up my site?

For most beginner sites a daily automatic backup is plenty, and many hosts include one for free. If you publish often or run a store, back up before every big change as well. The goal is simple: never be more than one day away from a working copy.

Do I need a staging site to try these fixes?

Not for the quick fixes here, since each one is reversible. A staging site, which is a private copy of your live site, is worth setting up later for testing bigger changes like a new theme. Many hosts create one for you with a single click.

Is it safe to edit wp-config.php?

Yes, as long as you copy the file first and add new lines above the comment that says to stop editing. The settings shown here, like the memory limit and debug mode, are standard and safe. If a pasted line ever breaks the site, just remove that line to undo it.

When to call for help

These fixes cover the problems beginners can safely solve themselves. If you have tried the relevant fix and the site is still down, or if the issue involves your database or a suspected hack you cannot clean, that is the moment to contact your host or a professional. There is no shame in it. Knowing which problems are quick fixes and which ones need a specialist is itself a skill, and now you have a map for both. Bookmark this page so it is there the next time something breaks, because in WordPress, eventually something always does.