The risk nobody warns you about before a redesign
A website redesign is the single most common way a local business accidentally destroys search visibility it spent years earning. The business is not doing anything reckless. It hires a designer, approves a better looking site, launches it, and then watches the phone go quiet.
The pattern is well documented in migration research. Industry analyses of site migrations consistently find that the majority result in measurable traffic loss, and that only a small minority end with improved rankings. Migrations executed without a rigorous redirect map routinely see organic traffic fall by as much as half. Recovery, when it happens at all, is slow: cleanly executed migrations tend to stabilize within about two months, while mismanaged ones can take well over a year to return to where they started.
None of that is caused by the new design. It is caused by what happened to the addresses.
What actually breaks during a redesign
Search engines do not index your business. They index specific URLs. Every ranking, every backlink another site pointed at you, and every piece of accumulated trust is attached to a specific address. Change the addresses without telling anyone where things moved, and all of it is orphaned at once.
URLs change silently
This is the primary failure. A site moves from /services/ac-repair.html to /air-conditioning-repair/ during a platform change. The old address returns a 404. Every link pointing at the old address now leads nowhere, and every ranking that address held is gone. On a site with fifty pages, this can happen fifty times in one afternoon without anyone noticing, because the new site looks correct to a human clicking through the new navigation.
Content gets cut for aesthetics
Designers reasonably prefer less text. But the page that was ranking was often ranking because of the depth of what it said. Trimming a 2,000 word service page to 300 words of elegant copy removes the reason it ranked. The page still exists at the same address, so nothing looks broken. It simply stops appearing.
Structured data disappears
Schema markup, business information, review markup and FAQ data are frequently attached to the old templates and are not carried across. The site loses its machine readable identity at exactly the moment search engines and AI tools are re-crawling it to figure out what changed.
Internal links get flattened
The old site may have had a deliberate structure where service pages fed each other and the homepage fed the important pages. A redesign built around a cleaner navigation often removes those contextual links. Authority stops moving through the site.
Speed regresses
New sites are frequently heavier than the ones they replace, because modern templates ship more code and larger images. A visually better site that loads three seconds slower converts worse, and the business attributes the drop to something else.
How we run a redesign that keeps what already works
Our sequence is deliberately conservative at the start and only becomes creative once the preservation work is settled.
Step one: inventory everything before touching anything
Before design begins we build a complete list of the existing URLs, which of them have any search visibility, which have external links pointing at them, and which produce contact form submissions or calls. This is the asset register. Nothing on it gets removed without a deliberate decision and a destination.
This step is where most redesigns go wrong, because it is unglamorous and it happens before anyone has seen a nice picture. It is also the step that determines whether the project preserves value or destroys it.
Step two: decide keep, merge, rewrite or retire, page by page
Each existing page gets one of four verdicts. Keep means the URL and its content survive largely intact because it is working. Merge means two thin pages combine into one stronger page, with the retired address redirected to the survivor. Rewrite means the address stays and the content gets rebuilt because the topic matters but the execution is weak. Retire means the page goes, and it redirects to the closest relevant survivor rather than to the homepage.
Redirecting everything to the homepage is a common shortcut and a bad one. Search engines increasingly treat a redirect to an irrelevant page as a soft 404, which means the value is lost anyway. The redirect has to go somewhere that genuinely answers the same question.
Step three: build the redirect map before launch, not after
Every changed address gets a permanent 301 redirect written and tested before the new site goes live. Single hop, not chains. A redirect that passes through two or three intermediate addresses leaks value and slows the page for the visitor.
We test the map against the actual old URL list, not against a sample. A redirect map that covers 90% of URLs is a map that loses the other 10% permanently.
Step four: migrate the structured data and the business information
Schema, business name, address, phone, service list and category information move deliberately. Consistency here matters beyond the site itself, because inconsistent business information across the web weakens the confidence search engines have that the listings describe one real business. Our guide to business information consistency covers why this matters for the map pack.
Step five: launch, then watch closely for six weeks
Launch is not the end of the project. In the first weeks after a migration, search engines re-crawl and re-evaluate everything. We monitor indexing status, crawl errors, redirect failures and ranking movement, and we fix what surfaces. A brief dip in the first two to four weeks is normal as engines re-process the site. A sustained drop is a problem with a cause, and the cause is usually findable.
Redesign or rebuild: how to tell which one you need
These are different projects and choosing wrong is expensive in both directions.
A redesign preserves. It is the right call when the site has real search visibility, real backlinks, or real content depth worth keeping. The work is restructuring and rebuilding on top of an existing asset. The constraint is that you inherit some of the old decisions.
A rebuild starts clean. It is the right call when the site has essentially no search visibility, no meaningful external links, and no content worth preserving. In that case the preservation work is overhead with nothing to preserve, and starting from a clean structure is faster and produces a better result.
The honest test is data, not opinion. If Search Console shows the site receives meaningful organic impressions and clicks across multiple pages, redesign. If it shows almost nothing, rebuild, and treat it as a first website design project.
Most local business sites we look at fall into the second category, and telling an owner that their existing site has nothing worth preserving is usually the more useful answer even though it sounds worse.
What we have measured ourselves
We are part of Rendimension, which operates several of its own domains, and we have used them to test assumptions rather than repeat industry advice we have not verified.
One comparison is directly relevant to redesign decisions. Two of our own domains were measured over the same 90 day window using Search Console. One had a domain authority of 16, 188 referring domains and 2,118 pages with impressions. The other had a domain authority of 5, 8 referring domains and 215 pages with impressions. The weaker domain, by every authority metric, produced more clicks, a higher click through rate and a better average position.
The reason was not authority and it was not design. It was that the smaller site had pages answering questions with almost no competition, while the larger site had pages competing for terms owned by established players. That result shapes how we approach a redesign: we spend the effort on what each page is asked to compete for, before we spend it on how the page looks.
What a redesign does not fix
Being direct about this saves money.
A redesign does not fix an offer nobody wants. If the pricing, the positioning or the service itself is the problem, a better site presents that problem more clearly to more people.
A redesign does not create traffic that was never there. Rebuilding a site that receives forty visitors a month produces a better site receiving forty visitors a month. Visibility is a separate job, handled by local SEO and AI search visibility.
A redesign does not stay current on its own. Eighteen months after a redesign, an unmanaged site is drifting out of date again. That is the failure website management exists to prevent, and it is the reason our plans bundle the rebuild with ongoing monthly work rather than selling the rebuild alone.
What this costs
A standalone redesign for a local service business generally falls in the same range as a new build, roughly $3,000 to $10,000 for most small service businesses, with larger or more complex sites running higher. The preservation work adds cost relative to a clean rebuild, which is why the redesign or rebuild question is worth answering honestly before quoting.
Our plans include the rebuild in every plan, starting at $499 per month for Presence, $599 for Growth and $999 for Growth plus AI. Scope and pages are agreed before we start building. For a business that has been burned by a redesign that lost its rankings, the relevant difference is that we are still responsible for the site in month six, when the consequences of migration decisions actually show up.
Signs it is time
The clearest triggers we see in San Antonio businesses are these. The site is not usable on a phone. The business has changed what it sells and the site has not caught up. Nobody has been able to edit it for two years because the person who built it is gone. It loads slowly enough that people leave. It was built on a platform that is no longer supported. Or the design so clearly belongs to a previous decade that it costs credibility before anyone reads a word.
Our detailed breakdown of redesign signals works through each of these. If you are not sure which side of the line you are on, the free website review will tell you whether your site has visibility worth preserving, which is the question that decides everything else.
The pre-launch checklist we will not skip
These are the items that separate a migration that holds its ground from one that costs a year of recovery. We run all of them before the new site is pointed at the live domain.
Full crawl of the existing site, exported. Every URL that currently resolves, including ones not linked from the navigation. Old landing pages, forgotten blog posts and orphaned service pages frequently carry links and rankings nobody on the team remembers.
Search Console export of every page with impressions. This is the ranked list of what actually has value. A page can look unimportant internally and be responsible for a third of the site's search visibility.
Backlink export. Any external site pointing at a specific old URL is a vote that is lost if that address dies without a redirect. These are the addresses that matter most in the redirect map.
Redirect map written, reviewed and tested against the real URL list. One hop each, no chains, no bulk redirects to the homepage. We test it on a staging environment before launch, not by watching errors appear afterwards.
Titles, descriptions and canonicals audited. Every surviving page keeps a unique title and description, and every page points its canonical at itself. Duplicate titles and missing canonicals are two of the most common regressions introduced by a template change.
Structured data ported and validated. Organization, service and breadcrumb markup carried across and checked, not assumed.
Analytics and conversion tracking verified on staging. Losing the ability to measure the migration is a quiet failure. If tracking breaks at launch you cannot tell whether the drop you are seeing is real.
Sitemap regenerated and ready to submit. Submitting the new sitemap immediately at launch shortens the window in which search engines are working from stale information.
Performance measured on staging, at mobile sizes. If the new site is slower than the old one, that is fixed before launch rather than discovered in the post launch traffic data.
What makes a San Antonio redesign different
Two local realities change redesign priorities here more than they would in a larger or denser market.
Many local sites were built by someone who is no longer reachable. San Antonio has a long tail of small businesses whose sites were built years ago by a relative, a former employee or a one person shop that has since closed. The practical consequence is that the redesign often starts with a recovery problem rather than a design problem: locating the domain registrar, the hosting account and the ability to edit DNS. We treat that as the first step, because a beautiful new site you cannot actually publish is not progress.
Service area coverage is usually wrong on the old site. Businesses grow outward from where they started. A company that began serving the near northside and now covers Stone Oak, Boerne, New Braunfels, Schertz and Converse frequently has a site that still describes the original, smaller footprint. A redesign is the natural moment to correct that, and it is one of the few changes that can produce visibility gains rather than just preserving what exists.
The caution attached to that is real. Expanding coverage does not mean generating a page for every surrounding town. Publishing near identical pages that differ only by city name is classified as doorway content and can damage the site. Coverage expands where there is genuine service and genuinely specific things to say about working in that area.
How we report during and after a migration
You should not have to take our word for whether a migration went well. In the six weeks following launch we track four things and report them plainly: indexed page count against the pre launch baseline, crawl errors and redirect failures, ranking movement for the pages that had visibility before, and form submissions and calls against the prior period.
If something drops, we say so, along with what we think caused it and what we are doing about it. A migration report that only contains good news is not a report.
