MisMatchMaker product and data changelog

The guide library now covers mandatory hotel fee disclosure under the U.S. FTC rule and California laws, the Digital Markets Act parity rules for Booking.com in the EEA, and the European Accessibility Act's potential scope for hotel booking websites and apps.

Each guide is bounded to its reviewed sources and states key exemptions or territory limits. Related fee, commercial, and accessibility-field pages now point readers to the dedicated legal explanations instead of repeating them.

The content library now covers three operator jobs that were previously difficult to answer in one place: checking a Tripadvisor hotel page, locating fields in HRS's Hotel Service Portal, and reconciling when an OTA collects from the guest with when the property receives or records funds.

Each page is bounded to what its cited primary material establishes. Tripadvisor and HRS pages are not presented as scanner-supported channels, and payment timings are described by the named payment model rather than generalized to every account or reservation.

The analytics bootstrap now queues commands in the form the Google tag processes. Analytics remains behind the existing consent choice, and the event contract continues to omit hotel names, listing URLs, and scan content.

The change was covered with checks for the queued command shape and consent path. The privacy page remains the place to read the data and consent details.

A content-gap release added focused operator guides, new calculator workflows, an audit-template directory, and a single anchored distribution glossary. The glossary links each platform-specific term to the documentation that publishes it, while keeping general vocabulary separate from cited platform definitions.

A glossary anchor-navigation issue was also fixed so a link to a defined term opens at that term, including when the link comes from another page.

The Amsterdam city study was published with its own sample description and source coverage. During review, a comparison case was corrected: text that says no fee amount should not be counted as disagreeing with a stated amount solely because the other listing includes a number. The corrected rule treats an absent amount as incomplete comparison evidence for that amount, rather than a measured conflict.

The current Amsterdam aggregation applies that correction. The earlier London snapshot predates it and cannot be fully recomputed from the evidence retained for that run, so the study pages disclose the method difference instead of implying direct comparability. Readers should use the limitation on each study page when comparing city figures.

The study programme now has a central page for its selection rules and limitations, with a separate route for each city record. The London page reports the first completed city run; the Amsterdam pilot remains a separate record with its own indexability determined by the publishable sample threshold.

Breadcrumbs, hub listings, and related links are derived from the same content registry, keeping each city page connected to the programme that explains its method.

A dedicated accessibility reference maps the detail a guest needs to the public fields documented by each reviewed platform. It distinguishes property-level access from room-level features and states where a platform exposes no comparable field in the sources reviewed.

The reference was built from platform documentation and accessibility standards, with source scope and the reader's need to verify the actual room kept visible.

The directory connects a public hotel brand to the partner portal or content owner that can change its listing. It also identifies where platforms do not publish a menu path, avoiding invented instructions for sign-in-gated systems.

Detailed pages were added for the portals with enough public evidence to document field locations and verification steps.