Case Studies / Dulles Glass
E-commerce
Dulles Glass
Two-year engagement building SEO-aware e-commerce architecture on Next.js. Rankings recovered within 2 to 3 months of restructuring.
Context
Dulles Glass runs a large e-commerce catalog with category and product pages that generate the bulk of organic revenue. The internal engineering team needed a partner who understood both the Next.js stack and how search engines read a product site. Most contractors could do one or the other. The brief was to find someone who could hold both.
Issue, action, artifact, outcome
| Issue | Action owned | Artifact or proof | Outcome claim |
|---|---|---|---|
| Deep catalog pages needed search-aware architecture, not only frontend execution. | Handled route structure, pagination, faceted navigation, and category/product page behavior in Next.js. | Route-level catalog rules, redirect notes, and product/category QA checklist. | Rankings recovered within 2 to 3 months of the restructuring phase. |
| Product and category schema had to survive the rebuild. | Preserved schema logic block for block across product and category templates. | Schema parity checklist tied to product and category template QA. | Search impact was considered upstream during engineering, not patched after launch. |
| Internal links needed to support catalog authority flow. | Rebuilt internal links so category pages supported the right product groups. | Internal-link map and sprint QA notes reviewed with the client team. | The engagement continued across two years of sprint work. |
What we did
- Next.js architecture tuned for a deep catalog, with pagination and faceted navigation handled at the route level.
- Product and category schema preserved block for block across the restructure.
- Internal linking rebuilt so category pages flowed authority to the right product groups.
- Ongoing engineering across sprints, working directly inside the client team rather than from outside.
Outcome
Rankings recovered within 2 to 3 months of the restructuring phase. Engineering velocity held across two years of engagement. The internal team was able to ship product changes without worrying that search impact had been considered upstream.
Claim boundary
Publicly stated claims are limited to the verified Clutch review, the two-year engagement context, the SEO-aware Next.js catalog work, and the documented ranking recovery window. Private revenue, traffic, and conversion data is not published here.
“The combination of technical skills and SEO awareness is not something you find often. Most developers build things without thinking about the search impact at all. He felt more like part of our internal team than someone we hired externally.”
Related proof
Migrating a product catalog?
Start with a 72-hour audit. We map every URL, redirect, and schema block before a single line of code moves.