WordPress Design Portfolio

From the blog

Latest Articles

Someone working on code in an editor on a laptop

WordPress Plugin Not Working? Diagnose It Before You Start Deactivating

Before changing anything, work out which of these you actually have, because they have different causes and different fixes:

  • The plugin will not activate
  • It activates but nothing happens
  • It worked yesterday and stopped today
  • It works for you but not for visitors
  • Activating it takes the whole site down

Most articles on this give you one list of fixes to try in order. That wastes time, because the fix for a caching problem will never solve a PHP version problem. Narrow it first.

The two minute checks

Do these before anything that involves a file.

Clear every cache, then hard refresh. On a WordPress site there are usually three or four stacked: a caching plugin, the host’s server cache, a CDN, and your browser. Clearing one and seeing no change proves nothing. Clear all of them, then reload with the cache bypassed.

Check in a private window. If the plugin behaves correctly there and not in your normal window, the problem is your browser or your login session, not the plugin.

Check as a logged out visitor. The reverse case matters more. A plugin that works while you are logged in and fails for everyone else is almost always caching, because most caching setups serve a stored page to logged out visitors and bypass the cache for administrators. You have been looking at the live site. Everyone else has been looking at a photograph of it.

Look at the plugin’s own settings screen. A surprising number of plugins install deactivated in all but name, waiting for a licence key, an API connection, or a single enable toggle.

Read the error instead of guessing

This is the step people skip, and it is the one that usually ends the problem in a minute.

WordPress can log every PHP error to a file. Add this to wp-config.php, and it has to go before the line that reads that is all, stop editing:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

That writes everything to wp-content/debug.log while hiding the errors from the page, so visitors see nothing unusual. Reproduce the problem, then open the log and read the last entries. The file name and line number in a fatal error tell you which plugin is responsible without any deactivating at all.

Three things worth knowing about this:

  • The WordPress documentation is explicit that debugging tools are meant for local and staging installs rather than live sites. Turn it on, get your answer, turn it off
  • Do not put the values in quotes. define( 'WP_DEBUG', 'false' ) is a non-empty string, which PHP reads as true, so you switch debugging on while believing you switched it off
  • Back the site up, or work on staging, before editing wp-config.php at all

If you cannot edit files, the host’s control panel usually has an error log of its own, and the Tools, Site Health screen inside WordPress reports a good deal without any file access.

Isolating a conflict without taking the site down

The standard advice is to deactivate every plugin, confirm the problem goes away, then reactivate one at a time. It works, and on a live site it is a terrible idea, because for the duration your visitors get a site with no forms, no shop and no security plugin.

There are two better versions.

Troubleshooting mode. The Health Check and Troubleshooting plugin from the WordPress team disables plugins and switches the theme for your session only. Everyone else keeps seeing the normal site. You can then re-enable plugins one by one from the admin bar and watch for the moment the problem returns. This is the right tool for a site that is live.

Staging. If your host offers one click staging, clone the site and break the copy instead. Most managed hosts and many cPanel hosts include this now.

Whichever route you take, test the theme too. A conflict between a plugin and a theme is as common as one between two plugins, and switching temporarily to a default theme rules half the possibilities out in one step.

When you cannot reach wp-admin at all

If activating the plugin produced a white screen or a critical error message and you are locked out, you have two ways back in.

Recovery mode. Since WordPress 5.2 a fatal error triggers an email to the site administrator address containing a secret link into recovery mode, where the offending plugin is paused and you can get to the dashboard. Check that inbox, including spam, before doing anything drastic. Two caveats: the email is rate limited, by default to one per hour, and the handler does not catch errors that happen while must use plugins are loading, so an mu-plugin fault produces no email at all.

Rename the folder. Over FTP, SFTP or the host’s file manager, go to wp-content/plugins/ and rename the suspect plugin’s folder, adding anything to the end. WordPress cannot find it, so it deactivates it and lets you back in. Renaming the whole plugins folder does the same for all of them at once.

Rename it back afterwards and the plugin returns, deactivated, with its settings intact. This is a reversible operation, which is why it is the standard move rather than deleting.

Now match the symptom to the cause

It will not activate

Usually an environment problem rather than a bug.

  • PHP version. Modern plugins declare a minimum, and an older PHP will refuse or fatal. Site Health reports your version
  • WordPress version. The same applies in both directions, and a plugin written for a much older WordPress can break on a current one
  • Missing PHP extension. Image, zip and encryption features need extensions your host may not have enabled
  • Memory. Activation runs installation routines, which is the moment a tight memory limit shows up

It activates but does nothing

Start with the obvious and work outward. Is there a setting that enables it? Is the shortcode or block actually on the page? Is the feature meant to appear somewhere you have not looked?

After that, suspect JavaScript. Open the browser console and reload. Script errors from one plugin will stop later scripts from another running at all, which produces exactly this symptom: a plugin that is installed, active, correctly configured and completely inert. Minification and combining scripts, usually from a performance plugin, is a frequent cause, so switch those options off and retest.

It worked yesterday

Something changed, and there are only so many candidates. In rough order of likelihood: the plugin updated, WordPress updated, another plugin updated, the theme updated, your host changed the PHP version, or a licence expired.

Automatic updates make this harder to see, because nobody remembers doing anything. The site activity or update log will usually tell you what moved and when, and matching that timestamp against when the problem started is faster than any amount of deactivating.

