Co-Authors Plus stores bylines in a custom taxonomy called author, with each term linked either to a WordPress user or to a guest-author post in the guest-author custom post type. Post-to-byline relationships live in wp_term_relationships, and guest-author profiles carry their own metadata in wp_postmeta under keys like cap-display_name, cap-user_email, and cap-website.

SleekAI maps that taxonomy and the guest-author postmeta into the chatbot's system message. When a reader asks "who wrote the piece on the school board vote," the bot pulls the correct co-author list including the freelancer with a guest profile but no WP account. The bio, photo, and external links from the guest-author postmeta all come along for the ride.

Generic chatbots default to wp_users and miss every guest author entirely. They also miss co-authoring on posts where the WordPress post_author column points to one person but the byline taxonomy lists three. Co-Authors Plus posts can have ten contributors, all of whom should show up in a byline answer, and only a bot that reads the taxonomy gets it right.

Co-Authors Plus solves a problem WordPress core never quite did: more than one person wrote this piece. For investigative journalism, academic publishing, and any site that pays freelancers, that taxonomy of co-authors is the single source of truth for who gets credit. A generic chatbot that reads wp_users and stops there will silently miss every freelancer with a guest-author profile, and it'll get co-authored bylines wrong by returning only the WordPress account that started the draft.

Readers notice. Writers definitely notice. SleekAI reads the actual author taxonomy and the guest-author custom post type, including the bio, website, and avatar postmeta that the plugin uses to render real profile pages.

That means a reader asking "who wrote this" on a four-author investigation gets the four-author answer, and a question about a specific guest contributor pulls the real bio instead of an apology. Author archive queries surface recent work by the same writer, which is a free SEO and engagement win on every long-form page. The variable scoping is explicit, so a public-facing bot doesn't leak guest-author emails or any field you don't want exposed.

Token usage stays modest because the bot pulls only the current post's bylines plus what the question asks for, not the entire author table. None of this needs a separate sync layer because SleekAI reads live from the same tables Co-Authors Plus writes to.