Visualize your WordPress site structure — templates, pages, navigation flow, widget areas, and link health — all in one dashboard.

fgauer

<p>PIR Site Structure Mapper gives you a complete visual map of how your WordPress site is structured. It reads your theme’s templates, pages, navigation menus, and content links, then presents everything in an interactive dashboard so you can understand and manage your site architecture at a glance.</p>
<p><strong>Works with three theme types:</strong></p>
<ul>
<li><strong>Block themes (Full Site Editing)</strong> — templates, template parts, patterns, block trees, and the full template hierarchy</li>
<li><strong>Elementor sites</strong> — Theme Builder templates, saved templates, widget trees, display conditions, and navigation</li>
<li><strong>Classic themes</strong> — PHP template files, template hierarchy resolution, widget areas, and navigation menus</li>
</ul>
<p><strong>Key features:</strong></p>
<ul>
<li><strong>Site Navigation</strong> — visual flow map showing how pages connect through menus, content links, and template links</li>
<li><strong>Template analysis</strong> — see which templates exist, which pages use them, and how the template hierarchy resolves</li>
<li><strong>Page inspector</strong> — template resolution chain, content block/widget trees, and link analysis per page</li>
<li><strong>Link health</strong> — internal, external, and unresolved links with live verification via HTTP HEAD requests</li>
<li><strong>Live crawl</strong> — HTTP-based site crawling to discover pages and links as rendered</li>
<li><strong>Widget areas</strong> (classic themes) — registered sidebars and their active widgets</li>
<li><strong>Plugin routes</strong> — custom post types, taxonomies, and special pages registered by plugins</li>
<li><strong>Guard system</strong> — configurable safety limits prevent runaway processing on large sites</li>
</ul>
<h3>Development</h3>
<p>The full source code for this plugin is publicly available at:<br />
https://bitbucket.org/fgauer/wp-plugin-visual-editor/</p>
<h4>Source Files</h4>
<p>The compiled files in <code>build/</code> are generated from human-readable source code included in the plugin:</p>
<ul>
<li><code>src/admin/</code> — Admin dashboard React components and CSS (builds to <code>build/admin.js</code> and <code>build/style-admin.css</code>)</li>
<li><code>src/public/</code> — Public-facing JS and CSS (builds to <code>build/public.js</code> and <code>build/style-public.css</code>)</li>
</ul>
<h4>Build Tools</h4>
<ul>
<li>Node.js (LTS recommended)</li>
<li><code>@wordpress/scripts</code> — WordPress wrapper around webpack, Babel, and PostCSS</li>
</ul>
<h4>Building from Source</h4>
<p>To regenerate the compiled files:</p>
<ol>
<li>Install dependencies: <code>npm install</code></li>
<li>Build assets: <code>npm run build</code></li>
<li>For development with live reload: <code>npm start</code></li>
</ol>
<h4>Third-Party Libraries</h4>
<p>All JavaScript dependencies are WordPress core packages (<code>@wordpress/element</code>, <code>@wordpress/api-fetch</code>, <code>@wordpress/components</code>, etc.) loaded at runtime via the WordPress script dependency system. No third-party libraries are bundled into the compiled files.</p>


Alternatives to PIR Site Structure Mapper

Top alternatives