How search works
Human search
The human form is search. It lists published observations, 100 per page, newest read first. The form sends q, use, and status. zip, rent, sort, and page still apply when they are in the address.
q matches a stated street address, property name, suite label, city, or postal code. It matches a street that states the same digits as a ZIP. It leaves the source URL unread. Punctuation is ignored. A blank form redirects to /search.
q— stated address, property name, suite label, city, or postal code. At most 120 characters.use— office, retail, industrial, or flex.status— current, or overdue (not re-read in 7 or more days).zip— five-digit ZIP or ZIP+4 the source page stated.rent— stated, or unstated. An unstated rent stays blank.sort— newest, address, or published.page— page number, starting at 1.
Addresses that stay out of the index
/search with no query is index, follow, and it is a sitemap URL. A query, a filter, a non-default sort, or a page after the first sends noindex, follow. Those addresses stay out of the sitemap.
The canonical of a filtered address is the clean page it was filtered from. On /search and /suites, a ZIP-only filter whose rows are exactly one indexable ZIP hub uses that hub: /houston/zip/{zip} or /san-antonio/zip/{zip}. Greater Houston applies the ZIP index gate. A San Antonio ZIP hub is the canonical when that ZIP has a published suite. A q value stays on /search, including a q that is only digits, because q also matches a street.
A filtered use hub keeps that hub as its canonical. The hub's own canonical stays the hub. /search with only use=office stays on /search, because that list covers Greater Houston and San Antonio together.
When nothing matches
An empty human search says: No observations matched. Try a street, building, or zip. The published ledger has no observation whose stated address, property name, suite label, city, or postal code matched. The page names no suite the ledger does not contain. A ZIP the source page did not state matches nothing.
The ZIP register for each city is on the city overview: Greater Houston and San Antonio.
Agent search
GET /agent/search.json is a separate read-only tool. submarket is optional. Omitting submarket is HTTP 200. The search is city-wide. The tool answers: city-wide; no submarket filter.
submarket matches a stated postal code, or a phrase in a stated address, property name, or city. A phrase shorter than 3 characters is HTTP 400. The tool answers: submarket phrase must be at least 3 characters, or pass a 5-digit postal code. The response field submarket is null. A public page does not name a commercial submarket, so the field stays null.
city=houston reads Greater Houston. Omitting city reads San Antonio. use and rent narrow the tool the way the catalog describes. A field the public page did not state is null. Null stays null. The human q parameter is not an argument of this tool.
GET /agent/search.json?city=houston&submarket=77002
GET /agent/search.json?submarket=78216
Catalog: /agent/tools.json. Markdown of this page: /search/help.md.
Where a rent is published
Counts and medians are computed on the city overview, the use hub, the ZIP hub, and the dated snapshot. This page prints none of them.