What this page adds

• It explains why Starter/Open records remain accessible for learning and review while thin versions are kept out of search indexes.
• It reduces repeated caution cards across Wiki and timeline surfaces by giving one richer explanation of the open status.
• It helps readers use unfinished source leads responsibly without treating them as final articles.

Open does not mean settled

An Open page can name a question, gather source leads, preserve a correction need, or point to a place hub. It should not be treated as settled public proof until the exact claim has public, reviewable evidence and support limits.

When an Open page should stay noindex

• The page is under roughly 850 to 900 words and mostly functions as a stub, row, register, or workflow note.
• The page is a fact-check, field note, register, threshold, residual-risk, exception-queue, release-criteria, or evidence-lane surface that is useful but not a strong public guide yet.
• The page is a tag, category, filter, search, paginated, or author archive with little original explanatory content.

How a page moves from Open to Supported

1. Write the exact claim in one sentence.
2. Name public, reviewable sources that support that exact wording.
3. List what the sources do not support.
4. Check privacy, living-person risk, sensitive identity wording, and community impact.
5. Record the decision: keep open, narrow, correct, hold, or support with sources.

Public value test

An Open page can become indexable only when it gives a reader enough original value to justify a public route. That value can be a source comparison, a method explanation, a place-based guide, a correction history, a rights-aware visual ledger, or a clear claim-review outcome. A page that only repeats a label, stores an internal queue, or points to future work should stay accessible but noindex.

Before indexing an Open page

• Expand the page beyond a short row or register into a reader-facing explanation.
• Add source links, source-type labels, and what the sources do not support.
• Add links to Research Method, Source Review, Evidence Gates, Safe Sharing, Corrections, and Contact where relevant.
• Remove draft-like language, placeholder language, internal-only wording, and unsupported identity conclusions.
• Confirm that sitemap, canonical, noindex, robots, and live route checks agree.

This lets the site preserve unfinished research without presenting unfinished research as the site’s public value. It also gives future editors a clear way to improve pages: add source discipline and reader usefulness, or keep the page out of search until it is ready.

Low-depth value guardrail

The safest site posture is not to delete every unfinished item. The safer posture is to preserve useful leads, noindex thin ones, remove them from sitemap, and build stronger guides that explain how to use them. That way readers can still learn from the research process without search engines treating every open row as a finished article.

For AdSense readiness, this distinction matters. A site with many indexable stubs can look shallow even when the underlying research is serious. A site with strong hubs, clear noindex rules, and useful reader-facing guides gives reviewers a clearer reason to trust the public surface.

That means Open is not a weakness when it is governed. It becomes a weakness only when open rows are indexed as if they were complete public articles.

Public proof rule: Do not expose private family, genetic, lineage, oral-history, or unpublished evidence as public proof.