Trust governance - 2 July 2026
P0 Reviewed Page Refresh 2026
Public publication gates for refreshing P0 Visa Atlas YMYL pages after reviewer handoff evidence, with source-freshness, content-diff and reviewedBy schema checks blocked by default.
This is a page refresh control surface. It does not claim that a credentialed reviewer has already approved these pages. Page changes and reviewedBy schema publication stay blocked until the acquisition handoff, reviewedBy evidence row, source-freshness recheck and final schema review are complete.
3
P0 refresh targets
3
Blocked pending reviewer handoff
0
Ready for publication claimed
0
ReviewedBy schema allowed
Page refresh publication gates
Targets are generated from P0 rows in the expert reviewer entity program. The feed defines when reviewed page refreshes remain blocked and which local evidence fields must exist before publication; it does not publish reviewer notes or claim completed reviews.
A P0 page refresh can move to publication only after acquisition handoff evidence, reviewedBy evidence, source freshness recheck, legal-advice boundary confirmation, content hash diff capture and final schema-fragment review are all recorded locally.
- This feed is a page-refresh control surface, not a claim that any P0 page has already been reviewed or republished by a credentialed reviewer.
- Reviewer notes, private comments, draft content diffs, contacts, engagement terms and rejected evidence stay local.
- A refreshed page must remain informational and must not become individual legal advice.
- Reviewed page refresh controls support trust governance, but they do not guarantee rankings, traffic, citations, AI visibility or market share.
- Public reviewedBy schema remains blocked until the separate reviewedBy schema rollout and final page-level schema review both pass.
Local refresh evidence workflow
Reviewer notes, contacts, engagement terms, draft diffs, rejected evidence, raw legal comments and private quality-review notes stay local. Public rows expose page targets, required fields and blocked publication gates only.
npm run seo:p0-page-refresh -- p0-reviewed-page-refresh-log.jsonl --jsonPost-review page update policy
Each target row repeats the applicable publication policy so page-specific handoffs remain auditable from the rendered report as well as the JSON feed.
- Do not edit or publish a P0 reviewer disclosure block until the matching acquisition handoff and reviewedBy evidence rows are complete.
- Recheck source freshness for every affected source-backed claim before copying a reviewed content diff into a public page.
- Record pre-review and post-review content hashes so page changes can be audited without publishing private reviewer notes.
- Keep the normal Visa Atlas legal-advice boundary visible on every refreshed page.
- Run final reviewedBy schema fragment review separately before any JSON-LD change is copied into a public template.
P0 reviewed page refresh queue
p0 - legal-eligibility
UK Skilled Worker eligibility, salary and total-cost review
A local reviewed-page refresh row is ready-for-publication, cites a handoff-ready acquisition row, cites an approved reviewedBy evidence row and passes source-freshness plus schema-fragment review.
uk-skilled-worker-yml-review / uk-regulated-reviewer-slot
blocked-pending-handoff
Target pages
Prerequisite controls
- High-risk page review acquisition - sourcing-required
/api/public/high-risk-page-review-acquisition - reviewedBy schema rollout - blocked-pending-evidence
/api/public/reviewedby-schema-rollout - Expert reviewer entity program - credential-evidence-required
/api/public/expert-reviewer-entities
Required local fields
- evidenceRowId
- queueId
- reviewerEntityId
- reviewerName
- reviewerEvidenceHandoffId
- reviewedByEvidenceRowId
- pageUrl
- preReviewContentHash
- postReviewContentHash
- changedSections
- reviewScope
- sourceFreshnessRecheckedAt
- legalAdviceBoundaryConfirmed
- schemaFragmentReviewed
- readyForPublication
- reviewedAt
- reviewedBy
Review scope
- eligibility wording
- salary threshold interpretation
- advisor/legal-advice boundary
- fee and IHS caveats
Source datasets
Page update policy
- Do not edit or publish a P0 reviewer disclosure block until the matching acquisition handoff and reviewedBy evidence rows are complete.
- Recheck source freshness for every affected source-backed claim before copying a reviewed content diff into a public page.
- Record pre-review and post-review content hashes so page changes can be audited without publishing private reviewer notes.
- Keep the normal Visa Atlas legal-advice boundary visible on every refreshed page.
- Run final reviewedBy schema fragment review separately before any JSON-LD change is copied into a public template.
Blocked pending reviewer handoff
- A named reviewer handoff exists from the acquisition workflow.
- The reviewedBy evidence log has a separate row for the same queue, reviewer entity and reviewed page URL.
- Pre-review and post-review content hashes are recorded locally.
- Changed sections, review scope, source freshness recheck date and legal-advice boundary confirmation are present.
- The reviewedBy schema fragment has been reviewed separately before publication.
Local commands
npm run seo:p0-page-refresh -- p0-reviewed-page-refresh-log.jsonl --jsonnpm run seo:review-acquisition -- reviewer-acquisition-log.jsonl --jsonnpm run export:reviewedby-schema -- reviewer-evidence-log.jsonl
- High-risk page review acquisition - sourcing-required
p0 - calculator-verdict
Canada Express Entry CRS, category and draw-history review
A local reviewed-page refresh row is ready-for-publication, cites a handoff-ready acquisition row, cites an approved reviewedBy evidence row and passes source-freshness plus schema-fragment review.
canada-express-entry-yml-review / ca-regulated-reviewer-slot
blocked-pending-handoff
Target pages
Prerequisite controls
- High-risk page review acquisition - sourcing-required
/api/public/high-risk-page-review-acquisition - reviewedBy schema rollout - blocked-pending-evidence
/api/public/reviewedby-schema-rollout - Expert reviewer entity program - credential-evidence-required
/api/public/expert-reviewer-entities
Required local fields
- evidenceRowId
- queueId
- reviewerEntityId
- reviewerName
- reviewerEvidenceHandoffId
- reviewedByEvidenceRowId
- pageUrl
- preReviewContentHash
- postReviewContentHash
- changedSections
- reviewScope
- sourceFreshnessRecheckedAt
- legalAdviceBoundaryConfirmed
- schemaFragmentReviewed
- readyForPublication
- reviewedAt
- reviewedBy
Review scope
- CRS calculator context
- category draw interpretation
- proof-of-funds caveats
- source freshness
Source datasets
Page update policy
- Do not edit or publish a P0 reviewer disclosure block until the matching acquisition handoff and reviewedBy evidence rows are complete.
- Recheck source freshness for every affected source-backed claim before copying a reviewed content diff into a public page.
- Record pre-review and post-review content hashes so page changes can be audited without publishing private reviewer notes.
- Keep the normal Visa Atlas legal-advice boundary visible on every refreshed page.
- Run final reviewedBy schema fragment review separately before any JSON-LD change is copied into a public template.
Blocked pending reviewer handoff
- A named reviewer handoff exists from the acquisition workflow.
- The reviewedBy evidence log has a separate row for the same queue, reviewer entity and reviewed page URL.
- Pre-review and post-review content hashes are recorded locally.
- Changed sections, review scope, source freshness recheck date and legal-advice boundary confirmation are present.
- The reviewedBy schema fragment has been reviewed separately before publication.
Local commands
npm run seo:p0-page-refresh -- p0-reviewed-page-refresh-log.jsonl --jsonnpm run seo:review-acquisition -- reviewer-acquisition-log.jsonl --jsonnpm run export:reviewedby-schema -- reviewer-evidence-log.jsonl
- High-risk page review acquisition - sourcing-required
p0 - regulated-profession
Germany Blue Card, Chancenkarte and recognition decision-tree review
A local reviewed-page refresh row is ready-for-publication, cites a handoff-ready acquisition row, cites an approved reviewedBy evidence row and passes source-freshness plus schema-fragment review.
germany-recognition-yml-review / de-regulated-reviewer-slot
blocked-pending-handoff
Target pages
Prerequisite controls
- High-risk page review acquisition - sourcing-required
/api/public/high-risk-page-review-acquisition - reviewedBy schema rollout - blocked-pending-evidence
/api/public/reviewedby-schema-rollout - Expert reviewer entity program - credential-evidence-required
/api/public/expert-reviewer-entities
Required local fields
- evidenceRowId
- queueId
- reviewerEntityId
- reviewerName
- reviewerEvidenceHandoffId
- reviewedByEvidenceRowId
- pageUrl
- preReviewContentHash
- postReviewContentHash
- changedSections
- reviewScope
- sourceFreshnessRecheckedAt
- legalAdviceBoundaryConfirmed
- schemaFragmentReviewed
- readyForPublication
- reviewedAt
- reviewedBy
Review scope
- degree recognition wording
- salary-threshold caveats
- decision-tree branch labels
- regulated-profession disclaimers
Source datasets
Page update policy
- Do not edit or publish a P0 reviewer disclosure block until the matching acquisition handoff and reviewedBy evidence rows are complete.
- Recheck source freshness for every affected source-backed claim before copying a reviewed content diff into a public page.
- Record pre-review and post-review content hashes so page changes can be audited without publishing private reviewer notes.
- Keep the normal Visa Atlas legal-advice boundary visible on every refreshed page.
- Run final reviewedBy schema fragment review separately before any JSON-LD change is copied into a public template.
Blocked pending reviewer handoff
- A named reviewer handoff exists from the acquisition workflow.
- The reviewedBy evidence log has a separate row for the same queue, reviewer entity and reviewed page URL.
- Pre-review and post-review content hashes are recorded locally.
- Changed sections, review scope, source freshness recheck date and legal-advice boundary confirmation are present.
- The reviewedBy schema fragment has been reviewed separately before publication.
Local commands
npm run seo:p0-page-refresh -- p0-reviewed-page-refresh-log.jsonl --jsonnpm run seo:review-acquisition -- reviewer-acquisition-log.jsonl --jsonnpm run export:reviewedby-schema -- reviewer-evidence-log.jsonl
- High-risk page review acquisition - sourcing-required
Cite or reuse this dataset
This reviewed page refresh control dataset is free to reuse under CC BY 4.0. Cite the JSON endpoint for publication gates and local evidence requirements, not as evidence that page reviews are already complete.
Suggested citation
Visa Atlas, "Visa Atlas P0 reviewed page refresh controls", https://visaatlas.org/research/p0-reviewed-page-refresh-2026. Last verified 2 July 2026.
Primary sources (17)
- /api/public/p0-reviewed-page-refresh
- /research/p0-reviewed-page-refresh-2026
- /api/public/high-risk-page-review-acquisition
- /research/high-risk-page-review-acquisition-2026
- /api/public/reviewedby-schema-rollout
- /research/reviewedby-schema-rollout-2026
- /api/public/expert-reviewer-entities
- /research/expert-reviewer-entity-program-2026
- /api/public/source-transparency-benchmark
- /api/public/visibility-metrics
- /api/public/visas
- /api/public/salary-thresholds
- /api/public/fees
- /api/public/cost-to-complete
- /api/public/express-entry-draws
- /api/public/express-entry-categories
- /api/public/calculator-verdict-contexts