Infrastructure & security
Protection that is already there when you publish
Small business sites are rarely targeted personally. They are found by scanners working through the whole internet. Edge Protection sits in front of every Siteleon site, absorbing volumetric attacks, filtering automated traffic and inspecting requests before they reach your pages or your forms. It is on from the first publish and needs no configuration to be useful. It also improves your numbers, because when bot traffic is filtered at the edge your analytics stop counting robots as interest.
What connects
Every published Siteleon site sits behind a protection layer that absorbs denial-of-service traffic, applies a web application firewall, filters bots and inspects requests before they reach the site.
What data moves, and which way
- Inspected at the edge: incoming requests — origin, pattern, rate and signature — before they reach your site.
- Out to the Analytics Engine: which traffic was automated, so visits and demand mean people.
- Out to your alerts: unusual activity worth telling you about, described in plain terms rather than log lines.
- In from your settings: the countries, rate limits and form protections you choose to tighten.
What Siteleon can do with it
- Absorb traffic floods away from your site, so a burst of junk does not take your enquiry form offline.
- Stop the common attacks against forms and pages — injection attempts, credential stuffing, scripted probing.
- Separate useful crawlers, such as search engines, from scrapers and spam bots.
- Tell you when something unusual is happening and what was done about it, without asking you to read a log.
Things you could ask for once it is on
- “Is the traffic spike on our Valencia page real, or is it bots?”
- “We are getting spam through the quote form — tighten it.”
- “What was blocked on the site last week, and was any of it a genuine visitor?”
Setting it up
Four steps, in this order.
- 01Nothing to turn on. Protection applies from your first publish and covers every page and every form.
- 02Review the default sensitivity. Most businesses never change it.
- 03Tighten specific forms if you start getting spam — rate limits and stronger challenges are set per form.
- 04If something you need is being blocked, add it to your allow list. Siteleon shows you what was stopped and why.
Permissions
Protection operates on traffic to your own site. Siteleon inspects requests in order to make a security decision, and does not use the contents of your visitors' form submissions for anything else. Settings are per site, so a change you make never affects another customer.
Where it stops
No protection layer stops everything, and Siteleon does not claim a figure. Filtering is a judgement, which means an occasional genuine visitor is challenged and an occasional bot gets through — the log shows both so you can adjust. Protection covers sites Siteleon publishes, and sites routed through Siteleon where the connection method supports it; a site you host elsewhere and connect only by snippet keeps its own protection. This layer secures delivery, not the passwords your team chooses.
Infrastructure & security
Others in this group.
Your business online. Built to adapt.
Start with the site you already have, or create something new. Siteleon helps you build it, understand it and keep improving it as the business changes.
No technical setup · Keep your existing site if you want to · [email protected]