Laptop protected by a glowing glass shield, with padlock, cloud upload, phone verification and bug-check icons floating around

Website Security Audit Checklist for Small Businesses in 2027

By · November 16, 2026 · 14 min read


Most small business owners treat the website as finished once it goes live. The design is approved, the contact form works, and attention moves on to sales. Security usually gets a look only after something breaks: a defaced homepage, a spam redirect, a customer email asking why your site triggered a browser warning.

A security audit flips that order. You check the site on a schedule, find the weak spots yourself, and fix them before an attacker finds them first. This checklist is written for owners and managers who run a website without a dedicated security team. You do not need to write code to work through most of it.

Why small business websites get targeted

Attackers rarely pick a target by name. Automated tools scan the internet for outdated software, weak logins, and misconfigured servers, then attack whatever responds. A small business website is easy to hit that way because it often runs on a popular content management system, uses several plugins, and has not been touched in months.

The consequences reach past the website. A compromised site can leak customer details, send visitors to malicious pages, get blacklisted by search engines, and take your online store offline during your busiest week. US government guidance for small businesses puts the total cost of cybercrime against small firms at billions of dollars in a single year, and the same guidance stresses that no business is too small to be a target.

An audit will not make you invulnerable. It does remove the easy openings, and the easy openings are what most attacks depend on.

How to run the audit

Pick a fixed date and put it in the calendar. Many owners choose the start of the year, with a lighter check each quarter. Write down who owns each item, whether that is you, a web developer, or your hosting provider. Keep a simple log of what you found, what you changed, and when. That record helps when a customer, insurer, or payment processor asks what you do to protect their data.

Work through the sections below in order. They go from the foundations that cause most breaches to the habits that keep a site safe through the year.

Take stock of everything you own

You cannot protect what you have forgotten about. Start by listing every part of your web presence:

Domain names and where they are registered.

Hosting accounts and servers.

The website platform and its version.

Every plugin, theme, extension, and third-party script.

Subdomains, test sites, and old landing pages.

Email accounts tied to the domain.

Payment, analytics, and marketing tools connected to the site.

Old test sites and abandoned subdomains deserve special attention. They tend to run outdated software, nobody watches them, and they sit on the same domain as your real business. If you do not need one, remove it.

Check that everything is updated

Outdated software is one of the most common ways websites get hacked. Attackers publish and reuse methods for known flaws, and each flaw stays exploitable on every site that has not applied the fix.

Check these items:

The core platform (WordPress, Shopify apps, Joomla, or a custom framework) is on a supported version.

Every plugin and theme is current, and each one is still maintained by its developer.

Plugins you no longer use are deleted, not just switched off.

The server software and programming language version on your hosting plan are supported.

Automatic updates are on wherever they are safe to use.

If a plugin has not had an update in a couple of years, look for a replacement. Abandoned code does not get patched when new flaws appear.

Review passwords and logins

Weak and reused passwords cause a large share of account takeovers. Attackers try credentials leaked from other breaches against your login page, and people who reuse passwords lose accounts that way.

Audit these points:

Every account uses a long, unique password, ideally stored in a password manager.

Multi-factor authentication is on for the website admin area, hosting panel, domain registrar, email, and payment tools.

Default usernames such as "admin" are changed or removed.

Former employees, freelancers, and agencies no longer have access.

Login pages limit repeated failed attempts.

Multi-factor authentication deserves extra weight. Government small business guidance lists it among the basic steps to protect a company, and it blocks most attacks that rely on a stolen password alone. Use an authenticator app or hardware key where possible, since text messages are weaker.

Apply the principle of least access

Not everyone needs full control of the website. A content writer needs to publish posts. They do not need to install plugins or edit server files.

Go through the user list and check that each person has the lowest level of access that lets them do their job. Keep the number of administrator accounts small. Give contractors their own named accounts instead of a shared login, and remove them when the project ends. Shared logins make it impossible to tell who did what after something goes wrong.

Broken access control sits at the top of the lists that security researchers publish for web applications. It means people can see or change things they should not be able to reach. For a small site, tidying user roles is the practical fix.

Confirm HTTPS and certificate health

HTTPS encrypts the traffic between your visitors and your site. Browsers warn people away from sites without it, and search engines favor sites that use it.

Check these items:

Every page loads over HTTPS, and the HTTP version redirects to it.

The certificate is valid, matches your domain, and renews automatically.

No page mixes secure and insecure content, such as images loaded over plain HTTP.

Your site sends security headers that tell browsers how to handle your content.

Set a reminder for certificate expiry even if renewal is automatic. A silent renewal failure shows visitors a full-page warning, and many of them will leave.

Test your backups, not just your backup schedule

A backup you have never restored is a guess. Plenty of businesses discover during a crisis that their backups were incomplete, corrupted, or stored in the same place as the site that just got hacked.

Check the following:

Backups run automatically, at least daily for a site that changes often.

Copies are stored off the server, in a separate location.

Backups cover files and the database.

