Compare the same offer, not just a number
When reviewing a hotel price seen on Google, fix the identity of the offer first: property, dates, room, party and conditions. One correct-looking amount does not establish consistency across the booking journey. A practical starting point for a small property is to compare the offer the traveller saw with the offer presented on the next page. Do this before deciding to reduce prices or increase advertising spend. This framework helps identify a visible discrepancy; it does not promise better conversion or describe a particular product’s capabilities.
Current policy context and its limits
Google requires matching total prices and preservation of selected stay details. We checked the two linked policies on 8 October 2026; this is an impact analysis, not an announcement of a new release. Our suggested offer card, review order and ownership process are editorial recommendations. They are not evidence that any account is compliant, that visibility has improved, or that Stayax automatically fixes a discrepancy. Do not report a problem as resolved without checking it again, because the offer’s dates or conditions may have changed between observations.
Create one sample offer card
Choose a fictional offer and record the observation date, time and language. Add the property name, arrival and departure dates, party size, room name, currency and stated conditions. This is a small reproducible working card, not an industry-standard form. Without these fields, two amounts may refer to different products. Keep real guest information and private commercial terms out of public working documents. Invented training details are enough. If you need a visual record, use a test view without personal information and highlight only the relevant difference.
Locate the first change in a fictional journey
Imagine an offer showing a total of 240 units for two nights. If the next page shows 260 units, first check whether the room and conditions stayed the same. A changed room calls for reviewing room selection; changed dates call for reviewing the date step. If those fields match, examine how the amount is presented. These figures are not a real property’s price, tax or commercial agreement. Describe the first changed field and pass a small reproducible example to the responsible person instead of demanding a redesign of the entire journey.
Keep comparison conditions consistent
For the second review, record device, language and sign-in state. Recording these conditions does not mean every variation is an error. It tells colleagues what you observed and under which circumstances. Someone reviewing another date, party size or room has not repeated the same test. If the original selection cannot be reproduced, say so; do not quietly substitute a different offer and call it a match. If an external page prevents completion, record that obstacle separately. Missing evidence is not a successful check.
Assign an owner and repeat the check
Give each finding an owner, a concise description and a retest time. “The room name changes at the second step” is more actionable than “booking is poor.” After a proposed correction, repeat the journey with the same offer card and compare the beginning with the end. Check whether the correction also changed another field. The closing note should explain what changed and the conditions of the retest. Another team member should be able to reproduce it. This operational review is not a security assessment or formal platform compliance certification.
Start with a small recurring sample
Initially select a few different offers and use the same fields for each. Keep discrepancy counts separate from the number of offers reviewed. A small sample does not prove that every price is accurate or that sales will rise. It can help show recurring issues and work still awaiting a retest. In a weekly review, discuss repeated findings, open work and completed checks. Use the same sample card in a software demonstration and ask how the visible offer survives each step, without assuming capabilities beyond public product information.