Intuitive Custom Post Order writes its manual sort to two places: menu_order on wp_posts for posts, pages, and custom post types, and term_order on wp_terms for taxonomies. The plugin's settings, including which post types and taxonomies are sortable, live in wp_options under hicpo_options. With AutoSort active, the plugin filters front-end queries to use orderby=menu_order ASC automatically. Editors drag items in the admin list table, and the front end immediately reflects the new order.

SleekAI's Wizard maps that same query into the chatbot's system prompt. When a visitor asks for the top three case studies or the first five categories, the bot returns the editor's order, not whatever the LLM thinks is reasonable. Editors get a free reorder audit. They can ask the bot which posts sit at the top of each enabled post type, which taxonomy term comes first, and which items moved this week. The plugin also supports site reordering on Multisite, which SleekAI can read through blog_order.

For long sorted lists, push titles plus the order field into an OpenAI Files vector store keyed on menu_order or term_order, so retrieval respects the manual sequence even when the model fetches only matching entries. Conversation logs save the query, the matched items, and the page URL. Over time the editorial team sees which positions get the most chat traffic, which is the strongest signal a drag-up is worth doing.

Editorial sort is one of the cheapest, highest-impact decisions a content team makes. Drag the best case study to position one and traffic that lands on the portfolio sees it first. Intuitive Custom Post Order makes this drag effortless for posts, pages, custom post types, taxonomies, and on Multisite even sites.

The trade-off is that the order lives in menu_order and term_order, columns most third-party tools ignore. Generic chatbots fall back on date order or alphabetic order, both of which contradict the homepage. SleekAI closes that gap.

The chatbot reads the same two columns the plugin writes, so the conversational answer matches the page. Editors get an audit tool they did not have before. The conversation log shows which positions visitors ask about and which buried items keep getting requested.

Drag those up and the next visitor finds them on page one and in the chat reply at the same time. Compared to building a custom JSON ranking file, this approach uses the data WordPress already stores. No new build steps, no parallel store, no risk of drift between admin and chat.