> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/appendix/website-integration/connecting-to-your-listing-pages.md). # Connecting to your Listing Pages Rechat's email marketing templates, by default, will link emails back to Rechat's listing page. This can be configured to use your brokerage website's listing page. To make this happen, your website must be able to load a listing page using an MLS number. Imagine if your website is GreenRealty.com. We can configure Rechat to open up your website's listing page given an mls number by opening up a url like `greenrealty.com/property/`. The URL structure doesn't need to be exactly the same. But it needs to work given an mls number. Some good examples: ``` https://greenrealty.com/ https://greenrealty.com/mls/ https://greenrealty.com/id/ ``` It is very common for listing pages to have a structure like the following: `greenrealty.com/listing/12345/6543-s-barry-drive` In this example, `12345` is the MLS number, but the listing address is also exposed in the URL (`6543-s-barry-drive`). Rechat cannot connect to this type of url because the way each website formats the address may be different. In this situation, you do not need to change your URL structure. You can keep it in place and create an internal redirect from `greenrealty.com/listing/` to the full listing address. Most real estate website vendors have this mechanism built into their websites. Once you determine your URL structure, send it to your customer success manager so we can configure it. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.rechat.com/appendix/website-integration/connecting-to-your-listing-pages.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.