1. SEO content and settings
The plugin reads post/page content and SEO settings to generate metadata, sitemaps, structured data, link analysis, and configured content directories. It stores SEO metadata, focus keywords, canonical URLs, social fields, redirects, and related settings in your WordPress database. Organization details and author profile fields you configure can appear publicly in rendered pages and structured data.
Dedicated tables use your database prefix followed by modulustools_meta, modulustools_redirects, modulustools_404_logs, and modulustools_ai_bots. Settings and integration configuration also use WordPress options. This installation data is not automatically sent to a Modulus Tools analytics service.
2. Missing-page and crawler logs
When the corresponding modules are enabled, the plugin can log missing request URLs, referrers, user-agent information, hit counts, timestamps, and a hash derived from an IP address for 404 monitoring. Crawler records can include the crawler label, requested URL, post identifier, user agent, status, and visit time.
URLs and referrers can contain sensitive query parameters. Review what your site records, restrict administrative access, and apply retention and backup practices appropriate to your visitors. Do not treat hashed identifiers as a guarantee of anonymity.
3. IndexNow and configured webhooks
When IndexNow is enabled, publishing or updating supported public content can send the site host, page URL, and generated verification key information to https://api.indexnow.org/indexnow. A configured IndexNow webhook can also receive this notification payload.
Important: the inspected 1.2.2 source initializes IndexNow as enabled for a new installation. Review General & Robots before publishing content, and disable it if you do not want these notifications. Notifications are not a guarantee of search-engine inclusion.
The recipient handles requests under its own policies. Review the IndexNow terms and any webhook provider before use.
4. Drafting and AI integrations
The local heuristic fallback generates suggestions on your WordPress server. If you use a configured WordPress AI integration or custom gateway, requested draft generation may send a prompt containing a post title, content excerpt, focus keyword, and task instructions to that provider. The custom-gateway code uses a content snippet of up to approximately 250 words.
Provider settings and any supplied API credential are stored on your WordPress installation. Do not send credentials or confidential content to support. Review the selected provider’s retention, billing, and privacy terms; configuring an integration does not make that provider part of Modulus Tools.
5. Public output and site responsibility
Sitemaps, structured data, metadata, and enabled llms.txt directories are intended to be accessible to visitors and crawlers. Review their generated contents before enabling them on a sensitive site. robots.txt preferences are crawler instructions, not authentication or access control.
As the site operator, you decide which modules run and are responsible for informing your visitors about your site’s processing, hosting, and third-party integrations. The plugin does not replace your website privacy notice.
6. Retention and removal
Data remains in your database and backups according to your administration and hosting practices. Use available controls to delete individual redirects or 404 records and review stored settings. Removing the plugin does not erase its data by default.
The uninstall routine removes its listed tables, settings, and profile metadata only when the administrator has enabled delete_data_on_uninstall before uninstalling. Back up anything you intend to retain. Hosting backups and third-party copies may persist separately.
7. Contact and support
For questions about this plugin, contact support@modulustools.com or use the WordPress.org support forum. Messages you choose to send are handled separately under our website and contact privacy policy.
Back to the WordPress plugin