Included on every plan, even Free

ScaleShield: the security and speed layer in front of every site

ScaleShield sits between the internet and your site. It sets up HTTPS with your free certificate, turns away bots and attack traffic, and serves cached pages, all before a request reaches your site. When a site is attacked it raises its own defences, then lowers them once the attack passes. No plugin, no setup, no extra charge.

On every plan, Free included. Hosting your own site starts at £12 a month on Starter. See all plans.

Watch the 2-minute film
Under attack, a site steps up its protection automatically and stands down on its own
Verified search engines go straight through, so your rankings are safe
G7Cloud Cache serves WordPress pages without starting PHP
Free automatic TLS on every site, wildcards included
Hosted in the UK, on servers we own and run ourselves.
What happens to every request
Always on
→ https://yourdomain.co.ukA record → ScaleShield
HTTPS handled
The secure connection is made with your free certificate
Handled
Bot filtering
Traffic that looks automated gets the browser check
Filtered
Firewall rules
Scanners, floods and traffic you blocked are refused
Checked
Cache check
A cached page is served without touching your site
Instant
Your container
Only clean, uncached requests reach your site
Clean traffic
2-minute film

Watch ScaleShield at work

Bot scores, the browser check, trap paths, your own rules, Auto-Protect, image conversion and both caches, each one shown doing its job. Best with the sound on.

Read the film instead
  1. 0:00

    How it works

    Every request to your site meets ScaleShield first. ScaleShield: the security and speed layer in front of every G7Cloud site.

    Between the internet and your site. Checked, filtered and often answered from cache, before your server does any work.

    Encryption: free automatic TLS. Firewall: your rules, threat lists. Rate limits: floods cut off. Bot check: every request scored. Anomaly detection: scanners trapped. Cache: pages in milliseconds.

  2. 0:18

    Bot protection

    Bot protection that never shows a CAPTCHA. Every request gets a bot score from 0 to 100. Browsers go straight through, bots are stopped at the door.

    A visitor on Chrome with complete browser headers, on home broadband and on no threat list, scores 6 and goes straight through. A scraper using python-requests, with no language header, from a hosting provider and on a threat list, scores 92 and is blocked.

    Somewhere in between? The browser proves itself. Passed, good for 7 days. No puzzle. Nothing to click, nothing to type.

  3. 0:30

    Search engines

    Fake Googlebot is caught. The real one never is. Every crawler is checked against the address ranges its owner publishes.

    Googlebot from Google's network: genuine, straight through, never challenged. Googlebot from a hosting provider: not a Google address, challenged.

    Verified and welcome: Googlebot, Bingbot, DuckDuckBot, AhrefsBot and SemrushBot. AI crawlers, by policy: GPTBot, ClaudeBot, PerplexityBot and Google-Extended allowed, Bytespider and CCBot blocked. Your site stays findable in AI search. Bulk AI scrapers are turned away.

  4. 0:38

    Anomaly detection

    Bots lose their favourite hiding places. Traps and detectors watch every request. Probe for a secret file and you are banned for 24 hours.

    Trap paths: touch /.env or /.git and you are banned. 50+ attack probes: known exploit paths, banned on the first try. 404 storms: 20 missing pages in 15 minutes, challenged. Traffic bursts: a network at 12 times its normal rate, challenged.

  5. 0:48

    Firewall

    Your rules. Live in about 5 seconds. Block, challenge or rate limit by country, network, path, IP, user agent and more. Known bad networks are challenged for you.

    243 countries and continents, each one a rule away. 4 threat feeds, kept current: Spamhaus DROP, Spamhaus EDROP, FireHOL Level 1 and blocklist.de. Listed addresses are challenged before they reach you.

  6. 0:56

    Rate limits

    Your login page stops being a target. Over 20 login attempts a minute from one address, and it has to pass a browser check before it tries again.

    Guarded: wp-login.php, xmlrpc.php, /login, /oauth/token and 8 more. Every page has a limit too: 250 requests in 30 seconds from one address and the check steps in.

  7. 1:04

    Attack mode

    It raises its own defences. Auto-Protect checks every 30 seconds, steps up by itself under attack, then stands down. Search engines are still welcome while it runs.

    Capable of 100,000 requests a second absorbed in front of your site.

  8. 1:14

    G7Cloud Cache

    Pages served in milliseconds. G7Cloud Cache keeps a ready copy of every page in front of your site, so most visits never reach your server.

    Edit a product in WordPress and only the pages that show it are refreshed, straight away. Nothing goes stale.

    Site having a moment? The last good copy is served. Never cached: logins, carts and checkout.

  9. 1:26

    Images

    Every image, rebuilt as it is requested. Photos are converted to AVIF or WebP on the fly, matched to what each browser supports. Same picture, a fraction of the weight.

    summer-sale.png at 1,840 KB becomes summer-sale.avif at 92 KB: 95% smaller. A browser that accepts AVIF gets AVIF at 92 KB, one that accepts WebP gets WebP at 118 KB, and one that accepts neither gets the original, untouched.

    An example shop page drops from 4.8 MB to 0.9 MB: 81% lighter. Converted once, then served from cache. On for every site, nothing to install.

  10. 1:36

    BotCache

    A cache reserved for crawlers. Search engines read a stored copy of every page, so a full crawl never weighs on your site.

    Under 100 ms a page, from the stored copy, not your server. Held for 30 days, not the week a visitor copy gets. Survives a cache clear.

  11. 1:44

    On every plan

    On by default. Nothing to manage. Every layer you have just seen is included on every plan, even Free.

    ScaleShield stands in front of every G7Cloud site. Hosting UK sites since 2017, with a 30-day money-back guarantee.

