> For the complete documentation index, see [llms.txt](https://documentation.ajaxsearchpro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ajaxsearchpro.com/advanced-options/primary-and-secondary-title-and-description-fields.md).

# Primary and Secondary title and description fields

![](/files/-L9ntY5hd-p3FPT_W9vb)

During the search post-process, the plugin parses the Post/Page/CPT titles and the contents, as defined by these fields. First it looks for the *Primary field*, and if it is not found or empty, it uses the *Secondary field.*

## Examples

### Custom field content as Title or Description

It is possible to define a single, text based custom field as the title or description field.

{% hint style="info" %}
 We recommend using it as the Primary field, so the plugin can fall back to a Secondary field, just in case.
{% endhint %}

![Custom field as title](/files/-L9nvhEtzVOM_XfmGhE6)

### Yoast SEO title and meta description custom fields

The Yoast SEO plugin uses the folling custom fields to store the custom title and meta desctiption fields:

* \_yoast\_wpseo\_title
* \_yoast\_wpseo\_metadesc

{% hint style="info" %}
These Yoast SEO fields are only defined, if the title/meta description are typed in manually.
{% endhint %}

### All in one SEO plugin meta title and desctiption custom fields

The All in One SEO plugin uses the following custom fields:

*  \_aioseop\_title
*  \_aioseop\_description

{% hint style="info" %}
 These  All in one SEO fields are only defined, if the title/meta description are typed in manually.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.ajaxsearchpro.com/advanced-options/primary-and-secondary-title-and-description-fields.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.