Building Vibe App Scanner’s search traffic from the ground up.

Vibe App Scanner helps founders check the security of AI-built apps. When we started building its public search presence, there was no established content engine to inherit. December 2025 recorded just 29 Google clicks and 429 impressions.

The job was to connect a real product to the questions its potential users were already asking. That meant useful public pages, a site search engines could navigate, and enough product-specific substance to give people a reason to visit.

The property had a handful of recorded impressions in late November. We call this building an early search presence, not a literal zero-to-traffic claim.

Early work covered the basics that new software sites often miss: distinct page information, crawlable routes, sitemaps and internal links. We developed relevant security content and product pages, rather than relying on the homepage to answer every search.

As the library grew, we improved shared templates and page relationships. That let related topics support one another and made useful pages easier to discover. Search data helped us decide where to deepen the content and where to fix an existing page before adding another.

Monthly clicks reached 475 in January, 875 in March and 1,080 in April. May then slipped to 1,036: growth was real, but it was not a straight line.

By summer, the public site had grown to more than a thousand pages. At that scale, a defect in a shared template or link pattern can spread across the whole library.

We repaired broken destinations and orphaned content, improved crawl access and structured data, and introduced repeatable checks around releases. We also added original product-derived research and refined pages around the decisions prospective users were trying to make.

The August release records cite 69 broken destinations and 90 orphan pages in an earlier Ahrefs crawl. A later built-site audit of 1,250 pages reported no broken internal destinations or content orphans. These were different audit methods, not a like-for-like score comparison.

Google’s June and August spam updates made it especially important to separate search visibility from actual clicks. June recorded 579,616 impressions and 1,507 clicks. By October, impressions were lower at 228,361, while clicks had risen to 1,784.

In matched 28-day windows around the June rollout, clicks increased 15.8% while impressions fell 38.6%. The August comparison was weaker, with clicks down 8.1%. We kept working on page quality, discovery and technical reliability rather than presenting every movement as a win.

September and October work improved rendering access, contextual links, content accuracy and how the product’s report workflow was explained. October finished with more Google clicks than any earlier month in the period shown.

We can build the search-facing part of a software business, implement the technical changes ourselves and keep improving it after launch. This was not a one-off batch of articles followed by a ranking screenshot.

The evidence shows a small initial presence becoming a recurring source of search visits. It does not isolate the effect of any individual change or prove a Google penalty recovery. Search clicks are not a verified count of customers or revenue.