A few months ago we wrote that AI search is changing how renters find apartments. More and more people open ChatGPT, Claude or Perplexity, describe the place they want and get back a short list of apartments. That post made the case that the shift is real and that it rewards properties whose data a model can read.
Traditional SEO optimizes for ranking, which means getting your page near the top of a list of links. Generative engines work differently. When someone asks an assistant for ‘a two-bedroom under $2,400 near downtown with in-unit laundry, available in September,’ the model is not returning a list of pages. It is assembling an answer, and to do that it needs facts it can lift: the rent, the bed and bath count, the neighborhood, the amenity, the availability date. Facts that live on your page as plain, structured text make you quotable, and GEO, for Generative Engine Optimization, is the usual name for the work of putting them there.
A picture, a PDF or a third-party widget the model cannot open leaves a property invisible, however beautiful the page looks to a human, and for a property running Engrain SightMap® the map is that widget. The standard SightMap embed is an iframe, a window in your page that shows content served from Engrain’s domain. Everything inside it (unit numbers, prices, availability, floor plans) belongs to that domain, so to a crawler reading your page the frame is a blank rectangle. Google crawls your floor-plans page and finds almost no content of its own there, and an assistant asked for that two-bedroom cannot lift a single fact about your inventory.
Nobody can promise a spot in an AI’s answer, the same way nobody can promise the top of Google, but you can remove every reason a model has to skip you for a competitor whose data is easier to read. None of the steps below needs a data-science team, and most of them are work you do once.
1. Publish structured data
Schema.org markup has fed Google’s rich results for years, and an assistant reads the same blocks when it wants a number it can quote. Add a JSON-LD block that describes an ApartmentComplex with its address, a geo location and an amenityFeature list, containing one Apartment (or Accommodation) per floor plan with numberOfBedrooms, numberOfBathroomsTotal, floorSize and an Offer holding the price (an AggregateOffer with a low and a high price where a plan’s units are not all priced the same).
ApartmentComplex: ‘Halstead Row’
→ geo: 40.71, −74.01
→ amenityFeature: in-unit laundry, rooftop, parking
→ numberOfAvailableAccommodationUnits: 12
→ Apartment: ‘The Birch’ · 2 bed · 2 bath · 1,100 sq ft
→ AggregateOffer: $2,380–$2,595 / month · 3 priced units
2. Take the units out of the iframe
Whatever sits inside the SightMap frame belongs to Engrain’s domain, so your own page gets no credit for the units, prices and availability a renter sees there. Render the same facts (plan names, bed and bath counts, square footage, price and availability) as HTML on your own page, next to the map, which stays where it is for the people exploring it.
3. Put every fact in text
A crawler, whether Google’s or an AI’s, generally cannot read the text inside an image or reliably parse a PDF floor plan. Wherever pricing sits in a JPEG, a floor plan in a PDF or a spec sheet in an image, publish the same facts as plain text on the page.
4. Answer the questions renters ask
Assistants are conversational, so the content they quote reads like a reply to a question someone asked. Answer questions such as ‘Is it pet-friendly?’, ‘What is included in the rent?’, ‘How far is it from the train?’ and ‘What is available for a September move-in?’ in plain language, in a frequently-asked-questions section wrapped in FAQPage structured data.
5. Let the AI crawlers in
Plenty of sites, often without realizing it, use robots.txt to turn away the very agents that feed AI answers. Check that yours admits GPTBot and OAI-SearchBot (OpenAI), ClaudeBot (Anthropic) and PerplexityBot (Perplexity), among others; blocking them is a legitimate business decision, but it works against being recommended.
6. Publish an llms.txt
An llms.txt sets out in plain Markdown what the site is and where its detail lives, in a form an assistant can read in one pass. Put it at yoursite.com/llms.txt and treat it as a low-cost bet, since it is a still-emerging convention that no model is required to read.
7. Keep every page current
When a page’s availability changes as the building’s does, a model has reason to trust the number it finds there. Report an accurate lastmod date for each page in your sitemap, and keep the content out of slow JavaScript a crawler may never wait for.
8. Keep one source for every number
If your rent says one thing on your website, another on a listing site and a third in an old cached page, an assistant has no reason to trust any of them and may quote the wrong one. Pick a single source of truth for rents and availability and let every surface read from it, the same discipline that makes all-in pricing a compliance win.
9. Watch the crawlers and the referrals
AI crawlers identify themselves, and assistants increasingly link their sources. Search your server logs for user-agents such as GPTBot, ClaudeBot and PerplexityBot, and track the visits referred from chatgpt.com, perplexity.ai and the like in your analytics.
What WP FloorMap automates
Every step above can be done by hand, on any site. A WP FloorMap site does most of them as it runs. Every property and floor plan emits its JSON-LD from the same Engrain SightMap and PMS data that renders the page, along with any data you add in WP FloorMap. The priced units on a plan aggregate into its price range and an in-stock or out-of-stock flag, and the property’s available-unit count sits on the complex. When a pet policy changes, a unit leases or a price changes, the markup follows on the next refresh. Floor-plan cards render on the server, so the plan name arrives as a heading with the bed and bath counts, the area, the price and the availability beside it as text, readable without running a line of JavaScript. The FAQ block emits its own FAQPage markup wherever you place it. An llms.txt that briefs a model on each property and an llms-full.txt that adds the floor-plan and unit tables are rebuilt from the property data through the day. The price on a card and the price in its Offer resolve through the same code, so the two cannot disagree. The robots file stays a job you do yourself, and your SightMap stays on the page for the people exploring it.

See your property on WP FloorMap
Send a SightMap link, and within 12 hours we reply with a working preview of your site, built from your live PMS data.
by Graham Dyer 