If the plugin itself updated and broke, most plugins can be rolled back to a previous version from the WordPress.org repository, which buys you time to report the bug rather than forcing a same-day replacement.

It works for you but not for visitors

Three causes, in order of how often they turn out to be right.

Caching, as described above. Exclude the relevant pages from the cache and retest.

Roles and capabilities. You are an administrator and can do things other users cannot. Create a test account at the role your visitors have and look through their eyes.

A firewall or security rule. This one is underdiagnosed. Security plugins and server level rules such as mod_security block requests that look suspicious, and plugin requests to admin-ajax or the REST API often qualify. The giveaway is a request that returns 403 in the browser network tab while everything else loads normally. Your host can check whether a rule fired and whitelist it.

Activating it takes the site down

A fatal error, which means a PHP conflict rather than a configuration mistake. Use recovery mode or the folder rename above to get back in, then read debug.log for the file and line.

The commonest cause is two plugins loading different versions of the same library, which produces an error about a class or function already being declared. Neither plugin is broken. They simply cannot coexist, and the answer is replacing one of them rather than fixing either.

The settings will not save

A distinct symptom with its own causes, and the interesting one is almost never mentioned.

max_input_vars. PHP limits how many variables a single form submission may contain, commonly to 1000. A large settings page, a long menu or a theme options panel can exceed that, and PHP then silently discards everything past the limit. Nothing errors. The page reloads looking successful and half your settings are gone, usually the ones furthest down the form. Raising the limit is a PHP setting, so it is a host question.

An expired nonce. If the form sat open in a tab overnight, its security token has expired and the submission is rejected. Reload the page and fill it in again.

A firewall blocking the POST. Server rules are more suspicious of submissions than of page loads, especially where a field contains code, a URL or a snippet of HTML. A settings page that saves everything except the one field containing a script tag is this, every time.

Database writes failing. Rarer, but a full disk or a corrupted options table produces it. The host can confirm disk space in seconds.

The white screen

A blank page with no message is PHP dying without being allowed to say why, which is why the first move is always making it talk. Enable debug logging and reload, and the blank page becomes a specific error in debug.log.

Three things produce most of them. A fatal PHP error, usually a conflict or a version mismatch. Exhausted memory, which the log reports as an allowed memory size message naming the file that asked for the last allocation, though that file is often innocent and simply unlucky. And an exhausted execution time on a long running task.

If the front of the site is white but /wp-admin still loads, the fault is in a theme template or a front end only plugin. If both are white, it loads earlier than that, which points at a plugin, an mu-plugin or wp-config.php itself.

The install or upload fails

  • Upload size. A plugin zip larger than the upload limit is rejected. Site Health shows the limit, and installing from the repository rather than by upload sidesteps it
  • Permissions. A could not create directory message means WordPress cannot write to wp-content/plugins. That is ownership rather than a WordPress problem
  • Disk full. Produces failures that look like anything else. Worth ruling out first because it takes one glance
  • Update failed, another update is in progress. A previous update died partway and left a lock behind. It clears on its own after a while

The host side causes

Worth knowing because no amount of work inside WordPress will touch them.

PHP memory limit. Exhausting it produces either a white screen or an allowed memory size error in the log. Raising it is usually a host setting rather than something you can do from WordPress.

Execution time. Import, backup and optimisation plugins run long tasks that a short max execution time kills partway through, which looks like the plugin silently failing.

Server firewall rules. Covered above. Ask the host to check their logs for your IP at the time the request failed, which is far more productive than asking whether anything is blocked.

Object cache. Where a persistent object cache is in use, stale cached options can keep producing the old behaviour after you have changed a setting. Flushing it is part of clearing caches, and it is the one people forget.

File permissions. A plugin that cannot write where it expects to will fail at install or when saving, often with no visible error.

Reading the network tab

Worth a section of its own, because for anything interactive, a form, a filter, a cart, an admin screen that spins forever, this is where the answer is and most people never open it.

Open the browser developer tools, go to the network tab, reload, then do the thing that fails. Watch the requests that appear, and look at the status code on each.

What you seeWhat it usually means
403 on admin-ajax.php or a wp-json routeA security plugin or server firewall rule is blocking it. Ask the host to check which rule fired
404 on a wp-json routeThe REST API is unreachable or the route is not registered. Permalinks, a disabled REST API, or the plugin failing to load
500A PHP fatal error inside the request. The detail is in debug.log
200 with an empty or truncated responsePHP died quietly, often memory or execution time. Check the log
200 with HTML where JSON was expectedSomething printed output before the response, commonly a PHP notice or a stray blank line in a plugin or theme file
The request never appears at allJavaScript failed before sending it. The console tab has the error

That last row is the one that saves the most time. If no request is made, nothing on the server is at fault and there is no point looking there. The problem is a script error, and the console will name the file.

The 200 with HTML case is worth recognising too, because it looks successful. A plugin expecting JSON receives a page of markup, cannot parse it, and gives up silently. The cause is usually something printing a warning that WP_DEBUG_DISPLAY would have revealed.

Before you contact support

A ticket that contains the following gets answered properly first time instead of producing a reply asking for it.

  • Exactly what you expected to happen and what happened instead
  • The relevant lines from debug.log, not a description of them
  • Your WordPress version, PHP version and the plugin version
  • What you have already ruled out, specifically that you tested with other plugins disabled and with a default theme
  • Whether it affects logged out visitors, logged in users, or both
  • When it started and what changed around then

