Settings
Spam protection and sign-in
Where: ExpertPress → Settings → Spam protection and sign-in (Захист від спаму і вхід)
What this tab is for
Protection of public forms and accounts: keeping clients and specialists out of the WordPress admin area, opening or closing specialist registration, built-in anti-spam checks, submission limits, sign-in locks and password length, an optional external captcha, and sign-in with Google.
The tab has two forms. Save spam protection saves everything except Google; Save Google sign-in saves the Google block. A link at the top opens History of spam protection changes (History of settings changes).
The protected public forms are: sign-up forms, contact and complaint forms, the review form and the form for reporting a service.
If the settings stored for this tab cannot be read, the tab shows a recovery notice and public forms are refused until the settings are saved again. If an external captcha is selected but its keys are missing or invalid, the tab shows “External protection is selected but not configured…” — until you fix the keys or choose no external service, visitors cannot submit forms.
Access to the WordPress admin area
Keep clients and specialists out of the WordPress admin area
- Where: ExpertPress → Settings → Spam protection and sign-in → Access to the WordPress admin area
- What it does: When on, clients and specialists (accounts with only the Subscriber or Customer role) who open
/wp-admin/are sent to their personal account, and the black WordPress admin bar is hidden for them. Editors, shop managers and other WordPress roles keep access. Buttons and forms on the site keep working. - Default: on.
- Values / limits: on / off. Works only with pretty permalinks (WordPress → Settings → Permalinks). Can be locked by a plugin or theme.
- When to change it: keep it on for a clean experience; turn it off only if another plugin requires subscribers to use wp-admin.
- Related: —
Specialist registration
Specialist registration is open
- Where: ExpertPress → Settings → Spam protection and sign-in → Specialist registration
- What it does: When off, the specialist registration page shows a “closed” message and new specialist sign-ups are refused. Existing specialists are not affected. The block links to Lists and registration questions, where the sign-up questions are edited.
- Default: on (open).
- Values / limits: on / off. Can be locked by a plugin or theme.
- When to change it: you have enough specialists for now; you only onboard invited specialists; you are under a spam wave.
- Related: Specialists can submit new services
Built-in protection
Hidden trap field
- Where: ExpertPress → Settings → Spam protection and sign-in → Built-in protection
- What it does: Adds a hidden field to protected forms that people never see but bots often fill in. A filled trap field rejects the submission.
- Default: on.
- Values / limits: on / off.
- When to change it: keep on; turn off only while diagnosing an accessibility tool or form plugin that fills hidden fields.
- Related: —
Minimum fill time (seconds)
- Where: ExpertPress → Settings → Spam protection and sign-in → Built-in protection
- What it does: Refuses a form sent faster than this after the page was opened (bots submit instantly).
- Default: 3 seconds.
- Values / limits: 0–120; 0 turns this check off.
- When to change it: raise to 5–8 under a bot wave; lower if real users with password managers are refused.
- Related: —
Submission limit per IP address
People on one network (office, mobile operator) may share these limits. Increase them if ordinary visitors are blocked for too many attempts. These limits count form submissions; the limits in the next section count account creation attempts after the form checks. Both apply.
Sign-up form submissions per window
- Where: ExpertPress → Settings → Spam protection and sign-in → Submission limit per IP address
- What it does: Maximum sign-up form submissions from one IP address within the counting period.
- Default: 10.
- Values / limits: 1–500.
- When to change it: lower during a sign-up spam wave; raise for events where many people register from one Wi-Fi.
Contact / complaint form submissions per window
- Where: same section
- What it does: Maximum contact and complaint form submissions from one IP address within the counting period.
- Default: 20.
- Values / limits: 1–500.
Review form submissions per window
- Where: same section
- What it does: Maximum review form submissions from one IP address within the counting period.
- Default: 20.
- Values / limits: 1–500.
Submission counting period, minutes
- Where: same section
- What it does: The window for the three limits above.
- Default: 60 minutes.
- Values / limits: 1–1440 minutes (fractions allowed, stored in seconds).
Complaints about services per user
- Where: same section
- What it does: How many complaints about services one signed-in user may send within the complaint counting period.
- Default: 5.
- Values / limits: 1–100.
- When to change it: lower it if a user floods moderators with reports.
Complaint counting period, minutes
- Where: same section
- What it does: Window for the complaint limit above.
- Default: 1440 minutes (24 hours).
- Values / limits: 1–10080 minutes (up to 7 days).
Failed sign-ins, passwords and sign-up limits
Failed sign-in attempts before the lock
- Where: ExpertPress → Settings → Spam protection and sign-in → Failed sign-ins, passwords and sign-up limits
- What it does: After this many failed sign-in attempts, further sign-in attempts are locked for the lock duration.
- Default: 5.
- Values / limits: 1–50.
- When to change it: lower under password-guessing attacks; raise if real users get locked out often.
Sign-in lock duration, minutes
- Where: same section
- What it does: How long the sign-in lock lasts.
- Default: 15 minutes.
- Values / limits: 1–1440 minutes.
Email confirmation link lifetime, hours
- Where: same section
- What it does: How long the link in the “Confirm email” letter works after sign-up.
- Default: 24 hours.
- Values / limits: 1–168 hours.
- When to change it: raise it if users often confirm late (letters land in spam folders).
- Related: Email templates
Minimum password length
- Where: same section
- What it does: Minimum number of characters for new passwords on ExpertPress forms.
- Default: 8.
- Values / limits: 6–32.
Sign-up attempts per IP address
- Where: same section
- What it does: Maximum account creation attempts from one IP address within the period below (counted after the form checks pass).
- Default: 5.
- Values / limits: 1–100.
Period for attempts from one IP address, minutes
- Where: same section
- Default: 15 minutes.
- Values / limits: 1–1440 minutes.
Sign-up attempts per email address
- Where: same section
- What it does: Maximum account creation attempts using one email address within the period below.
- Default: 5.
- Values / limits: 1–100.
Period for attempts using one email address, minutes
- Where: same section
- Default: 60 minutes.
- Values / limits: 1–1440 minutes.
External captcha (optional)
Off by default. The keys stay on the server and are never shown on public forms.
CAPTCHA service
- Where: ExpertPress → Settings → Spam protection and sign-in → External captcha (optional)
- What it does: Adds a third-party challenge to the protected forms.
- Default: No external service — built-in protection only.
- Values / limits: No external service — built-in protection only; Google reCAPTCHA v2; Cloudflare Turnstile. Selecting a service without valid keys blocks all protected forms.
- When to change it: built-in protection is not enough against a persistent bot.
- Related: —
reCAPTCHA public key (Site key) / reCAPTCHA secret key (Secret key)
- Where: same section
- What it does: Keys from your Google reCAPTCHA v2 account.
- Default: empty.
- Values / limits: the secret key is admin only; managers see “Only a site administrator can change secret keys.” Secrets are stored encrypted.
Turnstile public key (Site key) / Turnstile secret key (Secret key)
- Where: same section
- What it does: Keys from your Cloudflare Turnstile widget.
- Default: empty.
- Values / limits: the secret key is admin only.
Sign in with Google
Get the Client ID and Client secret from your Google Cloud OAuth application. Copy the Sign-in return address shown on the tab into Authorized redirect URIs of that application. After saving the keys, enable and check the button on the site. Saved with Save Google sign-in.
Show «Continue with Google»
- Where: ExpertPress → Settings → Spam protection and sign-in → Sign in with Google
- What it does: Shows the “Continue with Google” button on sign-in and sign-up. A user whose Google email matches an existing account is linked to it automatically; new users are registered (and must accept the Terms of use if a terms page is chosen).
- Default: off.
- Values / limits: on / off. The button stays hidden until both the application ID and the secret are set, even when this is on.
- When to change it: to reduce sign-up friction and forgotten passwords.
- Related: Terms of use
Google application ID (Client ID)
- Where: same section
- Default: empty.
- Values / limits: text from Google Cloud.
Google application secret (Client secret)
- Where: same section
- What it does: The OAuth secret, stored encrypted. When set, the field shows “Set — type a new value to replace it.” If it shows “Set, but it cannot be read with the current site keys — enter it again”, the site's security keys changed; enter the secret again. Remove the stored secret deletes it.
- Default: empty.
- Values / limits: admin only.
Sign-in return address (read-only)
- Where: same section
- What it does: The callback address to paste into Google Cloud:
https://your-site/wp-json/expertpress/v1/auth/google/callback.
Google sign-in history (read-only)
- Where: same section
- What it does: The last 30 Google account events: signed in, linked automatically, email confirmed by Google, registered, linked or confirmed from the profile, unlinked, released from a closed account.