Case Study

Project Everywhere: Standing Up a Live Search Everywhere Optimization Campaign

One Person Can't Market Everywhere. So the Bet Was Building an Entire Portfolio That Could.

Krisada / Claude Updated August 21, 2026 6 views
Proof Point

Two real bugs surfaced before the campaign had run a single day of distribution, and both were more interesting than any…

Measurement Frame

What was measured.

Build Date 2026-08-16
Wiring Completed 2026-08-17
Properties Live At Launch 2
Properties Planned 6
Timeline Events At Launch 8
Day Zero Digital Karma Score 1
Day Zero Gsc Impressions 28d 3,711
Day Zero Gsc Clicks 28d 446
Day Zero Distinct Queries 28d 101
Day Zero Good Bot Requests 28d 51,843
Baseline Metric Fields Uncaptured 16
Baseline Metric Fields Total 22
Banned Word Violations Found And Fixed 6
Day 7 Checkpoint Date 2026-08-23
Why It Matters

The short version.

Project Everywhere isn't a two-site pilot. It's the working name for Krisada's entire portfolio thesis: an interconnected system of properties designed to cut a clear signal through internet noise and prove entity clarity and authority using the portfolio's own established techniques, Exposure Velocity, the AI Digital Karma Protocol, Leverage Builders, Dataset SEO, AI to AI, and AI Website Systems, as its cornerstones, with Signal Architect Group as the architectural control room. This case study documents the first build session: standing up the master campaign page and timeline, publishing the seed article on RealSEOLife.com, and catching two real bugs (a hardcoded content pin quietly burying the launch article, and a banned word already live in six places) before the campaign's Day Zero baseline was even captured.

Context

What was the system?

Signal Architect Group holds the through-line without becoming a distribution channel itself, the same role its existing Digital Signal Architecture framework already played before this campaign gave it a name. Real SEO Life, DatasetSEO, AI Website Systems, LeverageBuilder, and the rest of the portfolio's named systems aren't marketing partners bolted onto the campaign. They're the cornerstones the campaign is testing, each one proving a different piece of the same underlying claim: that a genuinely interconnected portfolio, built on real entity clarity and real authority signals, can create the exposure one person's labor never could scale to alone.

The spec explicitly required auditing the existing repo first and extending existing conventions rather than inventing a parallel framework, so before anything got built, the actual site code decided the shape of the work, not the spec's assumptions. The handoff doc also claimed RealSEOLife.com already had the campaign's seed article live.

It didn't.

A search of the site turned up only a tag-level mention on unrelated articles. Rather than invent a URL to make the timeline look complete, the first build shipped with an intentionally empty evidence link, a placeholder that told the truth about what existed instead of a fake one that didn't.

Methodology

What changed?

Signal Architect Group became the control room: a new timeline collection (eight events, PE-000 through PE-007, one file per event following the site's existing convention) and an asset-role collection describing each portfolio property's functional role in the campaign, Real SEO Life, AI Website Systems, DatasetSEO, Digital Karma, 1 Mouse Marketing, and a not-yet-built Digital Asset Starter Kit. The timeline rendered as a native details-based expandable accordion, modeled on an existing pattern already live on AS400IBMSystems.com rather than a new UI invented for this campaign.

Once Krisada supplied the real seed article mid-session, it went live on RealSEOLife.com as "Project Everywhere: An SEO's Map to a Search Everywhere Universe," written by Krisada, cross-linked back to Signal Architect Group's timeline, and the empty PE-002 placeholder was updated to the real published URL.

The next real milestone wasn't distribution. It was capturing an immutable Day Zero baseline before any distribution began, using real numbers pulled live from the Digital Karma Data Warehouse rather than placeholders: GSC impressions, clicks, and distinct queries over a trailing 28 days, Good Bot request counts over the same window, and each property's Digital Karma Score where one existed. Across the two live properties, that baseline came out to a 0.72 Digital Karma Score, 3,711 GSC impressions, 446 clicks, 101 distinct queries, and 51,843 Good Bot requests, with 16 of 22 total metric fields honestly rendering as "Not yet captured" rather than a guessed zero, because Signal Architect Group has no GSC connection yet and Real SEO Life had no computed Digital Karma Score at the time.

Findings

What did the evidence show?

Two real bugs surfaced before the campaign had run a single day of distribution, and both were more interesting than anything a clean launch would have found.

First, the seed article was invisible on RealSEOLife.com itself. Not broken, not unpublished, just structurally buried: the articles hub had a hardcoded featured_slug pinned to a January article, and the homepage's separate featured-article mechanism was pinned to an unrelated older case study. The new article had neither pin, so despite being the most recent content on the site, it lost both prominent slots to stale manual overrides. The fix mattered as much as the bug: the articles hub pin was cleared entirely rather than re-pinned to the new article, because a manual pin was exactly the failure mode that caused the problem in the first place. The homepage widget kept its manual-flag design, so that one got set explicitly instead. Two different failure modes, two different fixes, not one blanket rule applied to both.

Second, the word "Operator," banned across the entire portfolio, had already made it into six live places on Signal Architect Group's Project Everywhere content, including one instance copied verbatim from the handoff doc's own wording. Source docs aren't automatically rule-compliant. They need the same sweep as freshly authored copy, and this campaign's own founding document proved it.

The third finding came from a direct architecture question: should the live measurement feed pull from a new pipeline straight out of the warehouse, or reuse something that already existed? Checking DatasetSEO.com's actual code first, rather than assuming a new pipeline was needed, found that export-datasetseo-intelligence.php already looped every active site nightly, already published per-property metrics files live and public, and already had both Signal Architect Group and Real SEO Life inside that loop with fresh data. Building a second pipeline would have duplicated logic that DatasetSEO's exporter had already gotten wrong and fixed multiple times historically. Two new lines in an existing nightly script, plus a small reader on Signal Architect Group's side, did the job instead. The 745 AI-bot-visit figure that later rendered on Signal Architect Group's own page matched DatasetSEO.com's independently rendered figure for the same property exactly, confirming the two numbers actually agreed rather than being separately computed and coincidentally close.

Key Takeaway

What can be reused?

A campaign built to prove that assets can earn exposure without hand-scaled labor almost got buried by hand-scaled labor's oldest failure mode: a manual pin nobody remembered to update. The fix wasn't a new rule against hardcoding. It was checking what already existed, on the actual live site and in the actual live warehouse export pipeline, before building anything new. Twice in one build, the right answer was reuse, not invention.

Evidence Library

Keep Browsing the Case Library

Move from this evidence file back into the full proof system.