You keep several versions, so a problem that went unnoticed for a week does not overwrite every good copy.

Someone has done a test restore in the past year and written down the steps.

US cybersecurity guidance recommends keeping backups in a separate, secure location. Ransomware and site takeovers are far less damaging when you can rebuild from a clean copy.

Look for misconfigurations

Security misconfiguration appears in industry vulnerability lists year after year because it is easy to cause and easy to miss. Settings that were fine at setup can turn risky over time.

Review these areas:

Directory listing is turned off, so visitors cannot browse your folders.

Error messages do not reveal file paths, software versions, or database details.

Admin pages are not open to the whole internet where they can be restricted.

Default accounts, sample content, and install files have been removed.

File permissions on the server follow the minimum required for the site to work.

Sensitive files, such as configuration files and backup archives, are not reachable by URL.

Ask your host or developer to confirm each point if you are unsure. It is a short job for someone who knows the server.

Protect forms, search boxes, and data entry points

Every place where a visitor can type something into your site is a place where an attacker can try to slip in malicious input. Contact forms, search bars, login fields, comment sections, and checkout pages all count.

Confirm that your platform and plugins validate and clean input before using it. Add a spam filter or CAPTCHA to public forms. Keep file upload features restricted to the types you need, and scan uploads where you can. If your site takes payments, use a payment provider that handles card details on its own secure pages, so you never store them yourself.

Add monitoring and malware scanning

Prevention fails sometimes. Monitoring shortens the time between a break-in and your discovery of it, and that gap often decides how much damage is done.

Set up:

A malware scan that runs on a schedule and alerts you to changes in files.

Uptime monitoring that messages you when the site goes down.

Alerts for new admin accounts, failed login spikes, and changes to core files.

Search engine webmaster tools, which can warn you about hacked content or malware flags.

A web application firewall, offered by many hosts and security services, to filter out known attack traffic.

Read the alerts. A monitoring tool that sends warnings to an unread inbox protects no one.

Review third-party code and services

Your site is only as safe as the outside code it loads. Analytics scripts, chat widgets, booking tools, fonts, and ad tags all run on your pages. If one of those providers is compromised, your visitors are exposed too.

Remove scripts you no longer use. Check that each remaining vendor is still active and reputable. Ask whether each tool really needs access to the data it collects. Where possible, limit what outside scripts can see on checkout and login pages.

Check privacy and legal basics

Security and privacy overlap. If your site collects names, emails, or payment details, you have a duty to handle that information with care, and laws in many regions set specific rules.

Review these items:

You collect only the personal data you need and keep it only as long as necessary.

Your privacy policy matches what the site actually does.

Cookie and consent notices work as described, where the law requires them.

You know what you would do and whom you would notify if customer data leaked.

Ask a qualified professional about the rules that apply to your industry and country. Requirements differ a lot between regions.

Prepare an incident plan before you need one

When a site is hacked, panic costs time. A one-page plan makes the first hour much calmer.

Write down:

Who to call first, such as your developer, host, or security contact.

How to take the site offline or switch it to a maintenance page.

Where the latest clean backup lives and who can restore it.

Which passwords and keys to change straight away.

Who tells customers, and what the message says.

Which payment processor, insurer, or regulator must be told.

Keep a printed or offline copy. If the site and your email are both down, a plan stored only online is no use.

Train the people who touch the site

Technical controls fail when someone clicks the wrong link. Phishing emails that imitate hosting companies, domain registrars, and payment providers are a common way attackers get credentials.

Spend a few minutes a month on a short refresher. Show staff what suspicious emails look like, remind them never to share passwords by chat or email, and make it easy to report something odd without fear of blame. People who feel safe reporting mistakes report them early.

A simple yearly and quarterly rhythm

A full audit once a year, plus lighter checks between, keeps the work manageable:

Monthly: apply updates, review user accounts, and read monitoring alerts.

Quarterly: test a backup restore, scan for unused plugins, and check certificate and domain expiry dates.

Yearly: run the entire checklist, review vendors and scripts, update the incident plan, and refresh staff training.

Keep the log up to date after every round. Over a few years, it becomes proof of good practice and a guide for what to fix next.

Where to go from here

Start with the items that carry the most risk for the least effort: updates, multi-factor authentication, backups, and removing unused accounts and plugins. Those four alone close the doors that most automated attacks try first. Then work down the list over the following weeks. A site that is checked regularly is harder to attack and quicker to recover, and that matters most when you are a small team with no spare hours to lose.

Frequently asked questions

What is a website security audit?

A website security audit is a structured review of your site, hosting, accounts, and connected services to find weaknesses before attackers do. It covers software updates, access control, encryption, backups, monitoring, and your response plan.

How often should a small business audit its website security?

Run a full audit at least once a year, with quarterly checks on backups and updates, and monthly attention to alerts and user accounts. Check sooner after a major redesign, a change of developer, or any sign of suspicious activity.

Can I do a website security audit myself?

