Posts 2 Posts
View on WordPress.orgScores higher than 70% of indexed plugins
About
Efficient many-to-many connections between posts, pages, custom post types, users.
What It Does
Posts 2 Posts creates efficient many-to-many relationships between WordPress posts, pages, custom post types, and users. It lets you define bidirectional connections such as linking books to authors, courses to instructors, or jobs to required skills, and then query and display those connections on the front end. Connection metadata is stored in custom database tables rather than post meta, which keeps large relationship networks fast.
Who It's For
This plugin is best for developers building content-driven sites where entities have multiple cross-relationships, such as recipe sites linking ingredients to dishes, universities connecting courses to instructors, or real estate portfolios tying agents to listings. It is most valuable on sites with hundreds or thousands of interconnected records where performance matters. Non-technical users will struggle without code-level configuration.
Who Should Skip It
Anyone running a small blog or simple site with no real relational content should skip this, since the setup requires writing connection types and queries in PHP. If you only need to link one post to one or two others, custom fields or a basic plugin like Custom Post Type UI will be far easier.
The Bottom Line
Posts 2 Posts earns an overall quality score of 79.81 out of 100 and remains one of the most efficient solutions for large-scale many-to-many content relationships in WordPress. Its high ratings and recent updates are tempered by low public support activity and a smaller install base than the leading alternatives. It is a developer tool, not a turnkey solution for casual site owners.
Related Plugins
Pick this when you need an admin UI for registering custom post types and taxonomies without writing PHP, and you do not require true many-to-many connections.
Choose this for a broader custom field and relationship toolkit with a visual builder, if you want one plugin to handle fields, CPTs, and simpler relations.
Choose Pods if you want to create custom content types and relationships through the admin interface rather than code-based connection definitions.
Pick this for a completely different purpose: instantly switching between user accounts during testing and support, not for content relationships.
Choose this if you only need to let users upload profile pictures, with no relational content requirements at all.