The Field Mappings tab defines how to extract and transform standard metadata fields (such as title, description, image, and date) from each page. For each field you specify which meta tags to check, in priority order, and optional cleanup or regex transformations. → Open Crawler Settings (Field Mappings tab)
Each mapping has:
| Part | Purpose |
|---|---|
| Field name | The name of the field (e.g. title, description, image, date). |
| Metadata priority | Ordered list of meta tag names (e.g. og:title, twitter:title, title). The first one found is used. |
| Remove text from field | Optional list of literal strings to strip from the value (e.g. \| Company Name, - Website). |
| Regex transforms | Optional pattern/replacement pairs applied after extraction (e.g. trim a suffix using a regex). |
The crawler stores the resulting values and they are used for search, citations, and display.
The internal name of the field (e.g. title, description, image, date). Use lowercase and avoid spaces. Common standard names are title, description, image, and date.
An ordered list of meta tag names to inspect. The crawler looks at each in turn and uses the first non-empty value.
og:title, twitter:title, title for a title field; og:description, description for description.A list of literal strings that are removed from the extracted value if present. Use this to strip a site-wide suffix or prefix (e.g. | Company Name, - Website) so the stored value is clean.
Pattern/replacement pairs applied to the value after extraction and after any “remove text” rules. Use standard regex syntax; in the replacement you can use capture groups (e.g. $1).
^(.+?) \|.*$, replacement $1 — keeps only the part before | ….When you change field mappings and save, you may be asked whether to trigger an index update. If you do, the new mappings are applied during the next indexing run. If you don’t trigger it, the config is saved but you’ll need to run reprocessing later for the changes to affect search and citations.