SiteSuperCharger

By AnAdminer

★ 5.0/5 (1 ratings)300+ active installationsVersion 5.8.101

Supercharges your website for the best SEO results.

Description

SiteSuperCharger helps your website look as attractive as possible to search engines helping you to acheive the highest search engine rankings.

Contact Marketing Heroes (https://www.mheroes.com) to get started!

Installation

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

For info about acquiring a GUID for SiteSuperCharger visit https://www.mheroes.com.

FAQ

Is SiteSuperCharger free?

You must purchase Search Engine Optimization services from Marketing Heroes (https://www.mheroes.com) to use SiteSuperCharger

Changelog

5.8.101

  • If your site’s Sitemap page goes missing, the plugin puts it back by itself (checked at most once a day). It never touches a page you already have at that address, in any state, and never adds a second copy.

5.8.99

  • When your marketing team merges near-identical pages into one main page, the old addresses keep forwarding visitors to the main page, also after the old pages are taken off the site. Before, taking an old page off could remove its forwarding too, so its address showed “page not found”.
  • Security: the limit on wrong login attempts and the spam protection on the booking form can no longer be dodged by a sender who lies about where it is connecting from, and visitors behind the same network edge no longer share one allowance.
  • Security: the plugin’s activity log now records the visitor’s real address, not one the sender claims, and it never stores the site’s connection key.
  • Security: the check that removes harmful plugins no longer gives a pass to anything merely named like our plugin, only to the one copy of it that is actually running, and it never switches our own plugin off.
  • Security: 32 plugins planted on websites during the break-in of 1-3 November are switched off and moved where they cannot run.
  • Security: the 38 throwaway administrator accounts used in that break-in are removed. Only those exact accounts are touched; anything that merely looks similar is reported to your team instead.
  • AI assistants that book an inspection or ask for a callback now go through the site’s assistant connection, which already worked; a request sent the old way is told where to go instead of being dropped.
  • Ready for PHP 8.4 and 8.5: no more deprecation warnings from the plugin.
  • New, off by default: agency staff can open this site’s dashboard from their own tools with a one-time sign-in, instead of a shared password. Nothing changes on a site until your marketing team turns it on, and the site owner can keep it off in wp-config.
  • Includes everything in 5.8.97. (5.8.98 was folded into this release and never published on its own.)

5.8.97

  • Activity records from the website now keep reaching your marketing team even when a security filter on the way objects to one of them, for example a failed login typed by an attacker. The one record is set aside on the website and everything behind it carries on.
  • The security check that removes harmful plugins now also catches one more harmful plugin and its hidden helper file, and sets aside any other plugin or helper file that carries the same warning signs (it is switched off and moved where it cannot run, not deleted).
  • Every plugin on your website now updates itself in the background when its maker releases an update, so sites no longer sit on old, vulnerable versions. Avada’s builder plugins are left for the team to update with the theme, and plugins that need a paid licence update only when that licence is connected.
  • Your home page and main area and service pages are kept in the fast cache: they are reloaded straight after a big content update and again every day, so visitors get them quickly. Pages are no longer missed when several updates arrive at once.
  • Contact forms made with Forminator no longer refuse an enquiry with “Invalid nonce” when the page came from the fast cache: the form fetches a fresh security code as soon as the visitor starts filling it in.
  • When another team legitimately edits a page SiteSuperCharger built, the page is no longer put back over and over. A page can be handed to that team, and a page edited again and again is left alone and flagged to your marketing team.
  • Added: a privacy banner. Analytics and advertising tools set up through the plugin (Google Analytics, Google Ads, Tag Manager, Meta Pixel) now load only after a visitor agrees, with “Accept all”, “Reject all” and “Manage choices” given equal weight. A browser’s Global Privacy Control opt-out signal is honored, and a “Your Privacy Choices” link appears at the bottom of every page. Sites without such tools show no banner.
  • Tracking (Google Analytics, Google Ads, Tag Manager and Meta) now loads only after a visitor accepts cookies, so reported visits and conversions will count visitors who agreed. Sites that already use their own cookie tool can have SSC’s banner switched off: ask support.
  • Added: the [ssc_privacy_policy_section] shortcode writes the cookies and analytics part of your privacy policy from what the site actually loads, and keeps it current.
  • Enquiries passed on to your marketing team are no longer held up if the website is interrupted while sending one, and junk submissions that leave no phone number or email address are no longer passed on. This is still switched off until your marketing team turns it on.
  • Includes everything in 5.8.96.

5.8.96

  • Enquiries sent through WPForms or Formidable Forms now count as leads in Google Analytics, the same as Gravity Forms and Contact Form 7. A saved draft of a Formidable form is no longer counted.
  • New, and switched off until your marketing team turns it on: enquiries from the website’s forms can be passed on to your marketing team, together with the ad or link that brought the visitor, so that every enquiry is counted. The email you receive for each enquiry is unchanged, and visitors whose browser asks not to be tracked are not tracked.
  • Clearing updated pages from the cache now happens one pass at a time, so a busy website no longer sends the same request many times at once or loses pages that were waiting to be cleared.
  • Known harmful plugins, and plugins that let anyone with a login run code or rewrite the whole database, are now switched off and set aside automatically, with their settings saved first. Your support team can keep one on for a site that really needs it.
  • Includes everything in 5.8.95.

5.8.95

  • Cache clearing works again on websites set to clear the cache directly, so updated pages are no longer served from an old copy.
  • The update-health check no longer reports healthy websites as unable to receive updates.
  • A maintenance period is no longer marked as over while some pages are still waiting for their content.
  • The website’s SEO plugin now describes the business with the same name, phone and address as the rest of the site, on pages SiteSuperCharger does not build. Everything else the SEO plugin publishes is left as it is.
  • Faster script loading no longer breaks small scripts that other plugins add to the page (for example contact-form spam protection).
  • Notices about the website now go to the team that manages it.
  • Includes everything in 5.8.94 and 5.8.93.

5.8.94

  • The daily broken-link email now says which page each broken link is on, with the page’s address, a working link to edit that page, and the link’s text.
  • Includes everything in 5.8.93.

5.8.93

  • Old links to /resources/ pages now take visitors to the page that replaced them, instead of a missing page.
  • Section pages are found and moved back to their own address after a reorganisation, instead of empty stand-in pages being created in their place.
  • When the cache service asks the site to wait, the site now waits as long as asked before clearing the cache again.

5.8.92

  • Pages that change are now cleared from the site’s cache reliably, even during a large update, and the fresh page is loaded into the cache straight after – so visitors see the new page sooner. The “Clear Cache – All Pages” button works again.

5.8.91

  • An automatic forward that was switched off because a real page lives at its address now stays off when the page it pointed to moves.

5.8.90

  • Large batches of addresses are now all cleared from the site’s cache, not only the first hundred, and any the cache service turns away for now are retried later instead of forgotten.

5.8.89

  • Automatic forwards that still stood in front of a published page are now found and switched off on their own, and cleared from the site’s cache, without waiting for someone to visit the page.
  • A page that moves back to its earlier address is no longer left behind its old forward.

5.8.88

  • Search engines are never kept out by robots.txt rules this plugin writes: anything that would block Google, Bing or another search engine is left out.
  • A page that is published at an address is always served there, even if an older automatic forward still points that address elsewhere; the forward is switched off.

5.8.86

  • Pages parked aside by an earlier repair are brought back to the address the plan asks for, with forwards from where they were.

5.8.85

  • Websites with no SiteSuperCharger pages no longer hold their tidy-up open waiting for a page list that was never coming.

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.

For older versions, see changelog.txt in the plugin folder.