SiteSuperCharger

Changelog

5.8.83

• Section addresses left with an internal number from an older repair also move home, with forwards.

5.8.82

• Visitors see the corrected address straight away: old addresses are cleared from the site’s cache when a page moves home.

5.8.81

• Very large sections finish moving home even when a request is cut short, and every page keeps its forward.

5.8.80

• Pages whose section address picked up a stray number are moved back under the right section, and every old address forwards to the new one. New numbered sections are no longer created.

5.8.79

• An old numbered address now always forwards to its own page, even when another redirect tool on the site has an older rule for it.

5.8.78

• The same applies to a forward paused while the old address was still a live page.

5.8.77

• An old address whose forward was paused while its new page was missing now forwards again once the page is back.

5.8.76

• Every automatic page move is recorded, and it can be switched off remotely.

5.8.75

• Pages that an earlier update left at a numbered address (“-2”) now move back to their proper address by themselves, with the old address forwarding to it.

5.8.74

• Your pages now always keep their proper web addresses. If something else on your website is already using an address, we no longer publish a numbered copy of the page (like “roofers-2”) — we hold the page back and tell our team instead.
• Redirect logging for page moves is switched off, so your website no longer builds up tens of thousands of unnecessary forwarding rules.
• Fixed: a large clean-up of old pages now always finishes on its own, even while your pages are being rebuilt.

5.8.73

• Pages that are no longer part of your plan, such as an area you no longer serve, are now removed from your website for good before each update, so updated pages keep their proper web addresses instead of getting numbered copies. Your own pages are never touched, and a very large clean-up happens gradually in the background.
• Fixed: an old address in one town is no longer forwarded to a page in a different town.

5.8.72

• Fixed: your business name is no longer turned into a link inside your own page text. Links to your service pages still appear everywhere else.

5.8.71

• Groundwork for removing pages that are no longer part of your plan.
• Fixed: your sitemap address no longer loops when your SEO plugin’s own sitemap is switched off.

5.8.70

• AI search and answer engines can now read your site by default. Sites that never chose a crawler setting were quietly turning several AI crawlers away; that default is now “allow all”, and robots.txt is rewritten on update.

5.8.69

• Fixed: some of your own location pages were left out of your XML sitemap because their web address ends in a number. They are listed again. Pages that really are duplicates are still kept out.

5.8.68

• Image optimization is more careful with your site’s resources. If preparing your existing images ever stalls, the plugin now slows its retries and lets your account team know, instead of trying every minute.
• Two background tasks can no longer start the same image optimization run at the same time.
• On sites no longer managed by SiteSuperCharger, the “install ShortPixel” notice no longer appears and its button no longer installs anything.
• The plugin now reads the version of ShortPixel Image Optimizer itself, and is not confused when ShortPixel Adaptive Images is also installed.

5.8.67

• Fixed: your account team could not see that your image settings matched our standard, even when they did, because the check compared how each setting was written rather than what it meant. It now compares the settings themselves, and anything changed by hand still shows up. This also clears the “settings differ from the standard” warning that site administrators saw in WordPress when nothing was actually wrong.

5.8.66

• Image optimization now runs all the way: ShortPixel works through the images already on your site in the background, and writes alt text, captions and descriptions for them using a short description of your business. New uploads get the same treatment automatically.
• If ShortPixel Image Optimizer is missing or switched off, site administrators now see a notice with a one-click button that installs it from WordPress.org and sets it up. Nothing is installed without that click or a request from your account team.
• Sites now report how many images have been optimized and how many have AI-written text, so your account team can follow the progress.

5.8.65

• Fixed: on sites running the current ShortPixel release, the image settings we manage for you were being written to a place ShortPixel no longer reads, so its own defaults applied instead of ours. They now land where ShortPixel actually looks, and the check that confirms they match now reads the same place.
• The site description ShortPixel uses when it writes image alt text is filled in from your account again instead of showing ShortPixel’s sample text.

5.8.63

• Fixed: your site was inviting people to book an appointment through a page that had been withdrawn, so those enquiries reached nobody. Booking is now advertised only where there is a real place for it to go, and your site tells us where that is. Until one is set up nothing is advertised, which is better than an invitation you never see.
• When a booking does come in, it now goes to the address you nominate rather than the website’s own mailbox.

5.8.62

