by
qaiyo
1 (0 reviews)
Qaiyo Admin Booster
Fixes the annoying wp-admin UX/UI rough edges that cost you time every day — without replacing the WordPress admin you already know.
Qaiyo Admin Booster ranks #33,993 among WordPress.org plugins with 10+ active installations, a 1/5 rating from 0 reviews, and was last updated Oct 28, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v1.5.3
Current Version v1.5.3
Updated 1 week ago
Last Update on 28 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
Top 50% by installs
Actively maintained
Rank
#33,993
—
No change
Active Installs
10+
—
No change
KW Avg Position
185
1 worse
Downloads
1.4K
+9 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 20
10+
20+
10,820
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 3 more installs to reach 20+
Rank Changes
Current
#33,993
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.5.3
- Last Updated
- Oct 28, 2026
- Requires WP
- 5.9+
- Tested Up To
- 7.1
- PHP Version
- 7.4 or higher
- Author
- qaiyo
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Qaiyo Admin Booster
No. It only fixes specific UX/UI rough edges. The standard WordPress admin stays exactly as it is.
SVG files can contain scripts, so only enable SVG uploads if you trust everyone who can upload media. The Pro version adds automatic SVG sanitization that strips scripts on upload.
On most hosts, yes. The limit lives in PHP's upload_max_filesize and post_max_size, which cannot be changed while WordPress runs — not with ini_set() and not from wp-config.php, because PHP has already received the upload by then. Turn on "Raise the server limit too" and Admin Booster writes the two values into the files your server reads before each request: .user.ini in the WordPress folder on PHP-FPM / FastCGI hosts (applies within about 5 minutes), .htaccess on Apache mod_php, and both on LiteSpeed / CloudLinux LSAPI hosts, where it depends on the host which one is honoured. The lines are clearly marked, nothing else in the file is touched, and switching the option off or deleting the plugin removes them. The settings page reads the limit PHP really applies and tells you whether it worked. If a host has locked the limit (php_admin_value), Admin Booster detects it and says so instead of writing anything. If the host simply does not read these files, the page shows a short "Server details" list you can send to your host.
No. It restores only the plugin or theme files that the update just replaced, using the copy WordPress itself makes during the update. It cannot undo database changes an update makes, and it cannot help if the problem only appears later (for example on a specific page or after a cron job runs). It also needs the server to be able to load its own pages ("loopback requests" — Site Health tests this); if it cannot, the settings page warns you. Keep regular backups.
If you turned on the Safe Mode link beforehand, open the link you saved, log in, deactivate the plugin you just updated under Plugins (or switch themes under Appearance), then click "Exit Safe Mode". If you did not, WordPress may have emailed the site's admin address a recovery link; otherwise you need FTP, SSH or your hosting file manager to rename that plugin's folder.
It is built so that a leaked link is not enough to take over the site: The key never reaches the server's logs. It sits after the # in the link, which browsers never send to the server, so it cannot end up in web server, CDN or proxy logs, or in a Referer header. A stolen database does not reveal it. Only a fingerprint is stored, keyed with the security keys in wp-config.php, so a database leak neither reveals the link nor lets anyone plant their own. The link alone does not log anyone in. Only administrators can sign in, always with their password (an existing login cookie is not accepted), and after 5 failed passwords logins lock for 15 minutes — security and two-factor plugins are off in Safe Mode, so this limit is built in. It cannot be used to plant a backdoor. Safe Mode is a recovery console: Dashboard, Plugins and Themes only. Installing or uploading plugins and themes, editing files, and creating or changing users are blocked. It cannot be used quietly. Every entry and every Safe Mode login is emailed to all administrators, logged with IP address and browser, and shown to administrators as a notice until dismissed. A used link does not stay valid. It is retired automatically as soon as the admin loads normally again — but not before, so you cannot lock yourself out if the first fix did not work. The Safe Mode session lasts one hour and is tied to the browser; on HTTPS sites the key is only accepted over HTTPS; you can optionally restrict it to fixed IP addresses; and "Create a new link" instantly invalidates the old link and every open session. The public site is never affected.
The plugin's folder is still in wp-content/plugins, but WordPress cannot find a plugin in it — most often because an earlier update or deletion stopped halfway and left some files behind. WordPress only lists folders that contain a plugin's main file, so the leftover is invisible, and it blocks a fresh install of the same plugin. With the Broken plugin folders module switched on, the folder appears at the top of the Plugins screen with a Delete button; delete it and upload the plugin again. The plugin's settings are stored in the database, so they are kept.
Yes. On the settings page, open the Export / import tab, download the settings file, then upload it on the other site. You see a preview of what will change before anything is saved, and you can undo the import with one click. Content types that do not exist on the other site are skipped, and site-specific features (Safe Mode, the server upload-limit files) are never copied.
The noindex detection recognizes Yoast SEO, Rank Math and SEOPress.
Please report security vulnerabilities privately by email to info@qaiyo-plugins.com rather than in the public support forum. See the SECURITY.md file included with the plugin for details. We aim to acknowledge reports within 72 hours.