Rhythm

A monthly visibility slice


Abstract still: a baseline, an accent polyline, and a peak dot.

A visibility slice is a month of the same prompts on ten named engines. It is a method, not a promise that you will be cited next week.

Answers wander. Ask the same question twice and the prose shifts. That is why we freeze the panel, name the engine, repeat the sample, and keep three columns. Statistical GEO is a slice you can defend. A screenshot is a souvenir.

Engines are not one pool. We name the surface. We do not sell a branded index. Mentions per 1,000 queries is a unit a meeting can hold — not a mysterious 0–100 score with a vendor name on it.

The loop is audit, access, facts, earned publishers, then the next slice. Skip a step and you decorate a number. Content without crawl is theatre. Crawl without extractable spans is a fetch of noise. Outreach on domains the model never cites is hope.

When we connect visibility to sessions, the method sits on the label. GA4 undercounts AI referrers. We do not invent last-click GEO ROI to fill the gap. Cookieless logs of human traffic from AI referrers are a different channel from product analytics cookies.

Payments stay out of v1. The slice is the product you can read. Rank guarantees are not. A manager still writes back. That is the rhythm: a calendar, a panel, three columns, and a human on the publish path.

All ideas