Corrections

Last updated: July 31, 2026

This page documents corrections made to OxalateWatch content. We maintain this log as part of our commitment to transparency and accuracy. For our correction policy, see our Editorial Policy.

2026 Corrections

July 31, 2026

Site-wide: Fixed canonical URL conflict where the server redirected non-www to www but all canonical tags pointed to apex. Corrected to consistent apex (oxalatewatch.com) across all pages.

Affected: 4,000+ pages. Reviewer: Editorial Team.

July 31, 2026

Compare pages: Fixed a template bug in the introductory paragraph where the higher-oxalate food was incorrectly described as the safer choice on some comparison pages (e.g., almonds vs almond butter). All 150 comparison pages regenerated with corrected logic.

Affected: 150 /compare/ pages. Reviewer: Editorial Team.

July 31, 2026

Crosstags & Specialty pages: Fixed unrendered template expressions and Markdown formatting marks appearing in visible page text. All 197 affected pages regenerated.

Affected: 87 /crosstags/ + 110 /specialty/ pages. Reviewer: Editorial Team.

July 24, 2026

Google Analytics: Fixed HTML-escaped GA4 tracking code (<script>) appearing as visible text on food pages. Unescaped across all page types to ensure proper script execution.

Affected: 5,000+ pages. Reviewer: Editorial Team.

July 23, 2026

Blog restructuring: Migrated blog from folder-based URLs (/blog/slug/index.html) to flat date-prefixed HTML files (/blog/YYYY-MM-DD-slug.html) for improved content management.

Affected: 74 blog posts. Reviewer: Editorial Team.

No Corrections Needed (Pre-Launch)

OxalateWatch launched in July 2026. The corrections above reflect our first wave of post-launch quality improvements. No data accuracy corrections have been required — all oxalate values remain as sourced from Harvard T.H. Chan SPH (2024) and USDA FoodData Central.

If you believe you have found an error on OxalateWatch, please contact cs@oxalatewatch.com with the page URL and a description of the issue. We respond to all correction requests within 5 business days.