Next.js website rebuild
Service-site rebuild on Next.js after a page builder stalled SEO
A professional services firm had a page-builder site where every landing page was a unique widget stack. We rebuilt on Next.js with typed service templates, metadata as configuration, and a content model that can later connect to a CMS.
Challenge
Titles and descriptions were duplicated. New practice-area pages required a developer. Core Web Vitals failed on mobile because the builder loaded its entire widget runtime on every URL.
Approach
- IA for practice areas, industries and articles with one H1 and unique metadata per template
- Next.js App Router with server components and a centralized SEO module
- Redirects from the builder’s URL debris
- FAQ and service content as structured data files, ready for an API later
Outcome
Editors received templates instead of a blank canvas. Metadata stopped colliding. The JavaScript shipped to a practice-area page was limited to navigation and forms.
Related services: Next.js · Web Development · Technical SEO
If this constraint looks like yours
Describe the platform and the operational problem. We will say whether the same approach fits.