Configuration
Set your canonical host, redirects, response signatures, and how to identify Encited's own traffic. Mostly set once, when you connect a site.
Primary domain redirect (apex vs www)
Pick one canonical host and 301-redirect the other, so search engines don't index two copies of your site.
301 redirects
Forward old paths to new ones with glob patterns and capture placeholders, without losing ranking signal.
Detect Encited visits
Every way to identify Encited traffic: the in-page marker, the render token your firewall can match, and the audit user agent.
Custom render user agent
Replace the Chrome user agent our renderer sends with your own value, for firewall allowlists and user-agent-based site logic.
Verifying response signatures
Confirm rendered HTML really came from Encited and wasn't altered in transit, using the RFC 9421 HMAC signature on every signed response.
MCP server: connect your AI assistant
Connect ChatGPT, Claude, Cursor, or Codex to your Encited account over MCP to read analytics and start audits and workflows.
SAML SSO setup
Set up SAML 2.0 single sign-on with Google Workspace or Okta, verify your email domain, and enforce SSO for your team.
Ignored paths
Keep some pages out of pre-rendering. Crawler requests to an ignored path go to your site unchanged.
Custom response headers
Add caching headers to matching paths on your site, such as Cache-Control on your assets.