There's no nice way to put this, so I'm just going to come out and say it: WordPress websites are prime targets for hackers. It's not that WordPress itself is an inherently unsafe content management system. In fact, I would go so far as to say that the WordPress security team does a <em><strong>fantastic<\/strong><\/em> job in developing a secure platform as well as maintaining a strategy for it.\r\n\r\nThat said, WordPress is a lot like Scarlett Johansson. Both are perceived as sleek, smart, professional, and reliable entities within their given niches. And they both continue to churn out big successes that earn them rave reviews. (ScarJo currently participates in the <em>Avengers<\/em> movie series whereas WordPress hosts some of the most high-profile websites around the world.)\r\n\r\nBut with all that good work and a solid reputation to back it up, both have become easy targets for people wanting to do them harm. For ScarJo, it was an unfortunate breach of privacy when someone leaked sensitive photos of her on the web. For WordPress, well, it's had its share of security breaches over the years.\r\n\r\nThere is a reason why WordPress is so popular.\r\n\r\nThe content management system performs consistently well for its users and makes it possible for companies of all sizes to sufficiently conduct business online. The <a href="https:\/\/pagely.com\/blog\/guide-to-wordpress-security\/">matter of WordPress security<\/a> shouldn't be called into question at this point, particularly with such robust security options including in managed WordPress hosting.\r\n\r\nWhat we need to focus on is getting its users to do the right thing and take responsibility for protecting their instances.\r\n<h2>WordPress Security: A Brief History of Exploits and Vulnerabilities<\/h2>\r\nYou've come here because you're wondering if WordPress is safe enough to run your online business from. And the answer to that is "Yes!" however...\r\n\r\nThere is always a "but" or "however" whenever we talk about securing a business's assets. Think about it like this:\r\n\r\nYou have a license that allows you to rent office space and conduct business in your city. You also own the domain name that enables you to do business online. But just as the physical location of your operations requires extra fortification--e.g. surveillance systems, security desks, restricted access privileges, business insurance, and so on--so too does your online location.\r\n\r\nPersonally, I think concerns over WordPress security are a bit overblown. I'm not trying to diminish the severity of security breaches that have hit WordPress servers. However, if you look at how quickly each was resolved as well as the circumstances surrounding how those exploits actually ended up on websites in the first place, you'll see that the fault doesn't always lie with the CMS. In fact, many of the issues stem from the things we <em>add<\/em> to it.\r\n\r\nTo demonstrate my point, here are some examples of high profile security exploits and vulnerabilities that have appeared over the last decade:\r\n<h3>The Slider Revolution Plugin Problems<\/h3>\r\nAs noted in this paper by <a href="https:\/\/securityaffairs.co\/wordpress\/35431\/cyber-crime\/revslider-plugin-vulnerable.html" target="_blank" rel="noopener noreferrer">Security Affairs<\/a>, the Slider Revolution (RevSlider) plugin has had its fair share of security issues. On more than one occasion, hackers have used the plugin to gain entry into WordPress websites for the purposes of installing malware.\r\n\r\nOne of the things that complicated this specific security exploit was the fact that a number of commonly used WordPress themes included the RevSlider. So, even if users who had installed the plugin issued the patch and followed the recommended security protocols, users who received the plugin through their theme might not have known to do the same (unless the theme developer tipped them off to it).\r\n<h3>The Panama Papers Breach<\/h3>\r\n<a href="https:\/\/www.wordfence.com\/blog\/2016\/04\/panama-papers-wordpress-email-connection\/" target="_blank" rel="noopener noreferrer">The Panama Papers hackers<\/a> didn't strictly exploit a known security weakness in WordPress in order to obtain sensitive data from Mossack Fonseca (MF). However, what they were able to extract through WordPress turned out to be quite valuable. And guess how they were able to get through?\r\n\r\nThe Slider Revolution plugin.\r\n\r\nIn all fairness, the law firm was to blame for this particular breach as it was determined that hackers exploited a vulnerability in an older version of the plugin. Because the persons responsible for maintaining the MF website hadn't updated the plugin to the latest version, their website was left wide open to attack.\r\n<h3>The 2015 Mass Plugin Coding Error<\/h3>\r\nThis was related to the WordPress Codex. What happened was this:\r\n<ul>\r\n \t<li>The Codex published information on how to use two functions when building a WordPress plugin.<\/li>\r\n \t<li>The instructions provided were not clearly stated, which led to a number of developers actively introducing a vulnerability that left their customers' sites open to a cross-site scripting attack.<\/li>\r\n \t<li>The plugins affected weren't a bunch of unknowns either. Many of Automattic's own plugins were part of the mass contamination.<\/li>\r\n<\/ul>\r\n<a href="https:\/\/blog.sucuri.net\/2015\/04\/security-advisory-xss-vulnerability-affecting-multiple-wordpress-plugins.html" target="_blank" rel="noopener noreferrer">Once the error was noted<\/a>, WordPress worked in conjunction with the developers of all affected plugins to fix the error and issue a patch immediately to all users. All other developers were put on high alert to check their plugins and fix the erroneous code.\r\n<h3>The TimThumb Image Resizing Tool Wreaks Havoc in Themes<\/h3>\r\nTimThumb was an image resizing script used within a number of WordPress themes. Of course, this was around the time when responsive web design started to take center stage in discussions around web design and so it makes sense that theme developers would want to use a tool that simplified the process for <a href="https:\/\/pagely.com\/blog\/pressthumb\/">resizing images<\/a>.\r\n\r\nNevertheless, no one originally thought to look into how TimThumb worked despite how pervasively it was used in WordPress themes. Basically, it hooked directly into the WordPress database and gave anyone unwarranted access to the backend of many websites. Because of this, hackers could inject malicious code without having to do much work to breach a site.\r\n\r\nAs of today, <a href="https:\/\/www.binarymoon.co.uk\/2014\/09\/timthumb-end-life\/" target="_blank" rel="noopener noreferrer">TimThumb no longer exists<\/a>--and it's because of how much damage this tiny script had the potential to bring to so many websites.\r\n<h3>The WordPress REST API Vulnerability<\/h3>\r\nThis is a big one and it occurred quite recently, too.\r\n\r\nWhen <a href="https:\/\/developer.wordpress.org\/rest-api\/#why-use-the-wordpress-rest-api" target="_blank" rel="noopener noreferrer">WordPress introduced the REST API<\/a>, it was meant to open up the content management system in a huge way for web developers:\r\n\r\n"Our imagination is the only limit to what can be done with the WordPress REST API. The bottom line is, if you want a structured, extensible, and simple way to get data in and out of WordPress over HTTP, you probably want to use the REST API."\r\n\r\nHowever, there was <a href="https:\/\/blog.sucuri.net\/2017\/02\/content-injection-vulnerability-wordpress-rest-api.html" target="_blank" rel="noopener noreferrer">a bug<\/a> introduced with <a href="https:\/\/pagely.com\/blog\/react-js-wordpress-rest-api\/" target="_blank" rel="noopener noreferrer">the REST API<\/a> that allowed anyone to add, change, or delete content on any WordPress website. When the vulnerability was discovered, WordPress worked to patch the bug and silently issued it out to users. While that was all well and good, <a href="https:\/\/thehackernews.com\/2017\/02\/wordpress-hack-seo.html" target="_blank" rel="noopener noreferrer">thousands of users<\/a> had yet to issue the patch long afterward.\r\n<h2>What Can WordPress Users Do to Secure Their Websites?<\/h2>\r\nWordPress is not typically a breeding ground for security exploits. When it or any of its contributing developers, have been guilty of introducing vulnerabilities into the system, they are fixed swiftly. However, without the active participation of WordPress users to protect their websites from external threats, WordPress might never really have a chance to be seen as a 100% secure content management system (do such a thing really exist?).\r\n\r\nSo, I want to talk next about what you can do to successfully run your business from WordPress and keep it safe in the process.\r\n<h3>Step 1: Understand the Threats<\/h3>\r\nTo talk about threats to WordPress security, we need to look at this from two angles. The first is from the perspective of what exactly within WordPress allows the intruding presence in. The second is on the kinds of malicious injections your site may be vulnerable to.\r\n\r\n<b>Inside WordPress<\/b>\r\nIn 2016, <a href="https:\/\/www.wordfence.com\/blog\/2016\/03\/attackers-gain-access-wordpress-sites\/" target="_blank" rel="noopener noreferrer">Wordfence reported<\/a> that roughly 56% of all hacked WordPress websites stemmed from a plugin.\r\n\r\n<img class="aligncenter size-full wp-image-14453" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Wordfence-Hacked-Sites.png" alt="Wordfence Hacked Sites" width="900" height="539" \/>\r\n\r\nOver a year later, <a href="https:\/\/www.wpwhitesecurity.com\/wordpress-security\/statistics-highlight-main-source-wordpress-vulnerabilities\/" target="_blank" rel="noopener noreferrer">a study of WPScan's Vulnerability Database<\/a> found WordPress plugins to still be the prime suspect in WordPress security breaches, being responsible for 54% of all vulnerabilities detected.\r\n\r\n<img class="aligncenter size-full wp-image-14454" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/WPWhiteSecurity-Chart.png" alt="WPWhiteSecurity Chart" width="900" height="616" \/>\r\n\r\nAs you can see from the data, <a href="https:\/\/pagely.com\/blog\/wordpress-security-plugins\/">WordPress plugins<\/a> aren't the only way hackers and bots are breaking their way into websites. Brute force attacks on the login are the second most common form of attack. Followed by WordPress core and theme vulnerabilities.\r\n\r\n<b>Outside WordPress<\/b>\r\nOn the other side of this are the <em>kinds<\/em> of attacks that target your files, the point of entry, plugins, themes, and other vulnerable spots in WordPress. Familiarize yourself with the most common types of security breaches so you'll know how to spot them when they happen.\r\n\r\nAccording to <a href="https:\/\/www.wordfence.com\/blog\/2016\/04\/hackers-compromised-wordpress-sites\/" target="_blank" rel="noopener noreferrer">this 2016 Wordfence report<\/a>, these are the types of actions hackers take once they're inside WordPress:\r\n\r\n<img class="aligncenter size-full wp-image-14455" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Wordfence-What-Hackers-Do.png" alt="Wordfence What Hackers Do" width="900" height="497" \/>\r\n\r\nYou may be surprised to see that most hackers aren't looking to steal your customer's or business's data. Instead, a lot of their actions are motivated by harming a website's reputation (through defacement or pulling a site down altogether) or by using it as a vehicle to infect others (through spam, phishing, and malware, among other tactics).\r\n\r\nUnderstanding the vulnerabilities of WordPress and what hackers are looking for is only the first step. Now, let's look at how you can raise your defenses.\r\n<h3>Step 2: Put up a Defensive Line<\/h3>\r\nIt's not enough to install a plugin and call it a day--especially as we've seen in the high-profile cases of security breaches mentioned above. To properly defend a WordPress website requires a multi-pronged approach. Everything from your server to your customer's data needs to be vigorously defended from attack.\r\n\r\nHere are the 11 things that need to be part of your <a href="https:\/\/pagely.com\/blog\/guide-to-wordpress-security\/">WordPress security strategy<\/a> going forward:\r\n\r\n<b>1. Use Secure Hosting<\/b>\r\n<img class="aligncenter size-full wp-image-14456" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/PressArmor.png" alt="PressArmor" width="900" height="324" \/>\r\n\r\nBefore you do anything else, make sure your web hosting plan has you covered. This translates to features like:\r\n<ul>\r\n \t<li>Datacenter security measures, including surveillance<\/li>\r\n \t<li>Avoiding shared hosting plans, as you can't mitigate security breaches from other sites that share your node<\/li>\r\n \t<li><a href="https:\/\/pagely.com\/tech\/" rel="noopener">Server-side security architecture<\/a> that includes a firewall and anti-malware software<\/li>\r\n \t<li>SSL certificate add-on<\/li>\r\n \t<li>Automated or managed backups<\/li>\r\n \t<li>Managed updates<\/li>\r\n<\/ul>\r\nEven better is to sign up for a <a href="https:\/\/pagely.com\/solutions\/secure-wordpress-hosting\/" rel="noopener">secure WordPress hosting<\/a> plan, so you can have experts handle some of the security measures I'm about to discuss for you.\r\n\r\n<b>2. Install an SSL Certificate<\/b>\r\nFor those of you who already have a website up and running, <em>and<\/em> it's still sitting on HTTP, get yourself an <a href="https:\/\/pagely.com\/blog\/definitive-guide-ssl-wordpress\/" rel="noopener">SSL certificate<\/a>. This certificate puts an extra encrypted buffer between your server and all others, which is why Google rewards <a href="https:\/\/pagely.com\/blog\/http-vs-https\/" target="_blank" rel="noopener noreferrer">HTTPS websites<\/a> with higher rankings.\r\n\r\n<img class="aligncenter size-full wp-image-14457" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Google-Secure-Connection.png" alt="Google Secure Connection" width="900" height="136" \/>\r\n\r\nNot only that, but Google also slaps a "Secure" label onto HTTPS web addresses to let visitors know when they're on a website that has this extra level of protection installed.\r\n\r\n<b>3. Remove Default Admin Username and Login<\/b>\r\nWith every new WordPress installation, you will be granted an "admin" username. Under no circumstances should you use this username. In fact, you should delete it completely. However, before you do, you must create a new admin user to replace it. Give yourself (or whoever the admin superuser is) a unique name. Then use WordPress's password generator tool to come up with a complex password.\r\n\r\n<img class="aligncenter size-full wp-image-14458" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/New-User-Password.png" alt="New User Password" width="900" height="345" \/>\r\n\r\nI would also suggest changing the login URL for your WordPress site. By default, WordPress will be located at something like:\r\n\r\n<em>https:\/\/thisisyoursite.com\/wp-admin\/<\/em>\r\n\r\nOr:\r\n\r\n<em>https:\/\/thisisyourothersite.com\/wp-login.php<\/em>\r\n\r\nPersonally, I like to use a plugin to do this. Ideally, it's one that handles other security protocols for you like <a href="https:\/\/wordpress.org\/plugins\/all-in-one-wp-security-and-firewall\/" target="_blank" rel="noopener noreferrer">All in One WP Security & Firewall<\/a>. With one quick switch, you can rename (and essentially hide) the main login page.\r\n\r\n<b>4. Hide WordPress Identifiers<\/b>\r\nRemember how I mentioned earlier that hackers can get into websites if users haven't updated their software to the latest and most secure versions? Part of the reason this is even possible is because hackers can easily track down websites running on outdated versions of WordPress or using themes with known vulnerabilities.\r\n\r\nRather than leave that data out in the open for hackers to discover and exploit, take steps to hide it.\r\n\r\nYou can hide your WordPress version by enabling that feature in your security plugin (like <a href="https:\/\/wordpress.org\/plugins\/wordfence\/" target="_blank" rel="noopener noreferrer">Wordfence<\/a>).\r\n\r\n<img class="aligncenter size-full wp-image-14459" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Hide-WordPress-Version.png" alt="Hide WordPress Version" width="900" height="142" \/>\r\n\r\nYou should also prevent others from discovering the list of usernames associated with your website (it'll make it all the more difficult for brute force attacks to take place):\r\n\r\n<img class="aligncenter size-full wp-image-14460" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Prevent-Username-Discovery.png" alt="Prevent Username Discovery" width="900" height="165" \/>\r\n\r\nIf you want to hide the name of your theme, you have a couple of options.\r\n\r\nThe first is to look within the Theme Customizer to see if it's easy enough to switch off. It should be in the Footer section. If not, you can edit the footer.php document on your site. There should be a section dedicated to "site-info". By deleting this, you'll remove the line at the bottom of the site that says what your site was made with. <a href="https:\/\/pagely.com\/blog\/wpbeginner-best-place-find-tips-tutorials-wordpress\/">WPBeginner<\/a> has <a href="http:\/\/www.wpbeginner.com\/wp-themes\/how-to-remove-the-powered-by-wordpress-footer-links\/" target="_blank" rel="noopener noreferrer">a quick tutorial<\/a> that will show you how to do this.\r\n\r\n<b>5. Install a Security Plugin<\/b>\r\nI've already mentioned a couple of different security plugins and how they can help fortify certain parts of your WordPress site. These kinds of plugins are also helpful in terms of providing:\r\n<ul>\r\n \t<li>A firewall<\/li>\r\n \t<li>Malware monitoring and protection<\/li>\r\n \t<li>DDoS scanner and protection<\/li>\r\n \t<li>IP blacklisting and whitelisting capabilities<\/li>\r\n \t<li>Geography-based blacklisting<\/li>\r\n \t<li>Enforcement of stricter password standards<\/li>\r\n \t<li>Enabling <a href="https:\/\/pagely.com\/blog\/set-two-factor-authentication-wordpress\/">two-factor authentication<\/a><\/li>\r\n \t<li>Monitoring of database, themes, and plugins for changes to files<\/li>\r\n<\/ul>\r\nIf you can, find yourself a WordPress security plugin that covers all these bases and more. As I'll mention a few points down, the fewer plugins you have installed on your system, the better. So, for all-in-one security solutions in WordPress, I'd recommend the following:\r\n<ul>\r\n \t<li><a href="https:\/\/wordpress.org\/plugins\/all-in-one-wp-security-and-firewall\/" target="_blank" rel="noopener noreferrer">All In One WP Security<\/a><\/li>\r\n \t<li><a href="https:\/\/wordpress.org\/plugins\/better-wp-security\/" target="_blank" rel="noopener noreferrer">iThemes Security<\/a><\/li>\r\n \t<li><a href="https:\/\/wordpress.org\/plugins\/sucuri-scanner\/" target="_blank" rel="noopener noreferrer">Sucuri<\/a><\/li>\r\n \t<li><a href="https:\/\/wordpress.org\/plugins\/wordfence\/" target="_blank" rel="noopener noreferrer">Wordfence<\/a><\/li>\r\n<\/ul>\r\n<b>6. Install Akismet<\/b>\r\nThe <a href="https:\/\/wordpress.org\/plugins\/akismet\/" target="_blank" rel="noopener noreferrer">Akismet Anti-Spam plugin<\/a> is such a simple one in terms of what it does. Yet, it can save your site as well as your blog readers from a whole lot of trouble by blocking malicious users from leaving comments that contain corrupt links within them.\r\n\r\n<b>7. Be Selective with Plugins and Themes<\/b>\r\nIn general, themes and plugins are just plain awesome. They decrease the amount of work you have to do from-scratch while also allowing you to quickly adopt newer design techniques that might otherwise take a while to master through coding. However, some WordPress themes and plugins need to be avoided.\r\n\r\nSo, here's what I would suggest:\r\n<ol>\r\n \t<li>Always fully vet any WordPress theme or plugin before you install it.<\/li>\r\n \t<li>Use only what you need. To start, install the <a href="https:\/\/pagely.com\/blog\/9-useful-enterprise-wordpress-plugins-for-2017\/" rel="noopener">enterprise plugin essentials<\/a>. You can add more as you find a need for them.<\/li>\r\n \t<li>Subscribe to the <a href="https:\/\/www.wordfence.com\/blog\/2017\/11\/october-2017-wordpress-attack-report\/" target="_blank" rel="noopener noreferrer">Wordfence security reports<\/a>. They list out the top themes and plugins that were most susceptible to security breaches. They also will often draw attention to fake plugins and themes created for the purposes of infiltrating websites.<\/li>\r\n<\/ol>\r\nAlso, once you're done with an old theme or plugin, get rid of it. Don't just deactivate it on the off-chance you might want to use it again in the future. Delete it entirely from your site. This'll free up storage, bandwidth, and also reduce the chances that a breach in that theme or plugin leads a hacker straight to you.\r\n\r\n<b>8. Keep Everything Updated<\/b>\r\nOutdated software is too often the reason why WordPress websites get hacked. There is a reason why WordPress sends you a notification whenever a new version of the core, your theme, or plugins are available.\r\n\r\n<img class="aligncenter size-full wp-image-14461" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/WordPress-Updates.png" alt="WordPress Updates" width="900" height="539" \/>\r\n\r\nGenerally, it's best to perform the update on a test version of your website. That way, if a new update creates a conflict with something else, you see the white screen of death, and your site goes down, as a result, you can save yourself the trouble of mistakenly issuing that update to the live site.\r\n\r\nThere are, of course, less severe issues that can happen when you update your WordPress software, too. Take, for instance, WooCommerce 3.3. This update had its users very excited. However, upon installation, many discovered that it created an issue with certain themes. Not a <em>huge<\/em> problem, but it was enough for WordPress to remove the version from the repository.\r\n\r\nSo, while you do need to keep everything updated--especially when security updates are issued--be careful in how you apply them to your site.\r\n\r\n<b>9. Generate Backups<\/b>\r\nOn a related note, you should have a system for generating regular backups of your WordPress site. In so doing, you'll have a way to instantly roll your site back to a recent version in case it gets pulled offline by a hacker or, as I just noted, a new plugin or update wreaks havoc on it.\r\n\r\nMany premium hosting plans--especially from managed WordPress hosts--will handle this for you. (They'll also handle WordPress updates, too!) If your hosting plan includes backups, take advantage of it and skip using a non-recommended plugin.\r\n\r\n<b>10. Restrict User Access<\/b>\r\nThe nice thing about a security plugin is that it will usually alert you to login activity with your admin users. (You can also watch what others do, too, but that might be overkill.) The reason I say this though is because, realistically, your site shouldn't have more than a few admins. Everyone else should have restricted access to WordPress. So, being able to watch over your admins can tip you off in case something odd is going down.\r\n\r\nAlso, by <a href="https:\/\/pagely.com\/blog\/wordpress-roles-capabilities\/">giving each user role<\/a> a custom WordPress dashboard, by blocking certain users from accessing plugins and themes, by changing read\/write permissions based on what they actually need to do, you can ensure that even once inside, a hacker can't do much.\r\n\r\nThe easiest way to restrict user access is to use a plugin like <a href="https:\/\/wordpress.org\/plugins\/user-role-editor\/" target="_blank" rel="noopener noreferrer">User Role Editor<\/a> that allows you to create custom rules for each role and block certain parts of WordPress based on them.\r\n\r\nI would also recommend you be mindful of your WordPress users. Say, for instance, an employee or contractor was recently terminated. Just as you would change passwords that allow them access to company software, you would want to do the same in WordPress. However, there's really no benefit in saving the username unless they were an author you want to continue attributing content to. Otherwise, delete them completely from the system to prevent their login credentials from ever becoming compromised.\r\n\r\n<b>11. Don't Store Sensitive Data in WordPress<\/b>\r\nWhether you use your WordPress site to collect leads or to generate sales, all that information needs to go somewhere. If you have the ability to do so, do not store that information inside of WordPress. You're basically just begging hackers to steal it from you.\r\n\r\nInstead, sign up with a secure third-party system that's been developed to store and protect this kind of information. For lead generation efforts, this means using a trusted customer relationship management (CRM) system like:\r\n<ul>\r\n \t<li><a href="https:\/\/www.hubspot.com\/" target="_blank" rel="noopener noreferrer">Hubspot<\/a><\/li>\r\n \t<li><a href="https:\/\/www.insightly.com\/" target="_blank" rel="noopener noreferrer">Insightly<\/a><\/li>\r\n \t<li><a href="https:\/\/www.salesforce.com\/" target="_blank" rel="noopener noreferrer">Salesforce<\/a><\/li>\r\n \t<li><a href="https:\/\/www.zoho.com\/crm\/" target="_blank" rel="noopener noreferrer">Zoho<\/a><\/li>\r\n<\/ul>\r\nFor sales, you will need a PCI compliant payment gateway to process your payments. If you're <a href="https:\/\/pagely.com\/blog\/woocommerce-guide\/" rel="noopener">using WooCommerce<\/a> to sell your services or goods, use one that seamlessly integrates into your store. My favorites are:\r\n<ul>\r\n \t<li><a href="https:\/\/www.2checkout.com\/" target="_blank" rel="noopener noreferrer">2Checkout<\/a><\/li>\r\n \t<li><a href="https:\/\/www.authorize.net\/" target="_blank" rel="noopener noreferrer">Authorize.net<\/a><\/li>\r\n \t<li><a href="https:\/\/www.braintreepayments.com\/" target="_blank" rel="noopener noreferrer">Braintree<\/a><\/li>\r\n \t<li><a href="https:\/\/stripe.com\/" target="_blank" rel="noopener noreferrer">Stripe<\/a><\/li>\r\n<\/ul>\r\nBy automating the collection of lead and customer data through these methods, you're also cutting down on the amount of time you'd otherwise spend managing them manually. I consider that a win-win.\r\n<h3>Step 3: Keep a Watchful Eye<\/h3>\r\nFinally, once your WordPress site is as secure as Fort Knox, make sure you have a plan for monitoring it for suspicious activity. WordPress may be secure now, but hackers never stop. They're always finding new ways to get inside of websites, so you need to be on high alert.\r\n\r\nThis means watching for the following signs:\r\n<ul>\r\n \t<li>Web traffic has suddenly dropped off.<\/li>\r\n \t<li>Site speed has slowed to a painful crawl.<\/li>\r\n \t<li>Your site doesn't appear in search results anymore, even when you search for your URL or the name of the site. (Google may have blacklisted the site if that's the case.)<\/li>\r\n \t<li>Your site is still in search results, but the metadata is all wrong (that's SEO spam for you...).<\/li>\r\n \t<li>There are new links embedded in your content that you didn't put there.<\/li>\r\n \t<li>Spammy pop-ups or ads appear on the site.<\/li>\r\n \t<li>Files have been changed in your database though no one on your team made them.<\/li>\r\n \t<li>There's a huge influx of new users.<\/li>\r\n \t<li>You're unable to send or receive emails through your website. (You'll usually discover this when a customer or prospect contacts you through another means to complain.)<\/li>\r\n \t<li>Your homepage has been defaced.<\/li>\r\n \t<li>Your site has gone down completely.<\/li>\r\n \t<li>You can't log into WordPress anymore.<\/li>\r\n<\/ul>\r\nAs soon as these changes have been detected, it's your job to go into full-on recovery mode. Of course, that depends on what sort of malicious activity took place. However, the first thing to do is check with your web host and WordPress security plugin. These two resources will be able to confirm that a) there was a breach and b) where it occurred. You can then take the necessary steps to remove the malicious activity and re-fortify your website.\r\n<h2>Wrapping Up<\/h2>\r\nLook, I realize laying out this robust guide to WordPress security and everything involved in maintaining it might make it seem like a contradicted my original point. And here is what I will say to that:\r\n\r\nWhether you use Drupal or Joomla or any other content management system to manage your business's website, security is going to be a top concern. Hackers have automated the ways in which they target and attack websites through the use of bots and bot networks, and so they're really not going to discriminate based on which content management system you're on. WordPress just gets a lot of flack because it's the most commonly used one.\r\n\r\nIf you're finding all of this hubbub around WordPress security to be overwhelming, then secure WordPress hosting with Pagely is probably your best bet. While there are still some parts of the security process you and your team will be responsible for, a managed WordPress host can provide you with a stable base to start from and provide some peace of mind when it comes to keeping your site safe.