All tools in this category Full tool catalog
Guide
Embedding tools for webmasters
Use lightweight pages under /embed/ to place the same client-side utilities on your site. Link visitors to the full tool page for localized UI, FAQ, and privacy notes.
All tools in this category Full tool catalog
Guide
Use lightweight pages under /embed/ to place the same client-side utilities on your site. Link visitors to the full tool page for localized UI, FAQ, and privacy notes.
Official iframe targets under https://salamyx.com/embed/... load the same browser-side tools with minimal chrome. The main site keeps SAMEORIGIN framing; only /embed/ is meant for third-party sites.
Use only these iframe src values for production embeds. Each full tool page remains the canonical document for SEO and assistants.
Production .htaccess in this repo sets Content-Security-Policy frame-ancestors * only for paths starting with /embed/. Other hosts should mirror that behavior.
For catalog metadata and automation, pair this with Tools API v1.
Embed pages are static HTML from salamyx.com. Your page loads our origin inside an iframe; follow your own cookie and analytics policies for third-party contexts.
Use the documented https://salamyx.com/embed/... URLs. Do not iframe the regular tool URL; it is intentionally not framed on third-party sites.
Listen for window message events where data.source === "salamyx-embed" and data.type === "resize", then set the iframe height from data.height.
Yes, when UX and security review are done per tool. This documentation page and the EMBEDDABLE_TOOL_ROUTES list in the repository stay the source of truth for the allowlist.
No. These tools still run in the visitor browser inside the iframe. The embed route only changes chrome and framing headers.
Keep the iframe pointed at salamyx.com so users see the real origin. Do not misrepresent the tool as your own software.