| 开发者 |
realtycandy
redjim |
|---|---|
| 更新时间 | 2026年10月2日 07:19 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
/details/{address-slug}/{listing-id}.<title>, meta description, Open Graph, and Twitter Card tags render on the server for every listing.RealEstateListing JSON-LD, so it can qualify for rich results in Google./details?id=... links 301-redirect to the canonical URL, so you keep the SEO equity./wp-content/plugins/, or install the plugin ZIP via Plugins → Add New → Upload Plugin./details/{address-slug}/{listing-id}.Yes. AeroIDX is the WordPress front end for the AeroIDX platform. You need an active account and an API key. Get one at https://app.aeroidx.com/api-keys.
Yes. AeroIDX detects Yoast SEO and Rank Math and feeds them the listing data so they generate the meta tags. If no SEO plugin is active, AeroIDX outputs the SEO tags itself.
Yes. AeroIDX serves listings at clean URLs, which requires the WordPress permalink setting to be anything other than "Plain".
Yes. AeroIDX supports both classic themes and block themes. The listing widget is injected into the theme's content area in either case.
Every listing is rendered at /details/{address-slug}/{listing-id} on your site. AeroIDX also generates an XML sitemap so search engines can find them all.
AeroIDX returns a proper HTTP 410 (Gone) page for delisted properties, so you don't accumulate broken links or soft 404s.
A listing page is built from live IDX data, so the very first time anyone opens a particular property the plugin has to ask the AeroIDX API for it. That one lookup is the slow part. Everything after it is served from cache — for a week, and refreshed in the background so visitors never wait on it again. Two things make that first visit rare:
/aeroidx-sitemap-index.xml. WP Rocket ("Preload" > "Activate sitemap-based cache preloading"), LiteSpeed Cache (its crawler) and most host-level page caches can walk it and request each page ahead of your visitors. That warms the page cache and the plugin's own cache in one pass, and it costs you nothing but a checkbox.AeroIDX listing pages aren't editable in the WordPress editor. They're rendered on demand from your IDX data. To style them, use the scoped CSS hooks the plugin exposes from your theme custom CSS, a page builder custom CSS field (Bricks, Elementor, etc.), or a child theme stylesheet. Your rules only affect AeroIDX pages:
body.aeroidx-page: body class on every page AeroIDX creates for you — Search, Sign In, My Account, Featured, Roster, the /aeroidx shell, and each market page. On the built-in listing and agent pages it comes from the classic templates, so block themes render those two without it.#aeroidx-listing-detail, .aeroidx-listing-detail: main wrapper of the listing detail page. Classic themes only.#aeroidx-agent-detail, .aeroidx-agent-detail: main wrapper of the agent listings page. Classic themes only..aeroidx-widget-mount: direct parent of every AeroIDX widget, on every surface the plugin renders..aeroidx-listing-gone, .aeroidx-agent-gone, .aeroidx-page-gone, .aeroidx-listing-error: the “no longer available” and error states.AeroIDX widgets and backend-built links (sign-in, sign-up, email links) only work on the ONE site your account is currently authorized for. A site becomes the authorized one in these ways:
No. You don't need to enter your API key again. When the live site is on a production environment and the authorized address looks like a staging or temporary one, AeroIDX moves the authorization to the live site on its own, within about an hour, or sooner when an admin opens wp-admin. A notice tells you what moved, and you can dismiss it.
A staging address is one like staging.example.com, a temporary domain from a host such as WP Engine, Kinsta, Pantheon or Cloudways, or localhost. If your live site moved and the old address doesn't look like staging, nothing moves on its own: press "Authorize this site" on the AeroIDX Home screen.
Going the other way is not automatic. A copy of your live site can never take the authorization from it. If you want widgets to work on a staging or local copy, press "Authorize this site" there.
A live site takes the authorization back within the hour, even from localhost. If you test widgets on a local copy, use a separate test key from your AeroIDX account. Otherwise your widgets on the local copy stop working after the next check.
Developers can change what counts as staging with the aeroidx_origin_looks_like_staging filter.
Known limitation: if AeroIDX is installed in a subdirectory (for example https://example.com/blog), only the site's origin (https://example.com) is sent — a visitor's browser only ever reports the origin, so this is what AeroIDX needs to authorize the site and route sign-in and email links back correctly; it also means those links land at your site's root rather than the subdirectory.
staging. subdomain, a temporary domain from hosts such as WP Engine, Kinsta, Pantheon or Cloudways, and localhost. It happens within about an hour, or sooner when an admin opens wp-admin, and you don't need to enter your API key again. A one-time notice says what moved.aeroidx_origin_looks_like_staging filter changes what counts as a staging address.aeroidx_sitemap_filters filter can adjust the filters sent with the sitemap request. The aeroidx_sitemap_include_mls filter still has the last word over the Sitemap card, so a site that turned the MLS feed off in code stays off.[aeroidx_widget] shortcode had no element to style, although the plugin's own documentation said they did. Every AeroIDX widget now sits inside .aeroidx-widget-mount.[aeroidx_market id="..."] shortcode, for dropping a single market into a page you already have.