One layer, three jobs

It caches your pages, filters bots and runs a firewall

Each job has its own page if you want the detail.

G7Cloud Cache

Full copies of your WordPress pages, served from in front of your site without starting PHP or touching the database. When you edit a post, only the pages that show it are refreshed.

How the cache refreshes

Bot protection

Scrapers, password-guessing scripts and spam bots are turned away with a short browser check: no CAPTCHA, nothing to click. Anything claiming to be a search engine is checked before it is let through.

How bots are filtered

Managed firewall

Scanners probing for weak spots get a 403 and a 24-hour ban, floods from one address are challenged, and your own rules block by country, network or page. We maintain it, and changes apply in about 5 seconds.

What the firewall blocks

When a site is attacked, ScaleShield steps up on its own

Traffic arrives in bursts: a TV mention, a product launch, a scraper finding your catalogue. ScaleShield answers cached pages itself and turns hostile traffic away, so your site spends its resources on checkout, search and admin.

When the traffic for one site turns hostile, Auto-Protect moves that site to a higher security tier by itself: every visitor without a recent browser-check pass is checked before going any further. Nobody has to raise a ticket.

How Auto-Protect works

Normal traffic
Standard filtering. Only traffic that looks automated is checked.
Attack detected
Traffic is checked every 30 seconds. A flood moves that site to a higher tier.
Held for at least 15 minutes
Then until the attack settles down.
Stands down
Back to normal automatically. No ticket, no waiting.

Google and Bing are still served the whole time, so an attack does not cost you search visibility.

15 minutes
minimum Auto-Protect hold

A site under attack stays at the higher tier for at least 15 minutes, then stands down once traffic settles.

30 seconds
between traffic checks

Auto-Protect looks at the traffic for every site twice a minute.

5 seconds
to apply a rule

A change, ours or yours, reaches every site in about five seconds.

243
countries

Block or challenge visitors by country, per site.

Bad traffic is turned away before your site does any work

A WordPress security plugin can only judge a request after WordPress has started: PHP runs and the database is queried first. The attack has already used your site's processor and memory.

ScaleShield sits in front of your site's own container. The managed firewall refuses scanners and floods, and bot protection turns away automated traffic, before either reaches your site. That matters most on login pages, search and checkout, where bots do the most damage.

  • Refused traffic uses none of your site’s processor, memory or database
  • Every visit to wp-login.php gets the browser check first
  • One layer, maintained by us: no rule sets for you to keep updated
Security plugin (inside your site)
Request→PHP starts→DB queried→Plugin blocks

Blocked, but it has already used your server.

ScaleShield (in front of your site)
Request→ScaleShield refuses→PHPDB

Refused traffic never touches your container.

