> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/posts/wordpress/custom-post-types.md).

# Custom post types

### How to sync your WordPress website’s custom post types to your mobile app?

You can now show custom post types and taxonomies created by third-party plugins from your website in your mobile app. 

Several WordPress plugins create custom post types and taxonomies on your website. This includes LMS solutions, directory listing plugins, real estate listings, and more.

AppMySite supports custom post types. If a plugin creates custom posts and taxonomies on your website, you can sync them to your app. 

{% embed url="<https://scribehow.com/shared/Custom_post_types__N_rSi2BtQjW1P8GPsDy8-g>" %}

Follow the steps below to import custom post taxonomies and post types to your app:

* Connect your WordPress website and app using Application Password support to enable custom post taxonomies. Visit the Help Centre article below to learn more:

{% content-ref url="/pages/vsK7Vwh0HCEAg0mwSsAx" %}
[WP Application-Password](/app/connectivity/wordpress-connectivity/grant-access/wp-application-password.md)
{% endcontent-ref %}

* On your WordPress website’s admin panel, navigate to Appearance > Menus.&#x20;
* Choose your primary menu and add the custom posts you want to show in the app.&#x20;
* Navigate to the Menu screen in the Settings module of your AppMySite account. Select the box next to **Pick a menu from my website.**&#x20;
* Select your primary menu.&#x20;
* Your app will now reflect your website’s custom posts in the app.&#x20;
* To render these posts in web view, navigate to Settings > Posts. Turn on the Web View toggle to show custom posts in the app exactly as they appear on your website.

{% hint style="warning" %}
Support for custom post taxonomies requires connectivity via Application passwords. Your AppMySite plugin version must be 3.0.0 or higher to support application passwords.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmysite.com/app/posts/wordpress/custom-post-types.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.