WordPress has no equivalent of a menu-item-driven view, so FW Real Estate's front-end views are placed on ordinary WordPress pages using either the block editor or shortcodes. Both render exactly the same output — the blocks are a thin wrapper over the same server-side render.
A normal site needs three pages, plus a fourth if you publish agent profiles:
| Page | Block or shortcode to place | What it does |
|---|---|---|
| Properties | FW Real Estate — Listing block, or [fw_real_estate] |
The property listing |
| Property | Same block with type = item and no fixed property, or [fw_real_estate type="item"] |
The detail page every listing card links to |
| My Account | FW Real Estate — User Section block, or [fwre_usersection] |
Favourites, saved searches, comparison, the agent's property manager |
| Agents | FW Real Estate — Agents block, or [fwre_agents] |
The agent directory |
You do not need to register these pages anywhere in the plugin's settings. FW Real Estate finds them automatically by scanning your published pages for the relevant block or shortcode, and remembers what it found. You can rename a page, move it to a different URL, or translate it — property links keep working because the plugin re-discovers pages by their content, not by their address or title.
Two rules govern which page the plugin treats as the canonical detail page and the canonical account hub. Understanding them helps if a link ever points at the wrong place:
type="item" with no property ID specified. A page pinned to one specific property — for example, a featured-property landing page — is deliberately excluded from eligibility. Without this rule, that page would swallow every property link on the site.[fwre_usersection] with no section named. A page pinned to a single section, such as Favourites, is treated as a leaf of the account area, not as the hub that navigation flows through.In practice: leave the type="item" block or shortcode without an id attribute on your detail page, and leave [fwre_usersection] without a section attribute on your account page. Pages that deliberately target one property or one section remain fully functional — they simply do not become the site-wide destination for dynamic links.