Performance

Website securityA practical baseline for law firm sites

Most law firm sites are not hacked by experts. They are hacked through an old plugin or a reused password. A short routine closes most of those doors.

By the Array Law editorsUpdated Nov 10, 20268 min read
Website security illustration
HTTPS
on every page, no exceptions
MFA
on hosting, registrar and CMS
Off-site
backups you have restored at least once

Key takeaways

  • Serve every page over HTTPS and keep the certificate renewing automatically.
  • Most breaches on small sites start with outdated software or weak logins. Updates and MFA fix most of it.
  • Keep backups off the server, and test a restore before you need one.
  • Hacked sites lose rankings through spam injections. Watch Search Console for security alerts.

Why a marketing site needs security too

Many firms assume their website holds nothing worth stealing. Client files live in the case management system, after all. But a firm website still matters to attackers, and a breach costs more than a few days of downtime.

  • Contact forms carry confidential facts. Prospects describe arrests, injuries and divorces in free text. If those submissions are stored on the server or emailed in plain text, a breach exposes them.
  • Your domain carries trust. Attackers use hacked sites to host phishing pages, send spam or redirect visitors to scams. Your name is on all of it.
  • Search visibility suffers. Google may show warnings in results or browsers, and injected spam pages can bury your real content.

There is also a professional angle. ABA Model Rule 1.6(c) asks lawyers to make reasonable efforts to prevent unauthorized disclosure of client information, and the comments to Rule 1.1 tie competence to an understanding of relevant technology. What counts as reasonable depends on the facts, so treat this post as a technical checklist, not legal advice.

None of this requires a security team. Most of the protection comes from a handful of habits applied every week, plus clear ownership. Decide now who at the firm is responsible for the website account, the domain and the hosting, and who the outside developer is if something breaks. Write those names down with the date.

HTTPS everywhere, configured properly

HTTPS encrypts traffic between the visitor and your server. Browsers like Chrome label plain HTTP pages as not secure, which is the last thing a prospect should see on a page asking for their story. Google has also used HTTPS as a lightweight ranking signal for years. The web.dev overview of HTTPS explains the reasons in plain terms.

Having a certificate is not the same as being configured well. Check these points:

  1. Automatic renewal. Free certificates expire every few months. Make sure your host renews them without anyone remembering to.
  2. One canonical version. Every variation, such as http, www and non-www, should redirect with a single 301 to your one preferred HTTPS address.
  3. No mixed content. Images, scripts or fonts loaded over HTTP on an HTTPS page trigger warnings. Old blog posts are the usual source.
  4. HSTS. Once everything works over HTTPS, an HSTS header tells browsers to never try HTTP again. Turn it on after testing, since it is hard to undo quickly.

These fixes also help speed and crawl efficiency. Redirect chains slow every first visit, a theme we cover in our guide on improving law firm website speed.

Updates and plugin hygiene

WordPress powers a large share of law firm sites, and it is reasonably secure when kept current. Most problems come from what is added to it. Each plugin and theme is third-party code with its own update cycle, and an abandoned plugin can stay vulnerable for years.

A routine that works

  • Update weekly. Apply core, plugin and theme updates on a set day. Security releases should go out within days, not at the next redesign.
  • Use a staging copy. Test larger updates on a staging site first, especially for page builders and form plugins.
  • Remove what you do not use. Deactivated plugins still sit on the server. Delete them. Fewer plugins mean fewer doors.
  • Check maintenance status. Before installing a plugin, look at when it was last updated and whether the developer responds to issues.
  • Avoid nulled themes. Pirated premium themes often ship with backdoors already installed.

The same logic applies to other platforms. Hosted builders handle core updates for you, but third-party apps, embed scripts and integrations still need review. Ask your developer for a list of everything that loads on the site and who maintains it.

If your firm is planning a rebuild, make maintenance part of the brief. Our law firm website design guide covers what to ask before you sign off on a platform.

Lock down every login

Stolen and guessed passwords remain one of the most common ways into small business sites. The fix is unglamorous and very effective.

  • Turn on multi-factor authentication for your domain registrar, DNS provider, hosting account, CMS admin accounts and the email accounts used to reset them. The registrar matters most. Whoever controls the domain controls the site and the firm's email.
  • Use a password manager and unique passwords for every account. Shared office passwords on sticky notes are still common in reviews we do.
  • Give each person their own login. Shared admin accounts make it impossible to see who changed what, or to remove one person's access.
  • Use the lowest role that works. A paralegal who posts blog content needs an editor role, not administrator.
  • Offboard promptly. When staff or vendors leave, remove their accounts the same day.
  • Turn on registrar lock and keep the registrar contact email on a firm address you control.

Limit login attempts on your CMS and consider hiding the admin URL behind your host's firewall. These are small steps, but automated bots try default login pages constantly.

