How to Fix Mobile View Problems in WordPress
Most mobile problems are one element wider than the screen. DevTools will point at it in under a minute.
Practical, tested fixes for the WordPress theme and plugin problems that actually come up — written to be followed, not skimmed.
Most mobile problems are one element wider than the screen. DevTools will point at it in under a minute.
Locked out by the plugin you need to remove. There are three ways in, and none of them require the dashboard.
Removing the malware is the easy part. If you do not find how they got in, you will be doing it again next week.
Finding broken links is easy. Fixing them well means treating internal links, external links and old URLs differently.
Google is telling you exactly what is wrong: the page asks not to be indexed. The only question is which setting is adding that request.
Edited the stylesheet, reloaded, nothing changed. There are five caches between your file and your eyes, plus one CSS rule quietly winning.
Before you replace the theme, find out whether the theme is actually the problem. Often it is the images, the host, or one plugin.
Guessing which plugin broke the site is slower than testing. The conflict test takes about ten minutes and gives a definite answer.
It is almost never a bug. Something disabled it deliberately — and in most cases that was the right call.
Unused themes are a real security liability — they still receive requests even when inactive. Removing them properly takes a little more than clicking delete.
Theme settings live in the database, not the theme folder — which is why reinstalling changes nothing. Here is what actually clears them.
If updating a theme wipes your changes, the changes were in the wrong place. Here is how to move them somewhere updates cannot reach.
Your posts are safe. What actually disappears is menus, widgets, theme options and any layout built with the old theme's shortcodes — and that is worth planning for.
A 403 is not a crash. Something looked at the request and said no. The trick is finding out what.
A 500 is a category, not a cause. The server log turns it into something specific in about thirty seconds.
The classic symptom: the home page loads, every post 404s. That single pattern tells you it is permalinks, not content.
"Briefly unavailable for scheduled maintenance" that never ends is a single leftover file. Here is how to remove it and, more importantly, clean up what caused it.
WordPress is running fine — it simply cannot talk to MySQL. There are only three real causes, and they are quick to tell apart.
This message looks worse than a white screen, but it is actually better news: WordPress caught the error, emailed you the cause, and left you a way in.
A completely blank page means PHP died and WordPress was told not to say why. The fix is to make it talk, not to guess.