SiteSuperCharger helps your website look as attractive as possible to search engines helping you to acheive the highest search engine rankings.<\/p>\n\n
Contact Marketing Heroes (https:\/\/www.mheroes.com) to get started!<\/p>\n\n\n
Install SiteSuperCharger via the plugin directory, or by uploading the files manually to your server. After activating SiteSuperCharger, you'll need to enter your GUID at Settings -> SiteSuperCharger<\/p>\n\n
For info about acquiring a GUID for SiteSuperCharger visit https:\/\/www.mheroes.com.<\/p>\n\n\n
You must purchase Search Engine Optimization services from Marketing Heroes (https:\/\/www.mheroes.com) to use SiteSuperCharger<\/p><\/dd>\n\n<\/dl>\n\n\n
__trashed<\/code> slugs, so a trashed page can no longer be advertised to search engines.<\/li>\n<\/ul>\n\n5.8.48<\/h4>\n\n\n- Managed blog archive: when the SSC app provides a blog archive path, the plugin now ensures the archive page exists and that WordPress renders the post index on it. Fixes sites whose blog posts were publishing correctly but whose blog page was missing or showed placeholder content. Never overrides an existing working posts-page choice, never edits page content, and leaves sites whose homepage is the blog untouched.<\/li>\n<\/ul>\n\n
5.8.45<\/h4>\n\n\n- Fixed: when a page on your site could not be matched to an entry in your site plan, the plugin quietly treated it as if it were the FIRST page in that plan. It then renamed the page to that first page's address. This is what put the wrong address on pages - for example a Kissimmee tile roofing page ending up at \/kissimmee-florida\/tile-roofing\/commercial-roofing\/, and, where that address was already taken, at \/commercial-roofing-2\/, \/commercial-roofing-3\/ and so on. The plugin now leaves a page it cannot match completely alone.<\/li>\n
- Fixed: the safety check that was meant to stop exactly this (\"never guess an address\") could never actually trigger, because the lookup it relied on never reported a failure. It reports one now.<\/li>\n
- Note: this stops any NEW addresses from being changed. Addresses already changed on your site are not touched by this update - putting those back is a separate, deliberate step.<\/li>\n<\/ul>\n\n
5.8.44<\/h4>\n\n\n- Fixed: addresses with a number stuck on the end (for example \/attic-insulation-158\/) are no longer listed in the sitemap your site sends to Google. On one site 196 of 646 listed addresses were of this kind, and they were being sent to Google every day. The pages themselves are untouched - nothing is deleted, moved or redirected by this change, they simply stop being advertised.<\/li>\n
- Changed: an address is only left out when the page belongs to the service AND the numbered part is confirmed against the rest of your site, so a page you wrote yourself and a genuine address like \/best-roofing-for-2024\/ are never affected.<\/li>\n
- Added: the plugin's Sitemap panel now reports how many such addresses it found and whether it could read the site at all, because \"found none\" and \"could not look\" are different answers.<\/li>\n<\/ul>\n\n
5.8.43<\/h4>\n\n\n- Fixed: the per-site \"pause\" setting did not reach the part of the plugin that changes page addresses, so a site that had been paused could still have addresses changed. It now stops all of it.<\/li>\n
- Fixed: pages the service built that had a number stuck on the end of their address (for example \/commercial-roofing-2\/) are corrected back to the proper address automatically, and the old address forwards to the new one. This is on by default, because leaving those addresses in place is the problem being fixed.<\/li>\n
- Changed: when the address a page needs is already in use by one of YOUR pages, the service page takes the address and your page is moved to a marked address ending in \"-admin-\" and its ID. Your page keeps its content, its title, its status and its place in your menus - only the address changes. CORRECTION TO EARLIER RELEASE NOTES: the 5.8.40 and 5.8.43 notes previously said pages you wrote yourself are never renamed. That was wrong, and this is the accurate description.<\/li>\n
- Changed: when the service cannot tell whether a page is one of yours or one of ours - for example one of ours that lost its shortcode when a page builder saved over it - nothing is renamed at all. It is left exactly as it is and listed for a person to look at.<\/li>\n
- Changed: a section page is not renamed if one of its own child pages already uses the address it wants, because the result would be an address with the same word twice (\/commercial-roofing\/commercial-roofing\/). Those are listed instead, to be dealt with properly rather than moved twice.<\/li>\n
- Changed: the plugin now shows a clear warning in your WordPress admin whenever any of its features has been switched off on your site, and how long it has been off. These settings are meant to be temporary.<\/li>\n<\/ul>\n\n
5.8.42<\/h4>\n\n\n- Fixed: when the plugin renames one of its own pages, other plugins can automatically create a forwarding rule for the old address, and some of those rules pointed the wrong way and sent visitors in a circle. The plugin now records the rules its own renames caused, so exactly those can be undone and rules a person created by hand are left alone.<\/li>\n
- Changed: undoing those rules is off by default and lists what it would do first.<\/li>\n<\/ul>\n\n
5.8.41<\/h4>\n\n\n- New: a genuine report-only mode. It works out everything it would change and then writes none of it, so the report can be read before anything happens on a live website.<\/li>\n<\/ul>\n\n
5.8.40<\/h4>\n\n\n- Fixed: pages that ended up with a number stuck on the end of their web address (for example \/commercial-roofing-2\/ instead of \/commercial-roofing\/). These were created years ago when two pages briefly wanted the same address, and once it happened nothing ever put them right. The plugin now recognises those pages as the ones it already made, moves them back to the correct address, and forwards the old address to the new one so no existing link or search result breaks.<\/li>\n
- Fixed: section pages (the directory pages that sit above your service and location pages) could end up with a name that belonged to a different page, and the name was never corrected afterwards. That is what made two different pages show up under the same name when choosing a page for a menu. Section page names are now re-checked and corrected every time the site is refreshed.<\/li>\n
- Fixed: a page could quietly get a numbered web address when an image happened to already be using the address the page needed. The plugin now checks for that case as well.<\/li>\n
- Changed: if a market is removed from your site's settings, the pages the service built for it are now removed from the website as well, and those addresses are retired outright rather than being forwarded somewhere else. Forwarding would tell search engines the page had moved, which would keep a market you no longer serve alive in search results. Any old forwarding rule still pointing at one of those addresses is cleared out at the same time.<\/li>\n
- Changed: pages the service built that are not part of your site's plan \u2014 extra copies of a page that already exists at its correct address, and leftovers from features that no longer exist \u2014 are now removed and their old addresses forwarded to the right page, rather than being left lying around. A page is only removed once the plugin has confirmed, for that individual page, that its content is already being served at the correct address. If it cannot confirm that, the page is left alone and reported instead.<\/li>\n
- Changed: this removal starts in report-only mode on every website. It lists exactly what it would remove and changes nothing until it is switched on for that site.<\/li>\n
- Changed: pages you wrote yourself are never removed, renamed, hidden or re-addressed by any of this, whatever the service may once have recorded about them.<\/li>\n
- Changed: any menu links pointing at a page being removed are pointed at its replacement first, so a menu never loses an entry.<\/li>\n
- Changed: the \"Clean up duplicates\" button no longer deletes anything permanently. It sets duplicates back to draft and forwards their addresses instead.<\/li>\n
- New: every time the site finishes refreshing its content it now checks its own pages for wrong addresses and wrong section-page names, and corrects what it can, automatically. This replaces a manual clean-up that had to be run by hand.<\/li>\n
- New: the Pages screen now labels pages the service manages and shows which record each one belongs to, so two similarly-named pages can be told apart at a glance.<\/li>\n
- New: where the same page ended up existing twice at two different web addresses, the extra copy is removed and its address forwarded to the correct one. The correct address is taken from your site's own settings record, so the forward always lands on the right page rather than on a best guess.<\/li>\n
- New: pages you built yourself are recognised as yours and are never touched, even if they happen to sit on a web address the service created long ago. Where that has happened, the Pages screen now says so and asks for a person to look, rather than the plugin deciding anything.<\/li>\n
- New: a site-level switch to pause all of the above on an individual website if it is ever needed.<\/li>\n<\/ul>\n\n
5.8.38<\/h4>\n\n\n- Combined release: this version delivers the 5.8.35, 5.8.36 and 5.8.37 improvements below as a single update. None of those version numbers were ever published on their own; 5.8.38 is the first release to carry them.<\/li>\n<\/ul>\n\n
5.8.37<\/h4>\n\n\n- Performance: pages now load noticeably faster for visitors. Every single page view \u2014 including the home page, the about page and blog posts \u2014 was quietly downloading the site's full settings file from the service first and waiting for it to arrive before anything could be shown. On larger sites that file is two to three megabytes, and the wait was close to a second on a good connection and much longer on a slow one. The file is now kept on the site and re-used between visitors, so that wait is gone for almost every page view.<\/li>\n
- The settings file is refreshed as soon as the service updates it, so nothing becomes out of date; it is also re-checked at least twice a day regardless, and can be refreshed on demand from the service at any time.<\/li>\n
- If the stored copy is ever missing or unreadable, the site simply fetches a fresh one exactly as it did before, and any problem is written to the site's own log rather than passed silently over.<\/li>\n<\/ul>\n\n
5.8.36<\/h4>\n\n\n- New: if a website stops being managed by the service, the plugin now steps back on its own. The pages the service created stop being served and forward visitors on instead, and the plugin stops sending anything back to the service. The plugin stays installed and keeps receiving updates, the site's own pages, posts and settings are left exactly as they are, and the built-in security protections keep running.<\/li>\n
- New: a site is told about this through the settings file it already checks, so it takes effect on its own without anyone needing to sign in to the site. If the site is put back under management, everything switches straight back on.<\/li>\n
- Note: forwarding is off unless a forwarding address has been set for the site. Where no forwarding address is set, the created pages are marked as permanently removed instead, which is the clearer signal to search engines.<\/li>\n<\/ul>\n\n
5.8.35<\/h4>\n\n\n- Fix: pages written for a specific city or town are no longer skipped over by an out-of-date redirect. On some sites an old redirect rule was still sending visitors (and Google) from a city page to the general, non-city version of the same page, so the city page's own writing was never seen even though the page was published and complete. Those out-of-date rules are now switched off automatically. They are only switched off, never deleted, so they stay visible and can be switched back on at any time.<\/li>\n
- New: when a page's web address changes during a content update, visitors and search engines are now forwarded automatically from the old address to the new one. Previously the old address simply stopped working, so anyone arriving from a search result, a link or a bookmark saw a \"page not found\". Renaming a section forwards every page underneath it as well. A page that is genuinely removed is not forwarded anywhere, and a forwarding rule set up by hand is never overwritten.<\/li>\n
- Fix: an automatic forwarding rule is now switched off by itself if the page it points away from comes back. Forwarding rules can no longer end up hiding a page that is live and complete.<\/li>\n
- Performance: content updates that rename or move a lot of pages now finish considerably faster. The forwarding rules for every moved page are worked out once at the end of the update instead of separately for each page, which on larger sites removes hundreds of repeated database scans and, with them, a real risk of an update timing out part-way through.<\/li>\n
- Performance: the automatic redirect check no longer re-runs on every page view on a site where it has found an unusually large number of rules and stopped for safety. It waits, then tries again after the next content update, so an unusual site cannot slow itself down.<\/li>\n<\/ul>\n\n
5.8.32<\/h4>\n\n\n- Fix: a site that had not yet finished linking to SiteSuperCharger no longer shows the temporary \"this page is being updated\" message on its pages. That message is now reserved for sites that are already connected, so a site that is still linking renders normally instead.<\/li>\n
- Fix: the canonical-address redirect now keeps each site on its own address scheme (http or https). A site set up without HTTPS is never sent to a secure address it does not have.<\/li>\n
- New: a per-site setting to switch the \"being updated\" message off if a site ever needs it, without changing any code.<\/li>\n<\/ul>\n\n
5.8.31<\/h4>\n\n\n- Fix: a site whose connection key was missing (blank) could get stuck disconnected permanently and never retry on its own. It now re-links itself automatically, on the same slow, once-every-few-hours schedule the plugin already used, and stores the new key in the normal place so it can still be rotated.<\/li>\n<\/ul>\n\n
5.8.30<\/h4>\n\n\n- Performance: pages with a lot of images now load much faster. Image lookups are grouped into a couple of database requests per page instead of one per image, and repeated images are only looked up once.<\/li>\n
- Performance: each page now loads its content from our servers once per visit instead of twice, so pages render faster and a slow or unreachable connection no longer doubles the delay.<\/li>\n
- New: if a page's content is temporarily unavailable, visitors now see a short, friendly \"this page is being updated\" message instead of a blank area, and search engines are told the page is temporarily unavailable so it keeps its place in search results.<\/li>\n
- New: a per-site setting to pause image substitution if a site ever needs it, without switching the whole plugin off.<\/li>\n
- Fix: image lookups no longer mis-handle file names containing quotes or backslashes.<\/li>\n<\/ul>\n\n
5.8.29<\/h4>\n\n\n- Fix: repeated content syncs no longer create duplicate directory\/parent pages with numbered web addresses (like -2 or -7), so page URLs stay stable on multi-location and multi-service sites.<\/li>\n<\/ul>\n\n
5.8.28<\/h4>\n\n\n- Fix: a site that was given a connection key but never finished linking to SiteSuperCharger now completes the connection on its own, so its pages load correctly instead of showing \"not found.\"<\/li>\n<\/ul>\n\n
5.8.27<\/h4>\n\n\n- Fix: your location and service pages now all load, even when several share the same name in different areas.<\/li>\n<\/ul>\n\n
5.8.26<\/h4>\n\n\n- Fix: pages listed in your sitemap that returned \"page not found\" are now created and load correctly.<\/li>\n<\/ul>\n\n
5.8.25<\/h4>\n\n\n- Fix: pages that were showing only a list of links now display their full content again.<\/li>\n<\/ul>\n\n
5.8.24<\/h4>\n\n\n- Fix: your page content keeps showing even after a page is edited in your site builder.<\/li>\n<\/ul>\n\n
5.8.23<\/h4>\n\n\n- Fix: your service pages now load at their correct address instead of redirecting to the wrong page.<\/li>\n<\/ul>\n\n
5.8.22<\/h4>\n\n\n- Fix: the FAQ section now appears once, below your page content, instead of repeating above it.<\/li>\n<\/ul>\n\n
5.8.21<\/h4>\n\n\n- Fix: a blog's featured image now appears on your site right away after it's added or updated.<\/li>\n
- Fix: an image that fails to load the first time is retried automatically instead of staying blank.<\/li>\n<\/ul>\n\n
5.8.20<\/h4>\n\n\n- Fix: blog featured images no longer disappear or show an outdated image after an update.<\/li>\n
- Fix: a failed image download is retried cleanly instead of leaving a broken image behind.<\/li>\n<\/ul>\n\n
5.8.19<\/h4>\n\n\n- New: your site can reconnect to SiteSuperCharger on its own if the connection is ever lost.<\/li>\n<\/ul>\n\n
5.8.17<\/h4>\n\n\n- Fix: keeps your site's status reporting to SiteSuperCharger reliably, so a quiet site is noticed promptly.<\/li>\n<\/ul>\n\n
5.8.15<\/h4>\n\n\n- Fix: the API token you enter on the settings page now saves and stays saved.<\/li>\n
- Fix: a saved token is shown masked so you can confirm the right one is in place.<\/li>\n<\/ul>\n\n
5.8.14<\/h4>\n\n\n- Fix: restores landing pages that were unexpectedly missing after an earlier update.<\/li>\n
- Fix: protects SiteSuperCharger pages from being removed during routine rebuilds.<\/li>\n
- Fix: clears legacy redirects on sites using a third-party SEO redirect tool.<\/li>\n<\/ul>\n\n
5.8.13<\/h4>\n\n\n- Fix: restores landing pages still being redirected to a broken URL by a third-party redirect plugin.<\/li>\n
- Fix: prevents future page renames from creating those broken redirects.<\/li>\n<\/ul>\n\n
5.8.12<\/h4>\n\n\n- Fix: restores landing pages that were redirecting to a broken URL and returning a 404.<\/li>\n
- Fix: prevents the redirect-hijack from happening again on future page updates.<\/li>\n<\/ul>\n\n
5.8.10<\/h4>\n\n\n- Fix: pages with very long content stay reliable on PHP 8.1+ even at the largest body sizes.<\/li>\n
- Fix: sites that previously used a third-party sitemap shortcode now display the full SiteSuperCharger sitemap automatically.<\/li>\n<\/ul>\n\n
5.8.9<\/h4>\n\n\n- Fix: pages with very long content no longer trigger a server error on PHP 8.1+.<\/li>\n<\/ul>\n\n
5.8.7<\/h4>\n\n\n- Fix: robots.txt compatibility with major search engines.<\/li>\n
- Fix: cleans up legacy robots.txt content on first load after update.<\/li>\n<\/ul>\n\n
5.8.6<\/h4>\n\n\n- Fix: prevents duplicate-post creation on large rebuilds.<\/li>\n
- Fix: transient HTTP errors during rebuilds now retry with backoff.<\/li>\n
- Carryforward: includes v5.8.4 and v5.8.5 (held internal, never shipped to wp.org).<\/li>\n<\/ul>\n\n
5.8.5<\/h4>\n\n\n- Fix: canonical-host redirects on subdirectory installs preserve the path. (Bundled into 5.8.6.)<\/li>\n<\/ul>\n\n
5.8.4<\/h4>\n\n\n- Fix: canonical-host enforcement skips .htaccess writes on multisite installs. (Bundled into 5.8.6.)<\/li>\n<\/ul>\n\n
5.8.3<\/h4>\n\n\n- Fix: canonical-host enforcement installs reliably on every plugin update path.<\/li>\n<\/ul>\n\n
5.8.2<\/h4>\n\n\n- Improvement: visitors on the non-canonical host are 301-redirected to the canonical host on every request, consolidating ranking signals.<\/li>\n
- Improvement: bot-crawler policy bundle included (originally held as v5.8.0 \/ v5.8.1).<\/li>\n<\/ul>\n\n
5.7.0<\/h4>\n\n
Release date: 2026-05-24<\/p>\n\n
\n- Improvement: Frequently-asked-questions content now stays current automatically and matches what's shown on the page.<\/li>\n
- Improvement: Related-page navigation links and richer structured data now render on area landing pages.<\/li>\n<\/ul>\n\n
5.6.8<\/h4>\n\n
Release date: TBD<\/p>\n\n
\n- Improvement: Scheduled posts now publish with their hero image.<\/li>\n<\/ul>\n\n
5.6.7<\/h4>\n\n
Release date: TBD<\/p>\n\n
\n- New: Added a broken-link checker.<\/li>\n
- New: Added a standalone mode for sites not connected to the platform.<\/li>\n<\/ul>\n\n
5.6.6<\/h4>\n\n
Release date: TBD<\/p>\n\n
\n- Fix: Plugin recommendations and warnings are more accurate.<\/li>\n
- Fix: Removing a plugin now reliably clears it from the list, and reports a clear error if it cannot be removed.<\/li>\n<\/ul>\n\n
5.6.5<\/h4>\n\n
Release date: TBD<\/p>\n\n
\n- Improvement: The image-optimization status now reflects the live state accurately.<\/li>\n
- New: The AI image SEO prompt for a site is now viewable in the plugin.<\/li>\n<\/ul>\n\n
5.6.3<\/h4>\n\n
Release date: TBD<\/p>\n\n
\n- Improvement: Image-optimization settings now sync reliably across sites.<\/li>\n<\/ul>\n\n
5.6.2<\/h4>\n\n
Release date: TBD<\/p>\n\n
\n- Fix: Blog hero images now attach reliably to published posts, including posts whose titles contain special characters.<\/li>\n<\/ul>\n\n
5.6.1<\/h4>\n\n
Release date: TBD<\/p>\n\n
\n- New: Support for scheduled post publishing.<\/li>\n<\/ul>\n\n
5.6.0<\/h4>\n\n
Release date: TBD<\/p>\n\n
\n- Admin improvements.<\/li>\n
- Stability fixes.<\/li>\n<\/ul>\n\n
5.5.35<\/h4>\n\n
Release date: May 4th, 2026<\/p>\n\n
\n- Admin improvements.<\/li>\n
- Stability fixes.<\/li>\n
- Bugfixes.<\/li>\n<\/ul>\n\n
5.5.34<\/h4>\n\n
Release date: May 4th, 2026<\/p>\n\n
\n- Admin improvements.<\/li>\n
- Stability fixes.<\/li>\n
- Internal cleanup.<\/li>\n
- Admin tools.<\/li>\n<\/ul>\n\n
5.5.33<\/h4>\n\n
Release date: Apr 30th, 2026<\/p>\n\n
\n- SEO improvements.<\/li>\n
- Stability fixes.<\/li>\n<\/ul>\n\n
5.5.32<\/h4>\n\n
Release date: Apr 29th, 2026<\/p>\n\n
\n- Internal cleanup.<\/li>\n
- Stability fixes.<\/li>\n
- Interface improvements.<\/li>\n<\/ul>\n\n
5.5.31<\/h4>\n\n
Release date: Apr 28th, 2026<\/p>\n\n
\n- Performance improvements.<\/li>\n
- Stability fixes.<\/li>\n
- Bugfixes.<\/li>\n<\/ul>\n\n
5.5.30<\/h4>\n\n
Release date: Apr 27th, 2026<\/p>\n\n
\n- Stability fixes.<\/li>\n
- Security improvements.<\/li>\n
- Bugfixes.<\/li>\n
- Admin improvements.<\/li>\n<\/ul>\n\n
5.5.29<\/h4>\n\n
Release date: Apr 26th, 2026<\/p>\n\n
\n- Improvement: SiteSuperCharger now keeps itself up to date automatically, so your site always runs the latest version without manual updates. This can be turned off if you need to stay on a specific version. Other plugins on your site are unaffected.<\/li>\n<\/ul>\n\n
5.5.28<\/h4>\n\n
Release date: Apr 25th, 2026<\/p>\n\n
\n- Improvement: The Overview tab now shows your site's connection details with click-to-select formatting, making support tickets quicker to file.<\/li>\n
- New: A \"Sync now\" button on the Overview tab pulls your latest settings from SiteSuperCharger immediately, handy right after you change settings.<\/li>\n
- Improvement: When you publish or update a page or post, that page's cache is refreshed automatically so visitors see fresh content right away.<\/li>\n
- New: A clear on-screen warning now appears if your site's connection to SiteSuperCharger needs attention, so you can fix it before features are affected.<\/li>\n
- Improvement: Clearer sitemap status messaging.<\/li>\n
- Improvement: The AI crawler policy setting is now a plain-English option list with a description for each choice, plus a link to view your live robots.txt so you can confirm the policy took effect.<\/li>\n
- New: Lead-conversion tracking for Gravity Forms, Contact Form 7, WPForms, and Formidable Forms: successful form submissions are now recorded as conversions automatically, with no extra plugin required.<\/li>\n
- New: Connect a Cloudflare account directly from the Security tab. Your credentials are sent securely to SiteSuperCharger and are never stored on your WordPress site.<\/li>\n
- Improvement: Sensitive credentials are no longer kept on your WordPress site; SiteSuperCharger performs credential-based actions on your behalf.<\/li>\n
- New: An \"Export URLs\" option on the Sitemap tab downloads a CSV of every published URL on your site (pages, posts, and public custom post types), replacing the need for a separate export plugin.<\/li>\n
- Improvement: More accurate plugin recommendations, including guidance on which separately installed plugins SiteSuperCharger now makes redundant.<\/li>\n
- Improvement: Refreshed save-button styling across the admin screens.<\/li>\n
- New: A manual \"refresh this page's cache\" button on the post and page editor for when you want to clear the cache without re-saving.<\/li>\n
- New: A daily email digest when your site's overall SiteSuperCharger health grade drops a letter, listing the failing checks. No email on recoveries or unchanged grades; can be turned off in settings.<\/li>\n
- New: A \"Recent activity\" card on the Overview tab shows the last few things SiteSuperCharger has done, without leaving the page.<\/li>\n
- Improvement: Maintenance actions are now clearer, with a labelled description and button for each.<\/li>\n
- New: A \"How to reach a perfect score\" guidance bar on the Health tab (shown when your grade is below A) lists the most common gaps in plain language.<\/li>\n
- Improvement: Add redirects directly from the Redirects tab with an inline form, instead of switching to the classic admin screen.<\/li>\n
- Improvement: The Tracking tab now lists every tracking ID your site emits and whether each is configured, so you can see exactly what's active at a glance.<\/li>\n
- New: A \"Current schema values\" card on the Schema tab shows how many trust badges and reviews are configured, plus a one-click button to run Google's Rich Results test for your home page.<\/li>\n
- Fix: Closes a landing-page 404 issue caused by slug collisions. When a landing page's preferred URL was already taken by another page, SiteSuperCharger used to create the page at a slightly different URL, breaking the canonical link. SiteSuperCharger now reclaims the correct URL safely: any stale or conflicting page is preserved (moved to Trash or renamed, recoverable) so the intended landing-page URL is restored.<\/li>\n<\/ul>\n\n
5.5.27<\/h4>\n\n
Release date: Apr 24th, 2026<\/p>\n\n
\n- New: A daily file-integrity check watches your plugin, theme, and core files for unexpected changes, helping catch tampering and silent file corruption early.<\/li>\n
- Improvement: Bundles every fix and feature from 5.5.22 through 5.5.26 (cumulative release).<\/li>\n<\/ul>\n\n
5.5.26<\/h4>\n\n
Release date: Apr 24th, 2026<\/p>\n\n
\n- WooCommerce purchase tracking in Google Analytics 4: product views, add-to-cart, checkout-started, and completed purchases all flow into GA4 automatically \u2014 no separate plugin needed. Includes a duplicate-event guard so refreshing the thank-you page never inflates revenue numbers.<\/li>\n<\/ul>\n\n
5.5.25<\/h4>\n\n
Release date: Apr 24th, 2026<\/p>\n\n
\n- New
[ssc-howto]<\/code> shortcode for service landing pages: produces a step-by-step instruction list with the search-engine schema markup that Google uses for HowTo rich results.<\/li>\n- Redundant-plugin nudge: when SiteSuperCharger now covers something a separately installed plugin used to do (for example MonsterInsights, Insert Headers and Footers, the Cloudflare official plugin), the admin sees a one-time, dismissible notice on activation pointing them to the SiteSuperCharger setting that replaces it.<\/li>\n<\/ul>\n\n
5.5.24<\/h4>\n\n
Release date: Apr 24th, 2026<\/p>\n\n
\n- Spam blog-post quarantine: backlink-spam posts (casino \/ pharma \/ payday-loan patterns) are auto-moved to Trash and an email is sent to the admin. Nothing is ever permanently deleted \u2014 every action is recoverable from Trash.<\/li>\n<\/ul>\n\n
5.5.23<\/h4>\n\n
Release date: Apr 24th, 2026<\/p>\n\n
\n- New: Google Consent Mode v2 support: tracking pixels (Google Analytics, Meta Pixel, Google Ads) now start in a privacy-respecting \"denied\" state and only upgrade to full tracking once the visitor accepts cookies through your consent banner. Works with common consent banners including CookieYes, Complianz, and Cookiebot.<\/li>\n
- Google Ads remarketing \/ conversion tag: enter a Google Ads ID in tracking settings and the AW- conversion tag is injected automatically.<\/li>\n<\/ul>\n\n
5.5.22<\/h4>\n\n
Release date: Apr 23rd, 2026<\/p>\n\n
\n- Fix: Closed two account-enumeration leaks that let anonymous visitors harvest usernames and site settings. Logged-in editors and admins still get normal access. Together with the existing protections, this stops the most common username-harvesting probes used against WordPress.<\/li>\n
- Improvement: Admin improvements.<\/li>\n<\/ul>\n\n
5.5.21<\/h4>\n\n
Release date: Apr 23rd, 2026<\/p>\n\n
\n- New: Delete leftover (orphaned) plugin folders directly from the Plugins tab, with safety checks so only genuine leftovers can be removed.<\/li>\n
- Improvement: Expanded plugin recommendations, flagging plugins that conflict with SiteSuperCharger, that are unnecessary on a managed site, or that SiteSuperCharger already covers.<\/li>\n<\/ul>\n\n
5.5.20<\/h4>\n\n
Release date: Apr 23rd, 2026<\/p>\n\n
\n- New: The Plugins tab now flags dangerous, conflicting, duplicate, and orphaned plugin installs, with a summary banner and per-row labels so you can see at a glance what needs attention.<\/li>\n
- New: Leftover plugin folders (disabled, old, or backup copies) are detected and surfaced for cleanup.<\/li>\n
- Improvement: The Plugins tab \"Updated\" column now shows the month and year for clarity across release years.<\/li>\n
- Improvement: Cleaner sitemap display on the Sitemap tab.<\/li>\n<\/ul>\n\n
5.5.19<\/h4>\n\n
Release date: Apr 23rd, 2026<\/p>\n\n
\n- og:video tags for blog posts with embedded YouTube\/Vimeo (og:video, og:video:type, og:video:width\/height).<\/li>\n
- preconnect hints for Google Maps on landing pages (maps.googleapis.com + maps.gstatic.com).<\/li>\n
- preconnect hints for YouTube\/Vimeo on blog posts with detected video embeds.<\/li>\n<\/ul>\n\n
5.5.18<\/h4>\n\n
Release date: Apr 23rd, 2026<\/p>\n\n
\n- Twitter\/X Card meta tags on all landing pages and blog posts (twitter:card, twitter:title, twitter:description, twitter:image).<\/li>\n
- Blog post Open Graph completeness: og:type=article, og:url, og:locale, og:site_name, article:published_time, article:modified_time, article:author, article:section, og:image:width\/height.<\/li>\n
- Landing page og:image:width + og:image:height via WP attachment lookup for richer social previews.<\/li>\n
- AI Crawler Policy settings card in v6 Security tab - editable with live AJAX save and robots.txt sync.<\/li>\n<\/ul>\n\n
5.5.17<\/h4>\n\n
Release date: Apr 22nd, 2026<\/p>\n\n
\n- New: Each site now reports its health (plugin\/WordPress\/PHP versions, content totals, and any plugin conflicts) automatically, so account managers can see site status without logging in.<\/li>\n
- New: Content cross-check catches missing or extra pages, blog posts, and FAQs early.<\/li>\n
- New: Common maintenance tasks (refresh cache, refresh settings, rebuild content) can now be triggered for you without anyone logging into the site.<\/li>\n
- Improvement: Blog post featured images are now described to Google with their dimensions, improving how posts appear in search results and Google Discover.<\/li>\n<\/ul>\n\n
5.5.16<\/h4>\n\n
Release date: Apr 22nd, 2026<\/p>\n\n
\n- Speed tab: per-site toggle to turn the built-in HTML minifier on or off. Useful when Cloudflare's own minify is also active and the two conflict.<\/li>\n<\/ul>\n\n
5.5.15<\/h4>\n\n
Release date: Apr 22nd, 2026<\/p>\n\n
\n- Critical fix for the HTML minifier: very large pages could trigger a regex backtrack that produced a blank response (white screen). The minifier now falls back to the unminified page in that situation instead of returning nothing.<\/li>\n
- HTML minifier default changed to OFF on auto-update so existing sites are never silently regressed; admins can opt back in from the Speed tab.<\/li>\n<\/ul>\n\n
5.5.14<\/h4>\n\n
Release date: Apr 22nd, 2026<\/p>\n\n
\n- Cloudflare cache purges are now scoped strictly to the
www.<\/code> and apex domain \u2014 staging or unrelated subdomains on the same Cloudflare zone are no longer touched.<\/li>\n<\/ul>\n\n5.5.13<\/h4>\n\n
Release date: Apr 22nd, 2026<\/p>\n\n
\n- Internal bugfixes.<\/li>\n<\/ul>\n\n
5.5.12<\/h4>\n\n
Release date: Apr 22nd, 2026<\/p>\n\n
\n- Native HTML sitemap: the
[sitemap]<\/code> shortcode now ships with SiteSuperCharger and the plugin auto-creates a \/sitemap\/<\/code> page on activation. Removes the need for the separate \"WP Sitemap Page\" plugin.<\/li>\n<\/ul>\n\n5.5.11<\/h4>\n\n
Release date: Apr 22nd, 2026<\/p>\n\n
\n- Internal bugfixes.<\/li>\n<\/ul>\n\n
5.5.10<\/h4>\n\n
Release date: Apr 22nd, 2026<\/p>\n\n
\n- Internal bugfix.<\/li>\n<\/ul>\n\n
5.5.9<\/h4>\n\n
Release …<\/p>","raw_excerpt":"Supercharges your website for the best SEO results.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/zh-hk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/42869","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zh-hk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/zh-hk.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/zh-hk.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=42869"}],"author":[{"embeddable":true,"href":"https:\/\/zh-hk.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/agnitekcom"}],"wp:attachment":[{"href":"https:\/\/zh-hk.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=42869"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/zh-hk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=42869"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/zh-hk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=42869"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/zh-hk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=42869"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/zh-hk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=42869"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/zh-hk.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=42869"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}