How can IONOS stop correcting misspelled file URLs automatically?

Definition: Add CheckSpelling off to the relevant .htaccess file. The setting disables Apache's spelling module, so a misspelled or incorrectly capitalized file name receives the missing-page behavior described by IONOS instead of loading a close match.

Key facts

• IONOS says that switching off CheckSpelling stops the server from listing apparent matches or automatically loading the closest matching page name. IONOS's .htaccess directives reference gives the setting.
• IONOS's example uses CheckSpelling off and says that a page-not-found error is shown instead of the closest-looking file or page.
• Apache documents CheckSpelling as on|off, with a default of Off, and lists .htaccess among its supported contexts. Apache's mod_speling documentation defines the directive.
• With the module enabled, Apache returns 404 when no matching document exists, 301 when one close match exists, and 300 when several close matches exist.

What should go in the .htaccess file?

IONOS places the switch under “Disable File Matching”. Its example can be copied into the .htaccess file that applies to the directory:

# Prevents the server from detecting spelling errors or incorrect
# capitalization in file names. Shows a page not found error instead
# of loading the file or page that most closely resembles the spelling.
#
CheckSpelling off

The same IONOS reference says that its hosting documentation covers Linux Web Hosting and Managed Dedicated Servers. It also reserves the right to completely or partially overwrite directives, or prevent their use, because of security settings or similar reasons.

How does the fallback behave?

Apache's mod_speling handles a request that the core server cannot serve because the document name is misspelled or miscapitalized. It compares document names in the requested directory without regard to case and permits up to one misspelling, such as a character insertion, omission, transposition, or wrong character. The module can also correct an erroneous extension.

The outcome depends on the directory scan. Apache proceeds with a 404 - document not found response when it finds no matching document. One almost-matching document produces a 301 - Moved Permanently redirection. Several close matches produce a 300 - Multiple Choices response containing the candidates.

With CheckSpelling off, IONOS describes the result as a page-not-found error rather than a list of apparent files or the closest matching page name. Apache's documentation identifies the directive as part of the mod_speling extension and gives its default as CheckSpelling Off.

What should you check before using it?

The correction scan examines directory contents. Apache warns that repeated corrections can affect server performance when many happen at once, and that document trees should not contain sensitive files that could be matched inadvertently. The module corrects file names and directory names, while misspelled user names are outside its scope.

Apache also says that spelling correction applies strictly to existing files. It gives a request for <Location /status> that could be treated as the negotiated file /stats.html as an example of the behavior to consider. The documentation says mod_speling should not be enabled in DAV-enabled directories because a newly created resource name can be redirected to an existing filename.

Related terms

• Which directories inherit an OVHcloud htaccess rule?
• Where do former htaccess redirects and header rules belong on WP Engine?
• Why can Apache MultiViews interfere with PrestaShop friendly URLs?

FAQ

Does CheckSpelling off rename or remove a file?

No. The IONOS example changes how the server handles a misspelled or incorrectly capitalized file name. The file itself remains subject to the normal file lookup.

What happens when there is no close match?

Apache returns 404 - document not found after scanning the directory and finding no matching document. IONOS describes the off setting as showing a page-not-found error.

Why can automatic correction be undesirable?

Apache documents a directory-scan performance cost when many corrections occur at the same time. It also warns that an existing sensitive file could be matched inadvertently.

Sources

1. IONOS, "Frequently Used .htaccess Directives", 2026
2. Apache Software Foundation, "mod_speling - Apache HTTP Server Version 2.4", 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer