Specoria
Menu
TR Free test
← All checks
lodging_amenities

Amenities in structured data

Why it matters Guests ask agents for specifics (“pool, free parking, breakfast included”); an agent filters on amenities it can read reliably.

Category
Property and service data
Weight
8 of 100 points (together with the common checks)
Critical blocker
No. If it fails, it only costs its own weight.
Applies to
Hotels and lodging
Effort
1 hour · developer
Score model
v2.4

How we measure it

We look for amenities (amenityFeature) in the hotel or room data. Present passes; amenities mentioned only in text (pool, breakfast, parking…) are a partial pass; nothing fails.

What the result page says

These are the sentences in the test result; “…” is replaced by what we found on your site.

  • PassedAmenities (amenityFeature) are listed in the structured data.
  • PartialAmenities appear in the page text, but not as amenityFeature data; agents filtering by “pool” or “free parking” may miss them.
  • FailedNo amenities were found, neither as amenityFeature data nor in the homepage text.

How to fix it

Target: Every amenity a guest might filter on is listed as a LocationFeatureSpecification (name + value: true).

Example code

"amenityFeature": [
  { "@type": "LocationFeatureSpecification", "name": "Free Wi-Fi", "value": true },
  { "@type": "LocationFeatureSpecification", "name": "Outdoor pool", "value": true },
  { "@type": "LocationFeatureSpecification", "name": "Free parking", "value": true }
]

Example values (example.com, product name, price) are placeholders; replace them with your own.

How to verify it yourself

The Hotel JSON-LD should carry an amenityFeature list with a name and value for each amenity.

Fix it with an AI coding agent

Paste this into Claude Code, Cursor or another coding agent working on your store’s code. Review the change before you deploy it.

You are working on my online store. Specoria’s agent readiness test checks the item below. Fix it so AI shopping agents can read the store and act on it.

## 1. Amenities in structured data (lodging_amenities)
Target: Every amenity a guest might filter on is listed as a LocationFeatureSpecification (name + value: true).
Example fix (adapt it to this codebase and platform; example values are placeholders):
```
"amenityFeature": [
  { "@type": "LocationFeatureSpecification", "name": "Free Wi-Fi", "value": true },
  { "@type": "LocationFeatureSpecification", "name": "Outdoor pool", "value": true },
  { "@type": "LocationFeatureSpecification", "name": "Free parking", "value": true }
]
```
Reference: https://specoria.com/method/checks/lodging-amenities/

## Rules
- First look through the codebase and tell me which files or templates you will change, before editing anything.
- Change only what these checks need, and keep the visible page and the structured data saying the same thing.
- Never invent prices, stock, shipping or return terms, reviews or product identifiers (GTIN): take them from the store’s real data or ask me.
- Don’t block or slow down real visitors and don’t add tracking.
- After deploying, run the free test again at https://specoria.com/ to verify the fix.

Specifications and guidance

The check is based on these open sources; links go to the publisher’s own pages.

Run the free test See the sample report →