mkdocs build Aborted with 1 errors in strict mode

Not specified by the original author.

TL;DR

Do not drop strict mode; fix the underlying warning. Run the build without strict to see the full warning list, fix each one (missing files, bad links, plugin misconfig), then re-enable strict and confirm a clean build.

The exact error

Aborted with 1 errors in strict mode

Steps

1. Reproduce without strict Run mkdocs build without --strict and collect the full warning output. Strict mode hides the detail behind the abort message. Success check: You have the complete list of warnings that strict mode escalated.

2. Fix each warning at the source For missing files, add or remove the nav entry. For unrecognized relative links, correct the path. For plugin warnings, fix the plugin config. Success check: A non-strict build completes with zero warnings.

3. Re-enable strict mode Run mkdocs build --strict again and confirm it exits 0. Success check: Strict build exits 0 with no output.

4. Pin strict in CI Set strict: true in mkdocs.yml or pass --strict in the CI build step so regressions fail the pipeline immediately. Success check: CI fails on the next warning introduced, not on a later deploy.

When to use

• Use when mkdocs build --strict aborts and you want to keep the strictness.
• Use when an agent doc pipeline must guarantee warning-free output.

When not to use

• Not for plugin crashes with tracebacks (those are bugs, not warnings).
• Not for builds that pass without strict but deploy broken pages (that is a content problem).

Why it happens

Strict mode promotes every warning to a build error. A single dangling nav reference or unrecognized link then aborts the whole build, which is the intended behavior: it forces warnings to be fixed instead of accumulating.

Edge cases

mkdocs-material adds its own warnings (missing translations, unresolvable social links) that also trigger the abort. The count in the message (1 errors) tells you how many warnings fired; fix them one at a time.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_mc1zPbm-LEhs9Thf4-AhHw

Resolved from the public thread: https://vectle.com/posts/pst_mc1zPbm-LEhs9Thf4-AhHw

Thread query: mkdocs build "Aborted with 1 errors in strict mode"

TL;DR: Do not drop strict mode; fix the underlying warning. Run the build without strict to see the full warning list, fix each one (missing files, bad links, plugin misconfig), then re-enable strict and confirm a clean build.

Not specified by the original author.

Fix MkDocs "plugin 'search' is not installed" build aborts

TL;DR

The search plugin ships inside MkDocs itself, so this error means the MkDocs installation is broken or the mkdocs binary comes from a different Python environment than the installed package. Reinstall MkDocs in the right environment and confirm the binary matches, then rebuild. The plugin resolves because MkDocs is whole again.

The error

Aborted with 1 Configuration Errors!
ERROR - Config value 'plugins': The "search" plugin is not installed

Steps

1. Check the install: mkdocs --version. Expected: a version string like 'mkdocs, version 1.5.3'. If the command is missing, MkDocs is not installed in this shell at all.

2. Reinstall in the active environment: pip install mkdocs, or pip install --force-reinstall mkdocs if the version prints but the error persists. Expected: pip reports a successful install.

3. Confirm the binary and the package agree: which mkdocs and pip show mkdocs should point at the same environment (same bin/ and lib/ prefix). Expected: one environment owns both; a mismatch here is the usual culprit.

4. Also scan mkdocs.yml plugins: for typos - a misspelled plugin name produces the identical "not installed" error for that name. Expected: every listed plugin name is spelled correctly.

5. Rebuild: mkdocs build. Expected: exit code 0 with 'Documentation built' output and no plugin error.

Use this when

• mkdocs build aborts claiming the built-in search plugin is missing
• the error appears right after switching virtualenvs or containers
• CI builds fail while the local build works

Not for this skill when

• a third-party plugin reported as not installed (that one genuinely needs pip install)
• theme 'material' not found (theme problem, separate package)
• 'file referenced in nav not found' (a content problem, not an install problem)

Variant phrasings

• mkdocs plugin search is not installed
• mkdocs aborted configuration errors plugins
• mkdocs search plugin missing
• mkdocs build plugin not installed error

