Merchant.WiKi

Merchant.WiKi SEO Audit — Where It Helps 
1. Launch inventory baselines after migrations or redesigns to catch missing URLs, sitemap gaps, and misconfigured canonicals. 
2. Build prioritized “ready to submit” lists for manual indexing by combining HTTP 200 pages, sitemap coverage, and low inbound links. 
3. Audit internal linking to surface orphan or weak pages before requesting more crawl budget. 
4. Export a full, normalized dataset for BI dashboards or agency handoffs without granting direct DB access. 
5. Validate Google Search Console signals (Page Indexing exports + Inspection API) against on-site data to see why URLs stay “not indexed”. 
6. Keep evergreen posts from slipping by spotting the oldest pages/posts (≥1 year since last update) and opening Gemini with a pre-written English script (“update the page… propose two external links…”) for rapid refreshes.
Author & Links 
• Built by Merchant.WiKi — your SEO knowledge hub: https://merchant.wiki/
Disclaimer 
• This plugin is currently in beta. Install it on staging or a fresh backup copy first. 
• Always take full file + database backups before running the audit queues or deleting data. 
• Merchant.WiKi provides the software “as-is” and is not liable for any data loss or downtime.
<h3>External services</h3>
<h3>Google OAuth / Google account authorization</h3>
<ul>
<li>Use: Lets administrators connect their Google account so the plugin can reach Search Console data and, if requested, Google Sheets.</li>
<li>Data sent: During the consent flow the site posts your Google Cloud client ID, client secret, redirect URI, and the one-time authorization code to https://oauth2.googleapis.com/token, then calls https://www.googleapis.com/oauth2/v2/userinfo to record which account is connected.</li>
<li>When data moves: Only when an administrator clicks “Connect Google Account” or “Connect Sheets”; no background jobs refresh tokens unless you start the OAuth flow.</li>
<li>Optional: Yes. Inventory building, sitemap caching, crawls, and reports continue to run without signing in to Google.</li>
<li>Terms: Google Terms of Service (https://policies.google.com/terms)</li>
<li>Privacy: Google Privacy Policy (https://policies.google.com/privacy)</li>
</ul>
<h3>Google Search Console API</h3>
<ul>
<li>Use: Fetches your property list and runs the URL Inspection API so you can log index verdicts and TTLs in <code>mw_gsc_cache</code>.</li>
<li>Data sent: Each inspection call posts the selected property (<code>siteUrl</code>) plus every queued WordPress URL as <code>inspectionUrl</code>, and uses your OAuth access token for authorization.</li>
<li>When data moves: Only while you run “Check Google Index Status” or refresh the property selector—no calls fire automatically otherwise.</li>
<li>Optional: Yes. The rest of the audit features work without Search Console; enabling it simply enriches the reports.</li>
<li>Terms: Google API Terms of Service (https://developers.google.com/terms)</li>
<li>Privacy: Google Privacy Policy (https://policies.google.com/privacy)</li>
</ul>
<h3>Google Sheets API</h3>
<ul>
<li>Use: Imports Page Indexing exports stored in Google Sheets and can build a combined export sheet through the “Assemble” tool.</li>
<li>Data sent: Requests include the spreadsheet ID/range you provide, and when you create the combined export the plugin writes rows containing the URL, verdict, coverage reason, last crawled time, exported timestamp, and source label to a new sheet in your Drive.</li>
<li>When data moves: Only when you opt into the Sheets import/export mode; the plugin never touches Sheets unless you paste sheet URLs and start the task.</li>
<li>Optional: Yes. CSV uploads cover the same workflow if you prefer not to grant Sheets access.</li>
<li>Terms: Google API Terms of Service (https://developers.google.com/terms)</li>
<li>Privacy: Google Privacy Policy (https://policies.google.com/privacy)</li>
</ul>
<h3>Gemini link</h3>
<ul>
<li>Use: Adds an “Open Gemini” button in the Stale Content Refresh table so you can open https://gemini.google.com/app with a prefilled brief for that URL.</li>
<li>Data sent: Clicking the button encodes the page URL, publish and update dates, title, and current meta description into the <code>prompt</code> query string; clipboard text with the page body stays on your device until you paste it.</li>
<li>When data moves: Only when someone presses “Open Gemini”; nothing is transmitted automatically.</li>
<li>Optional: Yes. You can ignore the Gemini link and still use every refresh workflow.</li>
<li>Terms: Google Terms of Service (https://policies.google.com/terms)</li>
<li>Privacy: Google Privacy Policy (https://policies.google.com/privacy)</li>
</ul>
You must be a verified owner of the site in Google Search Console to use the plugin.
Index coverage data can lag behind reality by several days.

Merchant.WiKi SEO Audit

Build URL inventories, cache sitemaps, refresh SEO signals, and connect Google Search Console for exportable index audits.

EnglishMike

Enhance your blog by creating multiple, three-level alphabetical indexes of your posts based on any combination of 
post title, author, extract, tags, categories, or custom fields of your choice. Select which posts are included in your indexes using 
a combination of categories and tags, display them in up to four columns on a single page or over multiple pages.
For example, the AZIndex plugin can be used to:
<ul>
<li>Create an alphabetical index of all your blog posts, based on their titles, using extracts as short descriptions.</li>
<li>Create a music review index, sorted by the name of the artist and the name of their albums.</li>
<li>On blogs with multiple authors, create an index of posts by each author’s name.</li>
<li>Create a full alphabetical index of all your blog’s published pages in seconds with no PHP, HTML, or CSS required.</li>
</ul>
Full list of features:
<ul>
<li>Index blog posts by title, extract, author, or any custom field.</li>
<li>Create indexes for your blog pages. Now you can create a full alphabetical index of every page and post on your site. </li>
<li>Select index contents using a combination of categories and tags.</li>
<li>One, two or three-level entries – heading, subheading, and description, all customizable.</li>
<li>Up to four columns on a page.</li>
<li>Multiple indexes can be created, each customized with its own settings.</li>
<li>Indexes may be embedded in posts as well as pages.</li>
<li>Fully customizable from the WordPress admin console. No need to know HTML or PHP.</li>
<li>Single or multi-page indexes with page links.</li>
<li>Optional alphabetical links.</li>
<li>Display alphabetical headings in your index with links back to the top of the page.</li>
<li>Group items with the same heading under one entry (e.g. all the novels of the same author).</li>
<li>Add your own text to the index page.</li>
<li>Control over the number of index items per page.</li>
<li>Indexes are cached to ensure speedy operation when dealing with large indexes.</li>
<li>Customize the stylesheets for the index contents directly from the index administration page.</li>
<li>Use CSS style striping to decorate your index entries (e.g. add a gray background to alternate entries). </li>
<li>Use your own customized sort to sort an index.</li>
<li>Customize which alphabetical links appear with your index. </li>
<li>Index entries that do not begin with a character or number can be placed at the beginning or the end of the index.</li>
<li>Punctuation like quotes or double-quotes can be ignored while sorting the index.</li>
<li>You can exclude categories and tags from an index. Useful if you just need to exclude a few posts from an index. </li>
<li>Option to automatically include child categories in the index. </li>
<li>Support for the superfast WP Super Cache plugin.</li>
<li>Support for national languages. Non-English characters in headings and alphabetical links should now be displayed correctly. </li>
<li>Translatable text provided — help requested for translating the strings (in azindex.pot), it would only take a few minutes of your time.</li>
<li>NEW in 0.8.0 Sort indexes by tag names or category names.</li>
<li>NEW in 0.8.0 New item filter allows you to tailor the sorting of the index to you needs.</li>
<li>NEW in 0.8.0 Three new output filters allow you to modify the HTML of the index, or even create your own!</li>
<li>NEW in 0.8.0 The table of indexes on the Index Management page is now sortable.</li>
<li>NEW in 0.8.1 Item display filter, allowing you to modify the content of an item before it is displayed.</li>
</ul>
IMPORTANT NOTE: This is still a BETA release, meaning that while the plugin is stable and has undergone 
considerable testing, you may encounter some bugs as new features and code are added. I have not been able to test 
all the plugin’s features on all combinations of WordPress versions, browsers, databases, and PHP versions, so 
some problems could remain on some of the many possible configurations. The best thing to do is just give it 
a try!
Please read the Other Notes section before installing.
If you try this plugin and like what you see, email to azindex@englishmike.net or visit the 
<a href="http://azindex.englishmike.net/feedback" rel="nofollow ugc">AZIndex Plugin Feedback Page</a> to provide your feedback.
Whether you’re reporting a bug, requesting a new feature, or just wanting to make a comment, I will be happy to hear from you.
Stay up-to-date with all the important information and updates about AZIndex by subscribing to the 
<a href="http://azindex.englishmike.net/email-subscriptions/" rel="nofollow ugc">AZIndex Announcements Mailing List</a>.
<h3>Release Notes version 0.8.1</h3>
Minimum versions tested
<ul>
<li>WordPress 2.5 is the minimum required (will not work with older versions of WordPress)</li>
<li>PHP4 (4.4.8) & PHP5 (5.2.6) (will probably work with earlier versions of PHP4 and PHP5)</li>
<li>MYSQL 4.1.22 & MYSQL 5.0.5 (will probably work with earlier versions of MYSQL 4.0 and 5.0)</li>
</ul>
Known issues
<ul>
<li>This plugin supports indexes in non-English languages, but all text is English-only.</li>
<li>The plugin still contains some debug code. It will not affect the behavior or performance of the plugin. It will be removed in later versions.</li>
<li>The wp_nonce functions have yet to be implemented.</li>
</ul>
Changes in version 0.8.1
<ul>
<li>Added new filter: azindex_item_display</li>
<li>Fixed bug in item filter.</li>
</ul>
Changes in version 0.8.0
<ul>
<li>Added support for sorting the index by tag names and category names.</li>
<li>Added four new filters: azindex_item, azindex_display_index, azindex_alpha_links, azindex_page_links</li>
<li>Added sorting of the index table on the Admin Management page.</li>
<li>Disabled the grouping option if no subheading is selected.</li>
<li>Updated pointers to new web site: http://azindex.englishmike.net</li>
<li>Several bug fixes relating to the caching of pages</li>
</ul>
Changes in version 0.7.5
<ul>
<li>Rewritten the upgrade process for when a database table change is required. From now on, the old settings will not be deleted until the plugin has confirmed that the upgrade was successful.</li>
<li>Started internationalizing the text in the plugin. This is the text like “(more)” and “(continued)” that appear on the index page. I will do the admin pages too once the plugin gets closer to being finished. I will, of course, make the POT file available for people to translate into their languages. Just email me the translated files and I will incorporate them into a later release.</li>
<li>Added titles to the links in the alphabetical links and page links in the index (text is included in the POT file)</li>
<li>The headings in the index now link back to the top of the index, not the top of the page. This is more convenient for the user when you have a large heading or a lot of text above the index.</li>
<li>Added a “div” around the whole index and given it the id of “azindex-(index-id)”. This was to let me point the links back to the top of the index, though it’s also a good idea in the long run too. I haven’t given it a class name yet, see below for the reason why.</li>
<li>Fixed a couple of spelling mistakes and some validation issues (there all!)</li>
<li>Fixed the stray end-style tag (now closes the spans properly)</li>
<li>Fixed a problem with the admin page’s custom field text box not appearing in some browers when selected.</li>
<li>Fixed a bug in the sorting of non-alphanumeric characters.</li>
<li>Fixed the “ignore characters” option which has been almost completely broken since 0.7.0.</li>
<li>Completely rewrote the alphabetical index code so that it doesn’t stop displaying links when the contents of the index are not in the expected order.</li>
<li>And last, but not least, tweaked the multi-column code to fix a problem where it would sometimes not work on IE6/IE7.</li>
</ul>
Changes in version 0.7.4
<ul>
<li>Fixed regression in sorting lower case alphabetical character in the wrong order.</li>
</ul>
Changes in version 0.7.3
<ul>
<li>Fixed regression when creating the az_indexes database table.</li>
</ul>
Changes in version 0.7.2
<ul>
<li>Fixed problem with older databases not working with collation.</li>
</ul>
Changes in version 0.7.1
<ul>
<li>National language support has been added. Please see the FAQ for more information.</li>
<li>Renamed the AZIndex menu item.</li>
</ul>
Changes in version 0.6.3
<ul>
<li>Fixed problems caused by the changes to the Admin Console in WordPress 2.7. </li>
</ul>
Changes in version 0.6.2
<ul>
<li>Fixed bug where database table names were incorrectly hard-coded. Should fix SQL errors when using excluded categories or tags.</li>
</ul>
Changes in version 0.6.1
<ul>
<li>Added an extra array check to fix bug that might causing error messages when saving a post.</li>
</ul>
Changes in version 0.6
<ul>
<li>Added support for excluding post in categories and with tags from an index. Useful if you only want to exclude a few posts.</li>
<li>Added option to include child categories along with the specified category. Useful if you have a heirarchy of categories.</li>
<li>Added full support for the WP Super Cache plugin. If you are using that plugin to cache pages on your site, then index pages will be cached too.</li>
<li>Fixed bug where a single item index was not being displayed.</li>
</ul>
Changes in version 0.5.4
<ul>
<li>Fixed problem when getting a serialized option in WordPress 2.6. Will continue to work on WP 2.5 and WP 2.6 if they decide to fix their bug. </li>
</ul>
Changes in version 0.5.3
<ul>
<li>Fixed sorting bug where the heading sort was case sensitive (yikes!)</li>
<li>Added filter called ‘azindex_heading’ to allow custom manipulation of headings before they are sorted. See the EnglishMike.net blog for more information.</li>
</ul>
Changes in version 0.5.2
<ul>
<li>Added “escape” parameter to shortcode to allow bloggers (i.e. me) to display the [azindex] shortcode in a post without it turning into an index or error message! (format is: escape=”true” if you want to display the shortcode)</li>
<li>Fixed name-collision bug with $mutex global variable.</li>
<li>Fixed bug where a link end tag was missing in some index formats.</li>
</ul>
Changes in version 0.5.1
<ul>
<li>Fixed bug that gave error messages when creating a new index.</li>
</ul>
Changes in version 0.5
<ul>
<li>Caching has arrived! Large indexes are now many times faster to load (if you use multiple pages) than before.</li>
<li>The cache can be cleared manually if necessary, or even disabled completely (though I would recommend against it!)</li>
<li>Added option to add alphabetical headings to your index. Each new letter of the alphabet now has its own heading.</li>
<li>Added further options to put an alphabetical heading at the beginning of each page or at the top of each column.</li>
<li>Improved the pagelinks so that they will never overflow the bounds of the page if you have many pages in your index.</li>
<li>Added “(continued)” and “(more…)” when a grouped heading crosses between columns or pages. </li>
<li>Fixed bug that was resulting in the wrong number of items going into a column.</li>
</ul>
Upgrading to version 0.5
<ul>
<li>No incompatible changes from 0.4.x. Indexes created with versions 0.3.x and 0.4.x will continue to work on 0.5.</li>
<li>New CSS styles for the indexes will be added if you have defined custom CSS for your index. Your own modifications will not be affected. </li>
</ul>
Changes in version 0.4
<ul>
<li>Added option for including blog pages in an index.</li>
<li>Added option for striping index entries (e.g. giving alternate entries a different backgound color).</li>
<li>Added option for custom sorting of an index. Simply create your own comparison function and add its name to the index’s settings page.</li>
<li>Added option for filtering out punctuation when sorting the index, so entries don’t get out of order if they begin with a quote or double-quote, for example.</li>
<li>Added option for placing entries that begin with non-alphanumeric characters at the end of the index.</li>
<li>Fixed bug causing the URL to grow when clicking on the index page links.</li>
<li>Fixed bug where entries with no heading were appearing in the index. </li>
<li>You can now upgrade to the latest version of the plugin without losing your existing index settings (from v0.3 and above). </li>
</ul>
Upgrading to version 0.4
<ul>
<li>No incompatible changes from 0.3.x. Indexes created with version 0.3.x will continue to work on 0.4.</li>
</ul>
Changes in version 0.3.1
<ul>
<li>Fixed bug preventing plugin working with PHP4.</li>
<li>Added better error checking and error messages to help users during problem determination.</li>
</ul>
Upgrading to version 0.3.1
<ul>
<li>No incompatible changes from 0.3. Indexes created with version 0.3 will continue to work on 0.3.1.</li>
</ul>
Changes in version 0.3
<ul>
<li>Fixed bug that prevented the plugin working with MySQL 4.1 and some early versions of MySQL 5.0</li>
</ul>
Upgrading to version 0.3
<ul>
<li>VERY IMPORTANT You must uninstall any earlier versions of the AZIndex plugin by clicking the Uninstall AZIndex Plugin link in the Manage >> AZIndexes admin page before you install the latest version. </li>
</ul>
Changes in version 0.2.1
<ul>
<li>Fixed bug where duplicate entries appear in the index when specifying more than one tag or category for the index.</li>
<li>Fixed bug where the Author (the author of the post) was not displayed correctly when specified.</li>
</ul>
Upgrading to version 0.2.1
<ul>
<li>Indexes created on v0.2 should continue to work on v0.2.1</li>
</ul>
Changes in version 0.2
<ul>
<li>Indexes are no longer tied to a specific blog page. For you convenience, a new page containing the ‘[az-index id=”x”]’ short-code will be created when you add an index, but you can copy that shortcode to any post or page you like.</li>
<li>Posts can now have indexes embedded within them. Just insert the short-code ‘[az-index id=”x”]’ where x is the id of the index. e.g. [az-index id=”1″]. </li>
<li>You can embed the same short-code in more than one post/page.</li>
</ul>
Upgrading to version 0.2
<ul>
<li>Delete all the indexes created with version 0.1. They will no longer work correctly. The quickest way to do this is to click ‘Uninstall’ and uninstall the plugin before you upgrade.</li>
<li>You can no longer preview the index page from the ‘Manage Indexes’ table. Go to Manage >> Pages instead.</li>
<li>The plugin’s administration page has been renamed from ‘Index Pages’ to ‘AZIndexes’</li>
</ul>

AZIndex

Stylish Indexes for your WordPress Blog. Create alphabetical indexes of your posts, with headings, subheadings, and descriptions, based on post title, …

Merchant.WiKi SEO Audit vs AZIndex