Hi everyone,
I’m trying to make the full Freshdesk Solutions/FAQ page visible directly on my website. I have enabled the solutions option in the Freshdesk widget, but I don’t want it to appear only as a small popup — I want users to see the complete FAQ content embedded into a full page.
Some older online suggestions mention using an iframe, but it seems Freshdesk no longer allows iframe embedding due to security restrictions.
Has anyone implemented a solution to embed the full Freshdesk FAQ/Solutions page on an external site?
-
If so, what approach did you use?
-
Did you use the Freshdesk API to pull articles and render them on your site?
-
Are there any examples or best practices you’d recommend?
Thanks in advance!
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi there,
It looks like Freshdesk pages are now sent with security headers that prevent iframe embedding (X-Frame-Options / CSP). So even though older posts mention iframes, that approach seems to be blocked today and not something you can enable with a setting. That lines up with what you’re seeing.
What people seem to do instead falls into two practical directions. One is using a custom support domain, like support.yoursite.com, and letting the full Freshdesk portal live there. It’s not embedded inside your page, but visually and UX-wise it still feels like part of your site, and you don’t lose built-in search, navigation, or article management.
Hope that this helps!
Hi there,
You’re right, iframes are often blocked these days because of security headers like X-Frame-Options and CSP, so they’re usually not a great long-term solution.
The most common and SEO-friendly approach is to rebuild the FAQ as a real page on your site. If the content lives somewhere else, you can fetch it via an API and render it on your own pages, either server-side or client-side. That way search engines can index it properly and you stay in control of the layout and performance.
If you’re hosting on DigitalOcean, a typical setup is to have a small API or static content source and then render the FAQ in your app or site at build time or request time. On App Platform, this works well with static sites or frameworks like Next.js that support server-side rendering. https://docs.digitalocean.com/products/app-platform/
If the FAQ content doesn’t change often, pulling it at build time is usually the simplest and fastest option. If it changes more frequently, fetching it on the server per request (or with short caching) is a good middle ground.
Another option is to keep the FAQ as a separate site or subdomain and just link to it clearly from your main site. That avoids embedding issues entirely and is still SEO-friendly if done right. https://docs.digitalocean.com/products/droplets/
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.