DEV Community

Cover image for How We Took a New SaaS From Search Confusion to a Clean Google Entity Before Launch
Almin Zolotic
Almin Zolotic

Posted on

How We Took a New SaaS From Search Confusion to a Clean Google Entity Before Launch

We’re launching KeepCard on Product Hunt tomorrow.

Before launch, we ran into a problem that a lot of early-stage products probably hit and don’t notice right away:

Google was getting confused about what KeepCard actually is.

Instead of understanding KeepCard as a B2B ecommerce product, it was blending our brand with unrelated products that had a similar name. The page itself was fine to a human, but search engines need more than “looks good” to understand a brand entity correctly.

So we spent time fixing the foundation.

What KeepCard is

KeepCard is a pre-return recovery platform for Shopify and WooCommerce merchants.

It sits in front of the normal return flow. A customer scans a QR card, verifies the order, selects a reason, and preference-based returns can receive a controlled keep offer before reverse logistics starts.

That’s very different from a generic “card app” or consumer wallet product.

And that difference needs to be obvious everywhere.

The real SEO problem wasn’t rankings first. It was identity.

A lot of launch-stage SEO advice focuses on:

  • titles
  • meta descriptions
  • page speed
  • keyword placement

Those matter, but our first issue was more basic:

Google wasn’t fully confident about the entity behind the name.

If your brand name overlaps with existing apps, products, or companies, then good markup alone may not be enough. Search engines look at:

  • page titles and descriptions
  • structured data
  • crawlable supporting pages
  • social cards
  • external mentions
  • linked profiles
  • consistency of naming across the web

So we approached this like an entity cleanup project, not just an on-page SEO task.

What we changed

1. We made the homepage name more explicit

Instead of only saying KeepCard, we started using:

KeepCard for Shopify and WooCommerce

That sounds small, but it gives search engines a much stronger disambiguation signal.

We updated:

  • title tags
  • Open Graph tags
  • Twitter cards
  • meta descriptions
  • application naming
  • structured data labels

The goal was simple: every important machine-readable surface should say the same thing.

2. We strengthened structured data

We expanded the homepage schema to describe KeepCard as:

  • an Organization
  • a WebSite
  • a SoftwareApplication
  • a Service

And we added supporting context like:

  • alternate names
  • audience
  • publisher
  • brand relationship
  • service type

The point wasn’t “more schema because schema is good.”

The point was to help Google understand:

  • who we are
  • what we offer
  • who it is for
  • what category we belong to

3. We de-indexed the wrong surfaces

Our merchant app lives on a separate subdomain.

That app is useful to users, but not useful as a landing surface for search engines. In fact, it can create confusion if it exposes thin or generic titles.

So we added noindex signals there and kept the public marketing site as the canonical search target.

This is underrated:

Sometimes SEO improves not by publishing more pages, but by making sure crawlers ignore the wrong ones.

4. We improved technical quality because trust compounds

We also cleaned up the technical side:

  • fixed render-blocking font issues
  • reduced layout shift
  • improved heading structure
  • added proper landmarks
  • cleaned up CSP problems
  • improved performance on mobile

We ended up with a clean Lighthouse result:

  • 100 Performance
  • 100 Accessibility
  • 100 Best Practices
  • 100 SEO

That score alone doesn’t guarantee rankings.

But it removes a lot of unnecessary ambiguity and friction.

Why I’m posting this before Product Hunt

Because launch traffic is noisy.

If people mention your brand tomorrow across:

  • Product Hunt
  • X
  • DEV
  • LinkedIn
  • indie communities
  • blog roundups

you want those mentions reinforcing one clear identity.

Not scattering weak, inconsistent versions of your brand across the web.

That means the best time to fix entity confusion is before the wave of citations starts.

What we’re doing now to build branded citations and backlinks

The next phase is consistency.

We want every mention of KeepCard to reinforce the same identity:

KeepCard is a pre-return recovery platform for Shopify and WooCommerce merchants.

So we’re pushing that exact framing across:

  • Product Hunt
  • DEV
  • founder social profiles
  • launch posts
  • directories
  • documentation
  • email signatures
  • future guest posts

Not for keyword stuffing.

For entity clarity.

What I’d recommend to other founders

If you’re launching a new product, especially with a brand name that could be confused with something else:

1. Stress-test your name in search

Search your exact brand and see what Google thinks it is.

2. Make your machine-readable surfaces consistent

Titles, meta descriptions, OG tags, schema, canonicals, and app naming should tell the same story.

3. Keep crawlers focused

Index the pages that explain your business best. De-index weak or confusing app surfaces.

4. Use the same one-sentence description everywhere

You need a stable phrase people can repeat when they mention your company.

5. Treat backlinks as entity confirmation, not just authority

A backlink helps more when the surrounding text clearly says what your company is.

Final thought

The biggest SEO win for a new SaaS is often not “ranking harder.”

It’s making it easy for Google to stop guessing.

That’s what we focused on for KeepCard before launch.

If you’re working on search clarity, launch prep, or technical SEO for an early product, I’d love to compare notes.

We launch tomorrow on Product Hunt.

You can see the product here: https://keepcard.io

Top comments (0)