For founders

For founders who shipped the site themselves

You built the site in an afternoon with a builder and it looks finished. Google, a shared link and ChatGPT may still be seeing the builder default. This is how to find out and fix it without hiring anyone.

The title is still the builder default

A page titled "Lovable App" or "Vite + React" ranks for nothing and reads as unfinished in a shared link.

Crawlers get an empty page

Client-rendered apps send a blank shell to anything that does not run JavaScript. Google can wait; most AI fetchers do not.

The canonical points at the preview host

Builders stamp the preview domain into canonical and Open Graph tags. Every share and every index entry then credits the wrong address.

The checks that matter here

  • Metadata defaults
  • Server-visible content
  • Canonical host
  • Open Graph and Twitter cards
  • AI crawler access
  • Entity clarity

What the repair does

Every grade A finding becomes a pull request on your repository: titles and descriptions, canonical and Open Graph tags, robots.txt lines for search crawlers, Organization JSON-LD from your own name and address. You merge it; nothing touches your live branch until you do.

Audit my site

Questions

I do not know Git. Can I still use the repair?
Yes. Your builder syncs the project to GitHub in a couple of clicks; the guide on the Repairs page walks through it for Lovable, Bolt, v0, Base44 and Replit. Merging a pull request is one button on GitHub, and the builder picks the change up.
Will a fix break my site?
Repairs are typed transforms on metadata and configuration files, opened on a separate branch. If a build fails, close the pull request; nothing else changed.
How often should I audit?
Every prompt in the builder can undo a fix. Watch the site and every push to the repository triggers a re-check that reports what regressed.

Also: agencies, marketers, developers, online stores, saas.