Getting Started with FAIND
This is the short version of what you do to go live with FAIND and how to keep your Knowledge Graph healthy afterwards. Setup is a DNS record and a one-line snippet — a few minutes of work, with no migration and no redesign. For the full step-by-step (including a Google Tag Manager option and a copy-paste privacy paragraph for your own policy), see the Implementation Guide.
1) Set up (two steps)
- Add the CNAME record your dashboard shows, so your Knowledge Graph is served on the subdomain FAIND provides. (Or use the FAIND-hosted address with no DNS change at all.)
- Install the one-line snippet in your site's
<head>— directly in your template, or via Google Tag Manager (a Custom HTML tag set to fire on All Pages).
The moment both verify, your Knowledge Graph build starts automatically and we email you when it is live. Full detail is in the Implementation Guide.
2) What to do
- Keep the snippet installed. It keeps your Knowledge Graph in sync when your pages change, and it measures AI-driven visits. Leaving it in place is what keeps the graph current.
- Mention FAIND in your own privacy policy. A ready-to-paste paragraph is in the Implementation Guide — it describes the snippet and the processing for your site's visitors.
- Classify it correctly in your consent tool (if you use one). The FAIND snippet is strictly necessary / technical: it sets no cookies and stores nothing on the visitor's device, so it needs no consent entry. Background: Snippet Data Statement.
3) What not to do
- Don't block or break the snippet — for example via a strict Content-Security-Policy, a consent tool, or a tag-manager rule that stops it from running. If it can't run, your graph can't stay current.
- Don't disallow AI crawlers in your
robots.txtfor the pages you want represented (for example GPTBot, ClaudeBot, Google-Extended, PerplexityBot). - Don't remove the snippet mid-term to “pause” — that silently stops updates. To stop the service, cancel your plan; we then take the graph down and delete the associated artifacts (see the Data Processing Agreement).
4) Privacy & consent, in one line
The snippet sets no cookies and stores nothing on your visitors' devices, so it triggers no consent requirement under §25 TDDDG — a note in your privacy policy is enough. What it processes, the legal basis and retention are set out in the Snippet Data Statement, and FAIND acts as your processor under the Data Processing Agreement.
5) Help & further reading
- Implementation Guide — full setup, the GTM option, robots guidance, and the copy-paste privacy blurb.
- Snippet Documentation — what the snippet does and its safety posture.
- Snippet Data Statement — the data-protection view for your DSB.
- Data Processing Agreement — the Art. 28 processor terms; a signature-ready PDF (pre-signed by us, with fillable fields) is available for your records / your DSB.
Questions about setup or data protection? Email privacy@getfaind.com, or reach out to your account contact.