---
title: "Traffic Boost Indexing | IndexNow SEO Plugin for Joomla Websites"
description: "Push new Joomla URLs to search engines with IndexNow and Google Search Console. Automate submissions and track indexing with detailed logs and retries."
url: "https://www.yoozecase.com/?item_id=20"
date: "2026-11-22T18:25:40+00:00"
language: "en-GB"
---

#  Traffic Boost Indexing

Stop waiting to be indexed!

**Latest Version**
3.8.1
**Requires**
Joomla 5+, PHP 8.1 or newer
**Release date**
13 November 2026
**Made for**
Joomla
**License**
GPL-2.0-or-later
**Price**
€25.00 (incl. 6 months of updates)

 [ 🛒 Get it for Joomla 👍 ](https://yoozecase.lemonsqueezy.com/checkout/buy/2fa37499-a59d-4cfb-af21-6e400ff5ead4)

 [ Demo page ](https://www.yoozecase.com/traffic-boost-indexing-demo)

Push new Joomla URLs to search engines instantly with IndexNow, Google Search Console support, automatic submissions and detailed logs.

##  What's new in version 3.8.1

- **Changed:** The dashboard module and the plugin dashboard say that each search engine decides itself whether and when a submitted page is included.
- **Changed:** Under failed submissions: a failure is not always caused by the site or the plugin, and the plugin tries again later.
- **Changed:** The message that IndexNow refuses the server address says that the hosting provider chooses that address.
- **Note:** Traffic Boost Indexing 3.8.1 - clearer about what a submission can and cannot do.

 ![Traffic Boost Indexing 1](https://www.yoozecase.com/files/traffic-boost-indexing_1.png)

 [](#)

 [](#)

---

##  Description

Get your Joomla content discovered faster with Traffic Boost Indexing. Automatically notify search engines when you publish or update articles, categories, tags, media and ZOO content.

Powered by IndexNow with Google Search Console integration, automatic retries and detailed submission logs. No manual URL submissions, no cron jobs and no extra work for editors.

##  Feature request

 ### What is the next feature for this plugin?

Submit your idea or vote on existing ones.

  #### Top voted

   Website (leave empty)

'; } html += ''; if (oc.title) { html += '##### ' + escapeHtml(oc.title) + '

'; } if (oc.text) { html += '' + escapeHtml(oc.text).replace(/\\n/g, '
') + '

'; } html += '

'; } // Auto winner(s) - top N from the already vote-sorted features if (mode === 'auto_winner' || mode === 'both') { var n = oc.winnerCount | 0; if (n '; for (var i = 0; i ' + (w.image_url ? '![](https://www.yoozecase.com/'%20+%20escapeHtml(w.image_url)%20+%20')

' : '') + '' + (i + 1) + '' + '' + escapeHtml(w.title) + '' + '' + getIcon(this.cfg.voteIcon) + ' ' + (w.votes | 0) + '' + ''; } html += ''; } } if (html === '') { this.elOutcome.hidden = true; return; } this.elOutcome.innerHTML = html; this.elOutcome.hidden = false; }; /** * Roadmap view (v3.2.0): renders the items as status columns, in the * canonical status order from cfg.statuses. Each column is an 12. inside \* the existing .yc-fb-list , holding its own inner  of items - \* this keeps the delegated click/change handlers on elList working \* unchanged. Unknown statuses fall back into the "open" column so no item \* can silently disappear. Empty columns are skipped when \* cfg.roadmapHideEmpty is set. \*/ Board.prototype.renderRoadmap = function (items) { var stats = (this.cfg.statuses && this.cfg.statuses.length) ? this.cfg.statuses : \['open', 'planned', 'in\_progress', 'shipped', 'declined'\]; var labels = this.cfg.statusLabels || {}; var groups = {}; var i, st; for (i = 0; i ' + '##### ' + '' + escapeHtml(labels\[sv\] || sv) + '' + arr.length + '' + '

    ' + '' + itemsHtml + '
    ' + '
'; } return html; }; Board.prototype.renderItem = function (f, index) { var disabled = this.cfg.isClosed ? 'disabled' : ''; var voted = f.voted ? ' yc-voted' : ''; var descHtml = f.description ? '' + escapeHtml(f.description).replace(/\\n/g, '
') + '

' : ''; var thumbHtml = f.image_url ? '![](https://www.yoozecase.com/'%20+%20escapeHtml(f.image_url)%20+%20')

' : ''; // Status workflow (v3.0.0): badge for any non-default status. The // roadmap view (v3.2.0) skips the badge - the column already // communicates the status, a badge would be redundant noise. var st = (f.status || 'open'); var labels = this.cfg.statusLabels || {}; var statusBadge = (!this.isRoadmap && st && st !== 'open' && labels[st]) ? '' + escapeHtml(labels\[st\]) + '' : ''; // Design themes (v3.1.0): arena / neon / pixel render extra per-item // furniture - rank number, avatar (image or initials), a "leader" pill // on rank 1, and a "votes" label. Classic/colour themes are untouched. var t = this.cfg.theme || 'light'; var themed = (t === 'arena' || t === 'neon' || t === 'pixel'); var rank = (typeof index === 'number') ? (index + 1) : 0; var rankHtml = '', leaderHtml = '', avatarHtml = '', votesLabel = ''; if (themed) { rankHtml = '' + pad2(rank) + ''; if (rank === 1) { leaderHtml = '' + escapeHtml(this.cfg.leaderLabel || 'Leader') + ''; } if (f.image_url) { avatarHtml = '![](https://www.yoozecase.com/'%20+%20escapeHtml(f.image_url)%20+%20')

'; } else { avatarHtml = '' + escapeHtml(initialsOf(f.title)) + '

'; } votesLabel = '' + escapeHtml(this.cfg.votesLabel || 'votes') + ''; } // Moderation overlay: subtle corner buttons, only when canModerate. // Buttons appear on hover/focus (styled in CSS). Even in customizer // preview we render them when canModerate is true so the moderator // can see what visitors with moderation rights will see. var modHtml = ''; if (this.cfg.canModerate) { var parts = []; var hideTitle = escapeHtml(this.t('hideTitle', 'Hide this feature')); var deleteTitle = escapeHtml(this.t('deleteTitle', 'Delete this feature')); if (this.cfg.allowSoftHide) { parts.push( '' ); } if (this.cfg.allowHardDelete) { parts.push( '' ); } if (parts.length || (this.cfg.statuses && this.cfg.statuses.length)) { var sParts = parts.slice(); if (this.cfg.statuses && this.cfg.statuses.length) { var opts = ''; for (var si = 0; si ' + escapeHtml(sl) + ''; } var setStatus = escapeHtml(this.t('setStatus', 'Set status')); sParts.push( '' ); } modHtml = '' + sParts.join('') + '

'; } } var mediaHtml = themed ? avatarHtml : thumbHtml; return ( '32. ' + leaderHtml + rankHtml + '' + mediaHtml + '' + '##### ' + escapeHtml(f.title) + '

    ' + statusBadge + descHtml + '

    ' + modHtml + '
' ); }; /** * Detects whether a JSON response looks like a CSRF/token rejection. * Two cases: * 1. com_ajax-level rejection (Joomla's auto-token-check on POST): top * level message contains the JINVALID_TOKEN_NOTICE text and HTTP * status is typically 403. * 2. Plugin-level rejection from requireToken(): payload.error === "Invalid token". */ Board.prototype.isTokenError = function (status, raw, payload) { if (status === 403) return true; var hay = ''; try { hay = JSON.stringify(raw || {}) + '|' + JSON.stringify(payload || {}); } catch (e) {} return /invalid (security )?token/i.test(hay); }; /** * Fetch a fresh CSRF token from the server. Updates this.cfg.csrfToken so * the next call (and any future calls in this Board's lifetime) use the * correct one. Cache-bust with a timestamp so no upstream CDN caches the * response. */ Board.prototype.fetchFreshToken = function () { var self = this; var url = this.cfg.ajaxUrl + '&task=token&_=' + Date.now(); return fetch(url, { method: 'GET', credentials: 'same-origin', headers: { 'Accept': 'application/json', 'Cache-Control': 'no-cache' } }) .then(function (r) { return r.json(); }) .then(function (data) { var p = self.unwrapAjax(data); if (p && p.ok === true && typeof p.token === 'string' && p.token.length >= 16) { self.cfg.csrfToken = p.token; return p.token; } throw new Error('No fresh token in response'); }); }; /** * Generic POST-with-token helper. Builds FormData from a plain object, * adds the current token, posts. On 403 / token-error response, fetches a * fresh token and retries exactly once. * * @param {string} task The task name (appended to URL and body) * @param {object} fields Key-value form fields (no token) * @return {Promise} Resolves to the unwrapped payload on success. \* Rejects with Error containing .reason on failure. \*/ Board.prototype.postWithToken = function (task, fields) { var self = this; function attempt(token) { var fd = new FormData(); fd.append('task', task); for (var k in fields) { if (Object.prototype.hasOwnProperty.call(fields, k)) { fd.append(k, fields\[k\]); } } fd.append(token, '1'); return fetch(self.cfg.ajaxUrl + '&task=' + encodeURIComponent(task), { method: 'POST', credentials: 'same-origin', body: fd, headers: { 'Accept': 'application/json' } }).then(function (r) { return r.json().then(function (data) { return { status: r.status, raw: data, payload: self.unwrapAjax(data) }; }); }); } return attempt(this.cfg.csrfToken).then(function (res) { // Success path if (res.payload && res.payload.ok === true) { return res.payload; } // Token rejection? Fetch fresh and retry once. if (self.isTokenError(res.status, res.raw, res.payload)) { return self.fetchFreshToken().then(function (fresh) { return attempt(fresh).then(function (res2) { if (res2.payload && res2.payload.ok === true) { return res2.payload; } var err = new Error( (res2.payload && res2.payload.error) || (res2.raw && res2.raw.message) || self.t('requestFailed', 'Request failed.') ); err.payload = res2.payload || null; throw err; }); }); } // Some other error - surface it var err = new Error( (res.payload && res.payload.error) || (res.raw && res.raw.message) || self.t('requestFailed', 'Request failed.') ); err.payload = res.payload || null; throw err; }); }; Board.prototype.handleSubmit = function () { var self = this; if (isInBuilder()) { this.showStatus(this.t('previewSubmit', 'Preview mode - submissions are disabled in the YOOtheme builder. Try this on the published page.'), 'info'); return; } if (this.cfg.isClosed) { this.showStatus(this.cfg.closedMessage || this.t('votingClosed', 'Voting is closed.'), 'info'); return; } var title = (this.elTitle && this.elTitle.value || '').trim(); var desc = (this.elDesc && this.elDesc.value || '').trim(); // Client-side validation: minimum title length. Server re-validates. var minLen = (this.cfg.minTitleLength | 0) || 2; if (title.length for hide/delete, remember parent + sibling for rollback. var li = btn.closest('li'); var parentEl = li ? li.parentNode : null; var nextEl = li ? li.nextSibling : null; if (li && (action === 'hide' || action === 'delete')) { li.remove(); } btn.disabled = true; var task = action === 'hide' ? 'moderate\_hide' : action === 'delete' ? 'moderate\_delete' : action === 'restore' ? 'moderate\_restore' : ''; if (!task) { btn.disabled = false; return; } this.postWithToken(task, { feature\_id: featureId }) .then(function (payload) { // Success - keep the UI as-is (already removed) and refresh // so vote counts, top box, and hidden-features panel reflect // the new state. self.refresh(); if (self.hiddenOpen) { self.hiddenLoaded = false; // force a refetch self.fetchHiddenFeatures(); } var msg = action === 'delete' ? self.t('deleted', 'Feature deleted.') : action === 'hide' ? self.t('hidden', 'Feature hidden.') : action === 'restore' ? self.t('restored', 'Feature restored.') : self.t('done', 'Done.'); self.showStatus(msg, 'success'); setTimeout(function () { self.hideStatus(); }, 3000); }) .catch(function (err) { // Rollback: re-insert the row if we removed it. if (li && parentEl) { if (nextEl) { parentEl.insertBefore(li, nextEl); } else { parentEl.appendChild(li); } } btn.disabled = false; self.showStatus(err && err.message ? err.message : self.t('modFailed', 'Moderation action failed.'), 'error'); }); }; Board.prototype.handleStatusChange = function (featureId, status, sel) { var self = this; if (!featureId || !status) return; sel.disabled = true; this.postWithToken('moderate\_status', { feature\_id: featureId, status: status }) .then(function () { self.refresh(); var label = (self.cfg.statusLabels && self.cfg.statusLabels\[status\]) ? self.cfg.statusLabels\[status\] : status; self.showStatus(self.tf('statusSet', 'Status: %s', label), 'success'); setTimeout(function () { self.hideStatus(); }, 3000); }) .catch(function (err) { sel.disabled = false; self.showStatus(err && err.message ? err.message : self.t('statusFailed', 'Could not set status.'), 'error'); }); }; /\*\* \* Toggle the hidden-features panel open/closed. First open triggers \* an AJAX fetch; subsequent toggles just hide/show the cached list. \*/ Board.prototype.toggleHiddenPanel = function () { if (!this.elHiddenList || !this.elHiddenLabel) return; var arrow = this.elHiddenToggle && this.elHiddenToggle.querySelector('.yc-fb-hidden-arrow'); if (this.hiddenOpen) { this.hiddenOpen = false; this.elHiddenList.hidden = true; this.elHiddenLabel.textContent = this.t('showHidden', 'Show hidden features'); if (arrow) arrow.classList.remove('yc-open'); return; } this.hiddenOpen = true; this.elHiddenList.hidden = false; this.elHiddenLabel.textContent = this.t('hideHidden', 'Hide hidden features'); if (arrow) arrow.classList.add('yc-open'); if (!this.hiddenLoaded) { this.fetchHiddenFeatures(); } }; /\*\* \* Fetch the hidden-features list via the moderator-only endpoint. \* Re-callable to refresh the list after a restore. \*/ Board.prototype.fetchHiddenFeatures = function () { var self = this; if (!this.elHiddenList) return; this.elHiddenList.innerHTML = '2. ' + escapeHtml(this.t('loading', 'Loading...')) + '
'; var url = this.cfg.ajaxUrl + '&task=moderate\_list\_hidden&board\_id=' + encodeURIComponent(this.cfg.boardId); fetch(url, { credentials: 'same-origin', headers: { 'Accept': 'application/json' } }) .then(function (r) { return r.json(); }) .then(function (data) { var payload = self.unwrapAjax(data); if (!payload || payload.ok !== true) { self.elHiddenList.innerHTML = '4. ' + escapeHtml((payload && payload.error) ? payload.error : self.t('hiddenLoadFailed', 'Failed to load hidden features.')) + '
'; return; } self.hiddenLoaded = true; var features = payload.features || \[\]; if (features.length === 0) { self.elHiddenList.innerHTML = '6. ' + escapeHtml(self.t('noHidden', 'No hidden features.')) + '
'; return; } var html = ''; for (var i = 0; i ' + escapeHtml(f.description).replace(/\\n/g, '
') + '' : ''; var restoreTitle = escapeHtml(self.t('restoreTitle', 'Restore this feature')); html += '9. ' + '' + '##### ' + escapeHtml(f.title) + '

    ' + descHtml + '' + escapeHtml(self.tf('votesMeta', '%s votes', f.votes | 0)) + '' + '

    ' + '' + '
'; } self.elHiddenList.innerHTML = html; }) .catch(function () { self.elHiddenList.innerHTML = '11. ' + escapeHtml(self.t('hiddenNetwork', 'Network error while loading hidden features.')) + '
'; }); }; function initAll(scope) { var roots = (scope || document).querySelectorAll('.yc-fb-root'); for (var i = 0; i ---

##  Changelog

---

 [ v3.8.1 13/11/2026 ](#) Changed- The dashboard module and the plugin dashboard say in one sentence that the plugin submits pages and that each search engine decides itself whether and when a page is included.

- Under failed submissions a short explanation: a failure is not always caused by the site or the plugin, a search engine can refuse submissions for a while, and the plugin tries again later.
- The message that IndexNow refuses the server address now says that the address is chosen by the hosting provider, outside the plugin.

 [ v3.8.0 11/11/2026 ](#) Added- The dashboard module on the Control Panel shows how people find the site through Google: clicks from Google, how often the site was shown in the results and the average position over the last 28 days, each next to the 28 days before, a line of clicks per week over 13 weeks, the searches that found the site and the pages with the most clicks, each with its clicks and impressions. Each number has a short explanation. The numbers come from the Search Console connection the plugin already has, are fetched at most once a day and load after the page, so the Control Panel does not wait for Google. A Refresh button fetches them again, at most once per 10 minutes.

- The Google results block in the plugin dashboard shows the same numbers.
- Two options on the Google Search Console tab: Show Google numbers, and Who sees the Google numbers (default Administrator and Super Users; Super Users always see them).

 Changed- The same page is submitted at most once an hour. Saving a page again within the hour no longer sends it again; it waits until the hour is over and then goes out with the latest content. Unpublishing, deleting and submitting by hand still go out at once.
- The dashboard module no longer shows the e-mail address of the Google account the plugin is connected with. It stays visible in the connection field of the plugin options.

 Fixed- An article that is the home page was submitted under its alias (for example /home) instead of the address of the home page. On a multilingual site the home page of each language is submitted with its language code.
- A page without a menu item yet was submitted under its internal address (/component/content/article/...), which redirects later. It is now not submitted until it has a menu item, and saving that menu item submits the page.
- On an update from 3.6.0 this release also brings the changes of 3.7.0.

 [ v3.7.0 09/11/2026 ](#) Changed- The console command ycindexing:process now retries failed submissions by default, like the scheduled task. Use --no-retry to skip that; --retry still works, so existing cron lines need no change.

- The console command ends with exit code 2 when a step of the run failed, also when that was the retry or the promotion of dry runs.
- The scheduled task, the console command and the button in the dashboard run the queue through one shared routine, in the same order. What each of them does is unchanged.
- The license panel says that saving the options keeps the key, and that Deactivate removes it from the site.

 Fixed- Reading the plugin cache waits for a write that is in progress, so two requests at the same moment cannot read half a file.

 [ v3.6.0 08/11/2026 ](#) Added- A copy of a site (a staging site, a clone, a backup restored on another account) is recognised. The plugin keeps a fingerprint of the installation: the folder, the database and the Joomla secret. When it differs, nothing is submitted: new and changed pages are recorded as a dry run, the queue waits, and uninstalling the plugin there does not release the license of the live site. Both dashboards show a warning with two buttons: This is a copy, submit nothing, and This is the real site (after a move to another folder, server or database).

 Changed- The log files are rotated once a day from the administrator and the queue cleanup, no longer checked on every visit to the site.
- The console command says why nothing was sent when the queue waits.

 Removed- The old AJAX task for submitting everything in one request. Since 3.5.0 both dashboards send in batches.

 Security- The stored Google Search Console connection uses separate keys for encryption and for the integrity check. The update converts the stored connection once; you do not have to connect again. Values in the old unencrypted form are no longer read.
- Fetching a sitemap connects to exactly the address that was checked, only over http or https. A sitemap address from the dashboard must be on this site.
- The link Open in Google Search Console only opens an address of Google Search Console. The copy button of the API key no longer carries the key in an inline script.
- The script that submits a page after a save in the YOOtheme Pro builder is only loaded for administrators who may submit, and lives in its own file.

 [ v3.5.0 08/11/2026 ](#) Changed- The dashboard in the plugin options and the administrator module now take their figures from the same place. Until 3.4.0 they counted in their own way: the plugin dashboard showed a page that waits for its publication date as pending on first load and changed its figures after the automatic refresh 30 seconds later.

- Numbers follow the language of the administrator, not the browser. An English administrator shows 2,019, a Dutch one 2.019.
- The button Submit all URLs in the module now sends the pages in batches of 500, like the plugin dashboard. On a large site the old single request could run into the time limit of the server.
- While IndexNow refuses the address of the server, the green box "IndexNow is active" is no longer shown next to the warning.
- The version shown in the dashboard comes from the installed package.

 Fixed- The link "Set now" in the warning about a missing API key did nothing in Joomla 5 and 6. It opens the right tab again.
- Connecting your own Google client: after you fill in the Client ID and Client Secret, a note says that you have to save first before the Connect to Google button becomes active.
- The site router is taken from the Joomla container, ready for Joomla 7.

 Security- The form token no longer travels in the address of a request. It is sent in a header, and every task that changes something is sent as POST. Before, the token ended up in the access log of the server. The buttons that connect and disconnect Google Search Console post the token as a form field.
- Connecting Google Search Console uses a random value that is valid for ten minutes and once. Before, the value was derived from the session and could be used again. The shared connection through connect.yoozecase.com is now also checked on the server, not only in the page.

 [ v3.4.0 07/11/2026 ](#) Added- Skipped items are listed in the dashboards with the reason (noindex, excluded path, not published, not visible without login, no address). The catch-up no longer judges the same item again every run.

- A page that waits for its publication date shows the date in both dashboards.
- A warning in the dashboard and the admin module when IndexNow refuses the address of the server: ten or more answers Too Many Requests over at least a day, without one accepted submission. It explains the likely cause (a shared outgoing address at the hosting provider) and what to do. While it lasts, new pages wait in the queue and the plugin tries once a day.
- A check of the queue table. When an update could not add a column or index, both dashboards say so and how to fix it.
- Disconnecting Google Search Console also withdraws the access at Google.

 Changed- Behaviour change: pages that a visitor who is not logged in cannot see are no longer submitted. This applies to articles, ZOO items and contacts with the access level Registered, Special or a group level, also when the access comes from the category. Their address would tell search engines that the page exists. The new option Filters, Submit restricted content turns the old behaviour back on.
- Unpublished items, items whose publication has ended and ZOO items that are not searchable are no longer submitted, on every route: saving, publishing from the list, the deferred ZOO route and the catch-up.
- An item with a publication date in the future waits in the queue and is sent by the first run after that date. Before, it was submitted at once and then never again.
- Submissions use a fixed site address, the new option IndexNow, Site address for submissions. It is filled in on the first visit to the administrator after the update and shown on the dashboard. A console run or an alias domain can no longer submit for another host, and the console command works without $live\_site when this address is stored.
- A 403 answer is only treated as final when it comes from IndexNow itself. A blocking page of a firewall, CDN or proxy is now retried.
- The error column shows a readable reason instead of the raw answer of IndexNow. The full answer stays in the log file.
- The IndexNow key is created during installation. A fresh install no longer waits for the first visit to the site.

 Fixed- Two runs at the same time (the scheduled task, the console, a button, a direct send) could send the same queue row twice. A row is now claimed before it is sent; a claim older than 15 minutes is released again.
- The same URL in one batch is sent once. The duplicate check now runs on the final URL after following the site's own redirects.
- Old rows are also cleaned on sites without the Clean old entries task, once a day. Before, cleaning was skipped whenever the queue was empty.
- The catch-up looks at the items that were not handled yet, with its own limit for articles and for ZOO items, so a busy ZOO site no longer pushes articles out.
- Addresses with non-ASCII characters (an accented letter or a curly apostrophe in an alias, an international domain name) were refused without a trace. They are now submitted in their encoded form.
- A sitemap index that lists itself, or nests deeper than three levels, no longer makes the sitemap reader loop.
- Saving a new ZOO item no longer waits for the submission on PHP-FPM servers.
- Unused Google tokens of the old plugin versions (IndexNow and YC Indexing) are removed from the database.
- On a phone the dashboard in the plugin options no longer runs past the edge of the tab. The Google Search Console status table scrolls on its own.

 [ v3.3.0 06/11/2026 ](#) Added- A check that compares the static JSitemap Pro files in robots.txt with the live JSitemap Pro sitemap. It shows which URLs are only in the file and, for sitemap\_xml.xml, which live URLs the file lacks, with what to change in robots.txt. It runs only when you click it, in the sitemap list of the dashboard and of the admin module. When the files differ, the dashboard and the module show the last outcome with its date for 24 hours.

 Changed- When JSitemap Pro is installed, a Sitemap line in robots.txt that points to a static JSitemap Pro file (sitemap\_xml.xml, sitemap\_images.xml and other sitemap\_\*.xml files in the site root) is no longer submitted next to the live JSitemap Pro sitemap. Such a file only changes when JSitemap Pro writes it again, so it could submit pages that were renamed or removed. The file stays in the list, marked as a static file and unchecked; you can still check it. When the live JSitemap Pro sitemap gives no URLs, for example after a timeout on a large site, the static file is used instead and the list says so.

 Fixed- The button "Submit sitemap" in the admin module on the control panel said "No sitemaps found" on every site, also when the plugin found several. The list now opens with the sitemaps and their URL count, like in the plugin dashboard.
- Messages of the admin module (bulk submit, sitemap, retry, export) appeared at the top of the page, out of view when you work in the module. They now show in the module, under its buttons.
- Installing or updating the package showed technical lines such as "set #\_\_modules\_menu record for module 146 (menuid=0)" on the installer page. These lines now go only to the log file administrator/logs/yc\_traffic\_boost\_indexing.php. When an install step fails, the message is translated.

 [ v3.2.4 02/11/2026 ](#) Fixed- A Download Key entered under System, Update Sites was cleared on every update when the license was not activated in the plugin. It now stays, and the plugin activates it by itself on the next administrator page. If that key cannot be activated, the license panel says why.

 [ v3.2.3 27/10/2026 ](#) Added- The dashboard and the admin module warn when there is no enabled task "Traffic Boost Indexing: process queue", with a button to create it. Without that task, missed items are never caught up and the batch mode never sends.

- The console command ycindexing:process now runs the catch-up of missed articles and ZOO items too, like the scheduled task. Use --no-catchup to skip it, and --live-site=https://www.example.com when $live\_site is empty.
- Items that are not submitted are logged with the reason (no URL, excluded path, noindex, submitted shortly before) when they come from the end-of-request route or the catch-up, also with debug mode off. A new ZOO item without an id is logged with the type of data ZOO passed.

 Changed- A scheduled run in which the catch-up or the retry fails is reported as a failed run.

 Fixed- New ZOO items were still not submitted after 3.2.2. On some sites ZOO hands the plugin the form data of a new item, without an id and without an alias, so looking the item up at the end of the request found nothing. The plugin now also looks for published ZOO items that were created or changed during that same request, in the same app, and submits them.
- On a site with more than one ZOO app, an item without its own menu item could get its URL from the menu item of another app. The plugin now uses a menu item of the item's own app and logs it when there is none.
- The console command php cli/joomla.php ycindexing:process did not exist: the plugin listened for an event name the Joomla console does not send. It is registered now.
- On the console, every URL started with the path of cli/joomla.php, because Joomla has no site address there. The command now stops with a clear message when no address is known, and uses the address from --live-site or $live\_site for this run.
- Deactivating the license key while the license server answered "too many requests" or "server error" cleared the key on the site while the activation stayed taken on the server. The key and its status now stay until the server confirms. Activating the same key again no longer takes a second activation, and a new key releases the old one.

 Security- The Google client secret and the health check token are no longer written into the options screen. The fields stay empty after saving and show only the last four characters of the client secret, or only that a token is stored. Leave a field empty to keep the stored value, type a single - to remove it. This also works while the plugin is disabled. A health token with other characters than letters and digits, or shorter than 16 characters, is refused with a message and the stored token stays.

 [ v3.2.2 18/10/2026 ](#) Added- Catch-up in the scheduled task "Traffic Boost Indexing: process queue": each run also submits published articles and ZOO items that changed or went live in the last 48 hours and have no submission since, at most 25 per run. This covers content that arrives without a usable save event (an import, a script) and items with a publish date in the future. A new switch on the Content Types tab turns it off; it is on by default.

 Fixed- New ZOO items were not submitted. ZOO reports a new item to the plugin before it has an id, so the plugin could not build its URL and skipped it without a trace. The plugin now resolves such an item at the end of the request, by its id or else by its alias, and submits it then. Edited items were not affected.

## Schema

```json
{
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
        {
            "@type": "ListItem",
            "position": 1,
            "name": "Home",
            "item": "https://www.yoozecase.com"
        },
        {
            "@type": "ListItem",
            "position": 2,
            "name": "Extensions",
            "item": "https://www.yoozecase.com/extensions"
        },
        {
            "@type": "ListItem",
            "position": 3,
            "name": "Traffic Boost Indexing",
            "item": "https://www.yoozecase.com/"
        }
    ]
}
```