Developers close a lot of tickets as cannot reproduce. Most of those are conflicts the reporter never isolated, so the half hour you spend on the steps above is the difference between a fix and a fortnight.

Stopping it happening again

None of this is exotic and all of it is dull, which is why it does not get done.

Keep a staging copy and apply updates there first. Take a backup before updating, and make sure you have actually restored one at some point, because an untested backup is a hope rather than a plan. Update in small batches so that when something breaks you know what did it. Remove plugins you are not using rather than leaving them deactivated, since an abandoned plugin is a security problem whether it is running or not.

And keep an eye on what is no longer maintained. A plugin that has not been updated in years will eventually meet a PHP version it cannot survive, and the failure will arrive on the host’s schedule rather than yours. We set out the wider routine in the WordPress maintenance checklist.

The order to work through

  1. Clear every cache and retest, logged in and logged out
  2. Turn on debug logging and read the log
  3. Use troubleshooting mode to test with other plugins off and a default theme, without affecting visitors
  4. If locked out, use the recovery mode email or rename the plugin folder
  5. Check PHP version, WordPress version and memory in Site Health
  6. Check the browser console and network tab for script errors and 403s
  7. Then, and only then, open a support ticket with the evidence

Steps one and two solve most of these. The rest exist for the ones that do not.

Common questions

Why is my WordPress plugin not working after an update?

Something in the environment changed. The usual candidates are the plugin updating, WordPress updating, another plugin updating, the theme updating, the host changing the PHP version, or a licence expiring. Check the update log for what moved and match the timestamp against when the problem started.

How do I find which plugin is causing the problem?

Read wp-content/debug.log after enabling WP_DEBUG and WP_DEBUG_LOG, because a fatal error names the file and line. If that does not identify it, use the Health Check and Troubleshooting plugin, which disables plugins for your session only so visitors are unaffected, and re-enable them one at a time.

What do I do if a plugin locks me out of wp-admin?

Check the site administrator email for a WordPress recovery mode link, which is sent automatically on a fatal error and pauses the offending plugin. Otherwise rename that plugin folder inside wp-content/plugins over FTP or the host file manager, which deactivates it. Renaming it back restores the plugin with its settings.

Why does the plugin work for me but not for visitors?

Most often caching, because caching setups usually serve a stored page to logged out visitors while bypassing the cache for administrators. The other two causes are user role capabilities, and a security plugin or server firewall rule blocking the plugin requests, which shows as a 403 in the browser network tab.

Why do my plugin settings not save?

The least known cause is PHP max_input_vars, commonly limited to 1000. A large settings form exceeding it has the extra fields silently discarded with no error, so the page looks like it saved. The other causes are an expired security nonce from a form left open too long, a server firewall rejecting the submission, and database writes failing because the disk is full.

Is it safe to turn on WP_DEBUG on a live site?

The WordPress documentation says the debug tools are meant for local and staging installs rather than live sites. If you must use it on a live site, set WP_DEBUG_DISPLAY to false and display_errors to 0 so errors go to the log rather than the page, take a backup first, and turn it off again as soon as you have your answer.

A plugin activates but nothing happens. What now?

Check whether it needs enabling, a licence key or an API connection, and whether the block or shortcode is actually on the page. Then open the browser console, because a script error from one plugin stops later scripts running. Minifying or combining JavaScript is a frequent cause, so disable those options and retest.

WordPress Maintenance: The Checklist and What It Involves

WordPress maintenance is the work that keeps a site running after it is built: updates, backups, security, performance and the checks that catch a problem before a visitor does.

It gets skipped because a WordPress site keeps working for a long time without it. Then one update collides with one plugin, or a form stops sending and nobody notices for five weeks, and the cost of the skipped hour turns out to be considerable.

This is what the work actually is, how often each part needs doing, and which parts matter most if you only have an hour a month.

Why a Finished Site Still Needs Work

A WordPress site is not one piece of software. It is WordPress core, a theme, usually fifteen to thirty plugins, a PHP version, a database and a web server, all made by different people on different release schedules.

Every one of those moves. Plugins release fixes, core releases security updates, hosts upgrade PHP, browsers change what they accept. A site that is never touched is not standing still, it is drifting away from everything around it.

Two specific pressures make this urgent rather than theoretical. Known vulnerabilities in outdated plugins are published, which means an unpatched site is on a list that automated scanners work through. And an old PHP version eventually stops receiving security fixes, after which the host will move you whether you are ready or not.

The Weekly Checks

Fifteen minutes, and most of it can be automated into alerts so you only look when something is wrong.

Does the Site Load

Uptime monitoring is free and it catches the failure that costs the most. Check the homepage, but also one inner page and one that runs a query, because a site can serve a cached homepage long after the database has stopped answering.

Do the Forms Work

The most common silent failure on a business site. A plugin update, an SMTP token expiring or a host blocking mail is enough, and nothing visible breaks. Send a real test through every form that matters and confirm the message arrives in the inbox it should.

Plugin Updates, Reviewed Rather Than Clicked

Read what each update says before applying it. A security release goes on immediately. A major version that rewrites a page builder waits for a moment when you can test it.

Comments and Spam

Clear the queue so genuine comments are not buried, and watch for a sudden jump, which usually means a form or a login endpoint has been found by a bot.

The Backup Actually Ran

