Requests reaching the index
Retrieval observation is separate from the controlled tests above. Our observation window is activity reaching Optimly’s index, not private conversations or the full market.
Current crawl-health analytics group requests by response status and user-agent labels. User-agent labels indicate a claimed client identity, not verified buyer intent. Worker origin fetches are excluded to avoid counting that internal hop as another client request; this is not a count of unique buyers or a general retry-deduplication method.
A page fetch alone does not reveal a buyer question. In a scoped review, we distinguish explicit ask-like information from inferred intent, including identifiable asks that remain unresolved or return 404/410. An HTTP 200 alone does not establish that a need was answered.
Any request analysis should state its source, date window, attribution confidence and counting method. We compare relevant BrandVault facts and their date with the available evidence, identify unknowns and consider plausible fit or mismatch. There is no standardized demand or buyer-fit score in the model-test report.
Updating BrandVault can change the context for an interpretation. It does not change historical requests or prove new demand. Explore the brand workflow.