Jan Fabry

<p>This is a tool to understand your rewrite rules (“Pretty Permalinks”). It is indispensable if you are adding or modifying rules and want to understand how they work (or why they don’t work).</p>
<p>It is only an analyzer, it does not change any rules for you. It parses the rules down to their components and shows the connection with the resulting query variables. It allows you to try out different URLs to see which rules will match and what the value of the different query variables will be (see screenshots).</p>
<p>This plugin was written as a tool to help answering questions about rewrite rules on <a href="http://wordpress.stackexchange.com/" rel="nofollow ugc">the WordPress Stack Exchange</a>.</p>


Monkeyman Rewrite Analyzer

Throws a warning if WP_DEBUG is on, other than that still a very handy tool to check your rewrite rules.

Very useful

Helped me sort some issues with the rewrite rules when developing a plugin. Works fine with WordPress 5.2 and does what you need it too.

Works Great

This plugin is really useful for specific needs.
But unfortunately not maintained anymore... =/
If someone need and update version of this check this out :

https://wordpress.org/plugin/url-rewrite-analyzer

Features:

- Nice and clean interface
- Remove all PHP warning / notices
- Update code structure
- Compatible with latest WP Version
- Light / Old / Dark UI

Good plugins !

Making sense of the rewrite mess. Display and play with your rewrite rules.

PiotrPress

Clearcode

<p>The CC-Cache plugin supports caching of Posts, Pages, and any public Custom Post Types – including single and archive pages.<br />
It also supports a “static page display” option: Front page, Posts page, and standard Latest Posts listing.<br />
This plugin is compatible with Multisite WordPress installations.</p>
<h4>How does it work?</h4>
<p>When a user (i.e. someone who is logged out of WordPress) opens a page for the first time, the plugin saves all the rendered html to a file in the wp-content/cache directory.<br />
From this moment onwards, any user who accesses the site will be served content directly from the generated html file. WordPress at this point is not initialized for this page.<br />
The generated cache file will be removed when you make changes to the corresponding Post/Page, and then the process starts from the beginning.<br />
You can also clear all cached files from the Cache options page (visit the ‘Settings > Cache’ page in wp-admin), or manually delete files from the wp-content/cache directory.</p>
<h4>Tips & Tricks</h4>
<p>You can check if a page’s content is served from a cache file by opening the page’s source code in the browser and scrolling down to the closing <code><body></code> html tag.<br />
If the content is cached, you should see a comment with the date and time the page was last cached, for example:<br />
    </p>
<p>You can disable cache for a single request and get the raw html by adding <code>cache=false</code> to a URL’s parameter, for example:<br />
    http://example.com/?cache=false</p>
<p>You can disable cache for a single request and get the raw html by adding <code>cache=false</code> HTTP header.</p>
<p>Logged-in users always get the raw html.</p>
<h4>Ideas for future versions</h4>
<ol>
<li>Add support for Categories, Tags, Taxonomies, and Authors.</li>
<li>Add support for RSS/Atom feeds.</li>
<li>Add support for Nginx and IIS servers.</li>
<li>Add support for other WordPress Filesystem Methods.</li>
<li>Add regenerate function for all cache files.</li>
</ol>
<h3>Requirements</h3>
<ol>
<li>Apache server</li>
<li>mod_rewrite</li>
<li>Write access to wp-content/cache directory</li>
<li>PHP interpreter version >= 5.3</li>
</ol>

CC-Cache

A simple and fast cache plugin based on static-rendered html files served by Apache with mod_rewrite.

Monkeyman Rewrite Analyzer vs CC-Cache