RowSpeak

RowSpeak’s origin story isn’t a typical product launch story. It starts with a name we could no longer use—and a domain change we’re still dealing with.

In April 2026, we had to stop using our original product name, Excelmatic.

We chose RowSpeak, with the slogan “Let Rows Speak.” It captured what we wanted to do: help people make sense of their data. New name, same focus on data analysis.

Then we changed the domain and implemented 301 redirects.

That’s when the trouble started.

Before the move, we had search visibility. Now, barely any.
Before the change, Excelmatic had recorded 440K Google impressions and 6K clicks.

As I write this in September, RowSpeak has fewer than 200 pages indexed and only around 200 impressions.

I’ve spent a lot of time trying to figure out what’s wrong and get the new domain indexed. So far, nothing I’ve tried has brought a meaningful recovery.

The most confusing part? Pages on the old domain have started appearing in Google’s index again, while the new domain still struggles to get indexed.

It’s frustrating to keep working on a product while also trying to recover the visibility it already had under another name.

My takeaway: choose a name and domain you can keep.
We needed to change our name. This wasn’t a rebrand just because we wanted something catchier.

But the experience has changed how I think about choosing a domain at the beginning.

I’d spend more time making sure it’s something we can confidently use long term—not just something that sounds good on launch day.

And if I already had a domain bringing in search traffic, I wouldn’t change it lightly.

I’m not saying every domain migration ends like ours. I don’t yet have a complete explanation for why ours has gone so badly. But setting up redirects and recovering search visibility have turned out to be two very different milestones for us.

We named the product RowSpeak because we wanted to let the data speak.

Right now, our own search data tells a pretty painful story.

Has anyone here been through a domain migration where Google kept indexing the old domain while barely indexing the new one? What eventually helped—and how long did it take?