How We Built Valentin Radu’s Entity System

Live deployment status: This is the record of work completed in authenticated WordPress and browser sessions on July 22, 2026. Six core pages are live on ValentinRadu.com, five recording-derived articles remain drafts pending full-source review, the DennisYu.com collaboration article remains a draft, and this report was published only after the live site was checked and cross-linked.

Valentin Radu already had real authority: he founded Omniconvert, teaches through CVO Academy, wrote The CLV Revolution, and shares customer-value material with Dennis Yu. The problem was not a shortage of proof. His personal site mixed that proof with a legacy template, sparse navigation, a blank blog, conflicting schema, and a namesake risk in Google.

1. What the authenticated session found

Before any deployment, we captured the live Home, About, Blog, and Gallery pages. The Home and About pages contained contradictory or leftover template language, the Blog reported no posts, navigation omitted essential entity pages, and the footer still showed 2023. We also found that the theme header was hard-coded to a legacy menu instead of the menu location the deployer assigned.

2. The exact source inventory and publishing rule

The checksum-verified deployment bundle contained 31 files: 12 source-package files, seven article artifacts, three WordPress deployer archives, four original visual assets, and five runbook or manifest files. Its entity ledger listed 14 source records, and its repurposing queue contained 24 rows after the header. Those counts describe the supplied inventory; they do not imply that every linked recording was fully reviewed during this session.

The source-safety rule controlled publication. The five source-derived WordPress posts were created as drafts and remain drafts because the complete original videos or recordings were not available for review. None has been given a featured image, and none will be published until it has transcript or embed evidence plus an owned visual. We did remove public links that led visitors to draft-only 404 pages.

3. What went live on ValentinRadu.com

After a full Duplicator backup, the domain-locked Valentin deployer was installed and activated. These six core destinations are now live:

• Home
• About
• The CLV Revolution
• Podcasts
• Media & Speaking
• Articles

All six use Valentin Radu as the WordPress author and an owned featured image with descriptive alt text. The live header and footer now link to all six destinations. We published one original, non-recording-derived index article—Start Here: Customer Value Resources from Valentin Radu—so the Blog archive is useful without prematurely releasing the five source drafts.

We corrected the broken book-image reference, removed duplicate lead images caused by the theme’s featured-image template, added a missing Blog H1, cleared cached legacy output, and corrected the old schema-plugin spelling “Valentine Radu” to “Valentin Radu.” The final desktop audit found one H1, the intended canonical URL, index/follow robots, no broken images, and no horizontal overflow on each core page.

4. Responsive and functional QA

We visually inspected all six core pages at desktop, tablet, and mobile sizes, producing 18 responsive after screenshots. We also inspected the five protected source-draft previews at desktop and mobile, producing 10 additional draft captures; all five had one H1, Valentin Radu attribution, no broken preview images, and no horizontal overflow. With the two Dennis draft views and two BlitzMetrics article views, the affected-page QA covered 32 responsive views. The complete evidence folder contains 42 genuine captures: four before images, 28 Valentin core/draft views, and 10 backup, deployment, Google, Dennis, and BlitzMetrics reports.

Rollback readiness was verified without clicking the destructive rollback control. The completed Duplicator package is 735.74 MB, and the deployer also preserved its pre-deployment snapshot. Executing rollback would delete newly created posts, so a destructive rollback test was not authorized.

5. Cross-site entity links and the DennisYu.com draft

The new resource index and core pages naturally connect ValentinRadu.com with DennisYu.com, BlitzMetrics, Omniconvert, CVO Academy, The CLV Revolution, and the shared Ecommerce Growth Stories material on Spotify. These links reinforce the real relationship among the people, companies, course, book, and podcast rather than manufacturing a separate entity on every page.

The DennisYu.com deployer created “Why Valentin Radu and I Focus on Customer Value” as draft post 37419 under Dennis Yu’s authorship. We removed its duplicated lead image, added a semantic H1, added the CVO Academy link, confirmed the other contextual links, and checked it on desktop and mobile. It remains a draft because Dennis must review it and approve an owned collaboration photo or clip before publication.

6. Knowledge Panel and Wikidata safeguards

A current Google search for “Valentin Radu Omniconvert” did not show an entrepreneur Knowledge Panel. A name-only search showed a Knowledge Panel for the Romanian conductor. That is the collision the runbook warned about.

We did not modify conductor entity Q15436894, did not submit a Knowledge Panel correction, and did not create a new Wikidata item. The present independent sourcing was not strong enough to make a separate entrepreneur item defensible under Wikidata eligibility rules. Search Console inspection submission was also unavailable because the authenticated Google account does not have access to the ValentinRadu.com property.

7. Time, problems, and decisions

The action log began at 03:51 PDT. WordPress recorded the article going live at 05:58 PDT. The final site audit closed at 06:15 PDT, for 2 hours 24 minutes of authenticated work. No separate dollar cost was charged or measured during the session, so this report records the actual time instead of inventing a monetary estimate.

8. Final compliance scorecard

Compliance score: 14 of 15 controls passed (93.3%). The only blocked control is Search Console property access. The score does not count a destructive rollback execution as required, and it does not treat unpublished, unreviewed source articles as a failure; keeping them in draft is the compliant result.

This deployment turned scattered proof into a live, navigable entity system while preserving the evidence boundary. The most important result is not that more pages exist. It is that every published claim, link, image, and status in this report matches work that was actually completed.