The settings screen is drawn by a script that builds every section, including the WP Visibility heading, after the page loads. If the page stays empty beside the admin menu, the script did not run or stopped with an error. Reload once. If it happens again, something in the browser or on the site is stopping it, and the list below helps you find it.
Two messages mean something else. “WP Visibility settings require JavaScript” means JavaScript is turned off in this browser; turn it on for your site. “WP Visibility build artifacts are missing” means the plugin’s compiled files are not on the server; download the plugin zip from your account and upload it again.
Reload, then try a clean browser
A slow or interrupted connection can leave the page half loaded, and a reload fetches the script again. If the controls are still missing, open the same page in another browser, or in a private window with extensions turned off. A content blocker or privacy extension can block scripts on admin pages. If the controls appear there, allow your site’s admin in the extension.
Look at the browser console
Open the browser’s developer tools, select the Console tab, then reload the settings page. In Chrome, Control+Shift+J on Windows or Command+Option+J on a Mac opens the Console directly (checked September 27, 2026). A red error line shows the file it came from. If it comes from another plugin’s file, that plugin may be interfering with the page; deactivate it briefly to confirm. If the error mentions a blocked request, continue below.
Optimization and security plugins
Plugins that combine, defer or minify scripts sometimes do so on admin pages too, and the settings screen’s script must load in order, after the WordPress scripts it depends on. Exclude wp-admin from optimization, or exclude the handle wpvis-settings (the file assets/build/settings.js in the plugin folder).
Saving settings goes through the WordPress REST API at /wp-json/wpvis/v1/, or ?rest_route=/wpvis/v1/ on sites with plain permalinks (REST API handbook, checked September 27, 2026). A firewall or security plugin that blocks REST requests lets the screen draw but stops every save with an error. Allow those requests for logged-in administrators.
Permissions
The menu and the screen are for administrators: both require the manage_options capability, which WordPress gives to administrators (checked September 27, 2026). A user without it does not see the menu, and opening the page by URL shows WordPress’s own “Sorry, you are not allowed to access this page.” message instead of an empty screen (checked September 27, 2026). An empty screen is not a permissions problem.
If none of that is it
Write to support@wpvisibility.com with your WordPress and plugin versions, the browser, and the first error line from the console. Those four facts give support a place to start.