Toolkit
The Result
From thousands of SEO errors to near zero
Over a seven-month push, the Notarize site went from thousands of crawl and indexation errors to a near-clean bill of health — bloated H1s rewritten sitewide, thousands of dead backlinks cleared, and the technical foundation rebuilt to rank. Alongside the SEO overhaul: new landing pages, a new blog, and a reusable component library, all on Webflow Enterprise.
Phase 1 · the core
The SEO overhaul
The headline work was technical SEO. Notarize is a large, high-traffic enterprise site, and years of growth had left it carrying thousands of accumulated errors that dragged on its search performance. Over roughly seven months I ran a full audit-and-remediation program and drove the error count down to near zero.
1,000s → ~0
Crawl & index errors resolved
Sitewide
Bloated H1 tags rewritten to clean semantics
1,000s
Dead & broken backlinks cleared
The workflow was disciplined. Crawl the entire site in Screaming Frog to surface every broken link, redirect chain, duplicate title, and malformed heading; track rankings and backlink health in Semrush; then work the list down methodically. Bloated and duplicated H1 tags — a recurring problem baked into templates — were rewritten to a clean, single-H1 semantic structure. Thousands of dead and broken backlinks were cleared or redirected so link equity stopped leaking. Metadata, redirects, and indexation rules were standardized so the fixes held instead of creeping back.
Phase 2
New landing pages, a new component system
In parallel with the SEO work I rebuilt Notarize's landing pages in a new design style and stood up a new component system on the Webflow site — most of the development, plus design work in Figma — so the marketing team could ship new pages fast without rebuilding layouts from scratch each time.
Phase 3
The blog — "The Stamp"
I designed and built the site's new blog in the same system: a featured lead, category filtering, a consistent illustrated card grid, and a topic tag cloud, plus a clean article template with a table-of-contents rail — all CMS-driven so the content team runs it themselves.
Enterprise component library
Built on Client-First, for enterprise clients
The component system is built with the Figma Client-First (Finsweet) methodology — the same class and structure system used across both Notarize and Datafold. It's a reusable Webflow library made specifically for enterprise clients: predictable naming, no style bloat, and components a marketing team can assemble into new pages and partner pages without a developer in the loop.
A/B testing & social proof
Beyond the rebuild, homepage experiments tested layout and messaging variations against a clear hypothesis each time, and a Trustpilot widget was embedded at the right point in the journey — after the value prop, before the conversion ask — so it read as a trust signal, not decoration.
Reflections
What I Learned
SEO is architecture, not a checkbox
Thousands of errors don't come from bad pages — they come from structural decisions baked into templates. Fixing them meant fixing the H1 pattern, the redirect logic, and the link structure at the source, so the whole site got cleaner at once.
Technical-debt cleanup compounds
Every dead link cleared and heading fixed made the next crawl cleaner and the rankings steadier. Progress wasn't a single launch moment — it was a curve that bent down week over week until the error count was effectively flat.
A component system is what makes enterprise velocity possible
Client-First turned page-building from bespoke work into assembly. The marketing team could stand up a new landing page or partner page from existing components — the real deliverable wasn't any one page, it was the system underneath them.
Consistency is the deliverable on a large site
One blog system, one component library, one heading structure beats a dozen clever one-offs. On a site this size, coherence is what keeps SEO clean, the CMS manageable, and the brand intact.