Yes, for many items. Reviewing updates, passwords, user roles, backups, and HTTPS needs no coding. For server settings, vulnerability scanning, and code review, ask your developer or hosting provider, or hire a security professional.

Is my small business website really a target for hackers?

Yes. Automated attacks scan for weak sites at scale, so size does not protect you. Government guidance for small businesses states plainly that no business is too small to be a target.

What is the most important item on the checklist?

No single item covers everything, but keeping software updated and turning on multi-factor authentication stop a very large share of common attacks. Tested backups then limit the damage if something still goes wrong.

How much does a website security audit cost?

Costs vary. A self-run audit costs only your time. Paid scanning tools and managed security plans usually charge monthly or yearly fees, and a professional penetration test costs more. Start with the free steps and add paid tools where the risk justifies them.

What should I do if my website gets hacked?

Follow your incident plan. Take the site offline or into maintenance mode, change all passwords, contact your host and developer, restore a clean backup, find and close the way in, and notify affected customers or authorities if required.

Do I need a web application firewall?

It is a useful extra layer for most business sites, especially online stores and sites with logins. A firewall filters known attack patterns before they reach your site, though it works best alongside updates and strong access control.

Does HTTPS mean my site is secure?

No. HTTPS protects data in transit between the visitor and your site. It does nothing about outdated plugins, weak passwords, or poor server settings, so it is one item on the checklist and not the whole job.

References

CISA - https://www.cisa.gov/secure-your-business

OWASP - https://owasp.org/Top10/2025/0x00_2025-Introduction/

{ "@context": "https://schema.org", "@graph": [ { "@type": "Article", "headline": "Website Security Audit Checklist for Small Businesses in 2027", "description": "A practical website security audit checklist for small businesses in 2027. Covers updates, passwords, backups, HTTPS, access control, monitoring, and a yearly audit schedule.", "datePublished": "2026-11-16", "dateModified": "2026-11-16", "inLanguage": "en", "keywords": "website security audit checklist, small business website security, website security audit 2027, secure small business website, website vulnerability checklist, small business cybersecurity, website backup and recovery, HTTPS and SSL checklist, multi-factor authentication, website malware protection", "author": { "@type": "Person", "name": "Rachal" }, "publisher": { "@type": "Organization", "name": "Golbeat" } }, { "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What is a website security audit?", "acceptedAnswer": { "@type": "Answer", "text": "A website security audit is a structured review of your site, hosting, accounts, and connected services to find weaknesses before attackers do. It covers software updates, access control, encryption, backups, monitoring, and your response plan." } }, { "@type": "Question", "name": "How often should a small business audit its website security?", "acceptedAnswer": { "@type": "Answer", "text": "Run a full audit at least once a year, with quarterly checks on backups and updates, and monthly attention to alerts and user accounts. Check sooner after a major redesign, a change of developer, or any sign of suspicious activity." } }, { "@type": "Question", "name": "Can I do a website security audit myself?", "acceptedAnswer": { "@type": "Answer", "text": "Yes, for many items. Reviewing updates, passwords, user roles, backups, and HTTPS needs no coding. For server settings, vulnerability scanning, and code review, ask your developer or hosting provider, or hire a security professional." } }, { "@type": "Question", "name": "Is my small business website really a target for hackers?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Automated attacks scan for weak sites at scale, so size does not protect you. Government guidance for small businesses states plainly that no business is too small to be a target." } }, { "@type": "Question", "name": "What is the most important item on the checklist?", "acceptedAnswer": { "@type": "Answer", "text": "No single item covers everything, but keeping software updated and turning on multi-factor authentication stop a very large share of common attacks. Tested backups then limit the damage if something still goes wrong." } }, { "@type": "Question", "name": "How much does a website security audit cost?", "acceptedAnswer": { "@type": "Answer", "text": "Costs vary. A self-run audit costs only your time. Paid scanning tools and managed security plans usually charge monthly or yearly fees, and a professional penetration test costs more. Start with the free steps and add paid tools where the risk justifies them." } }, { "@type": "Question", "name": "What should I do if my website gets hacked?", "acceptedAnswer": { "@type": "Answer", "text": "Follow your incident plan. Take the site offline or into maintenance mode, change all passwords, contact your host and developer, restore a clean backup, find and close the way in, and notify affected customers or authorities if required." } }, { "@type": "Question", "name": "Do I need a web application firewall?", "acceptedAnswer": { "@type": "Answer", "text": "It is a useful extra layer for most business sites, especially online stores and sites with logins. A firewall filters known attack patterns before they reach your site, though it works best alongside updates and strong access control." } }, { "@type": "Question", "name": "Does HTTPS mean my site is secure?", "acceptedAnswer": { "@type": "Answer", "text": "No. HTTPS protects data in transit between the visitor and your site. It does nothing about outdated plugins, weak passwords, or poor server settings, so it is one item on the checklist and not the whole job." } } ] } ] }

Tags: Cybersecurity, HTTPS and SSL checklist, MFA, small business website security, website backup and recovery, website security audit 2027, website security audit checklist, website vulnerability checklist