> For the complete documentation index, see [llms.txt](https://synap.ac/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synap.ac/docs/platform/portal/seo-and-legal-links.md). # SEO and legal links Search engine optimisation (SEO) metadata controls how publicly accessible portal pages may be represented by search engines and link previews. Legal links control the Terms and Conditions and Privacy Policy shown in the portal footer. ### Search metadata Where Branding is included in the portal's entitlements, administrators can set: * **Title:** the heading intended for a search result; * **Description:** supporting text intended to appear below the result heading; and * **Search image:** the image associated with supported previews. Search engines decide whether and how to use supplied metadata, so an update is not guaranteed to appear immediately or verbatim. ### Legal links Terms and Conditions and Privacy Policy are configured in **General settings**. Each can use Synap's default, a custom URL, a Library Note, or be hidden. The entire student footer can also be hidden. Use durable URLs or clearly owned Notes. Confirm that the selected content is accessible to logged-out users where required by your registration flow. Hiding a product link does not remove an organisation's legal obligations. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://synap.ac/docs/platform/portal/seo-and-legal-links.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.