> For the complete documentation index, see [llms.txt](https://docs.taptap3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taptap3d.com/integration-guides/search-visibility.md). # Search visibility SEO and answer-engine considerations for pages hosting inventory and ecommerce listing embeds. An iframe can display a listing, but the host page should not rely on the iframe alone to describe its content to search engines or answer systems. For the planned integration, the host should publish a useful HTML page of its own: a descriptive title, the approved item summary and a link to the canonical listing. This also gives visitors context when the iframe cannot load. ## Host page content Use the same approved facts in the page and the embed. If title, description, price or availability changes, update the host page too. Do not expose private record fields to improve search coverage. Keep stable URLs for objects. If an item becomes unavailable, decide whether its page remains a useful archive or should redirect; do not silently turn one item's URL into an unrelated item. ## Structured data Structured data must describe what the visitor can actually see and do. A displayed auction estimate is not a purchasable offer. Do not invent reviews, ratings, stock status or prices to populate a schema. Where a real commerce integration supports a purchase offer, its host owns the accuracy of the price, currency, availability and transaction link. Taptap3D's proposed listing contract does not currently provide a structured-data generator. ## Canonical URLs The proposed response supplies a `canonicalUrl` for the published listing. Use it for the fallback link. The host and publication service still need to agree on SEO ownership: an independent storefront product page is not automatically a duplicate that should canonicalise to the publication page. Adding an iframe does not establish a canonical relationship by itself. ## Documentation discovery These developer docs use descriptive headings, short answers, stable topic pages and explicit feature status. GitBook supplies the published site's sitemap and machine-readable documentation views. Machine-readable content helps readers and retrieval systems find the same facts. It does not guarantee search rankings, citations or inclusion in an AI answer. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.taptap3d.com/integration-guides/search-visibility.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 `build a script that syncs our docs to a CMS` 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.