Not that it is scheduled. That it ran, and that the file has a plausible size. A backup plugin that has been failing quietly for two months is worse than no backup, because you believed you had one.

The Monthly Work

Core and Theme Updates

Minor core releases are safe and should not be left. Major ones are worth a staging test if the site is complex. Theme updates need care if the theme was customised, which is why those changes belong in a child theme rather than in the theme files. The WordPress documentation on updating covers the order and the rollback.

Clean the Database

Post revisions, expired transients, spam comments, orphaned metadata and tables left behind by plugins that were removed years ago. On an older site this is often the single biggest easy win, and a database that has halved in size backs up and restores faster too.

Broken Links and 404s

Internal links break when pages are renamed, and external ones break on their own. Pull the 404 report, fix the internal ones at source rather than with redirects where you can, and redirect the ones that have inbound links.

Performance

Measure the same three pages every month so you have a trend rather than a number. A site that slowly degrades over a year is the normal pattern, and it is usually caused by added plugins, uncompressed images and a database that nobody has cleaned.

Users and Roles

Check who still has an account and what they can do. The developer who left in March, the agency that finished last year, the subscriber account created by a bot. Everybody should have the lowest role that lets them do their job.

The Plugin Inventory

Count them, and for each one answer whether it is still used, still maintained and still worth the weight. A plugin with no update in two years and an open support forum full of unanswered threads is a liability waiting for its turn.

Quarterly and Yearly

The PHP Version

Check what your site runs and whether that version is still supported. The PHP project publishes its support dates, and running past them means security fixes have stopped. Test on staging before moving, because old code and old plugins are where the breakage lives.

A Real Restore Test

Restore the backup to a staging site and look at it. This is the task everyone skips and it is the only one that proves the rest of the backup strategy works. Do it once a quarter and you will find the problem on a Tuesday afternoon instead of during an outage.

Licences and Renewals

Premium plugins, the theme, the SSL certificate if it is not automatic, the domain. An expired plugin licence usually keeps working while quietly stopping updates, which is the worst possible failure mode because nothing appears to be wrong.

Content and Search Review

Which pages bring traffic, which ones have quietly died, what is out of date, and what the search console is complaining about. This is where maintenance stops being defensive and starts earning something.

Updates Are the Part That Breaks Sites

Almost every maintenance disaster is an update applied without a way back. The method that avoids it is not complicated.

  1. Take a backup first, files and database, and know where it is.
  2. Use staging for anything significant. Most decent hosts include a one click staging site, and it turns an irreversible action into a test.
  3. Update one thing at a time when you are being careful. If ten plugins go on together and the site breaks, you now have a second problem, which is finding out which one did it.
  4. Look at the site afterwards. Not the dashboard. The homepage, a product or post page, the checkout or the main form, in a logged out browser.
  5. Keep a rollback option. Knowing how to restore the previous version of a single plugin turns a bad afternoon into five minutes.
  6. Automate security updates only. Automatic minor core and security plugin updates are worth having on. Automatic major updates on a complex site are how people find out their builder changed.

One more rule that saves more sites than any of the above: never edit theme or plugin files directly. The next update overwrites the change and the bug appears weeks later with no obvious cause. Use a child theme or a small custom plugin.

Backups, Where Most Sites Are Weaker Than They Think

Almost every site has backups. Far fewer have backups that would survive the event they are for.

  • Off the server. A backup stored on the same hosting account disappears with the account, and that covers a hack, a billing failure and a provider outage.
  • Files and database together. A database without the uploads folder restores a site with no images. The two have to be taken as a pair.
  • More than one generation. If a problem is found three weeks late, a single nightly backup has already overwritten every clean copy. Keep daily for a fortnight and weekly for a few months.
  • Tested. A backup is a hypothesis until it has been restored.
  • Known recovery time. How long it takes to get the site back is a business number, and most people have never measured it.

A reasonable target for a small business site is daily backups kept off site for thirty days, with a restore tested every quarter. That is not expensive and it removes the category of problem that ends companies.

Security Without the Theatre

Most WordPress compromises are not clever. They come through an outdated plugin, a weak password or a plugin downloaded from somewhere it should not have been.

  • Two factor authentication on every administrator account. The single highest value change available, and it takes ten minutes.
  • Limit login attempts and move or protect the login URL. Brute force traffic is constant and it is not personal.
  • Least privilege. Most people writing content need Author or Editor, not Administrator.
  • Remove what you are not using. Deactivated plugins and unused themes still sit on the server and still contain their vulnerabilities.
  • Never use nulled premium plugins. The cracked version is the distribution method for the backdoor. This is not a moral point, it is how those sites get owned.
  • A firewall or security plugin, but only one, and with its scanning scheduled rather than running on every page load.
  • HTTPS everywhere, with mixed content fixed rather than ignored.

The WordPress project keeps a hardening guide covering file permissions and server level settings for anyone who wants to go further.

Performance Is a Maintenance Task, Not a One Off

Sites get slower by accretion. Nobody makes a decision to slow a site down, it just gathers weight.

  • Caching, configured once and checked after major changes, because a stale cache causes its own support tickets.
  • Images, which are the main cause of a heavy page. Correct dimensions, modern formats and lazy loading below the fold.
  • Plugin weight. Measure what each one adds. A single slider or analytics plugin can cost more than everything else combined.
  • Database size, covered above, and noticeable on sites with heavy post revisions or a shop.
  • Hosting. There is a floor below which no optimisation helps, and cheap shared hosting with an overloaded server is that floor.

