Manny Wenas SEO

Description

At a copywriting conference around 2011, a group of journalists asked their SEO tool — half sarcastically — whether they should just repeat their keyword phrase fifteen times in a row.

The tool essentially said yes.

That’s the problem Manny Wenas SEO was built to fix.

Every other SEO plugin on the market was designed to make Google happy. Manny Wenas SEO was designed to make writers happy. The difference matters. Mechanical writing ranks worse than good writing. Always has. We just happen to be the first plugin to build that conviction into the scoring.

Our core principle: reward writers for organically placing their keyphrase. Never make them feel like they’re writing for a search engine algorithm. Mechanical writing is the enemy.

What makes this different

We check five things: your keyphrase in the title, in the opening paragraph, in a subheading, in the slug, and in the meta description. That’s it. We don’t count how many times you used it in the body. We don’t penalise you for not hitting a density percentage. We don’t tell you to stuff it into places it doesn’t belong.

If you wrote a good article and placed your keyphrase naturally in those five locations, you’ll score well. If you wrote a great article but missed one, you’ll still score well — and we’ll tell you which one you missed, not scold you for it.

Features

• Focus keyphrase (semantic matching) plus up to two related keyphrases
• SEO title, meta description, noindex/nofollow per post
• Open Graph and X/Twitter cards
• Sitemaps: posts, news, images, videos, categories, tags, authors, plus an HTML sitemap shortcode
• robots.txt management and weekly-generated llms.txt (anchor posts first)
• Connected @graph JSON-LD, server-side rendered
• Yoast SEO and Rank Math coexistence (we defer: no duplicate meta, schema or sitemaps)
• Google Search Console (OAuth), per-post query data
• WordPress Abilities API (WP 6.9+)
• 0-100 SEO and readability score with a written verdict in the editor

Deliberately excluded: redirects, 404 monitor, analytics dashboard, AI writer.

External Services

This plugin optionally connects to the following third-party services. All external connections are disabled by default and must be explicitly enabled by the site administrator.

IndexNow (optional, disabled by default)
When enabled, notifies search engines of new or updated content via the IndexNow protocol.
Sends: the URL of the published/updated post, plus the site’s IndexNow API key.
Triggered: when a post is published or updated, if the feature is enabled (Manny Wenas SEO > Verification & IndexNow).
Service provider: IndexNow (Microsoft/Bing)
Terms of use: https://www.indexnow.org/documentation
Privacy policy: https://privacy.microsoft.com/en-us/privacystatement

Google Trends (optional, disabled by default)
When enabled, shows a search-interest score for your focus keyphrase in the post editor.
Sends: the focus keyphrase you typed, to trends.google.com (unofficial endpoint, no account or API key).
Triggered: about 800 milliseconds after you stop typing the focus keyphrase in the SEO metabox, if the feature is enabled (Manny Wenas SEO > General). Results are cached for 24 hours, failed requests for 1 hour.
Service provider: Google LLC
Terms of use: https://policies.google.com/terms
Privacy policy: https://policies.google.com/privacy

Google Search Console (optional, OAuth-based)
When enabled, connects to your GSC account to display search query data for a post.
Sends: OAuth tokens managed by the site administrator and, when the metabox asks for query data, the URL of the post. No post content is sent.
Triggered: only after the GSC integration is manually authorized by the administrator.
Service provider: Google LLC
Terms of use: https://policies.google.com/terms
Privacy policy: https://policies.google.com/privacy

OpenAI / Anthropic (pro tier only, not included in this plugin)
The pro version of this plugin (distributed separately, not through WordPress.org) optionally connects to OpenAI or Anthropic APIs for AI-assisted meta generation. This functionality is not present in the version hosted on WordPress.org.