--- canonical: https://structuredpages.com/about/ type: AboutPage lang: en description: "Structured Pages is a structured content platform for turning large collections of related records into searchable, filterable catalog websites." date_modified: 2026-09-15 og_image: /images/about.webp --- # About Structured Pages is a structured content platform for turning large collections of related records into searchable, filterable catalog websites. ## Who builds this Structured Pages is built and operated by a solo developer. There is no large product team behind the platform or the demos on this site. One person designs the publishing system, builds the software, maintains the infrastructure, creates and checks the demo catalogs, and handles customer and contracting work. That keeps the product deliberately small and focused. It is built for things like products, parts, equipment, events, directories, collections, and reference data, particularly when people need to find a specific item by its attributes rather than read through a long page. ## Why I built it A lot of organizations have structured information already. It may live in a spreadsheet, database, PDF catalog, or internal system. The problem is often what happens next. The data gets copied into web pages. Product information gets duplicated in different places. Search and filtering are limited. Adding or changing hundreds of records becomes a manual publishing job. Structured Pages was built around a simpler idea: **Maintain the records once, then generate the catalog from those records.** The result is a website where people can search, filter, sort, compare, and open an individual page for any published item. ## What Structured Pages is [Structured Pages is not a generic website builder or CMS.](/structured-content-platform/) It is a specialized publishing system for collections of comparable records. If your data can be described as rows of things with attributes — products with dimensions, parts with compatibility information, wines with characteristics, museums with collection records, or events with dates and venues — Structured Pages can turn that data into a browsable website. The different catalogs on this site are deliberately varied. They demonstrate the same publishing model working with different kinds of structured information rather than representing one particular industry. ![Filterable Structured Pages catalog website on your subdomain](/images/structured-pages-hvce-subdomain-solution-550w.webp) ## One record, multiple outputs A catalog record is maintained in one place and used to produce the different representations of that record. That includes the public HTML page, catalog listings, structured data, sitemap entries, and other machine-readable outputs. Change a fact once and the published representations are regenerated from the same underlying record. The system keeps the outputs consistent. The accuracy of the underlying information still depends on the data supplied to it. ## Engineering discipline The platform is developed with a large automated regression suite because changes to a publishing system can affect thousands of generated pages at once. More than **2,900 automated regression tests** currently run as part of the development and release process. The platform has also been tested under sustained crawler-style load. In one test, approximately **15,000 URLs per hour** were processed on a **60,000-page** site. These are engineering measurements from specific tests, not guarantees about search rankings, indexing, traffic, or performance for every deployment. ## How the demos work The examples on this site are real demonstrations of the publishing system. They deliberately cover very different subjects: products, industrial equipment, languages, grape varieties, festivals, heritage sites, collections, and other reference datasets. The point is not that these subjects belong together. The point is that the same underlying system can represent very different kinds of structured information while providing the same basic capabilities: records, attributes, search, filtering, comparison, individual pages, and generated outputs. ## How to work with me If you already have a catalog or dataset and want help turning it into a finished site, I can build it as a scoped project. That can include data preparation, catalog design, import, configuration, deployment, and custom functionality where required. [Discuss a build](/contact/) A free pilot is available when it makes sense to test the system with your own data before committing to a larger project.