BLITZMETRICS · META / HOW WE DO IT

One article, every site’s brand: how we push from the master to the verticals

We wrote one article. It went live on fifteen sites the same day — each one looking like it was born there, and not one of them leaking the wrong brand’s name. Here’s the machine that did it.

By Dennis Yu · BlitzMetrics · July 6, 2026

We had one good idea and fifteen places it needed to live.

The idea was model judgment — routing each task to the cheapest AI that clears the bar. Good enough to put in front of clients and partners. But “put it in front of everyone” is where most content operations quietly fall apart.

Because the same article can’t wear the same clothes everywhere. On a partner’s site it has to look like their brand and carry their name — not ours. On our own network of Spotlight sites it has to match each vertical. Do that by hand across fifteen sites and two things happen: the versions drift out of sync, and sooner or later the wrong brand’s name ends up on a page it should never touch.

Write once, skin many

The article body has no brand in it. Where the brand would go, there’s a token: {{BYLINE}}, {{METHOD}}, {{EYEBROW}}, the cross-links. The look is driven by CSS variables. So the same words render three completely different ways depending on which profile you hand them.

The guard is the whole point

Co-branding for a partner is a trust exercise. When our content goes on Sigrun’s site, it has to be hers — her look, her program, our expert credited as a partner, and our own company name nowhere on the page. “We’ll be careful” is not a system. Code is.

Master to vertical — the part that compounds

This is why it matters beyond one article. The Spotlight network is a master site and a fleet of verticalized ones — HVAC, roofing, concrete, pest control, and the rest. The whole point of that structure is leverage: build a thing once at the master, push it to all the children.

Skinning is that push, made real for content. Fix a sentence in the master article, re-run the skinner, and every vertical gets the corrected, correctly-branded version. No fifteen-tab copy-paste, no drift. The same discipline extends to anything shared — a call-to-action, a design block, a set of brand colors. Write it at the master; push it down the network.

A gotcha worth writing down

We teach by showing our work, including the parts that fight back. The fleet runs a modern block theme, and it does two things to injected content: it scopes your styles so they only reach inside the content area, and it prints its own page title on top of yours. Result on the first try: a doubled title and a full-width blowout.

The fix isn’t a CSS brawl — it’s using the platform the way it wants to be used: assign the page the theme’s built-in no-title template (kills the duplicate cleanly) and pin the content width. Baked into the profile once, every fleet page after it came out clean. The lesson we keep relearning: when the platform resists, stop fighting the cascade and use its native lever.

Where this goes next

The brand profiles we built for the skinner are the same idea WordPress ships natively as style variations and synced patterns — one master, many token-sets, pushed to the children. So the next step writes itself: move the network’s shared layouts into master patterns and per-vertical style variations, and the “push from master to vertical” stops being a script we run and becomes how the whole network is built.

The article we pushed
The Content Factory

Part of the BlitzMetrics Content Factory. The skinner, the brand profiles, and the guard are one small stdlib tool — no dependencies, just tokens and a forbid list. Built the way we build everything: once, at the master, so it works everywhere downstream.