• Fixed: on sites where a service page is also the parent of other pages, that address could end up showing a blank template instead of the page. The page itself was never lost — it was answering at a second address all along. This release stops new ones being made that way on most sites. On the rest, the page is now flagged for your account team to put right, instead of being left to find.
• Star ratings the business had published about itself are no longer sent to search engines. Google does not count a business rating itself, and the reviews visitors read on the page are unchanged.
• Removed voice-assistant markup that pointed at page sections most themes do not have, so it never did anything.
• The business name now comes from one place, so a site no longer describes itself under two slightly different names.
• Sites now report a few extra facts about their own health — whether updates are switched on, whether any published page has quietly stopped being visible, and whether the content queue has stopped moving — so a site that stops taking updates can be spotted rather than sitting quietly out of date.

5.8.61

• Fixed: on a site with thousands of pages to put back, the recovery added in the last release could run during ordinary page views and slow the site to a stop. It now runs quietly in the background, a little at a time, and never while somebody is waiting for a page.
• The recovery also picks up where it left off instead of starting over, so it finishes even on very large sites.

5.8.60

• Fixed: the recovery in the last release now runs on sites whose page plan has not changed recently. Previously a site could take the update and still not get its pages back, because the recovery only ran when something else prompted the site to re-read its plan. It now runs on its own, once, as soon as the update installs.
• Sites that were never affected are unchanged, and the check costs them nothing.

5.8.59

• Fixed: pages that were unpublished by the recent town-to-town fault are put back automatically. They return published, at their own address, under their own town name, the next time your site syncs. Nothing needs to be done by hand.
• Pages you unpublished yourself are left exactly as they are. Only pages this plugin took down are restored, and only where your site plan still lists them.

5.8.58

• Fixed: the fault that moved pages between towns is now switched off on every site, rather than only being stoppable site by site. Two releases ago a page could be renamed from one town to another across a site, and any page standing in the way was unpublished to make room. Sites that had not yet been affected are protected by this update whether or not anything else is done for them.
• Your pages keep working the way they did before all of this: page addresses are built from the site structure, which is how they were built for years.

5.8.57

• Fixed: pages on your site are no longer moved to another town’s address, and pages are no longer filed as drafts to make room for that move. A fault introduced two releases ago could rename one page from town to town across a site and unpublish every page standing in its way, so a page about your city could answer under the name of a different one. That behaviour is off, and your pages come back published under their own names.
• Added: your account team can now turn the address-tidying feature off for a site without needing access to the site itself, so a problem like the one above can be stopped everywhere in minutes instead of site by site.
• Fixed: the existing off switch for address tidying now stops every part of it. It used to stop pages being unpublished but still allowed them to be moved, which meant turning it off did not stop what people could actually see.

5.8.56

• Fixed: when a duplicate article is tidied away, its old address now forwards to the copy that stays. In the previous release the extra copy was moved to the trash but its address simply stopped working, so anyone arriving from a search result or an old link landed on a dead page. Any address this affected is repaired on its own the first time the clean-up runs after this update; there is nothing to do on your side.
• Fixed: an article you have unpublished is no longer treated as the copy to keep. Before this, if you had unpublished the original and left the second copy running, the live one could be the one moved to the trash. When two copies are not equally visible the pair is now left alone and reported instead.
• Fixed: an article you take back out of the trash now stays out, and works. The next clean-up used to move it straight back in, and the forwarding rule left on its address would have sent visitors away from it. Both are cleared the moment we see it back.
• Fixed: a second copy you made yourself, with a duplicate-post or translation tool, is left alone.
• Added: your account team can now turn the duplicate-article clean-up off for a site without needing access to the site itself.

5.8.54

• Added: in-depth answers on your service pages. When your account team marks a question as a primary answer, it appears at the top of that page in its own section, with the short answer first and the full explanation underneath, ahead of the usual question list. Nothing changes on any page until an answer is marked.
• Added: the service can now remove a forwarding rule that sends one of your live pages to an address that no longer exists, or round in a circle. A permanent redirect into nothing is the worst thing a page can do for search, and on one site about a hundred and thirty pages were doing exactly that. Before a rule is removed the page it protects must be live, the address it points at must be confirmed dead by your own site, and a full copy of the rule is kept so it can be put back. Rules that send a page somewhere that still exists are reported, never removed.
• Fixed: the nightly summaries and switch confirmations the plugin sends home now arrive with their detail. They had been arriving empty, so the service could not see what each site had found or which clean-up features it had on.
• Fixed: an article could be published twice when two parts of the service happened to create it at the same moment, leaving a second copy at an address ending in “-2”. The two copies then competed with each other in search. Creating an article is now claimed in one step, so a second copy cannot be made.
• Added: any article that is already live twice is resolved automatically. The original copy stays and the extra copy goes to the trash. This runs after every site update and once a day, and reports what it did. (Two things this release promised did not work as described: the extra copy’s address did not forward to the original, and an article taken back out of the trash was moved back in by the next clean-up. Both are put right in 5.8.56, including the addresses already affected.)
• Note: this clean-up stays off until it is turned on for a site, and it starts at five rules a day. The duplicate-article fix is on for every site.