When Something Breaks

A short list covers most emergencies, and knowing it in advance is the difference between ten minutes and a ruined day.

A White Screen

Usually a fatal PHP error from a plugin or theme. Turn on debug logging to a file rather than to the screen, read the last error, and deactivate the named plugin by renaming its folder over FTP or the file manager if you cannot reach the dashboard.

A 500 Error

Often the server rather than WordPress. Check the host error log, and check whether a recent edit to .htaccess is the cause. Renaming that file and resaving permalinks resolves a surprising number of them.

Locked Out of the Admin

Reset the password through the database or create a user through a hosting tool. A security plugin that has blocked your own address is a common cause, and the block is usually cleared from the same plugin’s tables.

The Site Looks Broken After an Update

Clear every cache, including the plugin cache, the host cache and the CDN. If it persists, roll the plugin back to its previous version and report it to the developer rather than living with it.

Mixed Content Warnings

Something is loading over HTTP on an HTTPS page, almost always a hard coded image URL in old content. Fix it in the database with a search and replace rather than with a plugin that rewrites every page on the fly.

Doing It Yourself or Paying Someone

For a simple site with a handful of plugins, an hour a month is genuinely enough, and the checklist above is the hour.

It stops being enough when the site makes money, when downtime costs more than the fee, when there is a shop or a membership involved, or when nobody internally wants to be responsible for a restore at nine on a Sunday evening.

If you are buying it, the questions worth asking are specific:

  • Where are the backups stored, how long are they kept, and have you restored one for another client this year?
  • Do you test updates on staging, or apply them directly to the live site?
  • What is the response time when the site is down, and does that include weekends?
  • Do I get a monthly report that says what was actually done?
  • If I leave, do I get the backups and the access, and in what form?

A plan that cannot answer the first and the last of those is selling an update button with a subscription attached.

Keep a Log

The least technical item here and the one that pays off most.

Write down what was updated, when, and what broke. Six months later it answers the only question that matters during an incident, which is what changed. It also makes handovers possible, and it turns maintenance from a vague obligation into a record of work that a client can see.

A dated list in a document is enough. The tool does not matter.

The Tools Worth Having

You do not need many, and adding more plugins to solve maintenance is its own problem. Five categories cover it.

Backups

One plugin or, better, a host level backup with off site storage. What matters is the destination and the retention, not the brand. If the only copy lives in the same hosting account, it is not a backup, it is a convenience.

Uptime Monitoring

External, so it is not running on the server it is watching. Set it to check more than the homepage, because a cached homepage can look healthy while everything behind it is failing.

A Staging Site

Most decent hosts include one click staging. If yours does not, that is a reason to look at the hosting rather than a reason to update live and hope.

Security

One plugin, not three. Two security plugins running scans against each other produce false alarms and a slow dashboard, and neither is better than one configured properly.

Something That Records What Happened

An activity log plugin, or just a document. When a site breaks, the first question is what changed, and a log answers it in seconds.

What the Hour Actually Looks Like

In practice, a monthly maintenance hour on a normal business site runs roughly like this.

  1. Five minutes. Confirm the last backup ran and check its size against the previous one.
  2. Five minutes. Read the update list, decide what goes on now and what waits, and apply security releases.
  3. Ten minutes. Push the rest to staging, update, and click through the five pages that matter.
  4. Ten minutes. Apply to live, clear caches, and check the same five pages logged out.
  5. Ten minutes. Send a test through every form, and check one page that depends on the database.
  6. Ten minutes. Database cleanup, 404 report, user list, and a glance at the performance numbers against last month.
  7. Ten minutes. Write the log entry and note anything that needs a decision later, such as a plugin that has not been updated in a year.

The reason it fits in an hour is that the heavy work happened once, when backups, staging, monitoring and roles were set up properly. Sites where maintenance takes a whole morning every month are usually sites where that setup was never done.

Looking After Several Sites

The approach changes once you are past about three sites, because doing the same hour five times stops being realistic.

  • Standardise. The same backup tool, the same security plugin and the same host across the estate turns five problems into one.
  • Use a management dashboard that shows updates and backup status for every site in one place, and keep the per site checks for anything it cannot see, such as whether the forms work.
  • Stagger the updates. Apply a plugin update to the least important site first and leave it for a day. The least important site becomes your canary.
  • Keep one list of what runs where. Which site has which premium licence, which PHP version, which host, which client owns it.
  • Write down the recovery steps once and make them the same everywhere, so restoring a site is a procedure rather than an investigation.

That standardisation is also what makes the work sellable. A process that is the same on every site can be explained, priced and handed to somebody else.

Frequently Asked Questions

What does WordPress maintenance include?

Updates to core, theme and plugins, backups that are stored off site and tested, security checks, database cleanup, performance monitoring, broken link fixes and confirmation that forms and key pages still work.

How often should I do WordPress maintenance?

Weekly for uptime, forms, plugin updates and backup confirmation. Monthly for core and theme updates, database cleanup, 404s, performance and user accounts. Quarterly for PHP version, restore tests and licence renewals.

What happens if I never update WordPress?

The site keeps working until it does not. Known plugin vulnerabilities are published and scanned for automatically, so an unpatched site is a target, and eventually the host will move you to a newer PHP version that old code may not survive.

Should I turn on automatic updates?

