A small business should measure a website redesign against the specific failures the redesign was meant to correct. Traffic alone cannot show whether the site became clearer, whether a purchase path works, or whether the owner can maintain the new structure.
The JerryGBooks.net evaluation created a useful baseline. The site earned 64 out of 100. Its strongest elements were not technical: the author voice, personal story, and Aragost world gave the site identity. Its weakest elements were operational pathways. References to books, the library, purchasing, contact, and engagement did not always lead to complete destinations. The memoir also needed clearer priority.
Those findings define measurable redesign outcomes.
Convert Each Finding Into a Test
“Improve navigation” is difficult to measure. “A visitor can reach the memoir purchase option from the home page without encountering a broken or ambiguous path” is testable.
The redesign can therefore be evaluated with checks such as:
- Do all primary navigation items open the intended destination?
- Can a reader identify the primary book and purchase path?
- Can a visitor distinguish the author biography from the story-world content?
- Does the contact action work and set an expectation for response?
- Can the owner update a book, event, or article without rebuilding the page?
Behavioral data can strengthen those checks: purchase-link clicks, completed contact forms, movement from book pages to purchase destinations, mobile task completion, and the quality of questions arriving through the site.
Measure the Content Architecture, Too
The Culture Architect project provides a second kind of baseline. Its challenge was to connect an author, a leadership concept, and a book without allowing the site to become three competing stories. Success is not just a modern appearance. The site must keep the book central while giving the leadership concept enough context and the author enough authority.
That can be tested through page purpose and pathway reviews. Does each page advance one of those relationships? Does proof appear before the request to buy or engage? Are dependencies—approved content, assets, access, and technical decisions—complete enough for the experience to work as designed?
Include Maintainability in the Result
The Cintman WordPress approach uses native Gutenberg blocks, an Idea Flow child theme, shared templates and patterns, staging-first testing, backups, verification, and rollback. Those choices create another measurement category: can the business operate the site after launch without being trapped in a fragile builder or a collection of custom HTML fragments?
Enterprise web programs may measure hundreds of events with dedicated analytics and optimization teams. A small business can use fewer measures, provided they map directly to the redesign goals.
The Cintman Group, a local San Antonio generative AI studio, connects website strategy, content, implementation, testing, and ongoing care. A successful redesign should make the business easier to understand, the next action easier to complete, and the site easier to maintain.
The baseline should be saved before implementation. Screenshots, link checks, pathway notes, content inventories, and maintenance observations provide evidence that can be revisited after launch. Without that record, teams often substitute memory or visual preference for measurement.
Measure the repaired pathways first. Then use traffic and engagement data to understand how often visitors use them.
Define the broken pathway before defining the redesign metric. Explore website design services.
The Cintman Group
