Kalki Automation

Smart SEO toolkit: title/description editor, SEO score, focus keywords, readability, XML sitemap, redirects, schema markup, Open Graph, Twitter Cards, breadcrumbs, bulk editor, AI generation, internal link suggestions, and page builder integrations.
This plugin relies on external services for some optional features (APIs, notifications, and indexing helpers). See the External Services section below for each provider, what data is sent, and links to their terms and privacy policies.
<h3>Features</h3>
<ul>
<li>Real-time SEO analysis – 20+ checks: focus keyword in title/description/slug/content, keyword density, keyword in first H2, title/description length, content length, H1 count, headings structure, image alt text, internal/external links, paragraph count, sentence length, passive voice, transition words, Flesch Reading Ease, OG image, schema type. Score 0–100 with pass/warning/fail and points. Analysis caching for performance.</li>
<li>Readability scoring – Flesch Reading Ease, average sentence length, passive voice %, transition words %. Separate readability analysis available.</li>
<li>Tabbed SEO panel – General (focus keyword, SEO title, meta description, canonical, secondary keywords, live Google snippet preview), Social (OG/Twitter preview and fields), Advanced (noindex/nofollow/noodp, schema type, breadcrumb title), Score (circular gauge, checklist grouped by problems/warnings/passed).</li>
<li>Live snippet preview – Google-style SERP preview with desktop/mobile toggle; character counters and progress bars for title (30–60) and description (120–160).</li>
<li>Block Editor (Gutenberg) – Sidebar panel with score and checklist; meta box hidden when using block editor. Real-time content subscription for analysis.</li>
<li>Classic Editor – Full meta box with autosave and debounced analysis.</li>
<li>Elementor – Content extracted from Elementor layout for analysis; re-analyze on save; SEO score badge in editor. No runtime dependency.</li>
<li>Beaver Builder, Divi, WPBakery – Content extraction from builder data/shortcodes for accurate analysis.</li>
<li>XML Sitemap – Sitemap index; per-type sitemaps (posts, pages, categories, tags, custom post types); image sitemap; settings for enable/disable, exclude IDs, include noindex option. Ping Google on publish (rate-limited).</li>
<li>JSON-LD Schema – Article, WebPage, BreadcrumbList, Organization, WebSite (with SearchAction), FAQPage, Product (WooCommerce). Settings for organization name, logo, social sameAs. Filter <code>meyvora_seo_schema_data</code> for customization.</li>
<li>Redirect manager – 301/302/307/410 redirects; DB table; hit count and last accessed; CSV import/export; cache for performance.</li>
<li>404 monitor – Log 404 URLs with hit count and last seen; view in Redirects tab.</li>
<li>Breadcrumbs – Shortcode <code>[meyvora_breadcrumbs]</code>, template tag <code>meyvora_seo_breadcrumbs()</code>, schema-ready items. Enable in settings.</li>
<li>WooCommerce – Product post type in meta box and sitemap; Product schema (name, description, image, offers, SKU, availability).</li>
<li>Import – Import from Yoast SEO or Rank Math (post meta mapping); batch processing.</li>
<li>Post list – SEO score column (sortable), focus keyword, optional readability. Bulk “Analyze selected” and score filter (Good/Okay/Poor/No keyword).</li>
<li>Admin bar – SEO score badge on frontend when viewing a singular post/page; link to edit.</li>
<li>Per-post-type support – Filter <code>meyvora_seo_supported_post_types</code>; settings for which post types show the SEO panel.</li>
<li>Security – Nonces, capability checks, sanitization and escaping on all inputs/outputs.</li>
<li>Free – No upsells, no account required.</li>
</ul>
<h3>Source Code</h3>
The JavaScript and CSS used by Meyvora SEO are maintained and publicly available here: 
https://github.com/KalkiAutomation/meyvora-seo
WordPress.org release packages ship these scripts and stylesheets as readable source files (for example under <code>admin/assets/</code>, <code>assets/</code>, <code>blocks/</code>, and <code>integrations/assets/</code>). They are the same kinds of sources you find in that repository—they are not an opaque compiled-only artifact in the current workflow.
If you work from Git, clone the repository into <code>wp-content/plugins/meyvora-seo</code>, edit assets there, test in WordPress as usual, and open a pull request on GitHub.
<h3>External Services</h3>
This plugin connects to the following third-party services. By using the relevant features, you agree to their respective terms and privacy policies.
DataForSEO 
Used for: keyword research, search volume data, competitor page analysis, and ranked keyword data. 
Data sent: keyword queries, competitor URLs, your DataForSEO API credentials. 
Triggered when: you use the Keyword Research, AI SEO, or Competitor Analysis features. 
Terms of Service: https://dataforseo.com/terms-of-service 
Privacy Policy: https://dataforseo.com/privacy-policy
OpenAI 
Used for: AI-powered SEO content suggestions and analysis (including optional image alt-text generation when configured). 
Data sent: page content, keywords, and prompts you provide to the AI features. 
Triggered when: you use any AI content feature in the plugin. 
Terms of Service: https://openai.com/policies/terms-of-use 
Privacy Policy: https://openai.com/policies/privacy-policy
If you choose a custom OpenAI-compatible API endpoint in settings, requests are sent to the host and URL you configure; that provider’s terms and privacy policy apply instead of (or in addition to) OpenAI’s.
IndexNow 
Used for: notifying search engines of new or updated content for faster indexing. 
Data sent: URLs of published or updated posts/pages on your site. 
Triggered when: you publish or update a post/page (only if IndexNow is enabled in settings). 
Terms of Service: https://www.indexnow.org/faq 
Privacy Policy: https://www.indexnow.org/faq
Google Search Console (GSC) 
Used for: retrieving keyword and performance data for your site. 
Data sent: OAuth credentials and your site’s Search Console property URL. 
Triggered when: you connect your Google account in the GSC settings. 
Terms of Service: https://developers.google.com/terms 
Privacy Policy: https://policies.google.com/privacy
Google Sitemaps Ping 
Used for: notifying Google of updated sitemaps. 
Data sent: your sitemap URL. 
Triggered when: you publish or update content (only if sitemap ping is enabled in settings). 
Terms of Service: https://policies.google.com/terms 
Privacy Policy: https://policies.google.com/privacy
Google PageSpeed Insights API 
Used for: Core Web Vitals and PageSpeed performance data in the admin. 
Data sent: the page URL being tested and, if you add one, your Google PageSpeed API key. 
Triggered when: you run a Core Web Vitals / PageSpeed check from the plugin. 
Terms of Service: https://developers.google.com/terms 
Privacy Policy: https://policies.google.com/privacy
Slack (Incoming Webhooks) 
Used for: sending notification messages to a Slack workspace you configure. 
Data sent: message payloads to your webhook URL (commonly on hooks.slack.com). 
Triggered when: you enable Slack notifications and an event sends a message, or you send a test from settings. 
Terms of Service: https://slack.com/terms-of-service 
Privacy Policy: https://slack.com/trust/privacy/privacy-policy
OpenStreetMap Nominatim (geocoding) 
Used for: turning your local business address into latitude and longitude for Local SEO / schema fields. 
Data sent: the address text you enter (request is made from your browser to Nominatim). 
Triggered when: you use the “lookup coordinates from address” control in Meyvora SEO settings. 
Terms of Service / usage policy: https://operations.osmfoundation.org/policies/nominatim/ 
Privacy Policy: https://wiki.openstreetmap.org/wiki/Privacy_policy
User-specified URLs (HTTP requests) 
Used for: loading a competitor page for analysis, checking whether outbound links respond, and similar tools. 
Data sent: standard HTTP requests only to URLs you enter or that appear in your content (for example competitor pages or link targets). No fixed third-party vendor is used for these requests beyond the site you target. 
Triggered when: you use competitor analysis, the link checker, or related features against those URLs. 
Terms of Service: varies by each destination website. 
Privacy Policy: varies by each destination website.
Visitors’ browsers may also load Google Analytics 4 / gtag.js from Google when you enable GA4 measurement ID output in settings; see Google’s terms and privacy policy linked above.
Core SEO features (meta tags, sitemap generation, redirects, schema, on-server analysis without APIs) run on your WordPress installation without contacting these services unless you enable the relevant options.

