Why research on a project of our own
Applied research is usually done on client projects, and there is a structural problem there: the scope is agreed in advance and the time is limited by a budget. You can measure before and after, but you cannot change course halfway through just because an observation justifies it. Every decision has to be justified to someone else, and many interesting questions stay out of the contract simply because nobody asked for them.
Working on a project of our own removes those restrictions. You can observe the full cycle —decision, implementation and effect— without negotiating every step. If a hypothesis requires changing the category architecture, rewriting a product page or changing how the structured data is declared, it is done and documented. If the result contradicts what we expected, that is documented too, and that contradiction is useful information instead of a problem to be hidden.
There is an additional reason, a less comfortable one. It is easy to repeat what the industry says about how search engines and AI systems behave. When the work is done on third-party data, you never quite know which part of the explanation is observation and which part is someone else's interpretation. An environment of your own forces you to distinguish between what was measured and what is assumed.
The advantage of a project of our own is not having more freedom to do things: it is being able to hold a claim to the end and know what evidence supports it.