Cache behavior
- Structured AI responses are edge-cached per URL per crawler type
- Human traffic is always proxied live to your origin, not cached through Appear
- Cache TTL is configurable per domain in dashboard settings
- Cache is automatically invalidated on manual sync or content update webhook
Keeping content fresh
- Trigger a manual sync from the dashboard any time your content changes significantly
- Set up a webhook from your CMS to auto-sync when you publish new content
- Appear will flag pages where the cached AI response is older than your configured freshness threshold
- The sync rate limit is 2 minutes per domain to protect origin servers
Manual sync
When your site content changes, click Sync in the dashboard to regenerate all AI response profiles. The sync pipeline re-reads your published pages, regenerates structured content, and pushes the updated profiles to the edge cache. The entire process typically completes in under two minutes.
Webhook integration
For automated workflows, configure a webhook from your CMS (WordPress, Webflow, Shopify, or any system that supports outgoing webhooks) to notify Appear when content is published. Appear will automatically trigger a sync for the affected domain. Webhook endpoint details are available in your dashboard settings.