Breaker Block: The Question Four of Five Guides Never Answer

A breaker block is not a formation anyone can point to on a blank chart. It is a name applied to a zone that was already drawn, after that zone failed. The drawing does not change. What changes is the label, and the label depends entirely on a rule about what counts as failure.

That rule is where the published explanations of the term stop agreeing with each other, and it is also the part a reader most needs settled.

Key takeaways

  • The term renames an existing zone rather than identifying a new one, so nothing visible at the moment of drawing tells you which name it will end up with.
  • Google surfaces the breaker-versus-mitigation question in both its People Also Ask block and its autocomplete, and only one of the five readable guides addresses it at all.
  • The invalidation rule the whole construction depends on has at least three open choices, and the five guides settle them differently.
  • The page ranking first for the term gives an identification rule that contradicts the construction it has just described.
  • MetaTrader 5 ships no standard indicator of this kind, so every automatic detector is a third-party script that has hard-coded the unsettled choices for you.
  • No win rate, backtest result or false-signal rate appears in any of the five guides, and none appears here.

The Same Price Area, Renamed by What Happened Next

Start with the zone before it acquires the name. A trader marks the final counter-direction candle sitting immediately ahead of a fast one-sided move, which is the same rectangle a supply or demand zone puts at the origin of a move. While price turns away from it, it keeps whatever name it was given.

Then price goes through it. Under the rule that drew it, the zone is finished: the level it was supposed to defend did not hold. The breaker vocabulary keeps the rectangle instead of erasing it, reverses the direction it is expected to work in, and waits for price to come back to it from the other side.

A zone that was supposed to cap price and failed is now expected to support it. A zone that was supposed to support price and failed is now expected to cap it. Under older vocabulary that role reversal is simply a broken level being retested from the far side.

So the word identifies a state, not a shape. Two rectangles drawn identically on the same chart carry different names depending only on what price did afterwards, which means the name cannot be assigned at the moment of drawing and can be revised later by events.

Whether the story underneath the original zone holds up is a separate argument, and the page on what the order block claim actually rests on works through the evidence for it. This page takes no position on that and deals only with what the relabelling adds and what it leaves open.

Breaker or Mitigation Block: Four of Five Guides Never Say

Two comparisons are available to a reader meeting this term. One is against the order block it used to be. The other is against the mitigation block, the neighbouring term for a zone that also failed and was also kept.

Google surfaces the second comparison directly. It appears in the People Also Ask block for the term and again in the autocomplete suggestions, so it is a question people are demonstrably typing.

Six guides were retrieved for this page and five could be read. The literal string for the neighbouring term appears nine times in one of them and not once in the other four, every one of which discusses breaker blocks at length. Four of the five compare the term against the order block instead.

The result is lopsided. The comparison a reader could have worked out unaided, since one term is openly described as the other after a failure, is answered five times over. The comparison that actually needs an authority is answered once.

What the single guide that addresses it offers is a separation by liquidity: it treats the breaker form as the one where the move that broke the zone first ran past a prior swing high or low, and the other form as the one where no such run occurred. That is a coherent distinction. It is also unverifiable, because there is no second statement of it to check it against and no document of record to appeal to.

What a reader arrives wantingGuides that address it, of fiveWhat that leaves
A definition of the termFiveWell covered, and the definitions broadly match
How it differs from an order blockFourThe easier half, answered repeatedly
How it differs from a mitigation blockOneA single unverifiable account of the harder half
When the zone stops being validFive, and no two alikeThe rule the whole construction rests on is open
Who defined the termOne, with no source givenAn attribution that cannot be followed
Any measured rate of success or failureNoneNothing to test a claim against

Read the middle rows together and the shape of the coverage is plain. Effort has gone where the answer was easy, and the two rows that would let a reader use the term precisely are the two that nobody has filled in.

No Two Guides Agree on When a Block Is Invalidated

Everything above hangs on one event. The zone becomes a breaker only because it was invalidated, so a reader cannot apply the term at all without knowing what invalidation is.

Setting the five accounts side by side, the rule turns out to carry at least three separate choices, and each guide settles them without noting that a choice was made.

The first is which price event counts. A wick through the zone and a candle closing beyond it are different events, and they can be several bars and a good deal of range apart.

The second is which boundary counts. A zone has a near edge and a far edge, and a rule written against one of them marks a zone at a point where a rule written against the other has not triggered yet.

The third is what has to break. Some accounts require the rectangle itself to be violated. Others require the swing structure around it to give way, which is a separate definition with its own disagreements about the trigger and can happen well away from the zone.

Three binary choices allow eight combinations before anything else is varied, and the five guides do not converge on one. That is not a debate about interpretation. Two traders using the same word are marking different rectangles at different moments on the same chart.

The practical consequence lands on testing. A result reported for breaker blocks is a result for whichever combination the tester chose, and it cannot be compared with anyone else’s unless both rules are written out in full. The same trap sits under any rule built on a level failing and then holding again.

A different objection to these levels exists and is not the one made here: that a zone is only counted as valid once the outcome is known. That argument is made in full on the smart money concepts page. This section makes a narrower and more checkable point, which is that the rule differs between sources before any outcome is considered.

The Highest-Ranked Definition Contradicts Its Own Logic

The page currently ranking first for the term describes the construction correctly and then gives an identification rule that does not follow from it.

Take the construction on its own terms. A bearish breaker is a zone expected to cap price. It can only be the remains of a zone that was expected to hold price up and failed, because that is the failure the reversal of role is built on. A zone that was already expected to cap price and did so has not flipped, and there is nothing to rename.