5.8.53

• Fixed: the biggest single cause of pages that could not be found on service-area sites. When a region or city section of a site was renamed, the section was thrown away and rebuilt, so every address underneath it stopped working at once and nothing pointed at the replacement. A section now keeps its identity and simply moves, taking its pages with it, and every old address forwards to its new one.
• Added: a daily check that walks the addresses on the site and reports any that no longer lead to the right page, so a problem like the one above is found by us rather than by a visitor.
• Improved: when the service removes an old forwarding rule that was sending a good page to the wrong place, it now keeps a full copy first and can put it back exactly as it was. It also re-checks the address afterwards and says so if the page still is not loading properly.
• Improved: that clean-up starts at five rules a day on a site and only speeds up after clean days, with an overall limit, so nothing ever happens fast enough to go unnoticed.
• Fixed: a fact-check response or a trust badge that you remove in the app now comes off your site. Removing the last one used to leave the old details published on every page indefinitely.
• Fixed: automatic keyword links no longer appear inside the hidden data your pages send to search engines. On sites using this feature that data was coming out malformed, which can cost you rich results in search. Links also stopped picking up a doubled slash at the end.
• Note: everything new here stays switched off until it is turned on for a site. The section-renaming fix is the exception – it simply stops the pages breaking.

5.8.52

• Fixed: the “last updated” date that your sitemap reports to search engines for each page. The plugin was meant to carry the real change date across from your site plan, but WordPress silently replaced it with the time of the sync run, so every page looked as if it had been edited at the same minute on the same day. The real date now lands and stays.
• Fixed: the same date refresh after a FAQ update on a page. It reported the sync time instead of the FAQ change date; it now reports the change date.

5.8.51

• New: scheduled page launches. When your site plan gives a page a future go-live date, the page is created ahead of time as a scheduled page – invisible to visitors and search engines until its date, then published automatically at that moment by WordPress itself. Links to not-yet-live pages are held back everywhere until the page is actually live, so visitors never land on a page that isn’t ready.
• Improved: pages waiting for their go-live date are protected from cleanup and matched correctly on every sync, so nothing ever publishes early or gets duplicated.

5.8.50

• SEO meta: the guard that stops unexpanded template tokens reaching page descriptions now recognises a token anywhere in the value, not only a whole-field JSON descriptor. Prevents raw placeholders appearing in search results and social previews.

5.8.49

• Junk-slug sitemap guard: the guard that keeps minted junk URLs out of the sitemap now also recognises WordPress __trashed slugs, so a trashed page can no longer be advertised to search engines.

5.8.48

• 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.

5.8.45

• 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.
• 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.
• 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.

5.8.44

• 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.
• 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.
• 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.

5.8.43

• 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.
• 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.
• 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.
• 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.
• 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.
• 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.

5.8.42

• 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.
• Changed: undoing those rules is off by default and lists what it would do first.

5.8.41

• 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.

5.8.40

• 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.
• 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.
• 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.
• 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.
• Changed: pages the service built that are not part of your site’s plan — extra copies of a page that already exists at its correct address, and leftovers from features that no longer exist — 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.
• 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.
• 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.
• Changed: any menu links pointing at a page being removed are pointed at its replacement first, so a menu never loses an entry.
• Changed: the “Clean up duplicates” button no longer deletes anything permanently. It sets duplicates back to draft and forwards their addresses instead.
• 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.
• 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.
• 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.
• 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.
• New: a site-level switch to pause all of the above on an individual website if it is ever needed.

5.8.38

• 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.

5.8.37

• Performance: pages now load noticeably faster for visitors. Every single page view — including the home page, the about page and blog posts — 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.
• 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.
• 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.

5.8.36

• 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.
• 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.
• 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.

5.8.35

• 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.
• 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.
• 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.
• 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 …