Best Practices – Michele Born https://micheleborn.com Software developer Tue, 10 Mar 2026 17:16:42 +0000 en-US hourly 1 https://wordpress.org/?v=7.1 https://micheleborn.com/wp-content/uploads/2023/09/cropped-001-bear-32x32.png Best Practices – Michele Born https://micheleborn.com 32 32 Drowning in Spam https://micheleborn.com/2025/11/27/drowning-in-spam/ https://micheleborn.com/2025/11/27/drowning-in-spam/#respond Thu, 27 Nov 2025 03:57:34 +0000 https://micheleborn.com/?p=167 When Your Friend’s WordPress Site Is Drowning in Spam (And You’re the “Tech Person”)

Every now and then someone messages me with a classic WordPress emergency:

“HELP. My site is getting 400 spam comments a day. What do I do?”

And because I’m the designated “tech friend,” I obviously end up fixing it… for free… at 11 PM… while holding a cappuccino in one hand and my sanity in the other.

So let’s turn this into a teaching moment, shall we?

Here’s how to stop WordPress comment spam quickly:


Option 1: Decide Whether Comments Should Exist at All

Hot take: Most business sites don’t need comments.
If your friend isn’t running a blog with an actual audience, comments are basically an invitation for bots to have a rave in your inbox.

So the fastest possible fix is:

Settings → Discussion → Uncheck “Allow people to submit comments.”

Then kill comments on old posts:

Posts → All Posts → Bulk Edit → Comments → “Do Not Allow.”

Boom. Done. Enjoy the silence.

Here’s a visual:

Screenshot

Option 2: If You Must Keep Comments, At Least Approve Them First

If comments are “important” (read: someone said they might get one someday):

Settings → Discussion → “Comment must be manually approved.”

This stops the spam from showing publicly.
It doesn’t stop it from existing, but at least you’re not advertising Viagra in your testimonial section.


Option 3: Install the Only Plugin That Doesn’t Require Therapy

I absolutely hate plugins (except for ACF – I looooove ACF), but if you don’t have a dev, you might need one – and that’s ok. Just make sure you always have the latest version up. Here’s a suggestion.

Antispam Bee

  • Free
  • Lightweight
  • No API keys
  • No Jetpack accounts
  • No “connect to cloud protection” scams
  • Just works

You literally install it and walk away.

Plugins → Add New → Search “Antispam Bee” → Install → Activate

If that worked, congratulations — you’re now a junior sysadmin.


Option 4: If you must install CAPTCHA

CAPTCHAs are annoying… but sometimes we need it. So, let’s go over that.

Part 1: Get Google reCAPTCHA API Keys 

  1. Go to the Google reCAPTCHA Admin Console at google.com/recaptcha/admin.
  2. Sign in with your Google Account.
  3. Register a new site by providing the required information:
    • Label: A name to help you identify the website (e.g., “My Test Website”).
    • reCAPTCHA type: Choose the version you want (v2 “I’m not a robot” checkbox is common and visually clear; v3 runs in the background and provides a score).
    • Domains: Enter your website’s domain name (e.g., www.yourwebsite.com).
    • Accept the reCAPTCHA Terms of Service and click Submit.
  4. Copy the generated Site Key and Secret Key. You will need these for the next steps. 

Part 2: Install and Configure a WordPress Plugin 

  1. Log in to your WordPress dashboard.
  2. In the left-hand menu, navigate to Plugins > Add New.
  3. In the search bar, type in “CAPTCHA” or “reCAPTCHA”. Recommended plugins include “reCaptcha by BestWebSoft” or “Advanced Google reCAPTCHA”.
  4. Click Install Now next to the chosen plugin, then click Activate.
  5. After activation, go to the plugin’s settings page (usually found under Settings or as its own menu item in the sidebar).
  6. Paste your Site Key and Secret Key into the designated fields.
  7. Configure the settings to choose where the CAPTCHA should appear (e.g., login form, registration form, comment form, contact forms).
  8. Click Save Changes.
  9. Test the CAPTCHA by logging out and checking the form(s) where you enabled it to ensure it is working correctly. 

And… we’re done!

See you next time.

]]>
https://micheleborn.com/2025/11/27/drowning-in-spam/feed/ 0
GDPR Notes https://micheleborn.com/2025/02/09/gdpr-notes/ https://micheleborn.com/2025/02/09/gdpr-notes/#respond Sun, 09 Feb 2025 00:24:13 +0000 https://micheleborn.com/?p=118 Back when I started, not only the front-end developer, the back-end developer, the UX designer and the UI designer was the same person, we also didn’t have the concept of GDPR. The concept of GDPR specifically did not exist in 1998. GDPR was introduced in 2016 and fully enforced in 2018. However, data protection laws did exist before then. The EU had the Data Protection Directive (1995), which laid the groundwork for GDPR but was less strict and not directly enforceable across member states.
We must ensure that websites align with global data privacy regulations, which are becoming increasingly critical in today’s digital landscape.

Here’s a breakdown of the basic rules for each data privacy regulation:

GDPR (Europe)

  • Requires explicit and informed consent before collecting personal data.
  • Grants users the right to access, rectify, and erase their data (“right to be forgotten”).
  • Requires businesses to provide clear privacy policies explaining data usage.
  • Mandates data breach notifications within 72 hours.
  • Enforces data minimization, ensuring only necessary data is collected.
  • Restricts data transfers outside the EU unless safeguards are in place.

CCPA (California, USA)

  • Gives consumers the right to know what personal data is collected and how it’s used.
  • Allows users to opt out of the sale of their personal data.
  • Provides the right to delete personal information upon request.
  • Prohibits discrimination against users who exercise their privacy rights.
  • Requires businesses to have a “Do Not Sell My Personal Information” link on their website.

LGPD (Brazil)

  • Similar to GDPR, it requires clear and informed consent for data collection.
  • Grants users the right to access, correct, delete, and transfer their data.
  • Businesses must appoint a Data Protection Officer (DPO) to oversee compliance.
  • Requires data breach notifications within a reasonable timeframe.
  • Applies to any business handling Brazilian citizens’ data, regardless of location.

PIPEDA (Canada)

  • Organizations must obtain valid consent before collecting personal data.
  • Requires businesses to identify the purpose of data collection and limit its use.
  • Grants individuals the right to access and correct their personal information.
  • Mandates security safeguards to protect data from breaches.
  • Requires data breach reporting if there’s a risk of significant harm.

Each of these regulations has unique rules, but they all emphasize transparency, user control, and data protection. – hence the banner at the bottom of this page!

]]>
https://micheleborn.com/2025/02/09/gdpr-notes/feed/ 0