If you were rebuilding a small SEO-focused WordPress agency workflow from scratch in 2026, what stack/process would you choose?
TL;DR: Small SEO agency, mostly templated local-business sites, moving off Elementor, and looking for the best long-term WordPress workflow using the block editor, patterns, block themes, theme.json, cloud pattern hubs, and possibly the new Capabilities API.
I’d love input from people who build a lot of client WordPress sites and have opinions about sustainable agency workflows.
I’m working with a small agency in a very niche local small-business SEO space. Most client sites have a lot in common: similar content types, similar lead-gen goals, similar local SEO requirements, and a lot of templated/repeatable page structures. There is also a fairly heavy content publishing component because the niche is competitive. Our team is small: usually 1–2 developers, an account manager, a writer, and a designer.
Right now Elementor is a major bottleneck for us, and we’re trying to think longer-term rather than just swapping one page builder for another. The goal is to create a WordPress development system that is efficient for a small team, supports templated/local SEO builds, lets non-developers work safely, and stays stable/maintainable for the next 5 years.
If you were starting from scratch today, what would your ideal workflow and stack look like?
A few things I’m especially interested in:
• Would you go all-in on the block editor / block themes / theme.json / patterns?
• Would you use a lightweight block library, mostly core blocks, or invest in custom blocks? I personally have a lot of experience with Kadence and seems like creating a cloud pattern hub for the reputable elements would be helpful here
• How would you handle templated page types for local SEO without creating a brittle mess?
• What would you standardize across all builds: starter theme, patterns, CPTs, custom fields, SEO tooling, forms, schema, analytics, etc.?
• How much would you rely on synced patterns versus custom block development?
• For a small team, what should writers/account managers be able to edit safely vs what should stay developer-controlled?
• If your goal was “stable for 5 years,” what would you explicitly avoid?
• Has anyone started factoring the new WordPress Abilities API / capabilities-style agent tooling into their long-term architecture, or is that still too early for real agency workflows?
I’m especially interested in answers from people who build lots of repeatable service-business or SEO-oriented sites, not just one-off custom brochure sites.
If you had to choose a practical, durable stack for this exact situation, what would it be and why?