From Search Engine Strategies to Answer Engine Strategies

When we relaunched Search Engine Watch in August, I wanted it to be useful to the people making decisions about search today. We’re putting original reporting, practical tests and clear explanations at the centre of that work.

It also means bringing people together. We’re developing Answer Engine Strategies as the next part of the relaunch, with our first online event planned for Q4 2026.

The event will be completely free. We won’t sell you anything, and speakers won’t be pitching you anything either. No AEO or GEO add-ons. We won’t sell your data or pass your contact details to speakers or sponsors.

The goal is to share the best of what practitioners have learned through their work over the past few months. Whether you work alone, run an agency or lead a team, I want to hear what you’ve discovered and the strategies that came out of it.

The name comes from Search Engine Strategies, and that connection is important to me.

Danny Sullivan’s 1996 Webmaster’s Guide documented tests in which he changed web pages and tracked how search engines responded. Search Engine Watch grew out of that work. In 1999, Search Engine Strategies brought practitioners together to learn from each other.

A lot of people helped build that community. Danny’s legacy, for me, is the willingness to investigate a system that businesses depended on and make that knowledge useful to others. I want us to carry that forward.

Today, AI search can assemble an answer that helps someone compare their options before they visit a website. For a business, being visible and getting a visit are different outcomes. We need to understand both, and what either contributes to the business.

These changes affect where we put our time and money.

What should a team change?

Which recommendations have evidence behind them?

How will we know whether the work is helping?

I want Answer Engine Strategies to be a place where people bring something they’ve discovered through doing the work.

I’ll be looking for speakers with case studies that have something interesting to teach us. That could be a result they couldn’t initially explain, a test that challenged an assumption, or a decision that changed how they approached a project. I want to hear what they did, see the evidence and understand what they learned.

The programme will take shape around the strongest of those cases. Some may give us a strategy worth trying. Others may show where familiar advice breaks down, or raise a question that deserves more investigation.

That is the thinking behind the move from Search Engine Strategies to Answer Engine Strategies. “Answer” reflects the shift we need to understand. “Strategies” stays because that is what I want us to work on.