How Bank Conduct Index 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
- 113,204
- 4th of 24 measured in Legal/Civic, by sitemap URLs
- Page count over time
- 113,182 → 766 pages measured, 30 Sep to 25 Oct
- Languages
- English
- llms.txt
- Published
- llms.txt 14.5 KB · llms-full.txt 35.5 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
- Dataset, WebSite
- schema.org types on the homepage
- AI crawler access
- Allows all 11 major AI crawlers
- From the site’s robots.txt
- llms.txt link depth
- 101 page links
- Markdown links in the site’s llms.txt
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.
“What the UK Financial Ombudsman actually decided: uphold rates by firm and by issue, built from published final decisions, with the regulations each decision cited.”
“The Financial Ombudsman Service publishes every final decision it issues but offers only ten results a page with no way to filter by outcome. This site reads that record and reports the figure nobody publishes: how often each firm loses, and on what.”
“Corpus: 190,620 decisions; 2,176 firms with attributed decisions; 30.2% upheld across decisions with a recorded outcome.”
“Every headline figure covers BANKING, CREDIT AND MORTGAGE decisions only.”
“An outcome is taken from the Ombudsman's own published classification, never inferred from the text of a decision.”
“No rate is published for a firm with fewer than 30 decisions carrying a recorded outcome, or for an issue with fewer than 20.”
“A decision counts toward a firm only where the text names it unambiguously, so firm counts are a floor, not a total.”
“Dates are derived from the consumer's acceptance deadline, which FOS sets about a month after the decision.”
“Published final decisions are contested cases that reached an ombudsman. They are NOT a random sample of complaints, and this uphold rate is not the same as the complaint-level rate a firm reports to the FCA. Both are shown, labelled, on firm pages.”
Screenshots
Timeline
113,182 → 766 pages measured, 30 Sep to 25 Oct
| Date | Pages |
|---|---|
| 2026-09-30 | 113,182 |
| 2026-10-10 | 113,204 |
| 2026-10-18 | 766 |
| 2026-10-25 | 766 |
- 30 Sep 2026113,182 pages
- 10 Oct 2026113,204 pages
- 18 Oct 2026766 pages
- 25 Oct 2026766 pages