Manage your WordPress site security with WP Manager?

Procédure

The WP Manager in the LWS Panel brings together the protection settings for your WordPress site in its SECURITY tab: a ready-to-use security level (Level 1, 2 or 3, or Custom), the login address hidden by LWS Hide Login, protection rules that can be enabled one by one, a few critical actions, and an integrity scan. This help explains where to find them and what each setting is for, without going into WordPress administration.

Accessing the security settings

  1. Open WP Manager

    Log in to your LWS account and access the hosting where your site is located. In the Software section, click WP Manager.

  2. Open the site details

    In the Manage installations list, click the MANAGE button for the relevant site.

    Manage your WordPress site security with WP Manager?
  3. Click the SECURITY tab

    At the top of the tab, the line Choose a security level and its default settings offers Level 1 (Basic Security), Level 2 (Recommended), Level 3 (Maximum) and Custom. The LWS Hide Login block is just below, followed by the detailed settings.

    Manage your WordPress site security with WP Manager?

Choosing a security level

Each level activates a set of settings all at once. The table below shows which settings are activated by each level (✔). The Custom level lets you enable or disable the settings of your choice yourself.

SettingLevel 1 (Basic Security)Level 2 (Recommended)Level 3 (Maximum)
Scheduled tasks (cron)✔✔✔
Search engine visibility———
Debug mode———
Force HTTPS✔✔✔
Restrict access to files and folders✔✔✔
Disable file listing in folders without an index file✔✔✔
Block unauthorized access to the xmlrpc.php file✔✔✔
Block downloads of .sql files✔✔✔
Block access to readme and license files✔✔✔
Block access to .htaccess and .htpasswd files—✔✔
Disable pingbacks——✔
Disable file editing in the WordPress dashboard—✔✔
Hide author usernames—✔✔
Disallow PHP script execution in the wp-content/uploads directory—✔✔
Disable script concatenation for the WordPress admin panel——✔
Block access to the comment page for browsers without UserAgent or Referer——✔
Block access to sensitive files——✔
Protection against SEO bots——✔
Protection against malicious bots—✔✔
Protection against AI bots—✔✔

Hide the login address with LWS Hide Login

LWS Hide Login hides WordPress's default login page (/wp-admin and /wp-login.php) to protect your site from brute-force attacks. In the Set your custom login URL field, enter the address of your choice, then click Save.

Understanding each setting

To enable or disable a setting, click its switch: gray means it is inactive; green means it is active.

Manage your WordPress site security with WP Manager?

General settings and performance

  • Scheduled tasks (cron): WordPress runs its scheduled tasks (scheduled publishing, update checks, etc.) using the wp-cron.php file, normally triggered by visits to your site. This setting makes them run through a server scheduled task instead of wp-cron.php, making them independent of visits.
  • Search engine visibility: makes your site visible or not visible to search engines. Disabling it also turns off the XML sitemap.
  • Debug mode (wp-debug): displays WordPress errors so they can be identified and fixed more easily. Disable it once the problem is resolved.
  • Force HTTPS: forces your site to use the HTTPS protocol, for an encrypted connection between the server and your visitors' browser.

.htaccess rules and other security measures

  • Restrict access to files and folders: prevents direct access to certain files and folders on your site from a browser.
  • Disable file listing in folders without an index file: prevents the contents of a folder without an index file from being displayed, making it harder for an attacker to find sensitive files.
  • Block unauthorized access to the xmlrpc.php file: disables xmlrpc.php, which allows WordPress to communicate with other sites or services and is often targeted by brute-force and DDoS attacks.
  • Block downloads of .sql files: protects .sql files, which contain database information.
  • Block access to readme and license files: prevents access to the readme.html and license.txt files, which can reveal the WordPress version in use.
  • Redirect to HTTPS: forces access to the site via HTTPS instead of HTTP.
  • Block access to .htaccess and .htpasswd files: protects these web server configuration files.
  • Disable pingbacks: pingbacks notify another site that you have linked to it, but they can be misused for DDoS attacks.
  • Disable file editing in the WordPress dashboard: prevents site files from being modified from the WordPress admin area, limiting unauthorized changes.
  • Hide author usernames: hides author usernames so an attacker cannot use them to guess login credentials.
  • Disallow PHP script execution in the wp-content/uploads directory: prevents PHP from being executed in the uploaded files folder (images, documents).
  • Disable script concatenation for the WordPress admin panel: can help prevent certain JavaScript-based attacks.
  • Block access to the comment page for browsers without UserAgent or Referer: helps limit comment spam.
  • Block access to sensitive files: protects sensitive files such as logs, configuration files and backups.
  • Protection against SEO bots: prevents indexing bots from crawling your site (Google, Ahrefs, Semrush…). See the note on Level 3 above.
  • Protection against malicious bots: blocks bots known to look for flaws and vulnerabilities on websites.
  • Protection against AI bots: blocks artificial intelligence bots (ChatGPT, Claude, Gemini…) that crawl your site, for example to retrieve its content.

Critical actions

The Critical Actions block groups together three one-time actions, each with its own button:

  • Change the SALT security keys in the WordPress configuration file (button CHANGE): replaces the secret keys stored in the wp-config.php file, which secure login sessions. All users are logged out and must log in again. Useful if you think access to your site has been compromised.
  • Reset permissions (button RESET): sets file permissions back to 644, folder permissions to 755, and the wp-config.php file to 600.
  • Change the default administrator username (button CHANGE): an administrator name different from the default is harder for an attacker to guess.

Check WordPress integrity

The Scan your WordPress installation block checks the integrity of the WordPress core: it compares the files in your installation with the original WordPress files. A difference may indicate a corrupted file, an unauthorized modification, or a file added by a hacker. Click LAUNCH SECURITY SCAN, then review the result; the View scan and detection history link displays previous scans.

If the scan reports modified files, you can reinstall the WordPress core files from the SOS tab (core reinstallation button, same version, without touching your personal files), or restore a backup.

Frequently asked questions

My site no longer appears on Google

In the SECURITY tab, check that Search engine visibility is enabled and that Protection against SEO bots is disabled.

I can no longer log in to the WordPress admin area

If you defined a custom login URL with LWS Hide Login, the old /wp-admin address returns a 404 error: use the new address shown in the LWS Hide Login block. You can also log in without a password using the CONNECT button in the WP Manager list.

Related articles

help.lws.net/a/1616
Was this article helpful?

Yes

No

Read 14 236 times

Thank you! Feel free to ask questions about our documentation if you would like more information, and help us improve it.

Similar articles

A question about this article?

Ask the LWS team and the community. Answers are published after moderation.

Ask the LWS team and its community a question

GDPR: Controller: LWS-Ligne Web Services. Purpose: moderation and public publication of your question, possible notification of an answer. Legal basis: consent (Art. 6(1)(a) GDPR). Email retention: 90 days after notification, 12 months maximum without an answer. To exercise your rights, see the GDPR section of our Terms and Conditions.