26 August 2026

  • Prevented analytics interactions from being queued before consent and made Do Not Track override both stored and newly accepted analytics preferences.
  • Kept visa-finder validation visible until every required answer is complete, and made printable worksheet results use a reliable light palette.
  • Reserved the full consent-banner footprint, including its fixed bottom inset, so page endings remain reachable at narrow and wide breakpoints.
  • Normalized stable primary page/application IDs, document language, and compact local-site membership across all canonical public routes.
  • Added fail-closed regression tests for consent, tools, responsive disclosures, printing, and primary structured-data identity.

25 August 2026

Mobile, accessibility and delivery hardening

  • Standardized safe-area-aware viewport, header, reading-rail, navigation, cookie-banner and footer spacing across the publication shell.
  • Consolidated the active responsive enhancements into one versioned stylesheet and one versioned script, removing duplicate page requests and preventing immutable-cache drift.
  • Added an accessible mobile section jump to eligible long-form pages while keeping home and interactive tools free of misplaced pre-heading navigation.
  • Restored native field validation and stale-result warnings in the currency, income and bank worksheets, and corrected checklist control sizing without shrinking tap targets.
  • Made editorial links visibly underlined, excluded consent copy from search snippets, and passed representative mobile Lighthouse accessibility, best-practices, SEO and agentic-browsing audits.

24 August 2026

Search, delivery and task-intent hardening

  • Reconciled the reviewed public inventory, sitemap, feeds, structured dates and visible breadcrumbs so discovery files describe the same canonical pages readers see.
  • Excluded the duplicate Pages project hostname from indexing, tightened retired API responses, removed a consent-premature analytics connection, and protected the public inbox from Cloudflare rewriting.
  • Added focused official-source guidance for changed-passport TM47 reports, family guardian routes, Jomtien passport and address-evidence questions, and e-WorkPermit problem reporting.
  • Corrected a broken Chonburi Immigration hostname and redirected the retired family-planning route to its maintained intent owner.
  • Added fail-closed release checks for feed-date, breadcrumb, email-protection, duplicate-host, social-image-alt, security-disclosure and error-page regressions.

10 August 2026

Premium publication rebuild

  • Introduced the shared premium responsive shell, restrained visual system, accessible mobile navigation, and Tim-and-Paemi publication portrait treatment.
  • Rebuilt the home, visa, Pattaya, tools, blog, About, methodology, contact, FAQ, privacy, terms, and EN/DE/RU entry surfaces around shorter decision-first copy.
  • Removed unsupported consultation, response-time, approval, client, review, partner, and service claims from the public corpus.
  • Aligned publisher and authorship markup to TP-NETWORK-2026-08-04.1: compact publisher reference only, no inferred page authorship, no reciprocal network links.
  • Replaced invalid locale alternates with a reciprocal EN/DE/RU root set and aligned structured language signals.
  • Retired lead and subscription collection endpoints; contact is publication email only and asks readers not to send sensitive records.
  • Made scheduled quality checks read-only. Automated publishing, manufactured sitemap dates, automatic IndexNow submissions, and legacy network generators now fail closed.
  • Added deterministic network, schema, route, asset, fragment, and accessibility gates before release.

24 July - 1 August 2026

Official-source safety refresh

Decision-critical visa, tax, residence, insurance, work, and document claims were rechecked against responsible Thai authorities and missions. Unsupported universal fees, timelines, rankings, approval expectations, and commercial advice were removed or narrowed to the source that supported them.

How changes qualify

A material entry records a change that can affect a reader's decision, the publication's accountability, structured data, privacy, or release safety. Minor typography and routine maintenance are not inflated into freshness claims.

See the editorial methodology or submit a sourced correction through contact.