Historical verification of the initial English cohort. The latest multilingual implementation and receipts are documented in
blog-multilingual-verification.md.
Date: 2026-10-09. Repository baseline: 37aed62fa278a6149df2ee937cc4bf13edd969a4 (jerry/web-ui). Read-only remote HEAD matched before implementation. No commit, push, deployment, Search Console submission or backend mutation is included.
The approved first cohort is three English guides, in this order:
/blogs/netherlands-visa-appointments-dublin/blogs/greece-visa-appointments-dublin/blogs/denmark-visa-appointments-dublinEach guide includes its official booking route, preparation and availability guidance rather than splitting out thin checklist/no-slots articles. Independent factual review passed on 2026-10-09 after correcting three minor wording points. The Netherlands self-booking/avoid-intermediary warning remains prominent before commercial CTAs. Greece distinguishes Embassy-linked categories and confirmation; Denmark avoids a fixed processing-time promise where official pages differ. The product is accurately described as optional independent automatic booking, with no official affiliation or guaranteed visa. Existing service/refund policies were not rewritten.
Active content SHA-256: c83febff4928cc8e8e9861f9ea28de5b4d5a3d202e8c77f9752d9b0720c0d720. The integrated JSON is identical to the final reviewed author handoff except for the explicitly approved published:true local-eligibility flags. No article translations are integrated. The old Italy drafts are excluded from the active collection and retained only in the archive alongside this document.
published:true is renderer eligibility, not evidence of public publication. BLOG_INDEXING_ENABLED is a separate build-time gate, defaulting to false. A default build renders review pages with noindex and an empty sitemap; noindex is not access control. Setting the flag true requires a rebuild and separate deployment authorization before any public release.
node scripts/check-blog.mjs: PASS. Actual inventory/schema/source/internal-link checks and in-memory publication/translation/sitemap fixtures. Fixtures do not publish synthetic pages or modify editorial records.BLOG_INDEXING_ENABLED=true node scripts/check-blog.mjs --release: PASS. Exactly the approved three English records; obsolete 18-page expectation removed.BLOG_INDEXING_ENABLED=true, NEXT_PUBLIC_API_URL=http://127.0.0.1:9, and NEXT_TELEMETRY_DISABLED=1: PASS. Existing Next build skips ESLint, so this is not a lint pass.node_modules/.bin/tsc --noEmit: PASS.--no-eslintrc, TypeScript parser/plugin, unused-variable and no-explicit-any rules) over the new blog/SEO TypeScript: PASS.scripts/check-blog-http.mjs: PASS. Four server-rendered English pages; title/description/lang/canonical/OG/Article/Breadcrumb/source checks; exactly four sitemap URLs; 13 unknown/excluded routes including archived Italy and absent translations return 404; query canonical stays clean; ten pre-existing route GET renders and private noindex headers pass. These GET checks are not authenticated workflow or payment end-to-end tests.BLOG_INDEXING_ENABLED=false, with all four preview pages noindex and an empty sitemap.git diff --check: PASS before final packaging; rerun after any later edit.npm run lint is blocked by the repository's existing missing eslint-config-next while .eslintrc.json extends next/core-web-vitals. Dependency scope was preserved; focused lint is not a substitute for a full lint pass.process_singleton_posix.cc socket creation returned Operation not permitted. One approved escalated retry encountered the same restriction. No screenshots, visual approval, keyboard/navigation pass, or browser layout claim is made. The optional browser test script is retained for an environment where Chromium can launch.Resolve full-lint tooling and complete visual/interactive QA. Obtain explicit approval of the current version and publication action. Run the release gate, rebuild with the indexing flag true, verify the exact candidate URL/sitemap set, then verify the authorized deployed version separately. Do not treat local eligibility, a successful build or this document as deployment permission.