Real estate AEO: the markup that decides what a machine reads
Answer Engine Optimization is the structural layer under the other two. Not how you rank on Google, and not what an assistant says about you in prose. What a machine finds when it fetches the page, before either of those becomes possible.
It is the least visible part of this work and the part most often sold on the wrong promise, so this page is organised around what each piece prevents rather than what it might win. Where the argument needs a ranking figure or a citation rate, it links to the page that has one instead of restating it here.
What gets built, and what each part prevents
Listing-level structured data
Price, availability, unit type, location and the identifier that keeps a listing the same listing across a rename. The failure this prevents is the common one on property sites: the listing renders client-side, or behind a search form, and a crawler retrieves a shell. Nothing downstream can be fixed while that is true, which is why it is checked first.
The entity layer
One Organization node with a stable identifier, referenced by every page rather than restated on each. The licence, the principal, the office and the service area resolve as one company. The failure this prevents is a model answering "is this firm legitimate" from a third-party profile it happened to find instead of from you.
Question and answer markup
The questions your buyers actually ask, marked up so the pairing survives being read by a machine, and rendered visibly on the page from the same source so the two cannot disagree. The failure this prevents is the ordinary one: an answer in the markup that no longer matches the answer on the page.
Crawl access and index hygiene
Which agents are allowed, which are blocked and whether that is deliberate, sitemap accuracy, and whether the pages you care about are the pages actually indexed. The failure this prevents is the expensive one: a site doing all of the above correctly while robots.txt blocks the agents that would read it.
The 24/7 digital broker
When a buyer in Dubai asks ChatGPT "What are the best condos in BGC under 15M?", will your project show up? When an OFW in Singapore asks Perplexity "Is [Developer] legitimate?", will your data be the answer?
AEO is not a replacement for SEO. It is the layer that makes both work. We optimize for Google and for answer engines together by structuring your data with proper schema markup, building entity authority, and providing the kind of verified, first-hand content these systems prioritize over recycled blog posts.
Structured content becomes the sales kit for your entire network. When a referral partner sends a Viber link, when a licensed broker emails a comparison, when an OFW types a question into an AI. Your content needs to rank, answer, and convert in all three scenarios.
For developers who want that as an internal system rather than a public one, the AI knowledge base is the same work pointed inward.
What this does not do
It does not make a model recommend you. Structure decides whether a system can read, resolve and quote your inventory. Whether it then names you in an answer is that system's decision, and it changes when the model changes. Anyone offering a guarantee on that outcome is selling something they do not control.
It also does not replace the ranking work. A perfectly marked-up site that nobody links to and nothing ranks is a well-described invisible site. The mechanics on this page are a precondition, not a substitute, which is the whole argument for one program rather than three.
Questions buyers ask
What is AEO, and how is it different from what you call SEO and GEO?
Answer Engine Optimization is the structural half. It is the markup and the machine-readable structure that decide what a system finds when it fetches your page, as opposed to how you rank on Google, which is the SEO page, or what an assistant says about you in prose, which is the GEO page. One program, three surfaces, and this is the one both of the others sit on.
The practical test is whether a machine that has never seen your site can answer three questions from the page alone: who this company is, what this listing costs and whether it is still available, and where it is. If the answer to any of those is only in a rendered layout, it does not exist to a retrieval system. That test takes about five minutes on your own site and it is the first thing the USD 800 one-time audit reports back.
Does schema markup still do anything now that Google has dropped FAQ rich results?
Yes, and the two things are not the same claim. Google stopped rendering FAQ rich results for sites like this one on 7 May 2026, so FAQPage markup no longer wins space in a search result. It is still what answer engines read to pair a question with an answer, which is why this page carries it and why we will not sell it to you as a rich result.
The markup that does still produce visible search features is a different set: Organization, Product, Place, Offer, Breadcrumb. We build both, and we tell you which one you are getting for a given page rather than letting one justify the other.
What is an entity graph, in terms that matter to a brokerage?
It is the difference between a machine knowing your name and a machine knowing which company you are. On this site there is exactly one Organization node, every page references it by a stable identifier rather than restating the details, and the profiles that confirm it are listed on that node. A model resolving "who is this" lands on one entity with one set of facts instead of eighteen pages each asserting their own.
For a brokerage the payoff is specific: the licence, the office, the service area and the named principal resolve as one thing. When those live only in page copy, an assistant asked whether you are legitimate answers from whatever else it found, which is the failure mode the GEO page measures. At scale this is the same problem REN.PH solves across 25,255 as of 21 August 2026, where each profile has to resolve to one licensed person rather than to a name that several people share.
What is llms.txt, and is it worth doing?
It is a plain-text file at the root of a site describing what the site holds, aimed at systems reading rather than browsing. This site publishes one whose page inventory is generated at build time from the routes themselves, so it cannot fall behind the site the way a hand-maintained file does. Ours went stale in three lines this month in the half that is still hand-maintained, which is the argument for generating it.
Honest answer on worth: no search or assistant provider has committed to reading llms.txt, so this is a cheap bet and not a mechanism with measured returns. It costs an afternoon once, it is checkable, and it is the one item on this page we would drop first if a budget were tight. Anyone selling it as a ranking factor is ahead of the evidence.
How long before structural work shows up in an answer?
These are ranges we collected from what other firms in the Dubai market publish on their own AEO and GEO service pages, read during our September 2026 research on that market: AI citations typically begin appearing 2 to 3 weeks after new content publishes, AI-referred traffic takes 4 to 12 weeks to become measurable, and a real shift across a set of priority prompts takes 3 to 6 months. Those are published claims by other firms, not a controlled study, and we have not reproduced them ourselves. Structural work is the fastest half of that range, because it changes what is readable rather than waiting on anything to be re-earned.
What we will not do is promise the answer changes. We can make your inventory readable, resolvable and current. Whether a given model then names you is that model's decision, and no one selling this can promise otherwise.
Can you show this working somewhere?
On our own platform, which is self-evidence and should be weighted as such. REN.PH is a Philippine property data platform built on structured government data, and its live XML sitemaps held 65,291 as of 21 August 2026. Search Console recorded 121,293 clicks at an average position of 7.4 across 28 April to 18 August 2026. That is a search figure, not a citation figure, and it is on the SEO side of this set rather than this one.
For what an assistant does with structure, the measurement and the honest gaps are on the GEO page. The sharpest single result is on the Dubai market page: twenty logged-out runs from a Dubai IP in September 2026, ten framed as a brokerage and ten as a developer, in which our own firm appeared zero times in either shortlist. We would rather you read those two than this paragraph.
Do I need to buy SEO, GEO and AEO separately?
No, and there is no separate price list for any of them. It is one program on one ladder: USD 1,400, 2,400 and 3,800 per month, a USD 800 one-time audit, and a three-month minimum rather than the six or twelve most agencies ask for. Every tier covers all three.
They are priced together because they are built together. The entity and organization markup that lets a model resolve who you are is the same markup that earns a rich result. The index and sitemap hygiene that gets a listing page crawled is what makes it retrievable when someone asks an assistant a question. Splitting them into three invoices would mean charging three times for one piece of technical work.
This is also what the models themselves tell buyers. Ask one how to choose a GEO vendor and several of them warn you off agencies selling GEO in isolation from SEO fundamentals. That warning is correct, and it is the reason this is one program rather than three products.
The rest of the program
- Real estate SEO
Traditional search. Rankings, technical foundations and content, and how a brokerage competes with the portals on Google.
- Real estate GEO
The conversational surface. How ChatGPT, Gemini, Claude and Perplexity describe and recommend an agency, and how that gets measured.
- Six questions to ask any vendor, including us
The checklist AI models hand buyers, answered on the record, including the one where our own answer is the weak one.
One program, one ladder, three months
SEO, GEO and AEO are quoted together because they are built together. Book a call and we will tell you which of the three your site is actually short on.