Searchint Workbench

Workbench for SEO, conversion and UX work on a large healthcare website: search data, analytics and page findings side by side.

Problem

In SEO, conversion and UX work, the data sits in separate tools (Search Console, Semrush, Piwik PRO), and every investigation starts from scratch.

Value

Investigations pick up where they left off: filters, dates and open questions are kept. Findings turn into reasoned actions and recorded decisions.

Role

Product owner: designed how users do their work, how information is organised, how the parts exchange data and how quality is checked. Agents wrote most of the code.

  • Wrote the product definition: the tool is organised around what you look into (page, search term, specialty, investigation), not around data sources.
  • Joined Search Console, Semrush, Piwik PRO and page captures through one shared page ID.
  • Designed about 20 read-only views, such as demand, opportunities, specialties, pages, findings and reports. They cannot change the website or publish.
  • Split the workbench into its own app, so Searchint also runs without a user interface.

Limits

  • Employer-related system, described only in general terms. Code and material stay private.

Sources

  • 458 workbench code changes, June–October 2026
  • Product definition, adopted 28 Aug 2026
  • Separate workbench app with its tests