Case Studies & Process

Case Study: Rebranding and Rebuilding a Metals Manufacturer's Digital Presence (Kataria Metals)

Tikbo Team·· 5 min read

Kataria Metals came to us mid-rebrand — new name conventions, new visual identity, a decision to consolidate several older product line names under one brand — and asked us to rebuild their website and lay the groundwork for organic and paid growth from there. The tricky part of this engagement wasn't the rebuild itself. It was that a rebrand and a website rebuild happening at the same time creates SEO risk that has nothing to do with content quality and everything to do with continuity: old URLs, old brand mentions across the web, and existing search equity that a careless migration can simply throw away.

Key takeaways

  • Rebrands and website rebuilds happening simultaneously multiply migration risk — we scoped them as one coordinated project, not two.
  • The biggest early decision was what to do with legacy product-line URLs and whether to fold them into the new brand structure or preserve them.
  • Redirect mapping took longer than the actual site build, and we underestimated that at the start.
  • Paid media couldn't launch on the new brand until certain trademark and naming-consistency checks were done, which delayed our own timeline.

The situation: a name change, a rebuild, and old equity at stake

Steel and metals manufacturers often build a domain's authority slowly over years through B2B relationships, trade directory listings, and industry press mentions that reference the company by its old name and old URLs. Kataria Metals' rebrand consolidated a few previously separate product line identities into one unified brand, which meant some URLs, page titles, and even backlink anchor text across the web referred to names that were about to stop being used publicly. Rebuilding the website at the same time as the rebrand meant every architectural decision had to account for both problems at once: new information architecture reflecting the unified brand, and preservation of whatever search visibility the old structure had earned.

Scoping the two projects as one

We pushed back, early, on treating this as "rebrand project" plus "website project" run by two different workstreams reporting separately. They needed to be one project with one shared migration plan, because every URL decision the design and dev team made had SEO consequences, and every legacy-URL decision we made constrained what the new site's architecture could look like.

PhaseFocusKey decision point
Phase 1: AuditInventory every indexed URL, backlink, and directory listing referencing old brand namesWhich legacy names still carried active search demand
Phase 2: ArchitectureDesign new site structure reflecting the unified brand's product taxonomyFold old product-line pages into new categories, or preserve as legacy landing pages
Phase 3: Redirect mappingOne-to-one and one-to-many redirect plan for every legacy URLHandling URLs with no clean new-site equivalent
Phase 4: MigrationStaged launch, redirect verification, index monitoringTiming the switch to avoid a mid-crawl inconsistency
Phase 5: Paid and organic rampNew campaigns and content under the unified brandHolding paid launch until naming consistency was verified across all assets

What we decided about legacy product-line pages

The hardest call in Phase 2 was what to do with product-line pages that had built independent search visibility under names the rebrand was retiring. Folding everything into the new unified taxonomy was the cleaner brand outcome, but it risked losing whatever specific relevance those old pages had for narrow, high-intent industrial search terms. We didn't fold everything in wholesale. For product lines with clear standalone search demand, we kept dedicated landing pages under the new brand but preserved the specific technical terminology and use-case language that had made the old pages relevant in the first place — new brand name, same substantive content, redirected cleanly from the old URL. For smaller or overlapping product lines, we did consolidate into broader category pages, accepting some loss of narrow specificity in exchange for a cleaner, less confusing site structure going forward.

Field note. When a rebrand forces consolidation, don't assume every legacy page deserves to survive independently. Check actual search demand and backlink value per URL before deciding — some pages that felt important internally had almost no external search signal attached to them at all.

Redirect mapping took longer than the build

We underestimated this going in. The website rebuild itself — new templates, new design system, new content — moved at a predictable pace. Mapping every legacy URL to its correct new-site destination, and deciding what to do with the handful of URLs that had no clean equivalent (some old pages covered discontinued product configurations that genuinely didn't exist under the new brand), took considerably more back-and-forth than we'd planned for. We followed the redirect and site-move guidance in Google Search Central's documentation closely, particularly around avoiding redirect chains and making sure the migration didn't get staggered in a way that left Google crawling a mix of old and new URLs with inconsistent signals for an extended period.

Why paid media had to wait

Once the site was close to launch, the original plan was to bring Google Ads and organic growth work online together. We held paid media back for a short additional stretch because naming consistency wasn't fully resolved — some trade directories and industry partner sites were still referencing the old brand name in ways that would have made paid ad copy referencing the new name look disconnected from what a prospective buyer saw elsewhere when researching the company. Launching paid on an incompletely rebranded footprint risked confusing exactly the kind of high-consideration B2B buyer this client depends on, so we scoped an explicit "naming consistency check" gate before paid could go live.

What we'd do differently

We'd scope the redirect-mapping phase with more buffer from the outset — it's the part of a combined rebrand-and-rebuild project that's easiest to underestimate because it looks like "just a spreadsheet" until you're actually reconciling hundreds of URLs against a new taxonomy. We'd also start the directory and backlink-source outreach (asking partner sites to update references to the new brand name) earlier and in parallel with the build, rather than treating it as a post-launch cleanup task, since it ended up gating the paid media launch later than it needed to.

A rebrand is an SEO event whether or not anyone plans for it that way. The only choice you actually have is whether you manage that migration deliberately or let it happen to you.

If you're planning a rebrand alongside a rebuild

This combination comes up more than people expect, and it's worth scoping as one project from day one rather than discovering the overlap midway through. We've covered adjacent technical ground in our technical SEO for manufacturing websites guide and our industrial B2B SEO piece. If you're facing a similar migration, reach us at hello@tikbo.in or through our contact page before you start moving URLs around.

Next step

A rebrand touches SEO whether anyone plans for it or not. Better to plan for it.

Talk to us about a rebrand or rebuild

Or email hello@tikbo.in