Publish hundreds of search pages from one system, not one page at a time.
I help businesses that need hundreds of SEO pages or sites build the publishing system and data model first, so each new page is a configuration and not a new project.
Where the problem shows up
Most businesses publish search pages one at a time. A writer drafts the page, a designer lays it out, a developer builds it and someone checks it before it goes live. For ten pages this is a sensible process, because each page gets the attention it needs and the effort is easy to see.
The difficulty appears when the business needs hundreds of pages, one for each location, service, product or topic, or hundreds of separate sites. The same work is repeated for every page, the layouts drift apart, the information behind each page sits in a different spreadsheet, and the hundredth page costs as much as the first. Quality depends on who built which page, and nobody can say with confidence how the pages relate to each other. Some overlap and compete for the same searches, others are linked by habit instead of by meaning. What happens to a team when every new page is a new project? And what happens to search visibility when the structure of the whole site has never been measured?
The better principle is to build the system that produces the pages and let each page become a configuration of it. That means a clear data model for what is published, reusable page blocks, a publishing workflow that several teams can share, and a way to measure the structure of what has been published. That is the work I do.
What I have changed for others
500+ microsites: a publishing system instead of one-off builds
Each new SEO website was treated as a separate development project, so design, build and upkeep were repeated for every property. I designed a reusable publishing system that combines Figma-based design workflows, PayloadCMS, block-based page architecture and serverless deployment. It now supports more than 500 SEO microsites, and new website development takes less than one week. Read the case study.
Website architecture: from page-by-page review to a semantic graph
A large website had grown by addition and could only be reviewed one URL at a time, so overlap, gaps and isolated pages stayed invisible. I built an application that reads a sitemap, finds recurring themes with LDA topic modelling, scores page similarity with TF-IDF and cosine similarity, and draws an interactive network of related pages. It shows related pages, possible duplicates, content gaps, internal-link opportunities and topical clusters. Read the case study.
60+ websites: one shared schema to compare them
Performance data from more than 60 websites was defined and stored differently on each one, so the sites could not be compared. I designed a shared analytics schema and centralised the data in BigQuery, so that any property can be compared with any other. Read the case study.
What changes for your business
A programmatic system changes what a new page costs and how well you can see the pages you already have. The outcome you can expect to check is practical:
- New pages are configurations: a new page or site is added to the system and not built from scratch, which is how new website development came down to under a week on the 500+ microsite platform.
- One source for each page: the information behind a page lives in one structured place, so a change is made once.
- Shared blocks and design: design, content, SEO and development teams work from the same reusable parts.
- Structure you can measure: overlap, gaps and isolated pages are visible before and after publishing.
- Comparable performance: every page or property reports against the same definitions.
The work can include a data model for the page set, reusable block templates in Payload CMS, a publishing and deployment workflow, a structure and internal-linking analysis, and a shared reporting schema.
Where this leads next
Programmatic publishing depends on consistent data, so many engagements begin with information systems to settle what each page is built from. The structure of the published pages can then be measured with knowledge graphs, and the sites themselves run on infrastructure that can be recovered and handed over. If your pages are already generated from a clean dataset, we can begin with the structure analysis.