Meyvora SEO – Smart SEO Toolkit

Smart SEO toolkit for titles, meta, sitemaps, redirects, schema, Open Graph, and page builder integrations.

Webbjocke

<h4>A WordPress sitemap plugin</h4>
Simple Wp Sitemap is a sitemap plugin that generates both an xml and an html sitemap to your site dynamically. These two are updated automatically everytime someone’s visiting them. Which means they’re always up to date and that you only have to install and activate the plugin once, and it will just work for you without you ever having to worry.
Reason the sitemaps are generated dynamically instead of being created as actual files as they were in the beginning, is because it’s much faster and more solid. No problems with having to access, create and delete files, instead they’re just presented when needed to. It’s now suddenly as lightweight, simple and fast as one can expect!
Also supports the option to add pages to the sitemaps that aren’t part of your original WordPress site. For instance if you create a little html file and upload to your server and want it to be included in them, it’s easily done. You can also block pages that you don’t want to be included, and much more.
<h4>What it does</h4>
So what the plugin actually does is making one xml sitemap and one html sitemap available directly on your site. These aren’t actually real files that can be found in a folder or anything, instead they get generated when visited and can be found at like yourpage.com/sitemap.xml and yourpage.com/sitemap.html.
And yes, of course the sitemaps are mobile friendly. They also work well with caching plugins 🙂
<h4>Multisite and multilanguage compatible</h4>
The sitemaps are multisite and multilanguage compatible. Every site gets their own sitemap, and all multilanguage urls are included in them!

Simple Wp Sitemap

This is my favorite XML sitemap plugin. It's very straightforward to use, and simple in design and execution, but it gets the job done and doesn't blast you with credits or advertising while it does so. 

The developer is very good about responding to support threads, and to date is one of the few developers of XML sitemap plugins that has kept pace with the current version(s) of WordPress.

Most XML sitemap plugins require that you enter a comma-separated string of post IDs in order to exclude pages and posts from the sitemap. This plugin takes a different approach, and uses the actual URLs. While there may be a problem with that approach if one changes permalink structure, it's much easier to implement than using the post IDs. 

The only thing that keeps me from giving this plugin five stars is possibly not due to this plugin at all: I have to disable caching of the sitemap.xml file in WP Super Cache, or the output of sitemap.xml is invalid and doesn't display correctly in a browser. It would be nice to be able to cache the sitemap.xml file on larger sites. I've only found one other XML sitemap plugin that didn't conflict with WP Super Cache in the same way; most of them do.

Love It!

An easy sitemap plugin that adds both an xml and an html sitemap to your site, which updates and maintains themselves so you don't have to!

Meyvora SEO – Smart SEO Toolkit vs Simple Wp Sitemap