Verified crawlers, allowed on every plan

Search engines are let through. Impostors are challenged.

Tightening security should never cost you rankings, so this is settled before any other rule runs. A request claiming to be Googlebot is checked against Google's own published list of addresses. If it really came from Google, it goes through.

A request using the same name from an address Google does not own gets the browser check. Pretending to be a search engine is a common scraper disguise, and it stops working here.

  • Confirmed crawlers skip the browser check and the rate limits
  • Google and Bing are still served while a site is under attack
  • Fake crawlers are challenged, not taken at their word
  • Nothing for you to set up, on every plan

Checked before they are let in

Googlebot
Search, Inspection Tool, AdsBot, Storebot, GoogleOther
Allowed
Bingbot
Search, BingPreview, adidxbot
Allowed
Applebot
Siri and Spotlight suggestions
Allowed
DuckDuckBot
DuckDuckGo search
Allowed
YandexBot
Search and images
Allowed
Baiduspider
Baidu search
Allowed
Meta and Facebook
Link previews and sharing
Allowed
Anything claiming the name from elsewhere
A common scraper disguise
Challenged

Google, Bing, Apple and DuckDuckGo publish their crawler addresses, and we refresh those lists automatically. The others are confirmed by looking the address up with the search engine itself.

First request to a page
Request→Checks→PHP renders→Copy stored

The page is stored in front of your site, with a note of what it shows.

Every cached request
Request→Served from cache→PHPDB

PHP never starts and the database is never queried.

G7Cloud Cache · built into ScaleShield

It serves your WordPress pages too

The layer that turns away bad traffic also serves your pages. G7Cloud Cache keeps full copies of your WordPress pages in front of your site, so a cached page goes out without starting PHP or touching the database. Your site keeps its resources for checkout, admin and search.

Each cached page carries a note of what it shows: which posts, categories and menus. Edit something and only the pages that show it are refreshed, straight away. The full detail is on the G7Cloud Cache page. For the pages the cache leaves alone, such as carts, a managed Redis database (from £6 a month on any paid plan) can hold WordPress's object cache.

  • On by default for new WordPress sites, with no caching plugin to set up
  • Logged-in visitors, carts, checkouts and wp-admin are never cached
  • One customer never sees another customer’s basket
  • Images and other files are cached in front of your site too
BotCache · a cache reserved for crawlers

Search crawlers get a cache of their own

Crawlers visit every page and rarely need a brand new copy. So ScaleShield keeps a separate store of your pages just for them, held for 30 days rather than the week a visitor copy gets. The page a crawler saw a fortnight ago is still there waiting for it.

Stored pages go out in tens of milliseconds, so a crawler working through a large catalogue is not waiting on PHP or the database.

  • Kept apart from your visitors’ copies, so crawlers and customers never compete
  • Held for 30 days, so a crawler returning after a gap still finds a stored page
  • Kept when you clear your cache, so clearing it never slows your crawl
  • Logged-in visitors, carts and checkouts are never stored

Fast and fresh, without choosing between them

A stored page counts as fresh for 60 seconds. After that, the next crawler still gets its answer at once from the stored copy while a refresh runs in the background.

1
Crawler asks for a page
The stored copy goes out at once.
2
A refresh runs behind it
Your site renders the new version with nobody waiting.
3
The next crawler gets the fresh copy
More crawling keeps the store fresher.

So an edit reaches search engines on their next visits, without your site rendering every page for every crawler.

Why this helps your crawl budget

Google decides how hard to crawl a site partly on how well the site copes. Its guidance on optimising crawl budget says that when a site responds quickly and consistently, Google crawls more of it. When the site slows down, Google crawls less.

A large catalogue or news archive is only found as fast as it can be served. Serving crawlers from their own store keeps that pace up, and your site spends none of its own resources on the crawl.

Controls for the day you need them

Rate limits, country rules and attack mode, plus your own allow and block lists for each site. We run all of it for you.

Rate limiting

A flood of requests from one address is challenged before it reaches your site.

Country rules

Block or challenge visitors from any of 243 countries, per site. Useful when a shop only sells in the UK.

Attack mode

Switched on by Auto-Protect when a site is flooded, or by us on request. Every visitor without a recent pass gets the browser check while it lasts.

