內容簡介
Freexya 是一個多功能的 WordPress 外掛，整合了網站所需的多項功能，包括 SMTP 郵件發送、Cookie 同意管理、404 重定向及安全性工具，簡化網站管理流程，提升使用者體驗。
【主要功能】
• SMTP 郵件發送與日誌管理
• Cookie 同意橫幅與第三方腳本管理
• 404 錯誤頁面重定向與日誌
• 安全性設定與漏洞檢查
• 活動日誌追蹤變更歷史
• 自訂欄位管理與內容關聯
外掛標籤
開發者團隊
② 後台搜尋「Freexya – Cookie Consent, SMTP, Redirects & Security Toolkit」→ 直接安裝（推薦）
📦 歷史版本下載
原文外掛簡介
One plugin for the jobs every WordPress site needs, instead of five or six:
E-mails that do not arrive — send through SMTP or an API, keep a log of every message, and read the server’s own reason when one fails.
A cookie banner that really blocks — third-party scripts and embeds wait for consent, with Google Consent Mode v2.
404s after a redesign — a log of the broken addresses visitors hit, with their count, redirected in one click.
Security — a light firewall, HTTP headers, a limit on failed logins, and your plugins checked against known vulnerabilities.
Each job is a module you switch on from the hub, and a module that is off registers nothing: none of its hooks run on the site. The modules:
Dashboard — a readable admin home and a tidied toolbar.
Shortcuts — duplicate content, reorder it by hand, add entries in one click.
Roles & capabilities — capabilities sorted under the post type that creates them, and the site seen through a role’s eyes without leaving your own account.
Activity log — who changed what, with the before and the after.
Cookies — a consent banner, third-party scripts held back until consent, and a scan that finds them.
SEO — titles and descriptions with a suggestion drawn from the page’s text, sitemap, schema, llms.txt.
Mail — SMTP, an API provider, or a Gmail or Microsoft 365 account connected with OAuth, a delivery log, a test message, an invisible captcha for the site’s forms.
Redirects — exact redirects and a 404 log with the hit count.
Media — regenerate thumbnails in the background, in batches.
Security — a light firewall that refuses requests carrying an attack before WordPress runs, security headers, a content policy, a limit on failed logins, and a check of the installed plugins against known vulnerabilities.
Maintenance — a holding page, database clean-up, a database export, and the previous version of each extension kept before its update.
Custom fields — field groups with repeaters, flexible content and relations, kept in their own tables, and content types and taxonomies of your own.
Element — sixteen Elementor widgets for custom fields, NCF’s or ACF’s: repeaters as cards, tabs or tables, galleries and sliders, key figures, teams, timelines, taxonomies, maps.
Translate — your site in several languages: each page linked to its translations, a translation editor beside the original (blocks, Elementor, ACF and NCF fields), addresses in /en/, a menu per language, a language switcher, hreflang, and every text of the site translated from the admin. A site coming from WPML or Polylang moves over in one click.
Social — your Google reviews, your Instagram feed and your Facebook page on your pages, in a grid or a single post with a lightbox, set for computer, tablet and phone, and refreshed on their own; as a shortcode, a block or an Elementor widget.
Free and Pro
Everything above is free, on as many sites as you like. nexya Pro, sold on nexya.dev, adds three modules — nexya forms, Mailya for newsletters and a page cache — and the parts that do the repetitive work for you: suggested redirects and pattern rules, CSV import, a daily vulnerability pass and a file fingerprint with rollback, a two-step login, updates undone by themselves when they break the site, undo from the activity log, a second sending server and failure alerts for mail, a branded login screen and admin skin, banner appearance and consent service by service, scheduled database clean-up, orphan image sizes, folders in the media library, and longer log retention. The free version contains none of that code; nexya Pro is delivered by Freemius after purchase, and takes over from this plugin with the same settings.
Privacy
The plugin sends nothing to a third party by default. The features that reach the network, and what they send, are listed under External services below.
Multisite
Multisite networks are not supported. On a network the plugin stays switched off and says so.
External services
Nothing below runs unless you switch the matching module or option on. No data leaves the site by default, and the plugin sends no usage data anywhere.
WPVulnerability (Security module, vulnerability watch). When you start a check from the Security screen, the plugin asks the public WPVulnerability API whether the installed plugins have known vulnerabilities. For each installed plugin, its slug is sent to www.wpvulnerability.net; nothing else about the site is sent. Nothing is sent until you start a check. Terms and privacy (legal notice of its publisher): https://www.robotstxt.es/legal/
WordPress.org checksums (Security module). While the Security module is on, once a day and when you press “Check now”, the plugin asks api.wordpress.org — the same service WordPress uses for its own updates — for the checksums of the installed WordPress version, sending only that version number and the site language, then compares them with the core files on your server. Terms: https://wordpress.org/about/privacy/
IndexNow (SEO module, optional, off by default). Only if you switch it on, each time a page is published, updated or taken down its address is sent to api.indexnow.org, which shares it with the search engines that take part (Bing, Yandex, Seznam, Naver and others), along with the site’s host name and the verification key the plugin serves at the root of your site. Nothing is sent while the site asks search engines not to index it, or runs on a local address. Terms: https://www.indexnow.org/terms — Privacy (Microsoft, which runs the IndexNow service): https://www.microsoft.com/en-us/privacy/privacystatement
Stripe (nexya forms, Payment module, optional, nexya Pro). Only once you switch the module on and enter your own Stripe secret key, a form with a payment field sends, when the visitor submits it, the amount, the currency, the name of the form, the visitor’s e-mail address if the form asks for one, and the entry’s number to api.stripe.com to open a Stripe Checkout page; the visitor then pays on Stripe’s site. Stripe calls back the site’s own webhook address to confirm the payment. Terms: https://stripe.com/legal/ssa — Privacy: https://stripe.com/privacy
PayPal (nexya forms, Payment module, optional, nexya Pro). Only once you enter your own PayPal REST app credentials, a form with a payment field sends, when the visitor chooses PayPal, the amount, the currency, the name of the form and the entry’s number to api-m.paypal.com (or api-m.sandbox.paypal.com in sandbox mode) to open a PayPal approval page; the visitor approves the payment on PayPal’s site, and the site captures it when they come back. Terms: https://www.paypal.com/legalhub/home — Privacy: https://www.paypal.com/myaccount/privacy/privacyhub
Patchstack (Security module, optional). Only if you enter your own Patchstack API key, the same check also asks api.patchstack.com, sending each installed plugin’s slug and your key. Terms: https://patchstack.com/terms-and-conditions/ — Privacy: https://patchstack.com/privacy-policy/
E-mail delivery (E-mails module). When you pick an API provider instead of SMTP, the messages your site sends are handed to that provider’s API: sender, recipients, subject, body and attachments, at the moment the message is sent. You choose the provider and enter its API key. The providers offered are Brevo (https://www.brevo.com/legal/termsofuse/ — https://www.brevo.com/legal/privacypolicy/), SendGrid (https://www.twilio.com/en-us/legal/tos — https://www.twilio.com/en-us/legal/privacy), Postmark (https://postmarkapp.com/terms-of-service — https://postmarkapp.com/privacy-policy), Resend (https://resend.com/legal/terms-of-service — https://resend.com/legal/privacy-policy), SMTP2GO (https://www.smtp2go.com/terms/ — https://www.smtp2go.com/privacy/), MailerSend (https://www.mailersend.com/legal/terms-of-service — https://www.mailersend.com/legal/privacy-policy), SendLayer (https://sendlayer.com/terms-of-service/ — https://sendlayer.com/privacy-policy/), Mandrill (https://mailchimp.com/legal/terms/ — https://mailchimp.com/legal/privacy/), Mailgun (https://www.mailgun.com/legal/terms/ — https://www.mailgun.com/legal/privacy-policy/), Elastic Email (https://elasticemail.com/resources/usage-policies/terms-of-use — https://elasticemail.com/resources/usage-policies/privacy-policy) and SparkPost (https://www.sparkpost.com/policies/tou/ — https://www.sparkpost.com/policies/privacy/).
Gmail and Microsoft 365 sending (E-mails module, optional). Only if you choose Google (Gmail, Workspace) or Microsoft 365 (Outlook) as the sending method and connect an account. When you press “Connect”, your browser goes to accounts.google.com or login.microsoftonline.com, where you sign in and allow the site to send e-mail; the plugin then sends the authorisation code it gets back, with the client ID and secret you entered, to oauth2.googleapis.com or login.microsoftonline.com to obtain an access token, and renews that token there when it expires while the site is sending. No password is stored on the site. Each message the site sends then goes through smtp.gmail.com, or smtp.office365.com / smtp-mail.outlook.com, with its sender, recipients, subject, body and attachments, at the moment it is sent. Google — Terms: https://policies.google.com/terms — Privacy: https://policies.google.com/privacy. Microsoft — Terms: https://www.microsoft.com/en-us/servicesagreement — Privacy: https://www.microsoft.com/en-us/privacy/privacystatement
Cloudflare (Cache module, optional). Only if you switch the Cloudflare option on and enter your zone ID and API token: each time the nexya cache is emptied, the plugin asks api.cloudflare.com to empty the cache of that zone, sending the zone ID, the token and, when only some pages changed, their addresses. Terms: https://www.cloudflare.com/terms/ — Privacy: https://www.cloudflare.com/privacypolicy/
Form webhook (nexya forms, optional). Only if you enter an address in a form’s settings, each entry of that form is sent, when it is submitted, to that address as JSON: the form’s name and number, the entry’s number and date, the page it was sent from, the site’s address, and the answers with the label and type of each field. You choose the address (Zapier, Make, n8n, a CRM…); the plugin contacts no address you did not enter, and the terms and privacy policy that apply are those of the service you chose.
AI suggestions (optional). The plugin calls no AI provider itself. When you press a button that asks for a suggestion (a title, a description, an image text…), the text needed for it is handed to the AI client built into WordPress, which sends it to the provider of the connector you set up in WordPress, under that provider’s terms. Without such a connector, these buttons do not appear and nothing is sent.
Audience measurement tags (SEO module). If, and only if, you enter an ID or an address for one of them, the module prints that service’s tag on the front end; the visitor’s browser then loads the script from the service and sends it what that tag collects.
* Google Tag Manager and Google Analytics 4, from www.googletagmanager.com. Terms: https://marketingplatform.google.com/about/analytics/terms/us/ — Privacy: https://policies.google.com/privacy
* Plausible, from plausible.io or the address you enter. Terms: https://plausible.io/terms — Privacy: https://plausible.io/privacy
* Umami, from the address of your own Umami instance or Umami Cloud. Terms: https://umami.is/terms — Privacy: https://umami.is/privacy
* Matomo, from the address of your own Matomo instance or Matomo Cloud. Terms: https://matomo.org/matomo-cloud-terms-of-service/ — Privacy: https://matomo.org/privacy-policy/
nexya connection relay, Google, Instagram and Facebook (Social module, optional, off by default). Only once you switch the Social module on and press “Connect” for Google, Instagram or Facebook: your browser goes to studio.nexya.dev, run by the makers of nexya, with your site’s admin address and a one-time check value, and from there to accounts.google.com, www.instagram.com or www.facebook.com, where you sign in and allow access. The relay exchanges the code it gets back for access tokens (the app secrets stay on the relay, never on your site), holds them for at most ten minutes, and your site then claims them from studio.nexya.dev with a value that never left your server. For Google, your site asks studio.nexya.dev for a new access token, sending its renewal token, at most once a day when it refreshes the reviews. Afterwards the site reads, with those tokens: the reviews, average rating and name of your Google Business profile from mybusiness.googleapis.com, mybusinessaccountmanagement.googleapis.com and mybusinessbusinessinformation.googleapis.com (once a day); the last posts and the profile of your Instagram professional account from graph.instagram.com (every hour); the last posts, name and picture of your Facebook page from graph.facebook.com (every hour). The pictures and videos of those posts and the reviewers’ photos are downloaded to your own uploads folder, so visitors load them from your site, not from Google or Meta. In the simple mode for Google, the site sends your own Google Places API key and the place’s ID to places.googleapis.com instead, once a day. nexya relay — Privacy: https://nexya.dev/en/privacy-policy/ — Google — Terms: https://policies.google.com/terms — Privacy: https://policies.google.com/privacy. Meta (Instagram, Facebook) — Terms: https://www.facebook.com/terms.php — Privacy: https://www.facebook.com/privacy/policy/
Freemius (trial and purchase of nexya Pro). The Freemius SDK ships with the plugin in anonymous mode: on its own it sends nothing and shows no opt-in. Only when an administrator starts the Pro trial or buys nexya Pro from the plugin’s screens are the site address, the WordPress, PHP and plugin versions and the administrator’s name and e-mail address sent to Freemius, which handles the checkout and the licence. Terms: https://freemius.com/terms/ — Privacy: https://freemius.com/privacy/
Lists of known hosts (Cookies and Security modules). These are not remote files and nothing is loaded from them. The cookie module carries a list of third-party hostnames (Google Fonts, Font Awesome, public CDNs, YouTube, Google Maps and so on) as plain data: a script or frame already on your page whose address matches one of them is held back until the visitor consents. The Security module carries a similar list of well-known origins, offered as ready-made lines when you write your site’s content security policy, the header that tells browsers which origins your pages may load from. Both lists are plain data files, modules/Cookie/data/hosts.json and modules/Security/data/origins.json. The plugin itself never contacts any of these hosts.
Requests to your own site. The cookie scan, the sharing-image finder of the SEO module and a few background jobs fetch pages of your own site from your own server. Nothing leaves it.
Third-party libraries
Chart.js 4.5.1 (MIT) draws the statistics charts — assets/js/chart.min.js. Source: https://github.com/chartjs/Chart.js
Freemius SDK (GPL) handles the licence and the update checks. Source: https://github.com/Freemius/wordpress-sdk
Font Awesome Free 6.7.2 brand icons (CC BY 4.0) for the social networks of e-mails and pop-ups — assets/social/. Source: https://fontawesome.com
The plugin’s own JavaScript and CSS ship as written, next to a minified copy of each file (.min.js / .min.css, made with esbuild when the plugin is packaged). The minified copies are loaded on the site; with SCRIPT_DEBUG on, the readable files are loaded instead.
