How Defamation Guard is built
Measured numbers
Counted by the collection, not written by hand. A figure we cannot support is left out rather than shown as zero.
- Pages
- 377
- 20th of 24 measured in Legal/Civic, by sitemap URLs
- Page count over time
- 375 → 377 pages measured, 30 Sep to 25 Oct
- Languages
- English
- Uptime
- 100.00% over 30 days
- From the public status feed
- Deploys
- 11 in the last 30 days
- Last deploy 22 Oct 2026. From the public status feed
- llms.txt
- Published
- llms.txt 12.2 KB · llms-full.txt 55.2 KB
- Sitemap
- Listed in robots.txt
Tech and AI search
Read from the live site on 2026-10-23: its homepage, robots.txt and llms.txt. A line we could not read is left out.
- Built with
- Next.js
- Read from the homepage markup
- Structured data
- Organization, SiteNavigationElement, WebSite
- schema.org types on the homepage
- AI crawler access
- Blocks 6 of 11: anthropic-ai, Google-Extended, CCBot, Applebot-Extended, Bytespider, Meta-ExternalAgent
- From the site’s robots.txt
- llms.txt link depth
- 85 page links
- Markdown links in the site’s llms.txt
- Search
- Search box on the homepage
How it is built, by role
The same roles apply across the whole collection. Nothing in this block is specific to this site; what the site says about itself is quoted word for word below it.
- 1
Edge network
Visitors reach a site through an edge layer: a content delivery network with a web application firewall in front of it.
- 2
Application host
The edge talks to an application host that serves the site and renders its pages.
- 3
Data
What the pages show comes from a relational database or, for a site pre-rendered at build time, from data files built into its release.
- 4
Scheduled measurement
The collection measures its sites on a schedule: content dates and site health nightly, page counts read from each site’s sitemap weekly. Every reading is kept with its date. A site too large to re-walk is not re-measured, and shows no trend.
- 5
Public status feed
A monitoring panel sends a signed report on uptime, deploys and backups once a day, and the Operations page publishes it. A figure on this page that comes from that report says so.
In the site's own words
Each passage is copied unaltered from a page the site publishes, with the address it was taken from and the date we took it. We add nothing between them.
“Defamation Guard is a UK-focused defamation-law information and solicitor referral service.”
“Over 280 articles covering UK defamation law, online reputation, case law analysis, AI & technology, celebrity & media, professional guides, and practical guidance.”
“Our information is written with UK law in mind — principally the Defamation Act 2013, the Civil Procedure Rules of England and Wales, and how UK courts apply defamation law to modern digital communications.”
“Our information covers the unique features of online defamation, including how UK courts approach content removal, platform liability, and the rapid spread of harmful content across social media.”
“We write for people, not for lawyers. Our aim is to make defamation law understandable without pretending to be a substitute for legal advice.”
“We handle the case-assessment information you provide in line with our privacy policy and only share it with a referred solicitor with your consent.”
“There is no charge for using the information on this site or for a case assessment.”
“We are upfront that Defamation Guard is not a law firm, does not give legal advice, and does not act for you.”
Screenshots
Timeline
375 → 377 pages measured, 30 Sep to 25 Oct
| Date | Pages |
|---|---|
| 2026-09-30 | 375 |
| 2026-10-10 | 375 |
| 2026-10-18 | 377 |
| 2026-10-25 | 377 |
- 30 Sep 2026375 pages
- 10 Oct 2026375 pages
- 18 Oct 2026377 pages
- 25 Oct 2026377 pages