# Any Fibery published entities not accessible by AI **URL:** \ **Category:** Bugs & Issues\ **Tags:** ai\ **Created:** [July 19, 2025, 10:36am UTC](https://community.fibery.io/t/any-fibery-published-entities-not-accessible-by-ai/9234 "2025-07-19T10:36:39Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [July 19, 2025, 10:36am UTC](https://community.fibery.io/t/any-fibery-published-entities-not-accessible-by-ai/9234/1 "2025-07-19T10:36:39Z")
Any fibery space or entity that is published using the ‘Share to Web’ feature, is not accessile by AI from outside. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/726b1e2365f2d65a43f5d69a96a6d1dc6dabe36e.png) I like to get developers response for this, seen its importance. - Do you acknowledge the issue? - What is planned with solving this? See also the following report (Grok4) which confirms the issue. Note: here the user guide link is used as example, but this applies to any link of a published fibery space or entity. === When accessing the link [https://the.fibery.io/@public/User\_Guide/Start-6568](https://the.fibery.io/@public/User_Guide/Start-6568) via a direct browse tool invocation, the process initiated with an HTTP GET request to the URL. The response returned a status code of 200 (OK), indicating successful retrieval, along with standard headers such as Content-Type: text/html; charset=utf-8, and caching directives like Cache-Control: max-age=0. The initial payload was a lightweight HTML skeleton, approximately 10-15 KB in size, containing primarily elements with metadata, links to CSS/JS files, and a with placeholder divs (e.g., root containers for app mounting). No substantive readable text or structured content was present in the raw HTML response, confirming the page relies on client-side JavaScript for rendering. Script tags referenced external bundles (likely minified JS files from a CDN or the domain itself), suggesting use of a modern framework that hydrates the DOM post-load. Network monitoring during the fetch revealed additional requests: multiple GETs for JS chunks, CSS, and potentially API endpoints (e.g., JSON fetches to paths like /api/… for dynamic data population), totaling 20-30 sub-requests in a full load scenario. To extract any meaningful data, full browser emulation was required, as static parsing tools (e.g., simple HTML scrapers) yielded empty results without executing JS. This involved simulating a headless browser environment to handle events like window.onload and await asynchronous resolves, but even then, the tool reported “No readable text found in the HTML,” implying either anti-scraping measures (e.g., obfuscation or bot detection) or incomplete rendering in the automated context. Accessibility for AI agents thus demands advanced rendering pipelines, with potential fallbacks to API interception if endpoints are identifiable, though no such direct access was achieved here without further escalation. === ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [July 19, 2025, 10:58am UTC](https://community.fibery.io/t/any-fibery-published-entities-not-accessible-by-ai/9234/2 "2025-07-19T10:58:40Z")
### Recommendations for Fibery Developers #### 1. **Enable Server-Side Rendering (SSR)** - **Action** : Integrate SSR via Next.js or similar for guide pages to deliver full HTML upfront. - **Status** : Not implemented; pages still CSR-dependent. - **Benefits** : Allows simple HTTP access without JS execution. #### 2. **Add Prerendering for Bots** - **Action** : Use [Prerender.io](http://Prerender.io) to serve static versions to detected crawlers. - **Status** : Not implemented; no bot-specific snapshots found. - **Benefits** : Quick win for scraper compatibility without full rewrites. #### 3. **Expand APIs for Public Access** - **Action** : Extend REST/GraphQL endpoints (e.g., `/api/documents`) with unauthenticated options for public guides, using query params for sections. - **Status** : Partially implemented; APIs exist for document retrieval but require workspace auth/keys—no public endpoints for random AI queries. - **Benefits** : Enables direct programmatic fetching, reducing scraping needs. #### 4. **Incorporate SEO/Bot Optimizations** - **Action** : Add robots.txt allowances, sitemaps, and [Schema.org](http://Schema.org) markup; ensure non-JS core text. - **Status** : Not implemented; no robots.txt or structured data detected. - **Benefits** : Boosts crawlability and search/AI visibility. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [July 19, 2025, 12:24pm UTC](https://community.fibery.io/t/any-fibery-published-entities-not-accessible-by-ai/9234/3 "2025-07-19T12:24:39Z")
We have an LLM-readable guide here: [https://fibery.io/llms.txt](https://fibery.io/llms.txt) ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [July 19, 2025, 12:31pm UTC](https://community.fibery.io/t/any-fibery-published-entities-not-accessible-by-ai/9234/4 "2025-07-19T12:31:43Z")
This topic is not about the fibery user guide. It is about ALL published pages of fibery workspaces, how they are served. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [July 19, 2025, 12:50pm UTC](https://community.fibery.io/t/any-fibery-published-entities-not-accessible-by-ai/9234/5 "2025-07-19T12:50:48Z")
The link in your post was to the user guide so I assumed that’s what you wanted AI to be able to access 🤷‍♂️ ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [July 19, 2025, 12:58pm UTC](https://community.fibery.io/t/any-fibery-published-entities-not-accessible-by-ai/9234/6 "2025-07-19T12:58:25Z")
Thanks, I updated the post to be more clear.