🎉 Use coupon MYXERO to enjoy 20% recurring discount on any plan. View Pricing
Taiji Template Inspector
Taiji Template Inspector

Taiji Template Inspector

0/5 (0 ratings) — active installs Updated Mar 24, 2026
Dashboard overview showing template summary cards and the full template table with usage counts

Dashboard overview showing template summary cards and the full template table with usage counts

When you modify a WordPress template, you might be affecting dozens of pages without even knowing it. Taiji Template Inspector gives you full visibility: instantly see which pages, posts and custom post types use each template — before you change a single line of code.

Designed for WordPress developers and agencies working on complex sites, it turns template management from a guessing game into a controlled, auditable process.

View on GitHub

What you can do

  • See every page affected by any template — at a glance, sorted by usage count so the most impactful templates are always first
  • Expand any template row to inspect the individual posts and pages assigned to it
  • Open all impacted pages in one click — choose between frontend preview or backend editor
  • Spot orphaned templates — files missing from the theme are automatically flagged, so you can clean up safely
  • Export a full usage report as CSV for QA workflows and documentation
  • Filter by language when using WPML or Polylang on multilingual sites
  • Search templates instantly with the live search bar

Built for real projects

Taiji Template Inspector is read-only and completely safe to use in production. It uses optimised database queries with WordPress transient caching to minimise performance impact, even on large sites with hundreds of pages and multiple custom post types.

No settings to configure. Install, activate, and find it under Tools Taiji Template Inspector.

Who is this for?

  • Developers maintaining or refactoring WordPress themes
  • Agencies managing client sites with complex template structures
  • QA teams who need to verify which pages are affected before deploying changes