Admin Menu Editor vs Disable REST API — WordPress

Admin Menu Editor vs Disable REST API

Name: Admin Menu Editor
Rating: 4.6 (312 reviews)

Side-by-side comparison · 24 data points

Admin Menu Editor

4.6·312reviews·300,000+installs

wordpress

Change

1. Listing metadata

Field-level data

	Admin Menu Editor	Disable REST API
Tagline	—	—
Description	2624 / 5000 chars52% used	1013 / 5000 chars20% used
Screenshots	—	—
Languages
Platforms	WordPress	WordPress
Developer	Janis Elsts	Dave McHale
Listed	—	—
Last updated	—	—

2. Categories & rankings

Shared categories on the same row · in-category position inline

Admin Menu Editor

Disable REST API

Shared

At a glance

4 metrics · auto-computed

Feature comparison between Admin Menu Editor and Disable REST API
Metric	Admin Menu Editor	Disable REST API
Rating	4.6 ★	★ 4.8 ★
Total reviews	★ 312	38
Active installs	300,000+	80,000+
Free plan	—	—

Keyword	Admin Menu Editor	Disable REST API
online form	#352	Not ranked
online forms	#365	Not ranked
custom form	#754	Not ranked

5. App details

Long-form description · keyword frequency

Admin Menu Editor

Admin Menu Editor lets you manually edit the Dashboard menu. You can reorder the menus, show/hide specific items, change permissions, and more. Features Change menu titles, URLs, icons, CSS classes and so on. Organize menu items via drag & drop. Change menu permissions by setting the required capability or role. Move a menu item to a different submenu. Create custom menus that point to any part of the Dashboard or an external URL. Hide/show any menu or menu item. A hidden menu is invisible to all users, including administrators. The Pro version lets you set per-role menu permissions, hide a menu from everyone except a specific user, export your admin menu, drag items between menu levels, make menus open in a new window and more. Try online demo. Additional Features Despite the name, this plugin is not limited to just editing the admin menu. You can also: Create login redirects and logout redirects. Allow/deny access to specific posts based on user roles. Hide plugins on the Plugins -> Installed Plugins page from other users. Edit the display name, description, and other plugin details shown on the Plugins -> Installed Plugins page (e.g. for white-labelling). Shortcodes The plugin provides a few utility shortcodes. These are mainly intended to help with creating login/logout redirects, but you can also use them in posts and pages. [ame-wp-admin] – URL of the WordPress dashboard (with a trailing slash). [ame-home-url] – Site URL. Usually, this is the same as the URL in the “Site Address” field in Settings -> General. [ame-user-info field="..."] – Information about the logged-in user. Parameters: field – The part of user profile to display. Supported fields include: ID, user_login, display_name, locale, user_nicename, user_url, and so on. placeholder – Optional. Text that will be shown if the visitor is not logged in. encoding – Optional. How to encode or escape the output. This is useful if you want to use the shortcode in your own HTML or JS code. Supported values: auto (default), html, attr, js, none. Notes If you delete any of the default menus they will reappear after saving. This is by design. To get rid of a menu for good, either hide it or change it’s access permissions. In the free version, it’s not possible to give a role access to a menu item that it couldn’t see before. You can only restrict menu access further. In case of emergency, you can reset the menu configuration back to the default by going to http://example.com/wp-admin/?reset_admin_menu=1 (replace example.com with your site URL). You must be logged in as an Administrator to do this.

Top keywords

menu19×4.28%
user7×1.58%
url6×1.35%
hide5×1.13%
access4×0.90%
admin4×0.90%
admin menu4×0.90%
change4×0.90%
menus4×0.90%
permissions4×0.90%
dashboard3×0.68%
default3×0.68%

Disable REST API

The most comprehensive plugin for controlling access to the WordPress REST API! Works as a “set it and forget it” install. Just upload and activate, and the entire REST API will be inaccessible to your general site visitors. But if you do need to grant access to some endpoints, you can do that too. Go to the Settings page and you can quickly whitelist individual endpoints (or entire branches of endpoints) in the REST API. You can even do this on a per-user-role basis, so your unauthenticated users have one set of rules while WooCommerce customers have another while Subscribers and Editors and Admins all have their own. NOTE: Out of the box, all defined user roles will still be granted full access to the REST API until you choose to manage those settings. For most versions of WordPress, this plugin will return an authentication error if a user is not allowed to access an endpoint. For legacy support, WordPress 4.4, 4.5, and 4.6 use the provided rest_enabled filter to disable the entire REST API.

Top keywords

rest6×3.35%
api5×2.79%
rest api5×2.79%
access4×2.23%
endpoints3×1.68%
entire3×1.68%
wordpress3×1.68%
entire rest2×1.12%
entire rest api2×1.12%

Frequently asked

Common questions about this comparison

Which has better reviews, Admin Menu Editor or Disable REST API?

Disable REST API has the higher average rating (4.8★ from 38 reviews) compared to Admin Menu Editor (4.6★ from 312 reviews). Both are tracked daily by AppRanks, so the figures here update each refresh cycle.

Should I choose Admin Menu Editor or Disable REST API?

Disable REST API holds the higher average rating (4.8★ vs 4.6★). That is the one dimension AppRanks can separate them on here — read both apps' detail pages for the feature breakdown and recent listing changes.

Which is faster to set up, Admin Menu Editor or Disable REST API?

Both apps are one-click installs from the WordPress Plugin Directory. Admin Menu Editor has the deeper published review base (312 vs 38), which often — though not always — accompanies better-tested setup docs. AppRanks doesn't measure setup time directly: read the recent reviews on each app's detail page for user-reported install experience.

Which works better for small vs large WordPress Plugin Directory site owners?

Admin Menu Editor typically suits early-stage and growth-mode teams based on its published review base (312 reviews). Disable REST API typically suits early-stage and growth-mode teams based on its published review base (38 reviews). A larger review base generally means the app has been exercised at scale — relevant if you are processing high volume or handling enterprise compliance requirements.

Can I migrate data between Admin Menu Editor and Disable REST API?

Migration support varies by app and category. Admin Menu Editor and Disable REST API both publish their export options on their marketplace listing pages (or in their support docs); some apps offer one-click import from competitors, others require CSV. The fastest check: search "import from Disable REST API" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.

Admin Menu Editor vs Disable REST API

Admin Menu Editor

1. Listing metadata

2. Categories & rankings

Disable REST API

At a glance

AppRanks verdict

3. Search rankings

4. Activity in the last 90 days

Admin Menu Editor · 1 changes

Disable REST API · 0 changes

5. App details

Frequently asked

Which has better reviews, Admin Menu Editor or Disable REST API?

Should I choose Admin Menu Editor or Disable REST API?

Which is faster to set up, Admin Menu Editor or Disable REST API?

Which works better for small vs large WordPress Plugin Directory site owners?

Can I migrate data between Admin Menu Editor and Disable REST API?

See full keyword rankings, install trends, and weekly alerts

More popular comparisons