How to set up ModulusTools SEO Suite in WordPress

Install the published plugin and prepare your site

Confirm your installation runs WordPress 6.5 or later and PHP 8.2 or later. Back up your database and site files, and test a change on staging when your site already relies on another SEO plugin.

Find ModulusTools SEO Suite in Plugins → Add New Plugin or follow the WordPress.org link on this page. Confirm the slug is modulustools-seo-suite. Do not run competing metadata, schema, or sitemap generators without deciding which tool owns each output.

1. Install and activate the plugin from the WordPress directory.
2. Open ModulusTools SEO → Modules in the admin sidebar.
3. Review enabled modules before changing a live post.
4. Keep a copy of existing SEO settings before importing or replacing metadata.

Review modules and external connections first

Open General & Robots to review your organization details, title separator, and crawler preferences. Module controls let you choose the features your site needs rather than assuming every module suits every installation.

Important: the inspected 1.2.2 source initializes IndexNow as enabled. If you do not want public post URLs sent to IndexNow when content is published or updated, disable that setting before publishing. Review any configured webhook and AI provider too.

Core SEO controls do not require an external AI account. Local heuristic suggestions run on your server. If you choose a configured WordPress AI integration or custom gateway, a requested draft can send a title, excerpt, focus keyword, and task prompt to that provider. Do not test it with confidential content.

Configure and inspect one page

Edit a representative post or page and locate the ModulusTools SEO metabox. Write a descriptive SEO title and meta description, review the canonical URL and indexing directive, and choose a schema type that matches the actual content. Avoid changing an established page to noindex accidentally.

For example, a workshop page should describe the workshop clearly instead of repeating the same keyword in every field. Treat length and readability suggestions as editing prompts, not Google rules or a ranking score.

Publish the intended changes, then inspect the rendered page source for the title, description, canonical, robots directives, and social metadata. Check for duplicate tags from a theme or another plugin. Preview the page itself as a visitor, not only in the editor.

Check sitemaps, redirects, and structured data

Visit /sitemap_index.xml on your own site. If the route does not resolve after activation, open Settings → Permalinks and save once to refresh rewrite rules. Check that listed pages are public and intended for indexing before submitting the sitemap to your verified Search Console property.

Test a redirect on a staging or disposable URL before adding rules to important pages. Confirm its destination and status, and avoid loops. Review the 404 monitor for missing pages rather than redirecting every unknown URL to the homepage.

Inspect the page’s JSON-LD against its visible content. Do not invent product reviews, author credentials, business locations, or prices to fill fields. Valid structured data does not guarantee a search feature.

Use content directories and measure real outcomes

If you enable the content-directory module, inspect /llms.txt and /llms-full.txt for material you intended to make public. These summaries are not access controls and do not improve Google rankings merely by existing. robots.txt preferences also do not keep private content secure.

Use your verified Search Console property to assess indexing, search queries, impressions, and clicks over time. Crawler logs and the plugin’s checks are diagnostics, not proof of traffic growth. Read the plugin privacy page for stored logs, external requests, retention, and uninstall behavior.