Files
Ethan Palm 3dc3852b7a SEO descriptions (#4028)
* Improve SEO descriptions across 47 pages

Curated descriptions from two bot-generated PRs (#3908, #3949),
selecting the best approach for each page:
- Added missing title and description frontmatter to 10 API reference pages
- Benefit-focused descriptions for integration pages (not implementation-heavy)
- Accurate REST-aligned titles for API endpoints (Export, List, Trigger, etc.)
- Expanded short descriptions to 50–160 character range throughout

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* copyedit

* Update custom-domain.mdx

* Fix analytics API page titles to match spec summaries

"Export" was inaccurate — spec uses "Get" for both endpoints.
Also updated descriptions to use "Retrieve" for consistency.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-04 16:46:28 -08:00

28 lines
558 B
Plaintext

---
title: "Clearbit"
description: "Enrich visitor data with Clearbit to identify companies and users visiting your documentation."
keywords: ["Clearbit integration", "user enrichment", "visitor intelligence", "public API key"]
---
Add the following to your `docs.json` file to send analytics to Clearbit.
<CodeGroup>
```json Analytics options in docs.json
"integrations": {
"clearbit": {
"publicApiKey": "required"
}
}
```
```json Example
"integrations": {
"clearbit": {
"publicApiKey": "pk_1a1882"
}
}
```
</CodeGroup>