We ran Signal on our own site. Here's what it found.

If we're going to tell you Aivatar Signal finds what's breaking your site's visibility, the least we can do is show you what it found on ours. This is the unfiltered version.

Start freeSee Signal

Initial baseline — Foundation Weak, 31/100

The homepage had no H1. Every subpage's canonical pointed back to the homepage. The sitemap declared four phantom pages. JSON-LD referenced an unrelated domain. ICP was nowhere visible. Homepage content was 180 words. Technical 76/100, Content 10/100, Trust 20/100, AI Visibility 5/100.

What Signal actually caught

  • No H1 tag on homepage — Blocker.
  • Homepage and subpages served identical meta description — Blocker.
  • Canonical tag pointed to homepage from every subpage — Blocker.
  • Homepage content was thin (~180 words) — High severity.
  • ICP not stated above the fold — High severity.
  • Production sitemap referenced phantom pages — Medium.
  • JSON-LD schema pointed to unrelated domain — Medium.

The phases, honestly

  • Phase 0 — Emergency fixes — robots.txt, schema cleanup, navbar restore.
  • Phase 1 — Technical SEO foundation — per-route prerendering, unique metadata.
  • Phase 2 — Public website rebuild — homepage, about, pricing, navbar.
  • Phase 3 — Content depth and topical clusters — use cases, glossary, comparisons.
  • Phase 3.5 — Trust layer — founder section, case study, changelog.

What improved

  • Per-page unique title, description, canonical — Across 40+ routes.
  • Schema coverage — Every tool has its own SoftwareApplication schema. Glossary pages serve DefinedTerm schema.
  • Sitemap hygiene — 33+ real URLs, zero phantom pages.
  • Navigation — Four live tools surfaced as primary nav.
  • Homepage — ICP stated above the fold.