For minor core releases and security fixes, yes. For major plugin versions and anything that touches a page builder or a shop, no, because those need a staging test and a way back.

How do I update plugins safely?

Back up first, use staging for anything significant, apply updates in small batches, check the live site logged out afterwards, and keep a way to roll a single plugin back to its previous version.

Where should backups be stored?

Somewhere other than the hosting account, because a backup on the same server disappears with the account. Keep files and database together, hold several generations, and restore one every quarter to prove it works.

Why has my WordPress site got slower?

Usually accumulation: more plugins, uncompressed images, a database full of revisions and expired transients, and a caching setup that stopped matching the site. Measuring the same pages monthly shows the trend.

What causes the white screen of death?

A fatal PHP error, almost always from a plugin or theme. Enable debug logging to a file, read the last error, and deactivate the named plugin by renaming its folder if you cannot reach the dashboard.

Can I edit theme files directly?

You can, and the next update will overwrite the change. Use a child theme for template changes and a small custom plugin for functionality so your work survives updates.

Is a maintenance plan worth paying for?

It depends on what downtime costs you. For a simple brochure site, an hour a month in house is enough. For anything that takes payments or generates leads, the fee is usually less than one lost day.

If you do nothing else from this page, do three things: get backups off the server, put two factor authentication on the administrator accounts, and send a test through your contact form. Those three cover the failures that cost the most and take about twenty minutes between them.

More from us: advanced copywriting techniques to boost your SEO.

10 Advanced Copywriting Techniques To Boost Your SEO

Advanced Copywriting Techniques

Are you looking for ways to make your copywriting stand out from the crowd? This article provides an in-depth look at the techniques used by experienced copywriters to create effective, attention-grabbing content.

We’ll cover topics such as identifying your target audience, leveraging storytelling, using active voice, and testing and optimizing. By implementing these strategies, you can take your copywriting to the next level and capture more readers’ attention.

Read on to learn how you can write words that boost your SEO!

1. Identify Your Target Audience

Knowing your target audience is a key element of effective copywriting. By understanding your readers’ needs, interests, and pain points, you can craft content that speaks to them directly and resonates strongly with their experiences.

Take time to research your target audience and what they want in your content. Consider the age range, gender, location, interests, and other factors that will help you develop an accurate picture of your readers to tailor your message to them.

2. Keep It Simple

When writing copy for SEO, one of the most important rules is to keep it simple. Don’t try to be too clever with your words – focus on making your message clear and concise.

Your content should be easy to read and understand so that your readers can quickly digest the information. Use short sentences and paragraphs, and avoid complex words or phrases. The goal is to ensure both search engine bots and human readers easily understand your message.

Keeping your copy simple will help ensure that your content is picked up by search engines, resulting in higher rankings and more website traffic.

3. Use Strong Calls-To-Action (CTAs)

A strong call-to-action (CTA) can differentiate between a successful website and one that fails to convert its visitors into customers. CTAs should be clear, concise, and relevant to your target audience to capture their attention and encourage them to take action.

To create an effective CTA, consider what you want people to do after reading your content, such as signing up for a newsletter or downloading a free report. Ensure the CTA is easy to understand and visible on the page, so it’s not overlooked.

Additionally, consider adding incentives to increase conversions, such as offering discounts or exclusive access.

With the right CTA, you can turn more of your website visitors into leads and customers.

4. Leverage Storytelling

Storytelling is a powerful tool for copywriters to capture their readers’ attention and draw them into the main message. Leveraging storytelling in your writing can help create an emotional connection with the reader, which can be especially useful in SEO. By crafting compelling stories around your keywords or subject matter, you can effectively increase the chances that readers will click through to your website.

Storytelling techniques such as creating vivid characters and settings, using sensory language, and establishing conflict can help make your content more engaging and memorable, thus boosting its SEO potential.

5. Include Specific Data

Regarding copywriting for SEO, including specific data can be an effective way to improve your ranking. Specific data from statistics, studies, and research findings can add authority and credibility to a website or blog post.

Not only does this help to demonstrate that you are knowledgeable about the topic at hand, but it also helps to give readers more confidence in the accuracy of your content. Furthermore, including specific data can help draw attention to key facts and figures and make them easier to remember. As such, using specific data as part of your copywriting strategy can be a great way to boost your SEO.

6. Use An Active Voice

Using an active voice in your copywriting is essential for optimizing your SEO and ensuring your content gets noticed. Using an active voice lets you quickly and clearly communicate your message to readers.

When written correctly, using an active voice will help keep readers engaged, allowing them to understand better the point you’re trying to make without any confusion or ambiguity. Additionally, using an active voice helps make sentences shorter and easier to read, improving your search engine rankings.

7. Avoid Jargon

Jargon can be confusing and off-putting for readers and likely cause them to lose interest in your writing. Instead, focus on using simple language that your readers can easily understand. This will make your content more accessible and help ensure that they read through to the end. Additionally, avoid using overly technical words or industry-specific terms, as these are also likely to alienate your audience.

8. Focus On Benefits

One of the most important things you can do is focus on your product or service’s benefits. This helps potential customers understand what makes your offer unique and why they should choose you over a competitor.

By emphasizing the positive features and advantages of your products or services, you’ll be able to draw in more leads and convert them into sales. Additionally, focusing on the benefits will help to improve your SEO because people are more likely to search for words associated with the benefits than those related to features.

