Research and practical notes from Sight.
Product thinking, technical analysis, and field notes on SEO, AI visibility, answer engines, and the operating systems behind modern search teams.
Product
How we build
Method
What we measure
Practice
How teams act
- 2026-07-1901
Introducing Sight: one score for SEO and AI visibility
Why we built a single audit that covers classic search and AI answer engines - one report, one number, one punch list instead of two disconnected tools.
Read the article - 2026-07-1902
SEO vs GEO: what actually changed
AI answer engines didn't kill SEO - they added a second game with a different win condition. Here's the real shift from ranking links to being cited, and the share-of-voice idea it introduces.
Read the article - 2026-07-1903
Why your site might be invisible to AI
If your content only appears after JavaScript runs, AI answer engines that read raw HTML may see an empty shell. Here's the problem, how to spot it, and how to fix it.
Read the article
What we publish and how we approach it
The Sight blog documents the product, the measurement method behind it, and the practical decisions search teams face as AI answers become part of discovery.
Each note is designed to stand on inspectable evidence. We explain what was measured, how the result should be interpreted, where the method can mislead, and what a search or product team can do next. That keeps release notes, research, and operating advice useful beyond a single screenshot or model response, while giving readers enough context to test the idea in their own workflow.
Research with inspectable evidence
When we discuss AI visibility, citations, or model behavior, we separate the observed response from the metric derived from it. Product screenshots and examples are used to show the underlying answer, source, page, market, and collection date wherever those details matter.
Product notes with operating context
Release articles explain more than the control that changed. They describe the search workflow the feature supports, the input it relies on, the output it creates, and the handoff it is intended to remove for strategists, engineers, account teams, or clients.
Practical guidance without guaranteed outcomes
Search systems are probabilistic and competitive. Our field notes focus on useful actions, testable assumptions, and evidence a team can review. We avoid presenting one model response, one ranking movement, or one audit score as a universal promise of traffic or revenue.