OnlyDetect's September 2026 research identified several distinct public search tasks: finding a known creator, browsing by interest or location, comparing free offers, and evaluating a directory. The findings informed which guides to build. They do not demonstrate that OnlyDetect ranks for those queries or that publishing more pages will produce a particular amount of traffic.
The research record is a dated baseline. Its value is in making the questions and measurement limits explicit before drawing conclusions.
What the baseline contains
The saved research brief covers United States English-language queries and records estimates obtained through the OnlyDetect OpenSEO project. The underlying brief was dated September 27, 2026.
Selected estimates recorded in that brief were:
Scroll across the table on smaller screens.
| Query | Estimated monthly searches in the saved US snapshot |
|---|---|
| free onlyfans | 49,500 |
| onlyfans finder | 27,100 |
| onlyfans search engine | 2,900 |
| onlyfans free trials | 1,900 |
| onlyfans user search | 1,600 |
| onlyfans search by location | 1,600 |
| how to find small onlyfans creators | 110 |
These are third-party estimates, not OnlyFans internal search totals, audited demand, or visits to OnlyDetect. Closely related queries can overlap in intent, so adding the rows would not produce a defensible count of unique prospective readers. The project link may require account access.
What we learned from the query differences
A handle lookup and a general browsing query need different answers. The first benefits from exact spelling, official-link checks, and guidance for changed names. The second benefits from useful filters, transparent missing data, and comparisons of current offers.
A free-trial query also should not be treated as identical to a free-account query. The reader needs to understand duration and offer terms, not just an entry-price label.
Those differences support distinct guides with related links. They do not justify publishing many pages that repeat the same answer with a slightly altered keyword.
What this research does not measure
The snapshot does not establish:
- How many searchers will visit OnlyDetect.
- Which people will open a creator profile or follow an outbound link.
- Whether a creator's paid subscription is good value.
- The total number of active creators on the platform.
- Whether another directory's claimed database count is accurate.
- Which pages will be cited by an AI search service.
Those outcomes require different evidence. Search-query estimates cannot substitute for platform records, verified subscription experience, or actual site analytics.
A useful directory research agenda
Future studies should answer specific questions readers can use. Examples include the distribution of observed public subscription prices, how often sampled offers change, and how clearly public biographies explain included access.
A defensible study needs a stated population, collection date, inclusion rules, and treatment of missing values. If a price is absent, the dataset should not quietly convert it to zero. If the sample contains only recently refreshed accounts, the report should not describe it as the entire platform.
OnlyDetect's data methodology explains how public observations and eligibility are separated. That distinction should carry through to every chart and headline.
How we would compare future results
Keep a before-and-after record of the same measurement. For search performance, compare like periods and note changes to publication, indexing, and tracking. For data quality, rerun a defined sample and count unresolved records as well as successful checks.
If a guide gains visitors but produces no useful next step, revisit the match between its promise and its content. If a useful page is not being crawled, more prose alone will not solve that problem. A baseline helps identify which explanation the evidence actually supports.
Use the research at the right level
For a purchase decision, use current creator information rather than this demand table. For evaluating a directory, use the comparison scorecard. For OnlyDetect's standards, read the editorial policy.
This baseline will need a new dated measurement before its estimates can be described as current in a later period. Keeping the original snapshot visible makes changes easier to assess without rewriting history.