Find on page
Press Ctrl + F on Windows or Cmd + F on Mac to search the text of the page you are viewing.
WORKGROUPS 5 + 6 OUTPUT
First inspect what the hotel publishes and controls. Then inspect what AI systems actually say. Keep the two sets of findings separate.
Rule
A self-assessment result is never converted to a score, never compared with a conformance score, and never compared between properties.
Part one
Inspect the hotel website and authoritative sources. Record evidence, the finding, the fix, an owner, and the date. Some checks may require help from someone comfortable with structured data or page source.
Part two
Run a declared prompt set under consistent conditions. Record each AI engine separately. One favorable screenshot is not a measurement, and no engine results are pooled into one number.
Use the ten checks as separate findings. The first five provide a focused browser-based starting point; the remaining checks cover identity, source authority, consistency, and ownership. Each check now includes a plain-language procedure that can be completed without paid tools.
Before you start
You need a desktop or laptop browser. You do not need a paid tool, plugin, or account. Capture a screenshot for every check, record the exact URL and date, and keep the finding even when the check passes.
Press Ctrl + F on Windows or Cmd + F on Mac to search the text of the page you are viewing.
Right-click a page and choose View page source in Chrome, Edge, or Firefox, or Show page source in Safari after enabling the Develop menu. The code may look intimidating; you only need Find on page to locate one word at a time.
Plan for limited help on checks 02 and 05. These are the two most likely to require a few minutes from the person who maintains the website. Everything else is primarily reading, recording, and comparing.
Check: Start with a robots.txt screening check for possible blocks on public hotel content. This is an initial inspection, not complete verification of crawler access.
Record possible blocks and the maintainer's confirmation. Keep training-only crawler choices separate from search and retrieval access.
For the maintainer's verification and implementation steps, use the Robots.txt Implementation Guide.
Mark: Pass when access to the relevant public content is verified; Needs fix for a confirmed block on a relevant public path; Fail for a confirmed retrieval-agent block on the main content. Use Deferred when evidence is unavailable or inconclusive.
Fix: Have the website maintainer correct unintended search or retrieval blocks while preserving private paths and the hotel's separate training-crawler choices.
Check: When structured data is published or required for a declared eligible feature, validate that it identifies the property with the correctly cased lodging type reflecting its actual operating category.
Missing optional markup is not automatically a failure. A broader Organization record may coexist with the property record. Incorrect published markup can require correction, but structured data does not guarantee AI inclusion or recommendation.
May need help. If the search returns nothing, or you cannot tell which match describes the property, ask the website maintainer to confirm the structured-data type on the homepage.
Mark: Pass for valid, applicable lodging markup consistent with the property and visible content; Needs fix for published markup that is overly generic or incomplete; Fail for incorrect published markup or missing markup required by the declared feature. Record optional absence without marking Fail; use Deferred when applicability or evidence is inconclusive.
Fix: Correct the structured-data type and make sure it agrees with the visible page and the property itself.
Check: Check identity, location, category, contact, stay times, policies, amenities, and price. The workbook defines what counts as complete.
| Fact group | What counts as complete |
|---|---|
| Identity | The official property name used on legal and booking documents. |
| Location | Full street address, postal code, city, and country. |
| Category | The lodging type, stated in words on the page. |
| Contact | A telephone number and email address, both presented as text. |
| Stay times | Check-in and check-out with actual clock times. |
| Policies | Cancellation, pets, smoking, and deposit or card hold. |
| Amenities | Wi-Fi, parking, breakfast, and accessibility, each with its real status. |
| Price | An indicative nightly rate or rate range. |
Mark: Pass when seven or eight groups are complete; Needs fix for three to six; Fail for fewer than three.
Fix: Work from missing high-value facts first. Publish clear, specific answers as readable website text. The professional audit separately checks structured and machine-readable data.
Check: Confirm that the hotel's own domain answers all 16 practical guest questions listed below as readable page text – not only in images, PDFs, widgets, or third-party listings.
Complete question set
Parking availability and parking price are separate guest decisions. Wi-Fi and breakfast each require both provision and price, so all sixteen questions must be checked individually.
The answers most often missing are parking price, breakfast price, deposit or card-hold information, and the property's distinguishing feature.
Mark: Pass for at least twelve answers; Needs fix for eight to eleven; Fail for fewer than eight.
Fix: Add clear sentences for the missing policies, facilities, prices, room information, contact details, location, and property differentiator.
Check: View the homepage source, find the booking call to action, and confirm that it is a real link leading to a usable page for this property without an unintended robots block.
This check confirms that a property-specific path exists and is reachable. It does not establish that a guest completes a booking.
May need help. If copying the link or comparing its path with robots.txt is unclear, a website maintainer should be able to confirm both quickly.
Mark: Pass for a direct property-specific link; Needs fix for an indirect brand or group search; Fail for an empty, script-only, blocked, incorrect, or unusable destination.
Fix: Use a real link to the correct property page. This checks the path only; it does not claim that a booking or transaction occurred.
Check: Compare official name, address, telephone, coordinates, website, and parent or brand relationship across the hotel's authoritative sources.
Mark: Pass when material identity fields agree; Needs fix for a limited mismatch; Fail when identity is materially ambiguous or contradictory.
Fix: Designate a source of truth, correct owner-controlled surfaces, and document third-party corrections that are still propagating.
Check: Check that similarly named properties, restaurants, residences, destinations, and parent brands can be distinguished using stable facts, identifiers, and clear page content.
If another entity could reasonably be mistaken for the property and the website does not resolve the confusion, record that ambiguity as the finding.
Mark: Pass when the hotel is unambiguous; Needs fix when one relationship or identifier is weak; Fail when another entity could reasonably be mistaken for the property.
Fix: Strengthen canonical identity, entity relationships, official descriptions, and stable identifiers.
Check: For every material guest fact, identify an accessible, current, correctable source controlled by the hotel, brand, or responsible operator.
Mark: Pass when every priority fact has an official source; Needs fix for isolated gaps; Fail when important policies or attributes exist only on third-party sites.
Fix: Publish missing facts on an appropriate official page and assign an owner.
Check: Compare priority facts across the hotel site, business listings, booking content, brand systems, and major third-party profiles.
An outdated phone number on one listing is a limited inconsistency. Conflicting cancellation windows on the hotel website and booking engine are critical because they lead guests and AI systems to different conclusions.
Mark: Pass when no material contradiction remains; Needs fix for a limited inconsistency; Fail when guests or AI systems receive conflicting critical information.
Fix: Correct the source of record first, then submit and track downstream corrections.
Check: Confirm that changing facts – policies, prices, facilities, hours, availability signals, and contact details – have an owner, evidence source, review date, and cadence.
This check examines how the property is operated, so it is completed from internal ownership records rather than from the public website alone.
Mark: Pass when priority facts have current evidence and ownership; Needs fix for incomplete coverage; Fail when material facts are stale and unowned.
Fix: Assign the responsible role and a review trigger for each volatile fact.
AI visibility is non-deterministic. The practical question is not “What rank is the hotel?” but whether it appears, is recommended, is represented accurately, is supported by observable sources, and is described appropriately under declared conditions.
For discovery prompts that return a usable hotel list, record whether the property appears. Keep each AI engine, market, language, and prompt family separate.
When the property appears, compare material claims with the hotel's approved facts. In the workbook, record how many facts you checked and how many were correct.
Record whether the hotel is actively recommended or shortlisted rather than merely mentioned. Keep recommendation separate from presence.
When the answer shows sources, record them and mark whether the hotel's own website appears. A source is evidence to inspect, not a complete explanation of why the AI answered that way.
Choose Accurate, Materially incomplete, or Misleading for description quality. Record tone as Positive, Neutral, or Negative. These are observations – not scores.
Branded
Use branded prompts to inspect what an AI system knows, how it compares and describes the property, and what review themes it reports.
Discovery
Use discovery prompts to test whether the property surfaces for a category, traveler, occasion, or need without being led to it.
What do you know about [hotel name] in [destination]?
How does [hotel name] in [destination] compare to other [category] hotels there?
What do guests say about [hotel name] in [destination]?
What are the top [category] hotels in [destination]?
Best hotels in [destination] for [guest type].
Which hotels would you recommend in [destination] for [occasion]?
[hotel name]The official property name used across authoritative sources.
[destination]The market a traveler would naturally use: city, district, resort area, or landmark.
[category]The hotel's genuine operating category or competitive set – not an aspirational label.
[guest type]A traveler the property actually serves, such as families, business travelers, or guests with accessibility needs.
[occasion]A relevant trip purpose, such as a conference, anniversary, ski trip, or weekend stay.
[need or amenity]A material decision criterion supported by approved facts.
[fact]One factual field to verify separately, such as check-in, cancellation, parking, Wi-Fi, pets, or breakfast.
“What are the best boutique hotels in Napa Valley for couples?”
Here, the category is boutique hotels, the destination is Napa Valley, and the guests are couples. Replace these details with ones that fit your property. This is an example of tailoring a guest-type discovery prompt, not a seventh required prompt. Once you choose your wording, keep it the same when you repeat the test.
For a separate factual spot-check, use: “What is the [fact] at [hotel name] in [destination]?” Apply it only to approved facts guests actually decide on, then repeat it after corrections or material changes.
Add only the optional prompts that fit the property. A practical working set often grows to roughly 15–25 prompts for a smaller property. Keep Core and Optional results separately identifiable, with Branded and Discovery results separate within each set.
| Optional topic | What to test in separate prompts |
|---|---|
| Amenities and ancillary services | Discover hotels with a spa, dining, parking, or transfers; separately check a named hotel's facilities, inclusions, or fees. |
| Pricing and value | Discover hotels that meet a price/value need; separately verify a named hotel's rates for fixed dates, occupancy, and inclusions. |
| Offers and packages | Find hotels offering a relevant package, check its terms, or compare it with a specified alternative. |
| Policies and practical questions | Check facts guests decide on, such as cancellation, accessibility, pets, or breakfast. |
| Neighborhood fit | Find hotels in the area that matters to the guest, such as near a venue or transport connection. |
| Brand and loyalty | Test a relevant brand or program restriction, membership benefits, or the property's affiliation. |
Use a fresh chat for every prompt so a prior answer does not influence the next run.
Test logged out where possible. Otherwise use a dedicated account with memory and personalization off.
Keep the AI engine, product mode, market, location, and language the same during a baseline. Record that setup once on the workbook's Self Test Conditions tab.
Keep the prompt wording and placeholders unchanged inside a baseline. If wording changes, start a new comparison series.
Mark an answer Usable for this test? = Yes when the AI gives an answer. For discovery prompts, the answer must also list hotels. Rows marked No stay in the log but are left out of the rates.
Use 10–14 independent runs per prompt and engine across approximately two weeks when a stable baseline is needed.
For each run, record the engine, market, language, prompt type, date, and prompt; usability, appearance, recommendation, description quality, tone, sources, checked and correct fact counts, and a note or pasted answer.
Use a monthly review as the operating default. Use weekly monitoring only during active remediation, after a major launch or material change, or when paid monitoring requires it; keep the method fixed.
One response is recorded as a finding. After enough usable independent runs, choose one market and language on the workbook's Dashboard. Results are shown separately for each engine and for Branded and Discovery prompts. Presence and recommendation apply to Discovery; source, tone, and accuracy results keep both prompt types separate. Rows marked not usable remain in Run Log but are left out of the rates. These rates are observations, not a self-assessment score.
| Observation | Formula |
|---|---|
| Discovery presence | Usable discovery runs in which the hotel appears ÷ usable discovery runs |
| Discovery recommendation | Usable discovery runs in which the hotel is recommended ÷ usable discovery runs |
| Hotel-website source | Usable appearances that show sources and include the hotel website ÷ usable appearances that show sources |
| Positive tone | Usable appearances marked Positive ÷ usable appearances with Positive, Neutral, or Negative recorded |
| Fact accuracy | Facts recorded as correct ÷ facts checked |
Priority 1
The AI engines and search assistants most used by the hotel's target guests in its priority markets.
Priority 2
Additional engines important to a specific region, language, guest segment, brand, or distribution context.
Watch list
Emerging surfaces worth observing, without mixing them into an established baseline until the protocol is stable.
Google Free Booking Links can expose a direct supplier's name, an itinerary rate, and a landing page without charging for the click. Participation commonly depends on a reservation system, CRS, booking engine, franchise, or integration provider supplying accurate rates and landing-page information to Google.
Confirm
Ask the booking-engine, CRS, franchise, or integration provider whether Free Booking Links are active for the property and who supplies the rates and landing pages.
Verify
Check the displayed itinerary rate, direct landing page, property identity, and applicable policies against the hotel's live approved sources.
Identify
Record which owner, direct supplier, CRS, or integration partner is treated as the official direct source where that designation appears.
Record
Capture the date, market, search conditions, displayed rate, landing page, provider, evidence, owner, and any discrepancy requiring correction.
Participation, an Official site designation, a displayed rate, or a Free Booking Link click is action-readiness evidence only. It does not prove that an AI answer mentioned or recommended the hotel, and it does not prove transaction completion, conversion, or revenue.