Search-ready firm sites
WordPress sites on domains the law firms own, structured for search: the pages and fields a firm actually needs in public.
Case Engine
WordPress sites that help law firms show up in AI search, Google, and Maps
Case Engine needed a repeatable way to launch law-firm websites without rebuilding each one. WonderIT built a WordPress system where the design stays consistent, existing Word documents map into structured ACF fields, and Case Engine plus the firm review the wording before anything is public.
- ClientCase Engine
- IndustryLegal / SEO / WordPress
- ProductWordPress sites for Case Engine’s law-firm clients, launched from one ACF template
- FocusSEO-ready law-firm websites, fast site creation, structured ACF content
Overview
What we were asked to build.
Case Engine wasn’t launching one website. It needed infrastructure that could support many law-firm clients without turning every new firm into a separate development project. WonderIT was hired to build the sites those firms actually publish: WordPress on each firm’s own domain, structured for search, and produced as a fill of one template rather than a custom rebuild.
We built a JavaScript template that owns layout, sections, styles, and states. PHP hooks that template to Advanced Custom Fields. The template does not invent the page — it reads ACF and drops the content into a preset design. Each firm gets different copy and images inside the same system. Images come from Case Engine’s design team, already formatted and sized; we place them in the site. CloudFront caches them so WordPress is not serving every request.
Content usually arrives as Word documents — one document per page, because firm copy is large. n8n and OpenAI map that document onto the matching ACF fields.
Because these are law sites, wording is not optional. A Case Engine content creator reviews the mapped fields first. The law firm reviews next. Both have to approve before the site goes public.
Capabilities
What the product does for the firms.
One template, many firms
The template owns layout, sections, styles, and states. It reads ACF and renders a preset design. New firms change content and images, not the system.
Word in, fields out
One Word document per page goes through n8n and OpenAI into the matching ACF group. The site is filled. It is not authored by the model.
Review before it is law
Case Engine’s content creator reviews first. The law firm reviews second. Nothing publishes until both approve the wording.
The problem
What had to change.
A law-firm marketing site is easy to treat as a one-off WordPress job: new theme, paste the copy, ship. That falls apart when you are launching firm after firm and every site still has to be search-ready.
Unstructured editor content is bad for search and bad for reuse. Practice areas, locations, attorney bios, and FAQs need to be fields, not blobs. If each firm is a fork of the last theme, the search structure drifts and launch speed dies.
The copy already exists, and it is huge. It arrives in Word, page by page. Hand-entering that into WordPress is where “fast” goes to die — and you still cannot publish until a content creator and the firm have signed off on the legal language. The work was to make a publishing system where content could change without changing the underlying product.
Goals
What success looked like.
- Give Case Engine’s law-firm clients sites structured for search, not just to look like a law firm
- Make each new firm a fill of the same template on that firm’s own domain, not a rebuild
- Keep pages in ACF field groups so the design and the search structure stay stable when the copy changes
- Map one Word document per page into those fields, then stop — a person still owns the wording
- Keep WordPress lean so performance is not spent on a plugin pile
Approach
How we structured the work.
Build the site as a content model
Every kind of content lived in its own ACF field group. The template only renders what the fields contain, so design and search structure do not depend on how someone used the classic editor.
Make launch a fill, not a fork
JavaScript template, PHP to WordPress, ACF as the contract. The next firm should get their domain and their copy, not another theme.
Treat the Word doc as intake
One document per page, because the copy is too large to dump into a single file. n8n runs the workflow. OpenAI maps it onto fields. Mapping is the job. Writing the legal site is not.
Two gates, then publish
Legal language has to survive a content creator and the firm. The pipeline is allowed to be fast. Publishing is not allowed to skip review.
Keep WordPress lean
The core is ACF, SEOPress, a security plugin, and WordPress SMTP for custom template forms. Extra tools (CAPTCHA, a chatbot) only when a client asked. Fewer plugins means the page is not paying for software it does not use.
What shipped
In the product today.
- WordPress sites for Case Engine’s law-firm clients, each on a domain the firm owns
- A JavaScript template for layout, sections, styles, and states, reading from ACF into preset designs
- Separate ACF field groups for the different kinds of firm content
- n8n + OpenAI: one Word document per page mapped into ACF fields
- Dual review before publish: Case Engine content creator, then the law firm
- Images supplied and sized by Case Engine’s design team
Engineering
How it holds together.
- WordPress as the CMS and publishing surface
- Advanced Custom Fields, with separate field groups per content type
- JavaScript template + PHP to bind the template to those fields
- n8n for the document-to-fields workflow
- OpenAI to map Word-document copy onto ACF — not to author the site
- SEOPress for SEO; custom forms in the template, mail via WordPress SMTP
- CloudFront as a cache layer for design-team images
Results
What it became in production.
Case Engine now has a reusable WordPress foundation it can apply across law-firm clients without rebuilding each site’s underlying structure.
We cannot name firms, show client sites, or put launch-time or ranking numbers on this page. The proof is the system Case Engine still uses to take a firm from a Word document to a reviewed site on that firm’s own domain.
- A repeatable website product instead of one-off builds — the next firm gets the same system, not another theme
- Structured content in predefined ACF fields, so the frontend and search architecture stay consistent
- Automated intake: large Word documents enter through n8n and map into ACF, so launch is not hand-entering copy page by page
- Human-controlled publication: Case Engine’s content creator and the law firm still approve the wording before it goes live
- Sites on each firm’s own domain, not a Case Engine subdomain
Why this matters
What future clients can take from this.
If you need WordPress that behaves like a product — same system, many sites, structured content, a real intake from documents — this is the pattern.
It is also the pattern if the content is regulated. Speed lives in the mapping. Authority lives in the review. The model is not in charge of what a law firm says in public.