Keep an access list in a shared document: every system tied to the website, who has access, at what level and when it was last reviewed. Domain, DNS, hosting, CMS, analytics, Search Console, Business Profile, call tracking and form tools all belong on it. Reviewing it twice a year takes less than an hour and usually turns up at least one account that should have been closed.

Handle form data like client information

Your intake form is where the website touches confidential information. Design it so sensitive details travel as little as possible.

  1. Ask for less. A name, a way to reach the person and a short description are usually enough to start. Detailed facts can wait for the consultation, after a conflict check.
  2. Avoid storing entries on the web server when you do not need to. Many form plugins keep every submission in the database by default. If you must store them, purge them on a schedule.
  3. Send entries securely. Route submissions to your intake system through an encrypted connection rather than a plain email to a shared inbox.
  4. Add a short notice near the form saying that submitting it does not create an attorney-client relationship and that the person should not send confidential details yet. Many state bars expect similar language.
  5. Block spam without hurting people. Use a modern, low-friction spam filter. Puzzles that frustrate real users cost inquiries, and they can create accessibility problems covered in our post on website accessibility.

Review the third-party scripts on pages with forms. Chat widgets, heatmap tools and session recorders can capture what people type. If a tool records keystrokes, keep it off intake pages.

Email deserves a note here, because many forms still deliver to an inbox. Make sure the firm's email domain is configured with SPF, DKIM and DMARC records. They make it harder for attackers to send messages that look like they came from your firm, and they help your own form notifications reach the inbox instead of spam.

Backups you can actually restore

A backup that lives only on the same server as the site is not much of a backup. If the server is compromised or the hosting account is closed, both disappear together.

  • Keep copies off-site, in a separate storage account that the website itself cannot write over or delete.
  • Back up files and the database. Content, settings and form entries usually live in the database, and media lives in files.
  • Keep several versions. Some hacks go unnoticed for weeks. If you only keep last night's copy, you may restore the infection.
  • Test a restore. Once or twice a year, restore a backup to a staging site and confirm it works. Many firms only learn their backups are broken during an emergency.

A widely used rule of thumb is three copies, on two kinds of storage, with one kept off-site. You do not need to follow it exactly. You do need at least one copy that a compromised website cannot reach.

Write down where backups are, who can restore them and how long it takes. Keep that note somewhere other than the website.

Ask your host what it already does. Many managed hosts include daily backups, a web application firewall and malware scanning. Know which of these you have, how long backups are kept and how to request a restore. If the host's backups are your only copy, add your own off-site copy as well.

How hacks hurt SEO, and how to catch them

Many site compromises are designed to stay invisible to the owner. Attackers inject hidden links, create thousands of spam pages or redirect only visitors who arrive from search. The partner who types the URL directly sees nothing wrong, while search users land on a pharmacy scam.

Google's spam policies treat hacked content as a problem to remove from results. It may show a warning that the site may be hacked, and Safe Browsing can display a full-page warning in Chrome. Either one stops inquiries cold, and recovery can take weeks after cleanup. Clean, trustworthy sites are part of the foundation described in our law firm SEO guide.

Early warning signs

  • A Security Issues or Manual Actions notice in Google Search Console. Make sure someone at the firm receives these emails.
  • A sudden jump in indexed pages, or pages in a language you do not publish.
  • A site search on Google that returns spammy titles under your domain.
  • New admin users or plugins nobody installed.
  • Unexpected outbound links in your footer or old posts.

If it happens

Change all passwords, involve your developer or host, remove the malicious code and close the entry point, usually an outdated plugin. Restore from a clean backup if one exists. Then request a review in Search Console. If form submissions may have been exposed, talk to the firm's ethics or privacy counsel about notification duties.

Questions, answered

Is a free SSL certificate good enough for a law firm website?

For encrypting traffic, yes. Free certificates provide the same encryption as paid ones for most sites. What matters more is that the certificate renews automatically, every version of the site redirects to HTTPS and no page loads mixed HTTP content.

How often should WordPress plugins be updated?

Check for updates at least weekly and apply security releases within days. Test larger updates on a staging copy first. Remove plugins you do not use, since deactivated code still sits on the server and can be exploited.

Should we store contact form submissions on the website?

Only if you need to, and then purge them on a schedule. Route entries securely to your intake system instead. Ask for minimal details on the form, since full facts can wait until after a conflict check and consultation.

How do we know if our site has been hacked?

Watch Google Search Console for security alerts, check for a sudden rise in indexed pages, search your domain on Google for spam titles and review admin users and plugins regularly. Many hacks show spam only to search visitors, so the homepage can look normal.

Does a hacked website affect Google rankings?

Yes. Google may label results as possibly hacked, Chrome may show warnings and injected spam pages can crowd out your real content. Rankings and inquiries usually recover after cleanup and a review request, but it can take weeks.

Ready when you are

One page, one fix, one week at a time. Start with the playbook that matches your next problem.

Read the playbook