9. Be Consistent

Consistency is an important element of effective copywriting. Not only does it help ensure that your message is clear and consistent throughout your entire piece, but it can also help boost your SEO.

For example, if you are writing about a particular topic or product, use the same terms and phrases throughout your content to create keyword consistency. This will help search engines easily recognize the relevance of your content and rank it higher in organic search results. Additionally, keep your style and tone consistent throughout your copy as well; this will make your piece more appealing and engaging to readers.

Consistent with your copywriting techniques can effectively increase your SEO rankings and draw more attention to your content.

10. Test & Optimize

Testing and optimizing your copywriting is an important part of boosting SEO. After you have written a piece, it’s best to test different versions to see what works best. You can do this through A/B testing or use software like Google Optimize to make changes quickly and easily.

For example, try changing the headline, sub-headings, images, or even the placement of CTA buttons. Then track the results to see which version performs better. This helps you determine what resonates with readers and keeps them engaged.

11. Use Images in Your Blog Posts

Including images in your blog posts can be a great way to draw attention and engage readers. Images are eye-catching and break up the text, making it more interesting for people to read.

People are visual creatures, so using images effectively gives them an understanding of the content you’re presenting. Not only that, but research has shown that content with images gets 94% more views than content without images.

Using images can also help boost your SEO rankings by increasing engagement levels and improving click-through rates from search engine results pages.

12. Include More Questions in Your Headlines

Did you know that headlines with questions get 73% more social shares than those without? According to research conducted by Conductor, crafting an effective headline for your copywriting can make a huge difference in terms of engagement.

By asking the right question in your title and creating intrigue, readers are likelier to click on it and share it across their social media channels. This is an advanced technique that can be used to boost SEO and help spread awareness about your content.

Even though it may seem intimidating at first, mastering this strategy can have positive long-term effects for your business.

Why Invest in a Copywriting Agency?

Copywriting agencies offer a range of services that can help to boost your business. Investing in a copywriting agency is a great way to make sure that you are creating high-quality content for your website and other digital marketing platforms.

A copywriting agency will be able to provide unique, creative, and engaging copy tailored to meet the needs of your target audience. They also have the experience and knowledge necessary to ensure that the content they produce is optimized for search engine optimization (SEO) to help drive more traffic to your website.

Copywriting agencies understand the nuances of language, syntax, grammar, and punctuation, which are all important elements to consider when crafting interesting and informative content. Additionally, these professionals can review existing content to identify areas where it can be improved or updated for maximum effectiveness.

By investing in top copywriting agencies, you can rest assured that your business is putting its best foot forward online.

Conclusion

Copywriting is a powerful tool for engaging customers and creating successful marketing campaigns. You can create persuasive and compelling content that resonates with your target audience using advanced copywriting techniques.

Remember to identify your target audience, keep it simple, use strong calls-to-action, leverage storytelling, include specific data, use active voice, avoid jargon, focus on benefits, be consistent, and test and optimize.

With these tips, you can craft words that win and drive more conversions.

Finding Free Abandoned Content

Finding Free “Abandoned Content” That You Can Use On Your Site

Finding Free “Abandoned Content” That You Can Use On Your Site

Tens of thousands of domains expire every day, but what happens to the content that’s on those sites? It just disappears into nothingness, never to be seen again… right?

What if you could magically get the content that other people have abandoned, even after it’s gone from the search engines?

Well, you definitely can with hgint.com!

But (and here is where the magic happens) Google doesn’t crawl expired domains! If the original owner just let his site expire then obviously he doesn’t want it, and if it doesn’t appear anywhere in the search engines then we can use it without it being considered “duplicate content.”

Now before we go any further let’s talk about the ethics of this….

Is this stealing? It’s recycling.

No, I don’t consider it stealing. Taking unused webpages from Dropl.io is, to me, the same as taking something out of the trash. If I walked in your house and took a piece of furniture you made then that, of course, is stealing. But if I saw that same piece of furniture in your trash out by the curb then obviously you don’t want it, so taking it is fine.

I see websites the same way. Yes, the original owner created it, but if they let the site expire then they obviously don’t want it anymore, so I have no problem taking it!

So Let’s Get Started

To get started we will use ArticleMarket, it’s an awesome place to get pre-written blog articles for PBNs, blogs and more..

ArticleMarket is free to use, but you will need to create an account in order to use all the advanced features.

Once you’ve logged in to your free account the first step is to find the expired domains for your niche. Let’s say I’m looking for content for a food blog, I’ll start out by doing a search for the keyword “food.”

That gave us over 75000 results! There’s no way we can sort through that many sites, so we need to eliminate the junk domains that probably don’t have any good content.

Thankfully ArticleMarket has search filters we can use for that. To see all the filter options just hit the “Show Filter” link right above the search results.

Here are the things I look for to help me separate the junk sites from those that probably had good content.

High quality sites usually have…

  • A real Domain Rating of at least 5.
  • An Alexa rank (even if it’s not a good rank).
  • A .com, .net, or .org extension.
  • Only words in the domain, no random characters.

So let’s add those filters onto our search. Under the “Common Filter” tab check the following options.

Now click the “Additional Filter” tab and choose these options…

If you want domains in other languages besides English then, of course, choose the appropriate language.

Now we can see that those 75,ooo domains have been narrowed down to 247, which is a much more manageable number.

All we have to do now to look up each domain at archive.org and see if there’s any content we can use. Yes, it will take some time, but your hard work will pay off!

