> For the complete documentation index, see [llms.txt](https://docs.overflowcms.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overflowcms.com/faq.md).

# FAQ

## FAQ

**Is client-side rendering bad for SEO?** Listing pages generally index fine — crawlers do execute JavaScript. If you need guaranteed, fast-indexing pages with full control over meta/OG tags and structured data, that's what the upcoming SEO Engine tier is for.

**What happens if I cancel?** You can export your content — collections and items as JSON, media as files — at any point, including after cancelling. Cancelling stops billing at the end of the current period; your sites and content aren't deleted, but you'll need an active plan again to create new sites.

**Does it work with my Webflow interactions and GSAP/ScrollTrigger?** Yes. The embed script dispatches `oc:rendered` (once per list load) and `oc:item-rendered` (once per cloned item) as real DOM `CustomEvent`s, specifically so you can re-trigger interactions or animate newly-inserted nodes. See Rendering Events & Animations.

**Is a reverse proxy to my domain allowed by Webflow?** Webflow documents self-managed reverse-proxy setups for custom code/CMS integrations — you don't need an Enterprise plan to route a path like `/blog/*` elsewhere. This is the mechanism the upcoming SEO Engine tier will use for path-based setups.

**Can clients edit content without full Webflow Designer access?** Yes — that's the point of the separate editor UI. Invite them into your workspace with the `editor` role (see Team & Roles); they get drafts, scheduling, and inline image uploads without a Webflow seat.

**What's SEO Engine?** A plan tier in development that will add fully server-rendered pages under your own domain for content that needs to rank — see SEO Engine for current status. Everything else in these docs is available today on Starter or Pro.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.overflowcms.com/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.