
How to Check PHP Version on Windows 11 and in XAMPP
Step lists to check your PHP version on Windows 11 and XAMPP, fix the not recognized error, and see how it relates to the PHP on your live host.
Small Business
Most website security checklists are written for IT teams. They talk about DNS encryption, origin servers and bot management, and leave a shop owner or a tradesperson with no idea which items are theirs. This checklist is sorted by who does the work: you, your website platform, or whoever built the site. It follows the practices the US Cybersecurity and Infrastructure Security Agency (CISA) recommends for small businesses, read on 16 November 2026.
For a small business, website security comes down to five things. Protect every login with a unique password and two-step verification. Keep the software up to date, or use a platform that does it for you. Keep a backup you have tested. Make sure the site loads over HTTPS. And set up a free alert, such as Google Search Console, so you hear about a problem from Google and not from a customer. The 20 checks below put those five into practice and say who is responsible for each.
About the author: Amariq is a web design studio. We build and look after sites on Webflow, Framer, WordPress, Shopify and static hosting. This is a practical checklist for owners, not a security audit, and it does not replace advice from a security professional if you hold sensitive data such as health or payment records.
On 16 November 2026, Google (US, English) showed these for "website security checklist small business": Google Workspace's security checklist for small businesses, Cloudflare's "Website security guide: A 10-step checklist", Huntress's cybersecurity checklist, Moat IT's 15 checks, a Reddit thread, The Hartford's six best practices and Pansofic's checklist.
Cloudflare's ten steps are: strong authentication, role-based permissions, TLS, encrypted DNS, DNS security, hiding the origin IP address, DDoS protection, managing third-party scripts and cookies, blocking bots, and tracking traffic and security metrics. The first three apply to everyone. The rest assume you run your own servers and have a team to tune them, and each one maps to a Cloudflare product. The Google Workspace and Huntress lists are about the office: laptops, email and staff accounts.
What an owner still needs is a list that starts from their situation: "my site is on Squarespace" or "my nephew set up WordPress five years ago". The work is very different in those two cases, so we split the checklist that way.
| Your setup | Who runs the servers and updates the software | What is left to you |
|---|---|---|
| Hosted builder (Wix, Squarespace, Shopify, Webflow, Framer) | The platform | Logins, who has access, third-party apps, your domain and email |
| WordPress on managed hosting | The host looks after the server; core, theme and plugin updates depend on the plan | Logins, plugin choices, checking that updates and backups really run |
| WordPress on shared or self-managed hosting | You or your developer | Everything: updates, backups, firewall, logins |
| Static site on a host such as Cloudflare Pages or Netlify | The host. There is no database or admin login on the site itself | The accounts that publish the site, forms and any scripts you add |
If you are not sure which row you are in, ask whoever built the site, or see our guide to who is responsible for updates. Our comparison of managed and shared WordPress hosting explains the difference between the two WordPress rows.
| # | Check | How to do it |
|---|---|---|
| 1 | List every account that can change the site | Domain registrar, DNS, hosting or builder, website admin, business email, payment provider |
| 2 | Each account has its own strong password | Use a password manager. Never reuse the email password |
| 3 | Two-step verification is on for all of them | Look under Security in each account's settings. CISA advises requiring multifactor authentication and using phishing-resistant methods where available |
| 4 | The business owns the accounts | The owner's email is the login for the domain and hosting, not a past developer's or employee's |
| 5 | Each person has their own login with the lowest role they need | An editor does not need to be an administrator |
| 6 | Old users are removed | Former staff, past agencies, test accounts |
| 7 | Recovery details are current | The recovery email and phone number are ones you still control |
The domain and the email deserve special care. Whoever controls the domain can point it at a different site, and whoever controls the email can reset every other password. Our guide to DNS records explains what the domain settings do.
| # | Check | Hosted builder | WordPress |
|---|---|---|---|
| 8 | Core software is current | Done by the platform | Turn on automatic updates or update monthly |
| 9 | Themes and plugins are current | Review installed apps twice a year | Update monthly. Remove anything unused |
| 10 | Add-ons come from known sources | Use the platform's own app store | Use the official directory or the maker's site. Never use "nulled" paid themes |
| 11 | The server language is a supported version | Not applicable | Check the PHP version with your host |
| 12 | Third-party scripts are reviewed | Remove chat widgets, trackers and embeds you no longer use | Same |
CISA puts it simply: outdated software can contain exploitable flaws, so install security updates promptly. For WordPress owners, our guides to checking and updating your PHP version and whether WordPress updates PHP by itself cover check 11.
| # | Check | How to do it |
|---|---|---|
| 13 | Every page loads over HTTPS | Type your address with http:// and confirm it switches to https:// with no browser warning |
| 14 | The certificate renews by itself | Ask your platform or host. See our guide to an expired SSL certificate for what to do if it lapses |
| 15 | Forms collect only what you need | Do not ask for dates of birth, ID numbers or card details in a contact form |
| 16 | Card payments go through a payment provider | Use the checkout of Stripe, PayPal, Shopify or similar, so card numbers never touch your site |
| # | Check | How to do it |
|---|---|---|
| 17 | A recent backup exists somewhere other than the site | See our website backup guide for what each platform keeps |
| 18 | You have restored from a backup at least once | Until someone has restored from it, nobody knows whether the backup works |
| 19 | Google Search Console is set up | Its Security issues report shows hacked content, malware and deceptive pages that Google finds |
| 20 | A one-page incident plan exists | Who to call, where the backups are, how to log in to the registrar and host |
CISA lists backing up business data and having an incident response plan among its recommended practices, and says plans should be reviewed and practised at least once a year.
Google's Search Console help page describes three kinds of problem the report covers: hacked content placed on your site without permission, malware and unwanted software, and social engineering, meaning content that tricks visitors into doing something dangerous. Affected pages can appear with a warning label in search results, or the browser can show a full-page warning before the visitor reaches your site.
If the report is clean, you see a green tick. If it lists a problem, Google's process is to fix every listed issue across the whole site, test the fix, then select Request Review and describe what you did. Google says most reviews take several days or weeks, and warns against sending a second request while the first is open.
Setting up Search Console is free and takes a few minutes with access to your domain. If you only do one thing from Part 4 today, do this one. If the report does show a problem on a WordPress site, our guide to checking whether your WordPress site is hacked walks through the next steps.
It depends on the row you are in.
No plugin fixes a reused password. Do Part 1 before you buy anything.
| When | What |
|---|---|
| Today | Checks 1 to 3: list the accounts, fix passwords, turn on two-step verification |
| This week | Checks 4 to 7 and 19: ownership, users, recovery details, Search Console |
| This month | Checks 8 to 18: updates, HTTPS, forms, backup and a test restore |
| Every month | Updates on WordPress; a glance at Search Console |
| Every six months | Review users, apps, plugins and scripts |
| Every year | Read the incident plan and check the phone numbers still work |
Many owners hand the monthly and six-monthly rows to whoever maintains the site. Our guide to what a monthly maintenance plan includes lists what to expect.
We set up new sites with the basics in place: accounts registered to the client, two-step login switched on, HTTPS, form fields kept to what is needed, and Search Console connected. For WordPress sites we agree who applies updates and where backups are stored before launch. Our fees come from the scope of work and never from hours logged, and are paid in three parts: 40% at the start, 30% on design sign-off and 30% before the site goes live. When the last part is paid, the design, copy and code are the client's, and the domain, hosting and analytics stay under the client's own logins. See website maintenance or get in touch.
Use a unique password and two-step verification on every account connected to the site, keep the software updated or use a platform that does it, keep a tested backup, make sure every page loads over HTTPS, and set up Google Search Console to warn you about problems.
The platform runs and updates the servers and software, which removes the most technical work. Your part remains: strong logins, two-step verification, careful choice of apps, and control of your domain and email. Our article on hosted platforms and a server software flaw shows how that split works in practice.
Weak or reused logins. CISA's four essentials for small businesses are teaching staff to avoid phishing, strong passwords, multifactor authentication and software updates, and three of those concern accounts.
Yes. Every site should load over HTTPS. Most platforms and hosts include a certificate at no extra cost. Our SSL certificate cost guide covers when a paid one is needed.
On WordPress, apply updates at least monthly and security updates as soon as they are released. On a hosted builder the platform updates itself, so review your installed apps and users every six months instead.
Common signs are a browser warning before the site loads, pages or links you did not create, a sudden drop in search traffic, or an email from Google. The Security issues report in Search Console is the place to confirm it.
This is not legal advice. Many privacy and consumer protection laws expect a business to take reasonable care of personal data, and some require you to tell people after a breach. The details depend on where you and your customers are, so ask a lawyer about your own case.

Step lists to check your PHP version on Windows 11 and XAMPP, fix the not recognized error, and see how it relates to the PHP on your live host.

What a 301 redirect does, when to use 301, 302 or 308, and how to set one up on Webflow, Wix, Squarespace, Shopify, WordPress and Cloudflare. Checked 15 Nov 2026.

Google Analytics alternatives for a small business site: prices and free plans from each maker, cookie claims, and what you lose. Checked 14 Nov 2026.