TariffWatch Changelog

A free HTS Code Lookup tool shipped as part of a portfolio-wide three-tool trio, followed by six more pages under the Day 23 SEO ship and a content pass that expanded the HTS lookup page to clear the word-count gate and fixed an EEAT unclaimed-review false positive.

This release also ships the page you're reading: a public status page at /tariffwatch/status backed by hourly uptime snapshots, and this changelog at /tariffwatch/changelog.

The HTS Code Lookup tool exists because HTS code confusion is the single most common blocker importers hit before they can even run TariffWatch's exposure checker meaningfully. Giving that lookup away for free, with no signup, removes the first real friction point in the funnel rather than gating it behind an email capture.

The August Gold SEO ship added comparison pages against two named incumbents (Gaia Dynamics, Descartes CustomsInfo) plus a glossary, part of ten pages shipped across the portfolio under Google Perfection Standard v2.

Comparison pages against Gaia Dynamics and Descartes CustomsInfo target the two incumbents importers researching Section 232 exposure tools actually search for by name, each citing the incumbent's own public pricing and feature claims rather than an assumed comparison. The same citation discipline applied to EntryProof's comparison pages the same day.

A solo-founder due-diligence pass wired up `/api/tariffwatch/health` so uptime monitoring has a real endpoint to check, and shipped JSON-LD structured data closing a P0 finding that TariffWatch was shipping zero schema markup.

Like the equivalent fix on EntryProof, wiring up a real health endpoint and shipping JSON-LD schema were both closing gaps that make a product look unfinished to anyone evaluating it seriously. This is particularly consequential for TariffWatch given how many of its visitors arrive during an active, deadline-driven search for help with a federal comment window rather than casual browsing.

A dual-exposure rate calculation bug in the BIS-14 exposure checker was found and fixed, alongside five more sample comment letters and a load-test script for the scan endpoint. A Playwright E2E harness shipped this day too, giving TariffWatch's highest-stakes flow (a legally-consequential comment letter) real regression coverage for the first time.

Ten more fixes closed out account-delete and submit-letter page titles, legal footers, dynamic og:image and twitter:card tags, checker warning copy, retry-after handling, PDF downloads, accessibility labels, the methodology page, and an HTS autocomplete datalist on the Exposure Checker, plus the same portfolio-wide security and observability hardening that shipped across all three picks this day.

The dual-exposure rate bug was the kind of defect that looks correct at a glance and is wrong in a way that specifically matters here: TariffWatch's whole value proposition is telling an importer an accurate exposure number, so a calculation bug in that number is closer to a product-integrity issue than a cosmetic one. The Playwright E2E harness that shipped the same day exists to catch exactly this class of bug before it reaches a real importer relying on the number to decide whether to file a comment.

The landing page picked up a countdown clock, an expanded FAQ, and a samples gallery of drafted comment letters, along with Edge Config-driven pivot copy and the first scaffolding for a regulations.gov one-click submit flow. A watermark on generated PDFs is now crypto-signed, and Federal Register notice content is cached rather than re-fetched on every request. The BIS-14 exposure-item count was also reconciled against the actual 14-item enumeration after a headline mismatch was found.

The regulations.gov one-click submit scaffolding shipped as scaffolding rather than a finished integration deliberately: the actual regulations.gov API document ID for this specific docket was not resolvable as of this release (confirmed via a live API check the same day), so the flow was built to be ready the moment that ID resolves rather than blocked on it. The BIS-14 reconciliation fix mattered because a headline that says 14 items while the actual enumeration only lists 13 undermines trust in every other number on the page.

TariffWatch's M1a build shipped at /tariffwatch: a landing page, a Section 232 exposure checker, an AI-assisted comment-letter drafter for the BIS aluminum/steel duties docket, and the `pick3` Supabase schema. Same-day fixes closed a PDF-attachment encoding bug in the Resend delivery path and built a missing comment-letter-drafter cron that had been spec'd but not implemented, a real gap during the BIS comment-window panic period.

An attack-audit pass the same day closed all P0/P1 findings for TariffWatch, and a follow-up fix stopped deleted-account rows from staying claimable by the comment-letter drafter indefinitely.

TariffWatch launched directly into a live, time-boxed federal comment window (BIS docket BIS-2026-0331, comments closing Aug 27, 2026), which shaped every other decision this release made: the comment-letter drafter shipped in the same build as the exposure checker rather than as a later add-on, because a checker that tells an importer they're exposed without a clear next step is only half the product during a window this short.