The rule as written points at the wrong side. It describes the invalidated block as the bearish one, where the construction in the paragraphs above it requires the invalidated block to be the bullish one. Applied literally, it marks zones that never reversed role at all.

A reader has no way to settle this. On an indicator the platform reference states the calculation and any page that disagrees with it is simply wrong. Here there is no reference, so the most-read statement of the definition is also the one a beginner is most likely to copy.

The error is worth naming precisely rather than dismissing the page. Everything else on it is consistent, and the fault is one clause in one rule. On a term whose entire difficulty is the definition, one clause is enough.

Nothing Defines This Term, and the Absence Is Checkable

Absence is a hard thing to demonstrate, so it is worth doing it by measurement rather than assertion.

Across the five readable guides, the phrases a reader would need in order to be warned appear nowhere. No standard, not standardised, not standardized, who defined, synonym and interchangeable all return zero occurrences across all five files. Every one of them teaches the method as settled.

One guide names an originator for the approach and quotes him, with no source given for the attribution. A second carries a disclaimer stating that it does not endorse that originator, and then teaches the method in full anyway. Those two facts sit in different documents and neither acknowledges the other.

Platform documentation gives the same answer from a different direction. The MQL5 Reference list of technical indicator functions for MetaTrader 5 holds thirty-nine entries, one of which is the loader for custom indicators, and none of them concerns a breaker block, an order block or a mitigation block. The platform ships no such tool, so it publishes no such calculation.

That is the contrast with an indicator. A reader who wants to know what a moving average does can open a platform reference and read the formula. A reader who wants to know what a breaker block is has five guides, one attribution nobody can follow, and no document of record.

Whether any exchange, regulator or standards body defines this family of terms at all is the broader question, and the page on the gap this term is most often paired with shows the same absence producing three competing definitions of a single word. The smart money concepts page settles the general point for the whole vocabulary.

What a Detector Decides on Your Behalf

Because no platform ships this as a standard tool, every set of automatically marked breaker blocks comes from a script somebody wrote.

A script cannot leave anything open. It has to commit to a wick or a close, to a near edge or a far edge, and to the rectangle or the surrounding structure, because code that does not decide does not run. The unsettled choices from the section above are therefore settled inside it, silently, by its author.

Two further decisions arrive with it. A swing lookback fixes what counts as the prior high or low that the sweep must run past, and a lifetime rule fixes how long an unretested zone stays on the chart before it is dropped. Neither appears in any of the five guides.

The result is that two detectors on the same chart will mark different zones, and both will look authoritative. Boxes drawn by software carry a precision the underlying definition does not have.

The practical move is to read the input list before trusting the output. In the absence of a document of record, a script settings panel is the most complete definition available, and it applies to that script alone.

Which Figures This Page Does Not State, and Why

No performance figure appears anywhere above. That absence was chosen, and the reasoning behind it is worth setting out plainly.

The five guides were searched for one. There is no win rate, no backtest result and no false-signal rate in any of them; success rate and win rate return zero occurrences across all five files.

Numbers do appear in them, and they are of a different kind: reward-to-risk ratios and per-trade risk percentages, printed without a source on every page that prints one. Where a guide gives a number that no official document backs, this page gives nothing.

There is also nothing to verify such a figure against. No exchange publishes outcomes for a chart pattern, and the one class of document that could at least fix the calculation, a platform reference, does not cover this tool at all.

A reader who wants a rate has one route left, which is to write the rule out in full, including all three choices above, and to measure it on their own data. Any other number is somebody else selecting the examples.

Frequently Asked Questions

What is a breaker block in trading?
It is a zone that was first marked as an order block and then traded through. The rectangle is kept rather than erased, and the direction it is expected to work in is reversed, so a level that failed to cap price is watched as support and a level that failed to support price is watched as resistance.

How does a breaker block differ from an order block?
Only by what happened after the zone was drawn. An order block is a zone that has not been violated. A breaker block is the same zone after price went through it, held under a rule that the guides state in several different ways.

Is a breaker block the same as a mitigation block?
The guides do not settle this. Four of the five read for this page never mention the mitigation form at all. The one that does separates the two by whether the move that broke the zone first ran past a prior swing high or low, and no second account exists to check that against.

Who defined the breaker block, and is there a standard definition?
No exchange, platform or standards body publishes a definition. One guide names an originator and quotes him without giving a source, and the list of standard indicator functions for MetaTrader 5 contains no entry of this kind, so any automatic marker is a third-party script using its own rule.

Risk notice. This page is educational and describes what published guides state about one piece of chart vocabulary, and where they disagree. Nothing here is a recommendation to buy or sell any instrument, no chart marking is a forecast, and no figure of expected performance is stated or implied. Leveraged trading carries a high risk of loss.

Sources checked on 17 August 2026. One official document was used: Technical Indicators – MQL5 Reference, the list of technical indicator functions available to MetaTrader 5, consulted for whether the platform ships a standard tool of this kind. Two further platform references were sought and could not be read, so no claim about them is made here: the MetaTrader 5 terminal help pages for indicators returned not found, and the TradingView Pine Script reference returned a page whose text does not load without a browser. Six descriptions of the term were retrieved for comparison and five could be read. Those five enter this page in one capacity only, as evidence of what is being taught, what is left out and where two accounts conflict; no number was taken from any of them. The document counts and the phrase-occurrence counts printed above were produced here by searching the retrieved files.
Leave A Reply

Your email address will not be published.