Platform Guides

Appear works at the DNS layer. There are no platform-specific plugins or code changes required. The notes below cover common DNS configurations for each platform.

Framer

In your Framer project settings, ensure custom domain is configured. Then add the Appear CNAME in your external DNS provider (not inside Framer's domain settings). Framer sites are typically JavaScript-rendered, making adaptive rendering especially impactful.

Webflow

Add the CNAME in your external DNS provider, not in Webflow's hosting panel. Webflow does support CNAME records for custom domains, but the Appear CNAME should be added at the DNS provider level for correct routing.

WordPress

Works with any WordPress hosting (WP Engine, Kinsta, SiteGround, self-hosted). Add the CNAME in your DNS provider. Appear operates as a transparent proxy. Your WordPress admin, plugins, and caching layers are unaffected.

Shopify

Shopify custom domains use CNAME records pointing to shops.myshopify.com. Replace the Shopify CNAME value with the Appear edge target, then add Shopify's endpoint as your origin in the Appear dashboard. This routes AI crawlers through Appear while human traffic passes through normally.

Next.js

Compatible with Vercel, Cloudflare Pages, and self-hosted deployments. Add the CNAME in your DNS provider. Works with App Router, Pages Router, and both static and server-rendered deployments. Appear supplements Next.js's own rendering. It does not replace it.

Custom / other

Any stack that can be routed via DNS supports Appear. If your hosting provider allows CNAME records on the root domain (CNAME flattening / ALIAS records), you can point apex domains through Appear. Contact support if you need help with your specific configuration.