A property can be ready for the market at 9am and still miss a day of enquiries because one field is wrong. A postcode does not match, the tenure is missing, the rent frequency is unclear, or the image count falls below a portal’s requirement. Knowing how to validate property data before a feed is sent protects more than an advert - it protects your agency’s time, reputation and chance of securing the next instruction.
For busy sales and lettings teams, validation should not mean another long manual check. It means putting sensible controls around the information that moves from your CRM, spreadsheet or dashboard to every advertising channel.
Why property data validation matters
Property portals process a large volume of listings, and each one applies its own rules to fields, images, descriptions and classifications. Some issues cause an immediate feed rejection. Others are more costly because the listing goes live with incomplete or misleading information.
A flat advertised without its council tax band may create avoidable tenant questions. A new-build listed as a resale can appear in the wrong search results. A property marked as available after it has been let wastes negotiators’ time and frustrates applicants. When the same record is published to several portals, one small error can become a repeated operational problem.
Good validation improves speed as well as accuracy. When the source data is right, you can publish with confidence, update a price or status once, and avoid logging into a dozen portal accounts to correct the same detail. That is the practical value of a clean feed.
How to validate property data: start with the essentials
The first check is whether the listing has enough information to be advertised properly. Required fields vary by portal and listing type, but your team should agree a minimum standard before a property can be marked ready to publish.
For a sale listing, that usually includes the full address, postcode, property type, price, tenure where applicable, bedroom and bathroom count, accurate availability status, description, key features, images and agent contact details. Lettings records need further care around monthly rent, deposit, tenancy information, furnishing status, available date, council tax band and EPC details where required.
Do not rely on a negotiator remembering every field at the point of entry. Configure required fields in your CRM or use a simple pre-publication checklist in your property administration process. The objective is straightforward: no record should reach a feed until the information that buyers, tenants and portals expect is present.
Check formats, not just whether a field is filled in
A completed field is not necessarily a valid one. “TBC” in a postcode field, “0” bedrooms on a family house, or a price entered as free text can break a feed or produce poor search results.
Use consistent formats for phone numbers, postcodes, prices and dates. Keep numerical values in numerical fields rather than adding notes such as “offers over” where the portal expects a separate price qualifier. Confirm that date fields use the format your software and feed require. If your CRM exports XML, BLM or RTDF data, correct field mapping matters just as much as the value itself.
This is particularly relevant for multi-branch agencies. A branch may have its own local habits for entering descriptions or property types, but the central feed needs one reliable structure. Standardising the process prevents branch-by-branch variations from becoming portal errors.
Match the listing to the correct property classification
Property type, transaction type and status determine where an advert appears and who sees it. A house, flat, bungalow, plot, commercial unit and student property may all need different classifications. The same applies to sales, long-term lettings, short lets, holiday accommodation and overseas listings.
Take extra care with properties that sit near a category boundary. A maisonette is not always handled in the same way as a flat. A detached annexe might need a separate listing, not a mention within the main house description. A development containing several units needs accurate development and individual property data so portals can display it correctly.
Status is equally important. Available, under offer, sold subject to contract, let agreed and withdrawn are not interchangeable. Your internal workflow should make it clear who changes the status, when it is changed and how quickly that update reaches every portal. Real-time publication is valuable only when the source record reflects reality.
Validate addresses, location and map data
A correct address is the foundation of a searchable listing. Check the house or flat number, street, locality, town and postcode against a trusted source before publishing. One incorrect character in a postcode can place a property miles away on a portal map or prevent the address from being recognised at all.
For developments, rural homes and overseas property, address data can be less standardised. In these cases, check the displayed address, map pin and location description together. You may choose not to reveal the full address for security or vendor privacy, but the portal still needs enough accurate location information to return the listing in the right area search.
If your feed uses latitude and longitude, make sure they correspond with the actual property. Coordinates copied from a nearby office, a previous listing or a development entrance can create confusion for viewings and reduce trust before a buyer has even made contact.
Treat images, floorplans and documents as data too
Portal compliance is not only about text fields. Images, floorplans, EPCs and brochures all need checking before they are distributed.
Make sure the lead image is the strongest and most representative image, rather than a generic graphic or an internal photograph. Check that images belong to the correct property, display in the right order and meet the portal’s file and size requirements. A photo from a similar flat in the same block may seem harmless, but it can create a misleading advert and a difficult conversation later.
Floorplans should be readable and relevant to the advertised unit. For new homes, check that the plot number and layout are correct. For lettings, remove outdated floorplans or documents where a property has been altered. Where EPC information is supplied, confirm the rating, expiry and document match the address.
Check descriptions for accuracy and compliance
Descriptions sell the property, but they should never compensate for missing structured data. A portal cannot reliably filter a home with “two bedrooms” written in the prose if the bedroom field is blank.
Review the description for facts that have changed: price, availability, parking, garden access, lease length, service charge, furnished status and included bills. Avoid claims that cannot be supported. If a property is described as “walking distance” from a station or “ideal for students”, make sure the wording is fair and fits your agency’s policies.
A useful final read is from the applicant’s perspective. Does the headline match the price and property type? Do the key features agree with the photographs? Is the call to action clear? This takes minutes and catches the errors that automated rules cannot.
Build validation into your feed workflow
The best process combines automated checks with human judgement. Software can identify missing mandatory fields, invalid values, duplicate references and mapping errors. A person is still needed to spot the wrong lead image, an outdated description or a location pin that does not make sense.
For remote feeds, validate at three stages: in the CRM or source system, during feed import, and after publication. Frequent import checks help you find a broken XML, BLM or API connection before a backlog of changes builds up. For manual entry, set a clear approval point before a listing is sent live.
Estate Agent Feeds can support this process by importing and converting property data from your existing workflow, then distributing it to the portals you choose from one place. That reduces duplicate entry, but it does not remove the need for good source data. The cleaner the record going in, the faster and more reliable the publication result.
Keep an exception process, not a blame process
Even well-run agencies receive portal rejections. What matters is how quickly you identify the cause and stop it happening again. Keep a simple log of rejected listings: the portal, error message, affected field, source system and resolution. Patterns soon appear.
If the same issue keeps returning, fix the field rule, mapping or staff guidance rather than correcting individual listings one by one. This is where a small process change can save hours each month.
A practical pre-publication check
Before a listing is released, confirm that the address and map position are correct; the property type, price, status and core facts are complete; the description agrees with the structured fields; and the images, floorplan and compliance documents belong to that property. Then check that the record has been assigned to the right branch, portal account and marketing channels.
For large portfolios, sample checking may be sensible alongside automated validation. For a single premium instruction, a full review is usually worth the extra few minutes. The right level of checking depends on listing volume, system reliability and the cost of getting it wrong.
Accurate property data is not glamorous, but it is one of the quickest ways to make portal advertising less stressful. Set clear rules at the source, resolve exceptions early and give your team one dependable route from instruction to live advert. Your listings will spend less time in error queues and more time in front of the right buyers and tenants.