Images & content

A property page travels far. The same record reaches a traveller browsing on a metasearch engine, a B2B buyer reading on an aggregator, an operator looking at it in your Console, and an Adrasis AI Operator reply summarizing it. Images and content are what make those views feel like the same property told well, and a chain operating in 5 languages keeps each translation in sync from one shared record per property.

What "content" covers

Every layer can be in multiple languages, with source information, which value came from which source, which translation is yours, which is the original.

Multilingual is the default

Adrasis treats multilingual content as the norm:

• A property's English description and Turkish description coexist on the shared record, locale-tagged.
• A property image can have an English caption and a Spanish caption against the same image asset.
• An amenity carries labels in every language your organization operates in.

Travellers see the locale they request; operators see the locale they prefer. The catalog does not duplicate properties by language, it carries language on the record. Adding a new language is a content task, not a structural one.

Images, what the catalog records

For each image:

• The asset, the photograph itself.
• A caption per language, what it shows, in the operator's words.
• Ordering, first image, second, third; the gallery order travellers see.
• Tags, which room it depicts, what feature it highlights, whether it is the property main or a detail shot.
• Per-channel exposure, some channels accept many images, some only a few; you decide which surface where.
• Source information, which source contributed the image (a content feed, a direct upload, a partner sync).

You add, replace, reorder, and tag images through the property's content surface. The AI Operator can do bulk operations, "Replace the main image on every Antalya beach property with the new sunset shot."

Photo requirements

Console checks each photo when you upload it and names the reason when it refuses one, for example This photo is 6000x4000 pixels. A side can be at most 4096 pixels.

A camera photo is often larger than 4096 pixels on its long side. Resize it, for example to 3000x2000, before you upload it.

Description, what good catalog content looks like

A few practical heuristics:

• The first paragraph carries the weight. Travellers and snippet generators read the first 150–200 characters first; if the property has one differentiator, it goes there.
• Specifics over adjectives. 5-minute walk to two metro stations beats centrally located.
• Review descriptions in each language. Property details and included services must have the same meaning across languages. Use clear, natural wording in each language.
• Re-read after every catalog change. A new room type, a renovation, a category change, the description should reflect it.

The catalog's content surface is alive; you revisit pages, refine descriptions, replace tired imagery without rebuilding from scratch.

Per-language images

Sometimes the right image varies by language:

• A property's main image in English-language markets might be the pool-and-bar shot.
• The same property in a Turkish-language market might lead with a family-around-a-table image.
• A Middle East market main might emphasize the gardens and shaded outdoor spaces.

The catalog allows you to set per-language image ordering, same shared image library, language-specific gallery sequence. You do this where it matters; you do not have to do it for every property.

Content from multiple sources

If the same property arrives in your catalog from multiple sources (a channel manager, a content feed, a direct contract), the shared record reconciles them:

• Descriptions from one source merge with translations from another, with source information.
• Image libraries from multiple sources combine; duplicates are merged by content fingerprint.
• Amenity labels from one source's vocabulary translate into your shared classification through mapping.
• Operator overrides (your edits) win where you have set them.

See Match property records for the model.

Per-channel content exposure

Not every channel uses every content asset:

• A high-fan-out metasearch feed may only display a main, a short description, and a few amenities, even if your catalog carries dozens of images and a long description.
• A B2B aggregator may consume the full content payload, including operational notes.
• A direct-booking channel may carry your full marketing voice, including bespoke video and structured content blocks.

The platform sends each channel what it asks for; what does not fit a channel is not stripped from the shared record.

AI Operator and content

Common phrases that map to AI Operator content operations:

• "Find every property without a main image and queue them for content review."
• "Add a Turkish translation of the description on the Marina property."
• "Replace the second image on every Antalya beach property with the renovated-pool shot."
• "Show me properties where the description is identical across English and Turkish, they likely need a real Turkish version."
• "Apply our new family-friendly cancellation policy template to every property tagged Family-friendly."

Read operations return immediately; writes preview before applying.

Where to next

• The classifications that pair with content → Categories
• The place classification for the property's location → Location & geography
• The Content suggestions operator action that fills in catalog detail → Content suggestions
• The mapping system that reconciles content across sources → Match property records