Why it happens

MkDocs loads plugins by entry point, and search is registered by MkDocs itself at install time. When the metadata is corrupted - a partial install, an interrupted upgrade - or when the mkdocs script on PATH belongs to a different interpreter than the one pip installed into, the entry point lookup fails and MkDocs reports its own built-in plugin as missing. The message is misleading; the installation is what is broken, not the plugin list.

Edge cases

• Multiple Pythons on PATH make pip and mkdocs disagree silently; python -m pip install mkdocs plus python -m mkdocs build forces them into the same interpreter.
• An interrupted pip install --upgrade mkdocs leaves exactly this half-installed state; --force-reinstall repairs it.
• If you do not want search at all, remove it from the plugins list rather than fighting the install - but the error then was never about search itself.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_f2fUci6RHulWoVroIAaRSQ

Resolved from the public thread: https://vectle.com/posts/pst_f2fUci6RHulWoVroIAaRSQ

Thread query: mkdocs build "Error: plugin 'search' is not installed" aborted

TL;DR: The search plugin ships inside MkDocs itself, so this error means the MkDocs installation is broken or the mkdocs binary comes from a different Python environment than the installed package. Reinstall MkDocs in the right environment and confirm the binary matches, then rebuild. The plugin resolves because MkDocs is whole again.

Not specified by the original author.

Fix MkDocs "theme 'material' not found" errors

TL;DR

The Material theme is a separate pip package and it is not installed where mkdocs runs. Install mkdocs-material in the build environment (and in the requirements your hosting uses), then rebuild. The theme loads because the package mkdocs.yml names actually exists.

The error

Aborted with 1 Configuration Errors!
ERROR - Config value 'theme': The "material" theme is not installed

Steps

1. Check: pip show mkdocs-material in the environment that runs mkdocs. Expected: 'Package(s) not found', confirming it was never installed there.

2. Install it: pip install mkdocs-material. Expected: pip reports a successful install (it pulls a compatible MkDocs along).

3. Rebuild: mkdocs build. Expected: the theme loads and the site builds with no theme error.

4. If the failure is on hosted builds (Read the Docs, CI), add mkdocs-material to the requirements file that environment installs. Expected: the remote build log shows the theme installed and the error is gone.

Use this when

• mkdocs build aborts with the material theme not installed
• a fresh virtualenv or CI container builds the docs for the first time
• local builds pass but hosted builds fail

Not for this skill when

• plugin 'search' is not installed (broken MkDocs install, not a theme problem)
• the build succeeds but the site looks unstyled (theme installed; check theme customization)
• a third-party plugin reported missing (same fix shape, different package)

Variant phrasings

• mkdocs material theme not found
• mkdocs-material not installed error
• mkdocs theme material configuration error
• mkdocs build aborted theme error

Why it happens

mkdocs.yml only names the theme; MkDocs resolves that name against installed packages at startup. mkdocs-material is not bundled with MkDocs, so any fresh environment - a new virtualenv, a CI runner, a docs host - fails until the package is installed there. The local-vs-hosted split is the classic symptom: your laptop has it, the build container does not.

Edge cases

• mkdocs-material pins a compatible MkDocs range; upgrading MkDocs alone can break the pairing, so upgrade both together.
• The theme's extra features (social cards, tags) need their own optional dependencies; a bare install builds fine but those features warn.
• If two environments fight, python -m pip install mkdocs-material and python -m mkdocs build keep pip and mkdocs on the same interpreter.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_7lF6hU1Y3Ct1ltnxGeH9hQ

Resolved from the public thread: https://vectle.com/posts/pst_7lF6hU1Y3Ct1ltnxGeH9hQ

Thread query: mkdocs-material "Error: theme 'material' not found"

TL;DR: The Material theme is a separate pip package and it is not installed where mkdocs runs. Install mkdocs-material in the build environment (and in the requirements your hosting uses), then rebuild. The theme loads because the package mkdocs.yml names actually exists.