The searches are practical and specific because the shopper has nobody to ask. Water-based against silicone lubricant, how to tell whether silicone is body safe, which ingredients commonly irritate, how loud a motor is, how to clean and store something properly, what a waterproof rating covers. Those are the pages that bring people in, and each one needs to be complete on its own terms rather than a paragraph leading to a grid. Category and product pages then reuse the same vocabulary so a reader who arrives on a guide can move to the catalog without relearning anything.
The second layer is compatibility. Material against lubricant base, device against cleaner, condom material against oil, storage against other materials. That table is genuinely useful, rarely published well, and it earns links from communities and educators who need somewhere to point. It is also the content most likely to be quoted by an assistant, because it answers a question with a fact rather than a recommendation.
Technically the two risks are the age gate and the specification. A verification step that returns nothing to a crawler removes the library from the index, so it belongs on purchase paths rather than site-wide, implemented without a redirect. Specifications belong in HTML tables with real numbers, not inside a downloadable sheet or an image, because material, dimensions, decibels and rating are exactly the values both shoppers and search engines are looking for.