Discovery Context
Discovery Context
A project should explain what it does and who it helps. Our Discovery Context labels describe how much readers can learn from its public pages at the time we write a Project Note.
Discovery Context is recorded through the Project Note Process after its supporting public information is checked.
Context standards
What "Useful Context" means
A context label such as Useful Context means ProjectRadar found enough public information for readers to understand the project and decide whether to explore it. It does not mean the project has been certified, expertly audited, ranked by users, or guaranteed to perform well.
Context labels
What each label means
Clear Context
Readers can clearly tell what the project does, who it may help, and where to learn more.
Useful Context
The public pages explain what the project offers and who it is for. Some details are missing, but readers have enough information to decide whether to explore it.
Developing Context
The public pages explain part of the idea, but readers still need a clearer description, more detail, or information about who is behind it.
Early Context
The public pages leave important questions about who the project is for or how ready it is to use.
Limited Context
There is not enough clear public information yet for readers to understand the project, its audience, or its current status.
What we look at
Questions we ask about a project
We ask different questions about a mobile app, game, calculator, SaaS tool, browser extension, or content site. The assessment is limited to the public information available for that project.
Clarity
Can visitors quickly understand what the project does?
Usefulness
What problem does it help someone solve?
Audience
Is it obvious who the project is for?
Readiness
What do its public pages tell us about whether it is usable and maintained?
Policies and contact details
Can readers find relevant policies, pricing, contact details, and information about who runs the project?
Design and UX
Is the experience easy to navigate and understand?
Discoverability
Are titles, descriptions, structure, metadata, and content helpful for search and sharing?
About the project
Can readers understand why the project exists and its current status?
What the guide is
The label describes how clearly the project explains itself when the note is published. Readers can use it as a quick reference; builders can see which details need more explanation.
What the guide is not
It is not a category-position promise, endorsement, safety certification, expert audit, user rating, paid placement, analytics report, or guarantee of success, traffic, search visibility, revenue, quality, or customer outcomes.
Boundaries
What readers and founders should know
- It is not a user rating.
- It is not a certification.
- It is not a guarantee of success, traffic, search visibility, revenue, safety, or quality.
- It is not paid placement.
- It is not a promise that a project is right for every reader.
- Context labels can change if a project improves or new public information becomes available.
Improving context
Help readers understand your project
Explain what the project does and who it helps. Show its current status and pricing, make pages easy to find, include relevant policies and contact details, and keep the information up to date.
Common questions
Short answers for readers and founders
How is Discovery Context assigned?
A label is recorded through the Project Note Process after its supporting public information is checked. Tools may help organize that information. The label describes available context, not a rating or safety certification.
Is Discovery Context paid placement?
No. Founders cannot purchase a stronger context label, a better category position, or a more favorable writeup.
Does stronger Discovery Context guarantee results?
No. Discovery Context does not guarantee search visibility, traffic, revenue, safety, quality, or success. It summarizes what readers could learn from public information when the note was written.