Source identity
| Field | Recorded value |
|---|---|
| Source type | GitHub source |
| Original record | Janady13/thatstupidcomputer / private/standards/document-093.txt |
| Date | Not specified in source |
| Repository | Janady13/thatstupidcomputer |
| Revision | 57555cde46910102dd25d6c1c1fb2c359e9655bd |
| Branch | main |
| Path or archive member | private/standards/document-093.txt |
| Original SHA-256 | 105341f0f96da93653ab012f9ceaa02634965724ad23d4af61613ae310670073 |
| Git blob SHA | 15c70f7c847bda05150ddf2dfcf1c7f3540d0347 |
| Reading-copy SHA-256 | 105341f0f96da93653ab012f9ceaa02634965724ad23d4af61613ae310670073 |
Recovered source transcript
Download complete source text ↓69 lines · 5.2 KB
DOCUMENT 093 OF 135
Title: R10 public-content brief — What makes a page relevant to a customer question rather than merely keyword-rich?
Path: Publishing/Briefs/R10-search-relevance-ir.md
Group: briefs
Label: PUBLIC WORKBENCH · not approved
Review status: scope_stated_in_document
==============================================================================
# R10 public-content brief — What makes a page relevant to a customer question rather than merely keyword-rich?
**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R10. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work.
## Reader and purpose
A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **What makes a page relevant to a customer question rather than merely keyword-rich?**
**Distinct contribution:** A transparent relevance rubric and judged query examples, with evidence gaps and task completion instead of opaque SEO scores.
## Candidate search questions — hypotheses, not measured demand
- search intent page relevance audit
- information gain useful website content
- site search relevance evaluation
No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well.
## Proposed outline
1. Separate owned retrieval from Google
2. Judge actual questions
3. Identify missing information
4. Evaluate without claiming hidden weights
Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names.
## Evidence needed before making an expertise or results claim
- Query set with observed versus hypothesis labels
- Relevance rubric and judged examples
- Baseline/candidate failure analysis for owned retrieval
These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis.
## Proposed public route and internal relationships
Suggested route, pending canonical-host approval: `/expertise/search-relevance-ir/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy.
Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria.
## Conversion and measurement contract
Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval.
Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure.
## Publication gate
R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval.
No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes.
## Research references
- [D15 — Evaluation in information retrieval](https://nlp.stanford.edu/IR-book/html/htmledition/evaluation-in-information-retrieval-1.html): Relevance judgments and retrieval evaluation; not disclosure of a commercial engine ranking algorithm.
- [D20 — AI optimization guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide): Google AI Search retains core SEO foundations; no special llms.txt or schema requirement or ranking guarantee.
- [D21 — Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content): Original value, sources, authorship and first-hand expertise; not a points-based ranking formula.
==============================================================================