{By default, when a visitor hits a 404 URL, all suggestion methods run: slug matching, spelling correction, title matching, content search, category/tag matching, URL fixing, and archive fallback. Engine Profiles let you override this for specific sections of your site — choose exactly which methods run when a 404 URL falls within a URL pattern you define.}

{Example 1:} {Your store lives at /products/. Spelling correction works great on blog posts, but on a product section you want only exact slug matching and URL fixing — fuzzy spelling suggestions might point to the wrong product. Create a profile with the URL pattern /products/* and check only "Slug Matching" and "URL Fix".}

{Example 2:} {You have a documentation archive at /docs/ that you recently restructured. The content is too technical for spelling suggestions to be useful, so you enable only the Archive Fallback engine there.}

{How profiles are applied:}

- {Each profile has a URL pattern (e.g. /products/*) that is tested against the incoming 404 URL.}
- {Profiles are checked in priority order — lower number means checked first.}
- {The first profile whose URL pattern matches the 404 URL wins. Only the engines you selected in that profile will run.}
- {If none of your profiles match the 404 URL, the default behavior applies: all engines run.}

{Most sites do not need Engine Profiles. They are for advanced scenarios where one section of your site needs different suggestion logic than the rest.}

{Name} | {URL Pattern} | {Regex} | {Engines} | {Priority} | {Active} | {Actions}
--- | --- | --- | --- | --- | --- | ---
{No engine profiles defined.}

#### {Add Engine Profile}

{Name}: |
{URL Pattern}: | {Use * as wildcard for simple patterns. Check "Regex" for full regex patterns.}
{Regex}: | {Pattern is a regular expression}
{Enabled Engines}: | {Select which engines should run for URLs matching this profile. Leave all unchecked to run all engines.} {Slug Matching} {Spelling Matching} {Title Matching} {Content Matching} {Category/Tag Matching} {URL Fix} {Archive Fallback} {WordPress URL Guess Fallback}
{Priority}: | {Lower number = higher priority. First matching profile wins.}
{Active}: | {Profile is active}