Security Checks
Security Checks
The builder can check your website for common security problems, explain anything it finds in plain English, and fix it for you. Your first check on each website, and the fixes it makes, are free. After that, each check uses credits.
As your first check is free, the best time to run it is just before you publish, when your website is finished. You can run more checks later, for example after big changes, but these use credits. How many depends on the size of your website.
What it checks
Pages and forms where visitors type things in
Sign-in and access to private areas
Passwords, keys and personal information
Your website’s data and any connected services, like payments
Run a check
Click the three dots on the toolbar, then Security.
Click Check my app.
The security check, ready to run
A check usually takes 20 to 30 minutes. You can carry on working on your website while it runs.
Understanding your results
When it’s finished, you’ll see a summary:
Items to review: things worth looking at
UK2 can fix: how many of those the builder can fix for you
Fixed by UK2: how many it’s already fixed
Security check results
Under What UK2 checked, each area shows Checked or Could not check. “Could not check” doesn’t mean something’s wrong. It just means that area couldn’t be reviewed this time.
Each item in Items to review has a risk level (low, medium or high). Click an item to see:
What could happen if it’s left as it is
Who could be affected, like you or your visitors
A security item explained
Fixing problems
Click Fix at the top to have the builder fix everything it can. When it’s done, click Check again to make sure.
If your website is already live, publish again so the fixes reach your visitors.
