# Perplexity Search / Sonar API not picking up updated structured metadata

**URL:** <https://community.perplexity.ai/t/perplexity-search-sonar-api-not-picking-up-updated-structured-metadata/6664>\
**Category:** General\
**Tags:** sonar\
**Created:** [November 16, 2026, 4:26pm UTC](https://community.perplexity.ai/t/perplexity-search-sonar-api-not-picking-up-updated-structured-metadata/6664 "2026-11-16T16:26:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![danielcarter890](https://avatars.discourse-cdn.com/v4/letter/d/df705f/32.png) [@danielcarter890](https://community.perplexity.ai/u/danielcarter890)\
**Post date:** [November 16, 2026, 4:26pm UTC](https://community.perplexity.ai/t/perplexity-search-sonar-api-not-picking-up-updated-structured-metadata/6664/1 "2026-11-16T16:26:24Z")

</div>

Hello all,

I am experimenting with how Perplexity Search and Sonar API (sonar-pro) fetch and summarize [live content](https://tiktokio.cloud) from my website.

Despite the fact that PerplexityBot is not disallowed from my robots.txt file and the webpage has semantic HTML and JSON-LD Schema data, any query made to tools/sections on my website either gives an out-of-date cached snippet or fails to fetch the interactive components of the webpage completely.

For people optimizing their websites for Perplexity Bot or making queries on live URLs via Sonar API:

Does PerplexityBot evaluate client-side JavaScript or only static HTML content?

Is there any llms.txt file or structured meta tag that can help in faster indexing by Perplexity?

---

<div class="post-metadata">

**Author:** ![discourse\_ai\_spam](https://avatars.discourse-cdn.com/v4/letter/d/c68b51/32.png) [@discourse\_ai\_spam](https://community.perplexity.ai/u/discourse_ai_spam)\
**Post date:** [November 16, 2026, 4:26pm UTC](https://community.perplexity.ai/t/perplexity-search-sonar-api-not-picking-up-updated-structured-metadata/6664/2 "2026-11-16T16:26:27Z")

</div>

Unlisted on November 16, 2026, 4:26pm UTC



---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex001/uploads/sonar1/original/2X/2/2e68ab44b742a4f735b6576e92fa665ddde46b14.png) [@system](https://community.perplexity.ai/u/system)\
**Post date:** [November 16, 2026, 4:48pm UTC](https://community.perplexity.ai/t/perplexity-search-sonar-api-not-picking-up-updated-structured-metadata/6664/3 "2026-11-16T16:48:04Z")

</div>

Listed on November 16, 2026, 4:48pm UTC



---

<div class="post-metadata">

**Author:** ![aicost\_tools](https://avatars.discourse-cdn.com/v4/letter/a/b5e925/32.png) [@aicost\_tools](https://community.perplexity.ai/u/aicost_tools)\
**Post date:** [November 17, 2026, 10:10am UTC](https://community.perplexity.ai/t/perplexity-search-sonar-api-not-picking-up-updated-structured-metadata/6664/4 "2026-11-17T10:10:39Z")

</div>

I’d plan as if the crawler only sees your static HTML: if the tool sections are built client-side, server-render or pre-render at least the text and the key numbers, and keep the JSON-LD in the initial response, not injected by JS. I haven’t seen Perplexity document llms.txt as an indexing signal, so I wouldn’t count on it. Also check robots.txt and your WAF for both PerplexityBot and Perplexity-User, since a CDN bot rule can block one quietly. (Disclosure: I edit aicost.tools.)
