Current release scope

This release includes 554 public HTML pages in the XML sitemap: topic hubs, a sample-type hub, a searchable guide library, source-aware lab-test education pages, crawler resources, structured data, an AI citation file, a trust index, a citation policy index, a review and freshness index, a specimen index, a glossary index, a FAQ index, a human-readable FAQ library, a short-answer index, a human-readable answer library, an updates feed, a human-readable source library, and trust pages covering editorial standards, medical boundaries, privacy, review status, accessibility, corrections, contact status, and monetization disclosure.

What is ready to index

  • Core blood-test, STI testing, genetics, microbiome, and emerging biometrics hubs.
  • General lab-test safety guides, including result interpretation, abnormal result next steps, cost, privacy, accuracy, and test-label explainers.
  • Public guide pages include generated related-guide links that connect adjacent testing questions, source context, and topic clusters.
  • Public guide MedicalWebPage schema includes machine-readable source citations that match each guide's visible source list.
  • Public guide headings include stable section anchors, and guide schema exposes section fragment URLs for more precise citation.
  • Site-level trust boundaries and policy pages are summarized in trust-index.json for machine-readable citation and crawler discovery.
  • Citation rules, preferred citation targets, non-targets, and AI citation boundaries are summarized in citation-index.json.
  • Public page freshness and review-boundary metadata is collected in review-index.json, including the explicit boundary that Lab Intel does not claim independent clinician review.
  • Public guides are grouped by specimen, sample, collection method, or consumer biometric signal in specimen-index.json and the sample type hub.
  • The public lab test glossary now exposes stable term anchors and a glossary-index.json file for machine-readable definitions.
  • Published FAQPage schema is collected into faq-index.json and a searchable FAQ library.
  • Stable trust pages that define source standards, medical caveats, review boundaries, current privacy posture, and future monetization rules.
  • Machine-readable discovery surfaces including sitemap.xml, llms.txt, guide-index.json, trust-index.json, citation-index.json, review-index.json, specimen-index.json, glossary-index.json, faq-index.json, answer-index.json, source-index.json, feed.xml, robots.txt, and OpenSearch.

What is intentionally deferred

The narrow "STI testing after semen..." long-tail cluster is intentionally outside the public sitemap and AI citation file for this release. Drafts are retained internally for a future quality sprint, but the public release favors trust, discoverability, broad coverage, and clear medical boundaries over publishing every possible exposure variant before indexing begins.

Known early-release limits

  • No public correction inbox or contact form is live yet.
  • No personal lab-result interpretation, symptom triage, or private health intake is offered.
  • No independent clinician review is currently claimed; pages use Lab Intel editorial review boundaries.
  • No formal third-party accessibility audit has been completed yet.
  • No ads, affiliate links, sponsorships, paid rankings, or lead-generation forms are currently active.

Release quality gates

Before public changes are deployed, Lab Intel should keep checking production-domain canonical URLs, sitemap and file alignment, required metadata, JSON-LD parsing, internal links, XML validity, live page rendering, response security headers, and absence of old deployment domains in crawler-facing files. The repository includes a release-check script that runs these local quality gates before publishing.

Next expansion priorities

Future work should add a working correction/contact path, continue source-backed guide expansion, improve medical-review labeling if qualified reviewers are added, strengthen accessibility testing, and only then consider carefully disclosed monetization paths.