> For the complete documentation index, see [llms.txt](https://chartschool.stockcharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chartschool.stockcharts.com/table-of-contents/technical-indicators-and-overlays/technical-indicators/weighted-close.md).

# Weighted Close

## What Is the Weighted Close Indicator?

The Weighted Close indicator helps to identify a prevailing trend. It's an average of a period’s high, low, and close, with the close receiving double weight given its importance of mark-to-market. Weighted Close is plotted as a line that can be displayed in a separate panel or overlaid on the price chart, similar to the [Typical Price indicator](/table-of-contents/technical-indicators-and-overlays/technical-indicators/typical-price.md).

## How To Calculate the Weighted Close Indicator

The Weighted Close averages the high, low, and close but gives more weight to the closing price. The formula is as follows:

$$
Weighted\nobreakspace Close = ((High + Low + (Close \* 2)) / 4
$$

There are several ways to apply the Weighted Close to your trading. You can use it as a standalone indicator or with other trend-following indicators. For example, if you're using the Weighted Close with a [moving average](/table-of-contents/trading-strategies-and-models/trading-strategies/moving-average-trading-strategies/how-to-trade-price-to-moving-average-crossovers.md), consider it a buy signal when it crosses above the moving average. Conversely, when the Weighted Close crosses below a moving average, consider it a sell signal.


---

# 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://chartschool.stockcharts.com/table-of-contents/technical-indicators-and-overlays/technical-indicators/weighted-close.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.