XML imports have become an essential tool for many estate agencies. They allow agencies to expand their portfolio, work with collaborators, connect external providers, import new-build developments and display more properties on their website without having to enter each property manually.
However, as we saw in our webinar, working with XML can also raise questions, errors and situations that are not always easy to interpret.
That is why we would like to thank all Mediaelx clients who joined the webinar and took part with their questions. It was a very practical session, focused on real problems that many agencies face in their day-to-day work when dealing with imported properties.
If you were unable to attend live, you can now watch the full webinar on YouTube:
https://www.youtube.com/watch?v=Us1RunPYYgo
XML does not invent information: it shows what it receives
One of the main ideas of the webinar was very clear: XML does not invent information.
The website and CRM show the data they receive from the provider, collaborator, MLS or external system. Therefore, if the information arrives disorganised, incomplete, poorly structured or with errors at source, these problems may later be reflected on the estate agency website.
During the session, we explained that, in many cases, the issue is not actually with the website, but with the quality of the data received. This is especially important when an agency works with several XML providers or very large property catalogues.
Main questions we answered during the webinar
Throughout the webinar, we reviewed some of the most common questions received by our technical, SEO and support teams when an agency works with XML imports.
Among other topics, we discussed:
- Why the names of other agencies may appear within property descriptions.
- What happens when descriptions are edited manually and then change again the next day.
- Why duplicate property types or types that differ from those on the website may appear.
- How repeated, misspelled or inconsistent locations are created.
- Why only one photo may appear at first on some imported properties.
- What to do if images arrive with another agency’s watermark.
- Why not all the languages available on a website are always imported.
- What information may be left out of the XML, even if it is visible on the provider’s website.
- Why large feeds can affect the performance of the website or CRM.
- How to correctly manage XML providers, hidden properties and the removal of imported catalogues.
The aim was to explain each situation in a simple way, with real examples and practical recommendations so agencies can better understand what happens behind each import.
Data quality: one of the most important points
An important part of the webinar was dedicated to data quality.
When several agencies collaborate with each other, each one may use its own property types, locations, area names, descriptions, languages or image formats. This can cause the same area to appear written in several different ways or generate very similar property types.
For example, one agency may use “villa”, another “chalet”, another “casa independiente” and another “detached villa”. If there is no common criterion, the system receives these data as different elements.
That is why, during the webinar, we insisted on the importance of working with well-defined property types and locations, using mapping tools when necessary and reviewing the automatic notifications sent by the system when it detects new types or new locations.
Photos, languages and data that do not always arrive as expected
We also talked about a very common topic: photos and languages.
In some cases, after importing an XML, it may seem that a property only has one photo. This does not necessarily mean that the system has failed. When hundreds or thousands of properties are imported, the system prioritises the main image so that the property does not appear without a photo, and then gradually processes the remaining images.
We also explained that, if a photo appears with another agency’s watermark, that watermark is usually already included in the source image. Mediaelx does not add watermarks when exporting properties, so in these cases, the best option is to contact the collaborating agency so they can replace or correct those images at source.
Regarding languages, we reminded clients that an XML can only bring in the languages that exist at source. If the provider has descriptions in three languages and the destination website works in five, the other two languages will not be imported automatically.
Be careful with very large XML feeds
Another key point of the webinar was performance.
Importing an XML with thousands of properties and tens of thousands of images can consume a lot of server resources. For this reason, large imports must be managed carefully.
During the session, we explained that the problem is not always with the provider. Very often, the issue is the size of the feed, the number of images, the update frequency or the lack of filters before importing.
For this reason, we recommend filtering at source whenever possible. If an agency does not work in certain areas, with certain property types, price ranges or rentals, it is best not to import that information. This makes the XML lighter, more useful and easier to manage.
More properties does not always mean a better catalogue
One of the most important reflections from the webinar was that importing more properties does not always mean having a better website.
A large catalogue can be very positive, but only if it is well organised, up to date and adapted to the agency’s strategy. If the catalogue is filled with properties that are not relevant, areas the agency does not work in, low-quality images or incomplete data, the user experience may be affected.
That is why good XML management is not just about connecting providers, but about controlling what is imported, how it is displayed and whether it really adds value to the agency and its clients.
Introducing MediaElx XML Care & Support
At the end of the webinar, we introduced our new service: MediaElx XML Care & Support.
This service has been created to help estate agencies that work with XML and need to review issues, better control their imports and maintain a more organised catalogue.
XML is a very powerful solution because it saves time and makes it possible to work with large volumes of properties. However, it can also create side effects: duplicates, language issues, photos that do not update, incorrectly classified locations, performance problems or data that changes when updated from the provider.
We want to offer more specialised technical support so agencies can work with their XML feeds more professionally and spend less time solving issues.
Thank you for joining us
At Mediaelx, we would like to thank all the clients who attended the webinar, took part with their questions and shared real situations that help improve this type of session.
If you were unable to join live or would like to review any of the points covered, you can watch the full recording here:
https://www.youtube.com/watch?v=Us1RunPYYgo
We would also like to remind our English-speaking clients that this same webinar will take place in English next Thursday, 18 June, at 9:30 am.
It will be another opportunity to answer questions, explain how XML imports work and share practical solutions for estate agencies working with external providers, collaborators or large property catalogues.
See you soon!
Image gallery