Automatic bans

Trap paths only bots ask for, and known probe paths, lead to a ban: 24 hours at first, 7 days for a repeat within 30 days. Never permanent.

Free wildcard TLS

Certificates are issued and renewed automatically on every site, wildcards included. You never touch a certificate.

Watched by us

We maintain the rules for every customer, and our monitoring flags a traffic spike or a surge in blocks to us.

The same protection whether you run WordPress, WooCommerce, a Node.js app or a site built with the AI Website Builder.

On by default. Nothing to manage.

ScaleShield switches on the moment a site goes live on G7Cloud, whether it's a managed WordPress site, an app deployed from Git, or a site you made with the AI Website Builder. There is no setup step and no premium security tier.

No plugin to install

The protection and the cache live in front of your site, outside it entirely.

No certificates to renew

TLS certificates, wildcards included, are issued and renewed automatically.

No rules to maintain

We manage the firewall and bot rules for every customer at once.

No security surcharge

ScaleShield is on every plan, Free included.

ScaleShield and your site run in the UK

  • Your site, its database, your email and DNS run on our own servers in a UK data centre.
  • Nightly backups are kept on our UK servers too.
  • A monthly disaster-recovery copy of those backups is stored with Cloudflare in the EU, so we can rebuild even if the UK data centre were lost.
  • Support comes from the UK team who build and run the platform.

ScaleShield FAQ

Is ScaleShield included on every plan?

Yes. ScaleShield sits in front of every site on G7Cloud, including sites published on the Free plan of the AI Website Builder. The firewall, bot protection, G7Cloud Cache and TLS are all part of it, at no extra cost. Hosting your own site starts at £12 a month on Starter.

What does ScaleShield include?

Free automatic TLS certificates (wildcards included), a managed firewall, bot protection with a short browser check instead of a CAPTCHA, verified-crawler allowlisting, full-page WordPress caching through G7Cloud Cache, a separate cache for search crawlers, rate limiting, country rules and Auto-Protect, which raises a site’s protection by itself when it is attacked. We maintain all of it, and rule changes take effect in about 5 seconds.

What is G7Cloud Cache?

The full-page WordPress cache built into ScaleShield, on by default for new WordPress sites. It serves complete copies of your pages from in front of your site, without starting PHP or touching the database. When you edit something, only the pages that show it are refreshed. Logged-in visitors, carts, checkouts and wp-admin are never cached.

Do I still need a caching plugin or a security plugin?

You do not need a caching plugin: G7Cloud Cache does full-page caching in front of your site. A security plugin is up to you. ScaleShield turns away probes, floods and bots before they reach WordPress, and a plugin that scans your files for malware does a different job.

Will ScaleShield block search engines or my visitors?

No. A visitor claiming to be Googlebot, Bingbot, Applebot or another known crawler is checked first, against the addresses that search engine publishes or by looking the address up with it. Confirmed crawlers skip the browser check and the rate limits. Traffic that merely looks automated gets a short browser check rather than a block, with nothing to click.

What happens when my site comes under attack?

Protection steps up on its own. Auto-Protect checks every site’s traffic every 30 seconds. When one site is flooded, it switches on attack mode for that site: every visitor without a recent browser-check pass is checked before going further. It stays on for at least 15 minutes, then switches off by itself once the traffic settles. Google and Bing are still served throughout, so an attack does not cost you search visibility. Nobody has to raise a ticket.

Does the crawler cache serve Google stale pages?

A stored page counts as fresh for 60 seconds. After that, the next crawler still gets the stored copy at once while a new one is fetched in the background, and the crawler after it gets the updated page. So an edit reaches search engines on their next visits, without your site having to render every page for every crawler.

How do custom domains connect to ScaleShield?

You point one A record at ScaleShield, using the address shown in your dashboard when you add the domain. Traffic arrives there first, gets HTTPS with your free certificate, is filtered and checked against the cache, and clean requests go on to your site’s own container.

Every site gets this layer, from Free upwards

Auto-Protect, the verified-crawler allowlist, the crawler cache, the firewall and free TLS come with every G7Cloud plan. A site with a hundred visitors a day gets the same protection as one with a hundred thousand.