WPZOOM

If I buy one WPZOOM theme or plugin license, how many websites can I activate it on?

It depends on whether you buy a theme or a plugin, and which pricing tier you pick at checkout. Themes: most individual theme purchases include unlimited website usage — the themes page states every premium theme 'comes with a 12-month license that covers as many websites as you own. There is no per-site fee' and lists 'Unlimited sites' as a benefit. Plugins: individual plugin licenses are tiered, with the site count shown on the pricing option you choose — e.g., WPZOOM Portfolio PRO offers 'License for 3 Sites' and 'License for 10 Sites' (€99/yr Business tier), and both the Social Share and Instagram Widget plugins offer a Business tier with 'License for 10 Sites' ($79/yr). Product bundles have limited activations, except the All Access Pass, which includes unlimited site usage. Additional rules: localhost development sites don't count toward the limit (1 Site License covers 1 live site + 1 localhost dev site); you can temporarily activate on a staging domain; on a Multisite network each site counts as a separate website; and if you bought a Single Site license you must upgrade it to use a second site.

Found on /docs/how-many-sites-can-i-use-wpzoom-themes-on › How many sites can I use WPZOOM themes and plugins on?

What's your refund policy if a theme doesn't work out for my site — how many days do I have to request a refund, and are there conditions?

WPZOOM gives you 14 days to request a refund. The main FAQ states: "If a theme or plugin isn't right for you, ask for a refund within 14 days of purchase." Theme-level FAQs characterize it as a "no-questions-asked refund policy within 14 days of purchase if you're not satisfied with your theme" — i.e., no conditions beyond the 14-day window. Note: the FAQs link to a dedicated refund policy page (https://www.wpzoom.com/refund-policy/) "for the details," but that page was not among the retrieved content, so any fine-print exclusions or procedural conditions cannot be verified from these chunks.

Found on /faq › Frequently Asked Questions › Before you buy

How much does WPBruiser Pro cost, and is it a yearly subscription or a one-time purchase?

WPBruiser Pro is a yearly subscription, not a one-time purchase. Pricing is tiered: Starter — 1 site, $49/year; Professional — 3 sites, $79/year; Business — 10 sites, $149/year. Every plan includes 1 year of support and updates, with a 14-day money-back guarantee. The site states explicitly: "All purchase options are billed yearly. You may cancel your subscription at any time. Support, updates, and plugin downloads are for one year." Integration pages consistently list the entry price as "WPBruiser Pro, from $49/year."

Found on /blog/wordpress-security-plugins › The Best WordPress Security Plugins to Protect Your Site › Upgrade Your Website with a Premium WordPress Theme › 9. WPBruiser › WPBruiser Pricing

Does my purchase include plugin and theme updates plus support, and for how long — one year, or as long as my license is active?

Yes — every purchase includes both updates and support. Duration depends on the license: a yearly license includes twelve months of updates and technical support from the date of purchase, and the Lifetime All Access Pass includes updates and support with no renewal. The two framings in your question are actually the same model: licenses are annual subscriptions that renew automatically until you cancel, so you get 'continuous access to updates and support for as long as your subscription is active' — one year at a time. Per the Terms & Conditions, 'All updates and new versions are free of charge for existing customers while their license is active' and 'Support is free of charge for existing customers while their membership is active.' If you cancel or don't renew, updates and support stop (though your themes and plugins keep working), and renewing restores them for another year. Note: plugin purchase pages (e.g., Instagram Widget, Social Icons, WPBruiser, WPZOOM Forms) state 'Support, updates, and plugin downloads are for one year' with all options billed yearly.

Found on /themes/magazine › WordPress Magazine Themes › Magazine Theme FAQs

Can I import an Inspiro starter site like the food blog demo onto my existing site that already has content, or does it only work on a fresh WordPress install?

Yes — you can import an Inspiro starter site (including the Food Blog demo) onto an existing WordPress site with content; it is not limited to fresh installs. However, WPZOOM recommends a fresh install for best results. The Inspiro Starter Sites FAQ states: "We recommend importing on a fresh WordPress install for the best results. While you can import a starter site on an existing WordPress website, it may override your current settings, page design, and content. Be sure to back up your site before proceeding." The Food Blog starter site's own FAQ adds a reassuring nuance: "importing a Starter Site does not delete your existing content... If you have existing pages or posts, they will remain, but new demo content will be added," though it "may override theme settings and widgets." Practical takeaway: importing on your existing site is supported — your posts/pages won't be deleted and demo content will be added on top — but back up your site first and expect your theme settings, widgets, and possibly page design to be overridden. A fresh install is simply the cleaner path WPZOOM recommends.

Found on /plugins/inspiro-starter-sites › WPZOOM Inspiro Starter Sites › Frequently asked questions

What does the WPBruiser integration with Mailchimp for WordPress actually do — does it block bot signups before they ever reach my mailing list?

Yes — the integration blocks bot signups before they reach your Mailchimp list. WPBruiser checks every Mailchimp for WordPress (MC4WP) form 'so only real people are subscribed': each form gets an invisible token that the visitor's browser fetches in the background, and bots that submit without it are rejected. When a bot is blocked, 'the form shows an error and the address is not sent to Mailchimp' — the fake address never reaches your list, and the attempt is logged in WPBruiser › Reports with the form, the IP address and what the bot tried to send. Coverage includes every sign-up form built with MC4WP plus the Mailchimp Top Bar add-on. It's part of the free WPBruiser plugin (the free plan protects 2 forms), switched on with one click on the Integrations screen, and visitors see 'nothing to solve' — no CAPTCHA, puzzle or checkbox.

Found on /plugins/wpbruiser/integrations/mailchimp-for-wordpress › WPBruiser for Mailchimp for WordPress

WPBruiser mentions rate limiting — what are the actual numbers, like how many failed login attempts trigger a block and how long does the block last?

Yes — WPBruiser's login lockout (included in the free version) works like this by default: after 5 failed logins (the number is configurable — 'you choose the number'), the offending IP address is locked out for 20 minutes; if the IP keeps failing, the lockout extends to a full day; and an IP that tries a banned username like 'admin' or 'root' is locked out immediately. This covers the login form, XML-RPC, application passwords and other plugins' login forms, and lockouts can be released with one click. Two caveats: (1) the plugin landing page shows an example auto-block rule reading 'Block an IP after 10 failed logins' — that appears to be a sample configured value, not the default, since both the login-security guide and the release announcement state the default is 5 and that the threshold is user-chosen; (2) separately from login lockouts, WPBruiser Pro adds submission rate limits for forms — five submissions per IP every ten minutes by default, also configurable — which is a different mechanism from the failed-login lockout.

Found on /blog/wordpress-login-security › How to Secure Your WordPress Login Page: Best Practices › How to Secure the WordPress Login Page › 4. Limit the Number of Login Attempts

How do theme updates actually arrive — do WPZOOM themes update one-click through my WordPress dashboard with a license key, or do I have to download and upload manually?

WPZOOM themes update one-click through your WordPress dashboard — you do not need to download and upload manually. The mechanism: activate your license key on your website, and when a new theme version is released you'll see a yellow notice at the top of your WordPress Dashboard; click the "Update now" link on that notification, or check Dashboard → Updates / Appearance → Themes. The site is explicit that no manual handling is required: "Activate your license key and theme updates arrive in your WordPress dashboard like any other theme. Installing one takes a single click, with no manual file uploads and no FTP." Two conditions apply: (1) the license key "must not have expired, and you must activate it on your website" to benefit from one-click updates, and (2) license-key activation for 1-click updates is limited to the number of sites included with your purchase (themes themselves can be installed on unlimited sites). Manual download-and-upload is documented on WPZOOM's blog only as a general WordPress fallback method, not the primary flow for WPZOOM themes.

Found on /themes › Premium WordPress Themes › Easy to Use for Both Beginners and Experts

How does spam protection in WPZOOM Forms work under the hood — honeypot, CAPTCHA, or a third-party service like Akismet — and can I layer multiple methods?

WPZOOM Forms uses all three approaches, layered together, and explicitly encourages stacking them. (1) Honeypot: every form built with the 2.0 builder includes a hidden field visitors never see but bots tend to fill in; it is on by default per form (Builder → Settings → 'Enable spam honeypot field') and needs no configuration. A bot that trips it sees a 'success' message while the submission is silently discarded — nothing is stored or emailed. (2) CAPTCHA (optional): you pick one service globally under WPZOOM Forms → Settings → Spam Protection — Google reCAPTCHA v2 (visible 'I'm not a robot' checkbox on 2.0-builder forms; invisible badge on 1.x forms) or v3 (invisible, score-based; submissions scoring 0.5 and above are accepted, and the threshold is fixed) — or Cloudflare Turnstile (privacy-friendly: no cookies, no tracking, usually no interaction, challenge only when needed). Only one CAPTCHA service can be active at a time and it applies to all forms. (3) Third-party services: Akismet integrates automatically once the Akismet plugin is active — each submission (name, email, website, message, IP, user agent, referrer) is sent to Akismet for content analysis, so it catches human-written spam CAPTCHAs let through; flagged entries are stored with the Spam status (not emailed), and Mark as Spam/Not Spam in Submissions reports back so Akismet learns. CleanTalk has a direct integration (since July 2025) that checks submissions invisibly against CleanTalk's database. WPBruiser, WPZOOM's free anti-spam plugin, gives every form an invisible token the visitor's browser fetches in the background — a bot posting straight to the form arrives without one and is turned away before anything is stored or emailed; everything runs on your own server, so no visitor data goes to a third party. Layering: yes — the guide's recommended setup is 'Use the honeypot always, add one CAPTCHA service for bot traffic, and Akismet for human-written spam.' The only constraint is a single active CAPTCHA service: per the Troubleshooting section, 'Akismet, CleanTalk and the honeypot always work in addition to it,' WPBruiser 'works alongside the honeypot and Akismet' (you can leave the CAPTCHA off with it on), and CleanTalk 'works alongside the honeypot, a CAPTCHA and Akismet.' A layer table summarizes scope and what happens to blocked submissions for each layer (honeypot silently discards; CAPTCHA rejects with an error; WPBruiser rejects pre-storage and logs in Reports; Akismet stores as Spam for review).

Found on /documentation/wpzoom-forms/wpzoom-forms-spam-protection-guide › WPZOOM Forms Spam Protection Guide

If I customize my WPZOOM theme's CSS and templates, will those changes survive a theme update, or do I need to set up a child theme first?

It depends on where the customization lives — WPZOOM's own docs split it cleanly: **CSS added via the Customizer → Additional CSS panel (or Site Editor → Styles): survives updates, no child theme needed.** Changes there are "saved in the database, not your theme files, so they survive theme updates." WPZOOM's docs explicitly recommend this route for small tweaks: "If you want to make just some small changes, like adding custom CSS code, we recommend adding it in the Customizer > Additional CSS." **Template (PHP) edits and CSS written directly into theme files: will be erased on update — yes, set up a child theme first.** WPZOOM's update guide states: "Theme updates replace all theme files, erasing any direct customizations you've made. If you've modified your theme's CSS, template files, or functions.php directly, these changes will be lost when you update." By contrast, "Your child theme's customizations will survive parent theme updates. Without one, a single update can erase hours of work." WPZOOM's rule of thumb: "You need a child theme if you're: Editing PHP template files (like header.php, footer.php, or single.php); Adding custom functions to the functions.php file; Making extensive CSS changes you want version-controlled in files... You don't need a child theme if you're: Using only the Customizer or Site Editor (changes are saved in the database); Using a page builder; Adding a few lines of CSS via the Additional CSS panel." One caveat even with a child theme: WPZOOM notes "it's your responsibility to keep it up-to-date and synced with the parent theme. A major update of the parent theme can easily break your website if you didn't test your Child Theme against the new version on a local or staging environment before the update."

Found on /blog/how-to-customize-wordpress-theme › How to Customize a WordPress Theme: 5 Proven Methods › Frequently Asked Questions

Can I load my own Google Fonts in Inspiro's block theme on WordPress 6.5+, or am I limited to the fonts bundled with the theme?

Yes — you can load your own Google Fonts; you are not limited to the fonts bundled with the theme. WordPress 6.5 introduced the core Font Library feature, and WPZOOM's guide ('How to Customize Fonts in Block Themes using Font Library') walks through using it in block themes: in the Site Editor, open Styles → Typography, click the 'Manage Fonts' icon to open the Font Library, go to the 'Install Fonts' tab, browse or search for the Google Font you want, and click 'Install' to integrate it into your theme. The guide notes the Font Library 'is designed to be compatible primarily with block themes' (themes with full Site Editor support). Inspiro Blocks qualifies: WPZOOM describes it as 'the Full Site Editing free version... of the popular Inspiro Lite theme,' compatible with WordPress 6.5 – 7.1+. Inspiro Blocks' own documentation also covers customizing fonts via the Styles settings, and WPZOOM's block-theme docs include a section on 'How to Change Fonts and add New Google Fonts in your Block Theme.' So on WordPress 6.5+ with Inspiro Blocks, you can install any Google Font yourself via the Font Library. (Note: the separate 'Google Fonts API key' option in Theme Options applies to Inspiro Premium, the classic theme, not the block theme.)

Found on /docs/how-to-add-google-fonts-to-block-themes-in-wordpress-6-5 › How to Customize Fonts in Block Themes using Font Library › Introduction › How to Use the Font Library

What developer hooks and filters does WPBruiser Pro expose — for example, can I whitelist specific IPs or adjust blocking behavior programmatically?

Yes. WPZOOM publishes a dedicated 'Developer Reference: Hooks and Functions' page for WPBruiser/WPBruiser Pro. WPBruiser 3.3 introduced an extension API — 'It's what WPBruiser Pro uses to add its integrations, and you can use it to protect a custom form, supply your own IP-to-country data or add your own rejection rules.' Free-plugin hooks: `wpbruiser_loaded` (action), `wpbruiser_register_modules` (add your own module definitions), `wpbruiser_reject_reason` (reject a submission that passed every check by returning a `GdbcRequestController::REJECT_REASON_*` constant, or `null` to accept — Pro's rate limits use it), `wpbruiser_country_id_for_ip` (replace the bundled IP-to-country lookup), `wpbruiser_scripts_in_head`, and `wpbruiser_pro_version`. Pro-specific filters: `wpbruiser_pro_rejection_message` (change the message shown when a submission is blocked), `wpbruiser_excluded_gforms` (array of Gravity Forms IDs to leave unprotected), and `wpbruiser_pro_load_module` (return `false` to stop a Pro module from loading). There are also public PHP functions — `wpbruiser_get_extension_api_version()`, `wpbruiser_get_token_field_html()`, `wpbruiser_is_option_enabled()`, `wpbruiser_verify_submission()`, `wpbruiser_get_token_field_names()` — plus a `wpbruiser:token` browser event for JS-driven forms. On the IP example: yes, you can whitelist specific IPs, but the docs describe it as an admin-UI feature (WPBruiser → Security → White Listed IPs, accepting an address, range, or CIDR; allowed addresses 'skip all of WPBruiser's checks'). No filter for programmatically editing the allow list is documented — for programmatic control of blocking behavior you'd use `wpbruiser_reject_reason` (custom rejection rules) and the Pro filters listed above.

Found on /documentation/wpbruiser/developer-hooks › Developer Reference: Hooks and Functions

robots.txt

sitemap.xml

AI crawler access

Pages load cleanly

Markdown on request

Server-rendered text

Meta description

Page language

Organization schema

Sitemap dates