Platform Guides

Universal setup pattern

1. Add the website or public staging URL in the dashboard.
2. Verify ownership with DNS or the provided meta tag.
3. Run a crawl and confirm important pages were indexed.
4. Add widget.js to the site-wide head or custom-code area.
5. Create a /search-results page and add results.js there.
6. Add data-fs-* attributes to your search form and result template.

Webflow-style sites

Put the Search Bar Script in site-wide custom code so it loads on every page. Put the Results Page Script in page-level custom code for the search results page. For CMS collections, confirm that collection pages are published and included in the sitemap.

Framer-style sites

Use custom code areas for scripts and create a normal public results page. Test on the published site, not only an editor preview, because private previews and editor-only states are not reliable crawl targets.

WordPress-style sites

Add scripts through a trusted header/footer code plugin or theme area. Confirm caching plugins do not remove script attributes. Keep important posts, pages, and custom post types visible in the public sitemap.

Shopify-like sites

Add scripts through theme code or app-provided custom-code areas. Be deliberate about which product, collection, policy, and help pages should be indexed. Exclude checkout and account pages.

Custom React or Next.js sites

Add scripts through the app layout or a route-specific head implementation. Ensure public content is server-rendered or visible in the initial HTML if you expect the crawler to index it.

What not to crawl

• Localhost, private previews, or password-protected staging pages.
• Authenticated dashboards, account pages, checkout pages, or admin routes.
• Pages that only render meaningful text after client-only JavaScript completes.

Next steps

• Install the scripts
• Audit crawl readiness
• Troubleshoot platform-specific issues