# Mistake to Mastery

> Mistake to Mastery is an MCAT prep platform that turns missed questions into targeted drills and spaced review sessions.

This file provides a concise map of public, crawlable pages that describe the product and study approach.

## Product
- [Homepage](https://mistaketomastery.com/): Product overview and core workflow.
- [Blog](https://mistaketomastery.com/blog): Study strategy articles and methodology.
- [Patch Notes](https://mistaketomastery.com/patch-notes): Public changelog updates.
- [Terms of Service](https://mistaketomastery.com/terms-of-service): Legal and usage terms.

## Blog Articles
- [The Science of Learning From Your Mistakes While Studying](https://mistaketomastery.com/blog/learning-from-mistakes-while-studying): Most students spend review time re-reading notes and highlighting explanations. The research says that barely moves the needle. Here is what five decades of cognitive science actually say about reviewing mistakes, fixing weak spots, spacing your practice, and letting data guide your studying.
- [How to Review MCAT Full-Lengths](https://mistaketomastery.com/blog/how-to-review-mcat-full-lengths): Most full-length review is passive: it builds understanding without changing what you do under pressure. Here's the loop that actually moves scores: diagnose the miss, train the exact weakness with a fresh variant, and resurface it until the pattern disappears.
- [MCAT Error Log Template](https://mistaketomastery.com/blog/mcat-error-log-that-actually-works): Most error logs are built for documentation, not training, which is why scores plateau. Here's the 7-field format, the skill-tagging principle, and the follow-through loop that turns a logged mistake into a closed weakness.
- [How to Review MCAT Practice Problems](https://mistaketomastery.com/blog/how-to-review-mcat-practice-problems): Reviewing MCAT practice problems by reading explanations builds recognition, not skill. Here's the loop that actually changes scores: diagnose the miss, train the exact weakness with a fresh variant, and resurface it on a schedule until the pattern disappears.
- [How Long Should MCAT Full-Length Review Take?](https://mistaketomastery.com/blog/how-long-should-mcat-full-length-review-take): You can spend eight hours reviewing a full-length and still plateau. The real driver isn't time. It's whether each session produces fresh drills and a resurfacing schedule. Here's what review should look like and how long each version takes.
- [Why You Keep Missing the Same MCAT Questions](https://mistaketomastery.com/blog/why-you-keep-missing-the-same-mcat-questions): If your score is stalling, you're usually not making new mistakes; you're repeating old ones in new clothes. Here's how to diagnose the actual root cause, train fresh variants, and resurface the weakness on a schedule until the pattern disappears.
- [Should You Review MCAT Questions You Got Right?](https://mistaketomastery.com/blog/should-you-review-questions-you-got-right-on-the-mcat): Most students only review their wrong answers, and that's why they plateau. The questions you got right but felt unsure on are weak skills wearing a correct mask. Here's how to find them and convert them into durable points.
- [The MCAT Full-Length Review Checklist](https://mistaketomastery.com/blog/mcat-full-length-review-checklist): A checklist by itself doesn't raise your score; most quietly trap you in a passive review pattern. Here's a tool-driven version that diagnoses misses, drills fresh variants, and resurfaces weaknesses on a schedule until they're gone.
- [How to Review MCAT Full-Lengths in 1–2 Days](https://mistaketomastery.com/blog/how-do-you-review-mcat-full-length-exams-in-1-2-days): Trying to review a full-length in 48 hours isn't lazy; it's efficient, if you do the right things. Here's the crunch-time system: a 90-minute Day 1 triage, a 2–3 hour Day 2 fix, and a resurfacing schedule that makes the work stick.

## Optional
- [Sitemap XML](https://mistaketomastery.com/sitemap.xml): Full list of indexable URLs.

Private application routes such as /dashboard and API endpoints require authentication and are intentionally excluded.