> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/investing/market-valuation-and-on-chain/shiller-pe-ratio/faqs.md).

# FAQs

Shiller PE Ratio FAQs

<details>

<summary>Where does the data for this ratio come from?</summary>

The tool pulls the official CAPE10 series from Multpl, which is based on the research of Yale Professor Robert Shiller.

</details>

<details>

<summary>Why is the "Historical Mean" set to 17.0?</summary>

The long-term average of the Shiller PE since 1881 is approximately 17.0. Some investors prefer to use a higher mean (e.g., 19-20) for the post-WWII era.

</details>

<details>

<summary>Does a high Shiller PE mean the market will crash immediately?</summary>

No. Valuations are not timing tools; markets can stay overvalued for years. It is a measure of long-term risk and future return expectations.

</details>

<details>

<summary>What is the difference between Monthly and Yearly resolution?</summary>

Monthly provides more tactical data points, while Yearly is better for high-level secular trend analysis and historical backtesting.

</details>

<details>

<summary>How should I interpret the "Deviation" stat in the dashboard?</summary>

It shows how far the current ratio is from the Historical Mean. A +50% deviation suggests the market is significantly stretched relative to its historical norm.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.candelacharts.com/investing/market-valuation-and-on-chain/shiller-pe-ratio/faqs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
