← Back to TravMetricTRANSPARENT BY DESIGN · SITE-V1.1
What your score measures.
A bounded sample of up to four public HTML pages. Evidence, source links and visible coverage — so you know what a score is based on.
20 checks. Five points each.
Each met check contributes five points to a score out of 100. Each dimension contains five checks and is displayed as a percentage of checks met. There is no hidden AI weighting. The thresholds are TravMetric product heuristics; they have not been independently validated against AI recommendations, bookings, or an industry benchmark.
Discoverability — starting page
HTTPS with a valid certificate; no detected noindex/none directive; title of 10–120 characters; meta description of 50–320 characters; a same-origin canonical URL. These checks apply only to the submitted page after redirects.
Property clarity
An H1 of at least five characters on the starting page. Supported lodging context, a telephone/email route, a structured postal address, and amenity wording/data may be found on any successfully checked page.
Structured information
At least one readable JSON-LD block set with no malformed blocks on any checked page; a supported lodging entity; a name on a lodging entity; a matching website URL; valid-range numeric coordinates. Each lodging signal may be detected on a different page or entity; property consistency is not verified.
Answer readiness
At least 200 whitespace-separated words on one checked page; at least three non-empty H2/H3 headings on one page; supported FAQ phrases/schema or two question headings; guest-policy wording; rooms and contact links together on at least one page. Signals are not summed across pages merely to reach a threshold.
Supported lodging JSON-LD types: Hotel, Resort, Motel, BedAndBreakfast, Hostel, and LodgingBusiness. Parsing JSON-LD is not a full schema.org validation. Microdata and RDFa are not currently evaluated. Detected wording does not verify a hotel or the accuracy of its claims.
Which pages are selected?
- We validate the public URL, resolved addresses, and robots.txt rules, then fetch the submitted page. Standard entry-page redirects are allowed only after validation and a crawl-permission check.
- We inspect up to 1,000 links in its HTML. Candidate categories include contact/location, rooms/accommodation, amenities/services, guest policies, and FAQs. Missing entry-page signals increase the priority of related categories; contact and room information otherwise receive priority. This prioritization changes coverage, not the scoring weights.
- We select at most one link per category and at most three additional pages. They must use the same origin as the final starting page. External sites, booking/account/action routes, query-bearing URLs, common non-HTML assets, fragment-only links and nofollow links are excluded. Links found on supporting pages are not recursively followed.
- Each selected page gets its own robots path check. Additional-page redirects cannot leave that origin. Duplicate destinations are not counted twice. If a selected page is blocked, unavailable or times out, its status is shown; we do not silently replace it with guessed content or another page.
- The report shows checked pages and source URLs for each signal. Technical entry-page checks cannot be repaired by a title, description or canonical on another page. For other checks, one qualifying checked page can supply a signal. A page without JSON-LD is neutral for the JSON-LD check, but malformed JSON-LD on any checked page prompts review.
Access rules and time limits
TravMetricBot respects applicable robots.txt disallow rules. Unavailable rules, positive crawl delays, access challenges or unsupported responses prevent the affected page from being checked. A 404 or 410 robots response means no published rules. We never sign in, send your browser cookies, or bypass protections. Each fetch follows at most three redirects; every network destination is revalidated and pinned to a public address. Custom ports, IP literals, credentials, query strings and private networks are rejected.
HTML responses are limited to 1.5 MB per page; robots.txt to 256 KB. A scan has a 22-second total budget; each optional page has a four-second budget. When optional work cannot finish, a partial report based on successfully checked pages is returned. If the starting page cannot be read, no score is generated.
Read missing signals in context.
“Review” means a signal was not detected or did not meet its threshold in the pages checked. It is not proof that your entire website lacks the information. A policy or facility description may be on an unvisited page, a canonical may be unnecessary on a unique page, and a useful page may have fewer than 200 words. Partial coverage makes missing-signal conclusions less certain.
No JavaScript is executed. Navigation and footer text contribute to the word count. Whitespace counts do not work reliably for languages without spaces; wording recognition is limited to selected English and European-language terms. Deep or extensive JSON-LD is bounded. We do not verify names, addresses, facilities, coordinates, policy accuracy or identity consistency across pages. Group websites may describe different hotels on different pages; review the source links.
Site-v1.1 has broader coverage than the previous homepage-v1.0 method. A higher score after this update alone does not establish improvement. Compare reports only when their methodology and checked pages match.
A score of 100 means all checks in this version met their thresholds. It does not certify a hotel, establish content quality, measure actual AI visibility, or guarantee recommendations, rankings, traffic or bookings.
Data & fair use
Guest scans need no account, payment or AI API key and remain in browser memory until replaced or refreshed. Optional free accounts save your latest 20 signed-in scans privately; older saved reports are removed as new ones are stored. You can reopen, export or delete reports from your dashboard. Reports can be downloaded as JSON or printed/saved as PDF with your browser. The destination sees requests identified as TravMetricBot. Normal hosting logs may apply. Read the account-data page for recovery, storage, deletion and backup details.
The beta allows eight requests per ten minutes per trusted client bucket, up to 30 starts per minute and three concurrent scans per process. Visitors share a bucket when trusted proxy handling is disabled. These limits reset on restart and are not a distributed quota. Limits and the methodology may evolve as the beta is evaluated.
TravMetric is independent of AI providers. Paid subscriptions, verified ownership, portfolio reports and monitoring remain in development.
Check your hotel →