Case study
Saramis Global: a full rebuild, built SEO-first
By Nipun Arora Last updated 2026-09-01
Saramis Global (saramisglobal.com) is an accounting and audit-support firm. Its previous site had grown large and repetitive over several years of additions with nothing ever pruned, the ordinary way a site accumulates pages without a plan. The rebuild's first move was subtraction: three service lines, three pages, inside a 13-page site, all of it settled before a single design decision got made.
The situation
A site that had grown pages faster than it grew clarity
The old Saramis Global site had reached the size where more content no longer meant more authority. Near-duplicate pages compete with each other for the same search term instead of reinforcing it, the same failure this project's own keyword-ownership rule exists to prevent, and a visitor reading three overlapping pages about one service trusts the site less, not more.
A patch would have meant editing pages that should not have existed as separate URLs in the first place. The brief called for a full rebuild instead: three real service lines, three pages, and nothing standing in for a service the firm does not actually offer.
The search research
One service line, one page, decided before design
The research step here was structural rather than keyword-first: mapping the firm's three real service lines, bookkeeping and accounting, audit support, and tailored finance solutions, onto exactly three pages, and cutting everything that did not map onto a real, sellable service.
No blog, no solutions hub, and no how-we-work page separate from About made the final architecture: 13 routes total, home, a services hub, the three service pages, About with two sub-pages, Contact, three legal pages, and a 404. Every route earns its place against one question: does a real visitor, or a real search query, need this as its own page. A page that cannot answer yes gets folded into a page that can.
What was built
A static Astro build with a structured-data foundation
The site runs on Astro 7 with static output on Cloudflare Pages, self-hosted web fonts rather than a third-party font CDN a browser has to wait on, and a strict Content-Security-Policy with no inline scripts anywhere in the build.
Structured data starts with an Organization node carrying the firm's real registered address as a PostalAddress, machine-readable from day one rather than added after launch as an afterthought. That foundation is the same one every service page, and every future page, links back to as the site grows.
Scroll-driven interaction ships on a small number of moments, home's chaptered introduction chief among them, built on a reusable scroll engine rather than a one-off script per page. It never substitutes for content clarity: every scroll moment still renders as plain, readable markup with the animation as an enhancement, not a requirement to read the page.
Measured results
A smaller site, shipped clean
The measurable result of a pruning-first rebuild is a smaller, cleaner site that still covers everything the old one did, minus the duplication.
- 13 built pages, zero duplicate service pages
- As of 2026-08-31, the build carries 13 pages total, with no two pages competing for the same service term. Every one of the firm's three real service lines owns exactly one page.
- Clean build, every revision
- The build reported zero errors and zero warnings across every client-revision pass recorded in the project's build log through 2026-08-31, with the 13-page count holding steady through each one. A rebuild that stays clean under repeated client changes, not just on launch day, is the harder bar.
- Live on Cloudflare Pages since 2026-08-30
- The rebuild replaced the previous site in production on 2026-08-30, direct upload to Cloudflare Pages, with the previous version kept as a one-click rollback rather than deleted outright.
What it proves
Fewer pages, correctly owned, beats more pages competing with each other
A rebuild does not need to be bigger than what it replaces to be better. Saramis Global's 13 pages cover the same three service lines the old site did, with every page owning its own search term instead of splitting it against a sibling page.
This is the identical discipline behind nipunarora.me's own structured-data work and its keyword-ownership rule: one page, one keyword, no exceptions. It transfers directly to a rebuild this size, and it is the same reasoning covered in full on how I work with clients.
Considering a rebuild instead of another patch?
Hire me for your rebuild