Head over to archive.org and start looking up each site. Once you search for the site you’ll get a list of all the dates that site has been crawled by archive.org. The most recent ones might be “expired domain” messages, so you may have to look a few weeks or months back to get the actual site.

As you can see from the picture below I’ve found what looks to be a good expired site with some quality abandoned content, RealFoodFreaks.com.

In fact, it looks like that site has hundred of pages of unique recipes and health food related content.

But hold on! Before we start do anything else we need to make sure this content is actually abandoned. The owner could have let the site expire because they moved to a new domain, so let’s do a quick Google search using a random sentence from the page.

Everything looks good! This article isn’t found anywhere else, so it’s unique abandoned content we can use on our site.

Now it’s your turn… Try it yourself and let me know how it goes, and if you have any questions just ask them in the comment section down below.

A few extra helpful tips….

1: When you choose your random sentence to search for make sure you pick one that is at least a few paragraphs down from the top of the page. If you choose a sentence near the top of the text you’ll pick up excerpts from social media sites in the search results. Short excerpts like this are fine, and they shouldn’t stop you from using the content.

2: Never pretend to be the original author. I always include a disclaimer at the bottom of my pages that says “Originally published on whatever.com by author’s name”

3: If someone contacts you claiming to be the original author and asks you to remove the content, do it! Even though it’s abandoned it is, after all, their copyrighted work and we shouldn’t use it if they still want it.
Explore..

Best Sites That Help You in Buying High Authority Expired Domains

Best Sites That Help You in Buying High Authority Expired Domains

Buying High Authority Expired Domains: 11 Best Sites

The necessity of domain names is non-ignorable when it comes to getting an online space for your website. And for this, we do a lot with our domain names to prove our uniqueness but have we ever wondered about using the expired domain names? If not, just imagine how stress-free it could become, if we get an opportunity to buy a domain that already has amazing backlink profile and traffic. You can easily buy expired domains and can use them to harness your power on the internet.

Expired domain names are actually the domains that were once registered by the owner but were not renewed. Such domains become useless and can be smartly used by others. Citation Flow is a metric between 0 and 100 that calculates the backlinks of the particular expired domain from unique IPs and hence makes it easy for you to compare and choose among all.

Here I bring to you the Best expired domain list and websites that help you in buying reliable and strong Expired Domains.

  • Dropl.io: An affordable tool that helps the users to find the expired domains. The expired domains are listed by this software along with its market price, traffic, number of bids and also you can place your bidding offer to buy that expired domain.By looking deep into the details, you can buy any good reputed name using this tool. It has three methods of finding expired domains, auctions, and expiring domains, first by crawling the list of website domain names, second by crawling using a related keyword and third by, endless crawling. You can easily search using the keywords and this tool will freely help you by crawling every page for every niche related keyword.
  • NameCheap Domains: Ample of domains gets expired each day. If you are one of those wise individuals who can sense the vitality of expired domain names, then this platform is must to try platform that also helps the users to avail the expired domains, deleted domains and also the new ones. It allows the users to make a choice and then offer a bid for that domain name.
  • ExpiredDomains.net- Everybody wants to gather all the information for an expired domain without wasting a penny and this platform helps us in our way. This is the one-stop solution for all your needs. You can easily get the names of expired domains and other details without even signing in. Right from the expiry date to the drop date, you can easily get all the details.
  • Domain Hunter Gathererator- There is thousands of buyers who are buying the expired domain names from domain auction to save their years of hard work. With, Domain Hunter Gatherer, all you need to pay is just the cost of registration and after this you can go ahead with your search operation of finding the desired aged domain. Links like CNN.com, Wikipedia etc. can also be found with this tool and with smaller registration fees. Name.com- Another platform that has gained immense popularity and reputation is the Name.com. You can easily get along with it for finding the desired expired domain name using search filters. It also offers easy checkout process.
  • DomCop: Reason behind mentioning this name is, part from the expired domain auction, it offers ample of other benefits like Page Rank, citation flow, traffic rate, web rank and much more, that too within a click. It offers the users a way to compare the sites to make a wise decision.
  • Domain Monster: As the name suggests, this platform works as a monster ranging from a domain registration to finding the expired domains and more. It will give you whole information about the expired domain names and also gives you the chance to bid.
  • Domainhole: This platform regularly updates the list of terminating domains as numerous domains get expired every day. Hence, you easily remain updated with this platform and can narrow your search using keywords and filters as per your choice.
  • Domainsbot.com: This is a reliable and sure shot winner when it comes to finding the expired domain names using numerous filters that can narrow down your research. Once your selection is done, you can easily purchase the desired domain.
  • NameJet: This platform helps the users to participate in the domain auctions with desired domain names which have expired. It is one of those reliable platforms that you can make investments on without giving a second thought.
  • Stuckdomains.com: This easy to check in and check out portal is perfect for the quick bees to search and evaluate the desired domain name without any registration fee. Also, the filter options are also few which makes easy for the new users to find the desired aged domain.
  • DomainPeel.com: Another helpful name in the list as it offers spam-free expired domain list, hence offers you with only authentic info. It is perfect for the beginners as well who have very less knowledge regarding this industry.

I hope the aforementioned data helps you as it did to me. All the best and grab the best-expired domain name for your new online presence. If you need help building a website, Socialfuel is definitely recommended.

Explore..