Serql

Problem / Context

Google Search Console is excellent source data and an awkward team workspace. Useful analysis often starts with an export, grows into a spreadsheet, and ends as a report that is already stale. Serql is built around a simpler question: what if the recurring parts of search analysis were already part of the product?

The product brings properties into one workspace, then makes classifications, topic clusters, annotations, trend detection, and shareable reports first-class operations.

Constraints

• Keep setup short enough that a new workspace reaches useful data in one session.
• Preserve the meaning of the source data while making large query sets easier to organize.
• Make reports readable without requiring every stakeholder to share a Google account.
• Keep beta operations understandable as the product and its data model evolve.

Approach and key decisions

The interface treats classification as a saved product concept instead of an ad-hoc regular expression. Repeated analysis becomes a named segment, and every view can reuse it. Trend and opportunity views sit close to the underlying rows so an automated signal never becomes a black box.

Live report links separate presentation from editing. That gives teams a calm read-only surface while the working workspace keeps its richer controls.

type Classification = {
  name: string;
  rules: Rule[];
  scope: "query" | "page";
};

Outcome

Serql is in public beta with one-click classifications, topic clusters, automated annotations, opportunity analysis, and shareable reports. The current work is less about adding dashboards and more about making each recurring SEO workflow faster, clearer, and easier to trust.