# Another custom documentation issue

**URL:** <https://forum.cursor.com/t/another-custom-documentation-issue/54686>\
**Category:** Help\
**Created:** [February 25, 2025, 12:38pm UTC](https://forum.cursor.com/t/another-custom-documentation-issue/54686 "2025-02-25T12:38:56Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrismv48](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/chrismv48/32/28292_2.png) [@chrismv48](https://forum.cursor.com/u/chrismv48)\
**Post date:** [February 25, 2025, 12:38pm UTC](https://forum.cursor.com/t/another-custom-documentation-issue/54686/1 "2025-02-25T12:38:56Z")

</div>

Hi everyone. I’ve been trying to get Cursor to reference custom docs that are publicly hosted on the web, but I get the “0 pages indexed” issue no matter what I try. I even followed the suggestion of generating a sitemap via [xml-sitemaps.com](http://xml-sitemaps.com) and referencing that to no avail.

Next, I thought maybe I could create a cursor rule that includes a site directory for the docs but when referencing the rule and asking about the docs, Cursor seems to be unable to access the URLs directly and instead hallucinates the answer. Finally, I tried downloading all the docs to markdown format and just throwing that into a rule but that just gave a context limit error because of the size of the markdown.

I love Cursor, but this issue is pretty frustrating and I hope they can fix it. In the meantime, can anyone suggest any workarounds?

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [February 25, 2025, 5:31pm UTC](https://forum.cursor.com/t/another-custom-documentation-issue/54686/2 "2025-02-25T17:31:06Z")

</div>

Hey, can you share the link to the documentation?

---

<div class="post-metadata">

**Author:** ![chrismv48](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/chrismv48/32/28292_2.png) [@chrismv48](https://forum.cursor.com/u/chrismv48)\
**Post date:** [February 25, 2025, 6:07pm UTC](https://forum.cursor.com/t/another-custom-documentation-issue/54686/3 "2025-02-25T18:07:11Z")

</div>

> **[Pit Viper](https://pitviper.turquoise.health/)**
>
> Documentation and CSS framework for Turquoise Health's design system, Pit Viper.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [February 27, 2025, 6:47am UTC](https://forum.cursor.com/t/another-custom-documentation-issue/54686/4 "2025-02-27T06:47:32Z")

</div>

cc @danperks

---

<div class="post-metadata">

**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\
**Post date:** [March 3, 2025, 9:34pm UTC](https://forum.cursor.com/t/another-custom-documentation-issue/54686/5 "2025-03-03T21:34:52Z")

</div>

![Screenshot 2025-03-03 at 21.34.17](https://us1.discourse-cdn.com/cursor1/original/3X/4/a/4a9d945483d597b23b3295b70dd65ad0b2b18304.png)

Unfortunately, it appears the docks have some kind of anti-bot protection behind them, so they are not scrapable yet by Cursor.

We are hoping to improve this soon so we can add support for these kinds of websites!

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [June 18, 2026, 10:31am UTC](https://forum.cursor.com/t/another-custom-documentation-issue/54686/6 "2026-06-18T10:31:27Z")

</div>