Skip to content

01 A CMT Web product

SEO operations grounded in evidence.

Kepler keeps the data, reasoning and limits behind each suggested next step together—so a team can decide what deserves attention before it changes anything.

Built for reviewable SEO work—not ranking promises or automatic client-site changes.

Original Kepler concept artwork showing a blue planet
Kepler, illustrated as a working surface—not a black box.

02 How it works

A process that keeps the why attached to the work.

The useful part is not a bigger dashboard. It is being able to move from an observation to a decision without losing what made the work worth doing.

  1. 01

    Collect

    Bring approved site and first-party observations into a bounded record with its source and collection limits.

  2. 02

    Interpret

    Turn observations into clear, reviewable signals instead of a score that asks you to trust a black box.

  3. 03

    Prioritize

    Rank the work that merits attention, with the evidence, confidence and unanswered questions still visible.

  4. 04

    Decide

    Keep a person in charge of what changes, where it changes and whether the available proof is enough.

  5. 05

    Measure

    Record what happened after an approved change, including neutral and inconclusive outcomes.

03 What stays visible

A recommendation should be explainable without a meeting.

Kepler is designed to keep the limits as visible as the signal, so the next step is easier to defend, defer or reject.

Site evidence

A crawl record can distinguish what was fetched, what was skipped and where coverage stopped instead of treating an incomplete pass as a complete audit.

First-party context

Search and analytics inputs are treated as authorized business data with freshness, coverage and source limits—not as universal truth.

Opportunity reasoning

Suggested work carries the observations and conditions that support it, so a team can challenge the recommendation before acting.

Change history

A useful record connects an approved change to its scope, its review trail and the later measurement rather than assuming every change caused a result.

04 Guardrails

Useful analysis has limits. Kepler says where they are.

It is built to support careful work: make an informed decision, preserve the record and know when the available evidence is not enough.

  • No ranking promises

    Search outcomes depend on many factors outside a tool. Kepler is designed to make the work and its evidence clearer, not to guarantee a position.

  • No automatic client-site changes

    Recommendations are not publication authority. A human reviews the proposal, scope and rollback path before any controlled change.

  • Evidence can be incomplete

    Missing, sampled or stale inputs stay visible. When the record cannot support a conclusion, the honest answer is that it cannot decide yet.

  • Boundaries stay explicit

    The product is designed around organization boundaries, review trails and scoped access so one client’s evidence does not become another client’s context.

Make the next SEO decision easier to defend

Open Kepler to see the product, or talk with CMT Web about the work your site needs next.