Title: Launchmind Blog Author: launchmind Published: December 28, 2025 Last modified: October 8, 2026 --- Search plugins ![](https://ps.w.org/launchmind-blog/assets/banner-772x250.png?rev=3497445) ![](https://ps.w.org/launchmind-blog/assets/icon-256x256.png?rev=3497313) # Launchmind Blog By [launchmind](https://profiles.wordpress.org/launchmind/) [Download](https://downloads.wordpress.org/plugin/launchmind-blog.6.4.0.zip) * [Details](https://wol.wordpress.org/plugins/launchmind-blog/#description) * [Reviews](https://wol.wordpress.org/plugins/launchmind-blog/#reviews) * [Installation](https://wol.wordpress.org/plugins/launchmind-blog/#installation) * [Development](https://wol.wordpress.org/plugins/launchmind-blog/#developers) [Support](https://wordpress.org/support/plugin/launchmind-blog/) ## Description Display AI-powered Launchmind blog content on your WordPress site. ### Testing **For WordPress.org Reviewers:** A demo API key is available for testing purposes: ``` lm_test_demo1234567890 ``` This key provides access to 6 sample blog articles for testing the plugin functionality. **Test the connection:** 1. Install and activate the plugin 2. Go to **Launchmind** in the WordPress admin sidebar 3. Click the **Settings** tab 4. Enter the demo API key: `lm_test_demo1234567890` 5. Click **Save Settings** 6. Click **Test Connection** – should show “Connection successful” 7. Go to the **Articles** tab to see 6 sample posts 8. Add the Gutenberg block (`Launchmind Blog`) or use shortcode `[launchmind_blog]` on any page **Sample articles included:** * 10 Tips to Boost Your E-commerce Conversion Rate * The Ultimate Guide to SEO for Online Stores * How to Create a Winning Product Description * Email Marketing Strategies That Actually Work * Social Media Marketing for Small Businesses * Customer Retention: How to Keep Customers Coming Back **Getting your own API key:** Sign up at [launchmind.io](https://launchmind.io) to get your personal API key for production use. ### Privacy Policy This plugin connects to external Launchmind.io servers to fetch blog content. By using this plugin, you agree to Launchmind’s [Terms of Service](https://launchmind.io/terms) and [Privacy Policy](https://launchmind.io/privacy). **Data transmitted:** * Your Launchmind API key (for authentication) * Content requests (post slugs, language preferences) * A daily status report: plugin, WordPress and PHP version, article count, rendering mode, and (since 6.0) whether Werken bij is active and how many positions are open **Data NOT transmitted:** * Personal data of your WordPress site visitors * WordPress user information * Any other site data All API communication uses HTTPS encryption. **Deactivating and uninstalling:** Your content is yours and stays in your own database. Deactivating or uninstalling the plugin never deletes articles, their images, the blog page, the careers page, the stories from your people or the position pages. Uninstalling only removes the plugin’s own settings, scheduled tasks and caches. * The careers page is regular page content and keeps rendering in your theme without the plugin. Links to the position pages and to stories need the plugin, because those pages use the plugin’s post types. * On deactivation, open positions are set to draft (marked as closed by Launchmind, so reactivating publishes them again) and the list of positions on the careers page is replaced once by a link to your own application page. * JobPosting structured data is added by the plugin while it is active. Without the plugin there is no JobPosting data. ## Screenshots [⌊Modern admin dashboard with article overview⌉⌊Modern admin dashboard with article overview⌉[ Modern admin dashboard with article overview [⌊Gutenberg blog list block in the editor⌉⌊Gutenberg blog list block in the editor⌉[ Gutenberg blog list block in the editor [⌊Single post block displaying article content⌉⌊Single post block displaying article content⌉[ Single post block displaying article content ## Blocks This plugin provides 2 blocks. * Launchmind Blog * Launchmind Single Post ## Installation 1. Upload the plugin to `/wp-content/plugins/launchmind-blog`. 2. Activate the plugin through the Plugins menu in WordPress. 3. Navigate to the Launchmind menu item (left sidebar) and enter your API key. 4. Add a Gutenberg block (`Launchmind Blog`) or use the shortcode `[launchmind_blog]` on any page. ## FAQ ### Where do I find my API key? Log in to your [Launchmind Dashboard](https://launchmind.io/backlinks/dashboard) and navigate to the “Webshop Plugins” tab. Your API key is displayed in the green box. ### Can I use shortcodes instead of Gutenberg blocks? Yes! Use `[launchmind_blog limit="6" columns="3"]` for a blog list or `[launchmind_post slug="your-post-slug"]` for a single post. ### Does this plugin track my visitors? No. This plugin only communicates with Launchmind servers to fetch your blog content. No personal data from your site visitors is collected or transmitted. ### What data is sent to Launchmind? Only your API key and content requests (such as post slugs and language preferences) are sent to authenticate and retrieve your blog posts. No visitor data is transmitted. ### Is the “Powered by Launchmind” branding required? No. The branding is disabled by default. You can optionally enable it in the block settings or shortcode attributes if you wish to display it. ## Reviews ![](https://secure.gravatar.com/avatar/7ef8a127a2a91ba373437755b9f92edef6ca2b943e2b7e147d0c1b35f3ffcf7b? s=60&d=retro&r=g) ### 󠀁[Fijne WordPress-plugin voor SEO zonder gedoe](https://wordpress.org/support/topic/fijne-wordpress-plugin-voor-seo-zonder-gedoe/)󠁿 [harrie07](https://profiles.wordpress.org/harrie07/) January 6, 2026 Ik gebruik de Launchmind WordPress-plugin nu een tijdje en wat mij vooral aanspreekt is hoe weinig tijd het kost. SEO stond altijd wel op mijn lijstje, maar eerlijk gezegd kwam het er vaak niet van omdat het zoveel handmatig werk is. Na de onboarding was eigenlijk alles duidelijk. De blogs worden automatisch aangemaakt en ik krijg ze per mail ter goedkeuring. Met één klik staat het artikel live op mijn site. Ik hoef niet meer in WordPress te rommelen of teksten te kopiëren en plakken. Wat ik prettig vind, is dat ik wel de controle houd. Als iets niet past, keur ik het gewoon niet goed. De content sluit goed aan bij mijn website en is duidelijk geschreven met zowel Google als AI-tools in gedachten. Voor de prijs die je betaalt is dit een fijne oplossing. Een SEO-specialist of marketeer kost al snel duizenden euro’s per maand, terwijl dit veel werk uit handen neemt voor een fractie daarvan. Voor mij werkt het vooral omdat het consistent doorgaat zonder dat ik er steeds bovenop moet zitten. Al met al een handige plugin als je wel aan SEO wilt doen, maar geen zin hebt in gedoe. ![](https://secure.gravatar.com/avatar/93ca26b8a91e1b017f3f34e6342b88adcef92c5b2c1454220080ebf5f25cbb9a? s=60&d=retro&r=g) ### 󠀁[Already getting traffic](https://wordpress.org/support/topic/already-getting-traffic/)󠁿 [voortkasumov](https://profiles.wordpress.org/voortkasumov/) December 29, 2025 After just 3 weeks we are already getting visitors coming from various AI models. Can not wait to see the results snowball even more. Next best thing. ![](https://secure.gravatar.com/avatar/8e11de7a9fa47ba255b598176ad12702f2168c703c3e2f9feb7d866d52554b40? s=60&d=retro&r=g) ### 󠀁[Perfect for AI engines and SEO](https://wordpress.org/support/topic/perfect-for-ai-engines-and-seo/)󠁿 [cormanders](https://profiles.wordpress.org/cormanders/) December 28, 2025 Does exactly what it promises LaunchMind automatically creates and publishes GEO and SEO optimized blogs that help my website appear in AI engines and AI answers. It saves a lot of time and already brings in more qualified traffic. Highly recommended. [ Read all 3 reviews ](https://wordpress.org/support/plugin/launchmind-blog/reviews/) ## Contributors & Developers “Launchmind Blog” is open source software. The following people have contributed to this plugin. Contributors * [ launchmind ](https://profiles.wordpress.org/launchmind/) [Translate “Launchmind Blog” into your language.](https://translate.wordpress.org/projects/wp-plugins/launchmind-blog) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/launchmind-blog/), check out the [SVN repository](https://plugins.svn.wordpress.org/launchmind-blog/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/launchmind-blog/) by [RSS](https://plugins.trac.wordpress.org/log/launchmind-blog/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 6.4.0 * **Your careers video on the page.** Add a YouTube or Vimeo link in Launchmind and it appears right below the top of your careers page, with your accent colour on the play button. * **Fast and privacy friendly.** Visitors first see a still image. The player only loads when someone presses play, from youtube-nocookie.com or Vimeo with Do Not Track, so the page stays light and no video cookies are set before that click. Without JavaScript the image links to the video. * **Found in Google.** For Vimeo videos the page gets VideoObject structured data, so Google can show the video with your careers page. #### 6.3.3 * **Colleague quotes take turns.** The quote band now shows every checked quote from your colleagues, one after the other, with dots to pick one yourself. It pauses when a visitor hovers over it and does not move for visitors who prefer less motion. * **A small team overview.** Below the stories, your careers page shows the people a new colleague will work with: photo (only with consent) or initials, name and role. * **Icons that match your benefits.** Each point under “What we offer” gets a fitting icon (growth, flexibility, team, pay and more), in your accent colour. * **Photos stay sharp.** Photos of colleagues are never shown larger than their real size, and the quote band uses a round portrait instead of a large, stretched photo. * **Vacancy pages that feel finished.** A link back to all vacancies, facts with icons, check marks in lists, a sticky apply button on phones, and other open positions at the bottom. * **Smooth on scroll.** Sections fade in as visitors scroll and the stories carousel moves by itself until someone touches it. * **Works with caching plugins.** The careers script is excluded from delay and defer in WP Rocket, LiteSpeed Cache, Autoptimize and SiteGround Optimizer, so the vacancy title no longer slides under a floating header. #### 6.3.2 * **A hero that fills the screen.** With a photo, the top of the careers page now has your text on your brand colour and the photo filling the full height up to the edge of the screen, the way many company sites open. * **Key figures at a glance.** A row with open positions, number of colleagues, year founded and location sits right under the hero. Only what is known is shown. * **Stories as a carousel of portraits.** Colleague stories are large portrait cards (a cut-out team photo on your brand colour, or initials) in a row you can scroll or step through with arrows. * **Careers page lines up with the rest of your site.** Colour bands now keep their content within your site’s content width (read from your Elementor kit or theme. json, or measured from your header), also on themes that stretch full-width sections to the edge of the screen. Nothing sticks to the edge of the screen anymore. * **Highlighted quote is always readable.** The quote has its own layout instead of the theme’s pull quote style, so a theme can no longer put a light box or icon behind white text. * **Sharp photos of colleagues.** Small or cut-out photos (for example from a team page) are shown as a round avatar next to the name; only large, sharp photos get their own panel. * **Consistent headings in cards.** Card headings keep a fixed size, also when the theme uses very large headings. #### 6.3.1 * **Careers stories stay out of your blog.** Stories from your colleagues now live apart from your articles: they no longer appear in your blog overview, archives, search results, RSS or page builder loops, and in WordPress they have their own“ Careers stories” view next to Articles. They still have their own page and show up on your careers page and in your sitemap. * **Stories are always stored on your own site.** In sync mode the plugin now stores the careers stories itself, published, so the careers page and story pages keep working without the Launchmind connection. #### 6.3.0 * **A careers page that looks like your own website.** The careers page now reads your site’s colours and fonts (Elementor kit or theme.json) and builds bold sections from them: a hero in your brand colour, sections with small labels above the headings, text next to photos, a dark band for open positions and a closing band with buttons. Buttons copy the style of a button already on your site, such as the one in your header. * **Your own photos, chosen for you.** Launchmind picks photos from your own website( home, about, team and careers pages) for the hero, the “who we are” section, the culture section and the closing band. Photos in your media library are used directly, with all their sizes. No stock photos, and never an AI portrait of a real colleague. Without suitable photos the page uses colour bands. * **Your careers page shows what your culture is like.** A new section describes in three or four short blocks what it is like to work with you, written from your profile, your website and what your colleagues said in interviews. A block can carry a short quote from a colleague, word for word and with their first name, only from interviews you chose to use. * **Headers that float over the page no longer cover the title.** If your header floats over the top of the page, the careers page and vacancy pages now start below it. The page title of your theme is replaced by the title in the hero, so it is never shown twice. * **Vacancy pages with a proper header.** Each vacancy opens with a header in your brand colour with the title, location and employment type, and the apply button. The text has an apply card next to it that stays in view while reading. * **Fixed:** vacancy summaries no longer glue words together (“doen?Als”) or start with the job title, also for vacancies synced before this version. A company name ending in a period no longer gets a double period (“B.V..”). #### 6.2.0 * **Replace an existing careers page without logging in to WordPress.** If your site already has a careers page at the same address, for example built with Elementor or another page builder, you can now choose in Launchmind to replace it. The plugin then puts your old page aside as a draft (renamed to {address}-oud, nothing is deleted), places the new Launchmind careers page at the same address with the same title, and points your menu items to it. Untick the choice in Launchmind and your old page comes back at its address and in the menu, and the Launchmind page is put aside as a draft. Without this choice nothing changes: an existing page is never touched. * **Or add the careers page next to your current one.** Choose a different address in Launchmind (for example /careers/) and the plugin creates the careers page there, leaves your current page exactly as it is and does not add a second menu item. If the address of an existing Launchmind careers page changes, the page moves to the new address. #### 6.1.0 * **Your careers page now looks like the rest of your website.** The careers page is built from regular WordPress blocks (groups, headings, paragraphs, buttons, pull quotes, images and expandable questions) instead of HTML blocks. Your theme styles them exactly like every other page: your fonts, your headings, your buttons and your content width. On Elementor sites the buttons use the button style of your Elementor kit. The accent colour is taken from your own site (Elementor kit or theme palette) and only falls back to the brand colour from your Launchmind onboarding. * **The careers page tells your story.** Besides the introduction and what people can expect, the page now has a section about who you are, a highlighted quote from a colleague with their photo, stories from your people as cards with photo, name and role, your open positions as cards, frequently asked questions about working with you and a closing invitation with a button to your open positions or open application. All text is written from what you told us and what your colleagues told us, never invented, and is ready right after onboarding. * **Stories from your people get their own header.** Each employee story starts with the photo, name and role of the colleague who tells it and ends with a short invitation to look at your open positions and other stories. Position pages end with the same invitation. * **Photos stay yours.** Photos of colleagues (only shared with their consent) are saved in your own media library, just like article images. * **Existing careers pages are converted once.** A careers page created by 6.0 is converted to the new layout on the next sync, but only if you did not change the Launchmind section yourself. If you did, you get the usual “New content is available” notice and nothing is overwritten. #### 6.0.0 * **New: Werken bij (careers).** If the Werken bij module is active for your site in Launchmind, the plugin now builds your careers section in WordPress itself. It creates a careers page (by default /werken-bij/) with your introduction, what people can expect when they work with you, your open positions and stories from your own people. Every open position becomes a real page in your own database at /werken-bij/vacatures/{position}/, with location, employment type, salary and an “Apply” button. That button goes directly to the application address of your own organisation: applications never pass through Launchmind. Without an active module nothing changes on your site. * **Open positions stay correct on their own.** Positions are synced every hour, checked completely once a day and updated within seconds when something changes in Launchmind. A position that closes or passes its end date is set to draft, never deleted. If you edit a position in WordPress yourself, your version is kept and marked instead of overwritten, just like articles. * **Found by search engines as a job.** Every position page carries JobPosting structured data, so Google can show it in its job results. A closed or expired position loses that data at once. If Rank Math already holds its own JobPosting for a page, the plugin leaves that one in place instead of adding a second. The address in that data is always the position page exactly as your WordPress serves it, so a www or language prefix can never send Google to the wrong page. The JobPosting data is added by the plugin while it is active; without the plugin there is no JobPosting data (and the positions are drafts then, see below). * **The careers page is real content in your own database.** The page is not a shortcode that the plugin fills in on every page view: your introduction, what people can expect, the quotes, the open positions (title, location, employment type and a link to the position page) and the stories are written into the page itself as regular HTML blocks. It reads well without the plugin and without the plugin’s stylesheet, and you can edit it in the block editor, the classic editor or Elementor. After every sync that changes something, the plugin rewrites only the section between its markers (`` and ``); everything you add above or below it is yours and is never touched. * **Your edits always win.** If you change the section between the markers yourself, or remove it, the plugin stops updating it and shows “New content is available” in wp-admin, with an “Accept” button that replaces only that section, and a “ Not now” button. Nothing is overwritten without that click. * **Your existing pages stay yours.** If you already have a careers page, the plugin adopts it and leaves its content exactly as it is. It only adds its section when the page is empty, or at the bottom of the page after you click “Accept”. A page built with a page builder such as Elementor or Divi is never written to; the notice explains how to add the [launchmind_werken_bij] shortcode widget there instead. A menu item is offered once and never put back if you remove it. Polylang and WPML are taken into account, and caching plugins such as WP Rocket are cleared for the careers page after every change. * **Stories from your people are stored on your site in every content mode.** Stories are saved as real posts in your own database, with their images in your media library, also when your blog runs in Live mode. In Live mode they are stored as drafts so your blog overview, page builder loops and sitemap never list an article twice; if you switch to Sync mode they are published automatically. A quote on the careers page links to the story it comes from. * **When Werken bij stops, your content stays.** If the module is switched off in Launchmind (confirmed twice in a row) or you deactivate the plugin, the careers page, the stories and the position pages all stay in your database. Open positions are set to draft, so no outdated job ad stays online, and the list of positions on the careers page is replaced once by a neutral link to your own application page. Reactivating brings everything back. * **New: filter the blog by topic.** [launchmind_blog category=”your-topic”] shows only the articles of one content pillar, in every content mode. [launchmind_vacancies limit=”10″ columns=”2″] shows only the open positions. * **Dashboard:** a new Werken bij section shows whether the module is active, how many positions are open, when the last sync ran, and has a “Sync now” button. * **Fix:** the version number the plugin reports internally now matches the release( it still said 5.14.0 in 5.15.0). #### 5.15.0 * **Your connection details and visitor e-mail addresses no longer appear in your own error log.** If Launchmind writes an error to the log of your own site, for example when the Launchmind API cannot be reached or an image cannot be saved, the technical message that goes with it can contain the connection key of your site or an e-mail address of a visitor. Every Launchmind log entry now removes those before it reaches the error log, whatever caused the message. Nothing changes about what the plugin does, only about what it leaves behind in your log. #### 5.14.0 * **Your blog overview now stays current behind every caching plugin.** A freshly published article always had its own working address right away, but the blog overview and its older pages could sit in the HTML cache of caching plugins such as Flying Press, WP Rocket or LiteSpeed Cache for weeks. Those plugins only clear the pages they know a new post belongs to, and a brand-new post does not belong to any page yet, so the overview kept serving an old copy. After every Launchmind change the plugin now clears the overview, its pagination and your sitemap files itself, whichever caching plugin you use. If your listing lives on a custom page( for example a page builder grid on /blogs/), add its address under Settings, Listing Page Cache Purge. #### 5.13.3 * **Internal hardening of the 5.13.2 address fix.** The rewrite repair now lives in its own module, the second-chance flush after activating the plugin only runs when the first flush did not restore the rules, and a repair that did not succeed no longer marks the rules as correct, so both safety nets stay active. No visible behavior change: article addresses keep working as in 5.13.2. #### 5.13.2 * **Fix: switching the plugin off and on no longer breaks your article addresses.** Activating the plugin flushed WordPress’s rewrite table before the Launchmind post type had been registered, which removed the /blog/{slug}/ rules. Every article stayed in your database, on the blog overview and in the sitemap, but its own address returned a 404 until someone opened Settings, Permalinks and pressed Save. That is not something you should ever have to know. The plugin now registers its post type before that flush, and checks on every page view that the routing rule still exists, repairing it on its own if any action or tool ever removes it again. * **Fix: the daily health report counts your articles again.** It counted a post type that does not exist (a name mix-up with an internal query variable), so every site reported zero articles to Launchmind while the blog was full of them. The dashboards on the Launchmind side now show real numbers. #### 5.13.1 * **Cover images now carry a real alt text.** Every synced featured image used to land in the media library without one, so themes rendered it with an empty alt attribute. The plugin now writes the descriptive alt text Launchmind delivers( or the article title as a fallback) and leaves any alt text you set yourself in the media library untouched. * **Step-by-step articles get HowTo structured data.** When an article contains a numbered list of three or more steps, the plugin adds a HowTo block next to the existing Article, FAQPage and BreadcrumbList markup. * **Author and organization profiles are linked.** The author’s LinkedIn profile and your company’s LinkedIn page and website are now listed as sameAs on the Person and Organization nodes, which is the strongest E-E-A-T signal a search engine can read. * **Your site serves an llms.txt.** AI answer engines look for /llms.txt to learn what a site is about. The plugin now serves one with your organization description and your hub articles (or the 20 newest), unless a physical llms.txt exists or your SEO plugin already provides one. #### 5.13.0 * **Changes now arrive within seconds instead of within an hour.** The plugin used to check for new articles once an hour, so a freshly approved article could sit and wait, and an article you took offline could stay on your site for another hour. Launchmind now notifies your site the moment something is published, updated or taken offline, and the site fetches it straight away. The hourly run stays in place as the safety net. * **Your blog page is set up properly on install.** The plugin created a bare / blog page with nothing else on it: no SEO title, no meta description, no menu item, and nothing at all in Sync mode. It now sets the page up completely, in the language of your site, adds it to your main menu if there is no link to it yet, and fills in the SEO fields of Yoast, Rank Math, SEOPress or The SEO Framework. Existing pages are left exactly as they are. * **Multilingual sites get a blog page per language.** On Polylang and WPML the plugin creates one page for each language that your site speaks and that Launchmind delivers, and links them together so the language switcher works. * **Sync is the new default for fresh installs.** Real WordPress posts in your own database, images in your own media library, and content that keeps working even without a Launchmind connection. That last argument for Live mode, being instantly up to date, is gone now that changes are pushed through. Sites that already made a choice keep it. * **The article count no longer stops at 50.** The dashboard counted how many articles it had fetched rather than how many there are, so every customer with a larger library saw the same number. Paging through the list works properly now too. * **A tidier admin screen.** The Analytics tab is gone: it repeated the counters already at the top and had no figures of its own. Settings has moved to its own menu item next to Dashboard and Articles, so what you look at daily and what you set once are no longer mixed together. #### 5.12.1 * **The readability dot is filled in as well now.** 5.12.0 deliberately left it grey, because the only figure we had was a raw reading-ease score that measures something different from what Yoast shows: it penalises long Dutch compound words while ignoring what actually makes a text readable. Launchmind now runs the same set of checks Yoast does (sentence length, paragraph length, subheadings, sentence beginnings, transition words, passive voice) and reports the share that pass, which is directly comparable to the figure in your editor. #### 5.12.0 * **Tags are now the article’s own keyword, not the whole list.** Every article carried the same ten tags, because the plugin received the keyword set of the entire cluster rather than the keyword this particular article targets. Articles now get their own keyword, which is what a tag is meant to be. * **Q&A articles get a category.** They come from an interview and belong to no content pillar, so they were left without any category at all. They now get their own “Q&A” category. * **The SEO dot in the article list is no longer grey.** Yoast only runs its analysis inside the editor, and a synced article never passes through it. The plugin now fills in the score Launchmind already determined. Note this is Launchmind’s assessment shown in Yoast’s colours; opening the article in the editor makes Yoast calculate its own. The readability dot is deliberately left alone, because we do not measure that reliably enough to colour it. #### 5.11.9 * **The sharing image is now exactly 1200×630 on every article.** That is the size Facebook, LinkedIn, X, WhatsApp and Slack all expect. Previously the plugin could only crop down, so an article whose cover was smaller ended up below the recommended width and networks fell back to a small card. The image is cropped from the centre and saved as a JPEG, which also keeps heavy PNG covers from bloating the preview. #### 5.11.8 * **Fix: the plugin now sets the sharing image tags itself on Yoast sites.** Three earlier attempts to get Yoast to pick the prepared image each failed at a different point in its pipeline, most recently by quietly swapping the address back to the original file. Rather than keep guessing at its internals, the plugin now removes only Yoast’s two image tags and writes them itself. Everything else Yoast does, titles, descriptions, canonicals and schema, is untouched. #### 5.11.7 * **Fix: the sharing image is now its own image, so nothing can override it.** Cropping inside the original image was not enough: Yoast takes the URL, looks up the image it belongs to, and then falls back to the full-size original. The page ended up stating the cropped size above the uncropped file. The prepared sharing image is now stored as an image in its own right, so its full size _is_ the crop and no SEO plugin can reach past it. This also makes it work identically on Rank Math, SEOPress, All in One SEO and on sites with no SEO plugin at all. * Added the `name="image"` tag that LinkedIn asks for in its own Post Inspector, alongside the standard tags. #### 5.11.6 * **Fix: the sharing image really is applied now.** The code added in 5.11.5 ran but changed nothing, because of a faulty check on our side. Verified on a live site: the prepared image was ready and the page still pointed at the original. No re-sync is needed after this update, the change takes effect on the next page view. #### 5.11.5 * **Fix: the sharing image now actually reaches Facebook and LinkedIn.** 5.11.4 prepared a correctly cropped sharing image but never got it onto the page, because recent versions of Yoast decide the sharing image in a way the previous approach could not reach. The plugin now writes it into the SEO plugin’s own field during the sync, where it is also visible to you under the article, and enforces it on the page itself. * **Works without an SEO plugin, and with the other ones.** Yoast, Rank Math, SEOPress and The SEO Framework each get the image in their own field. Sites running no SEO plugin at all, and sites on All in One SEO, get the tag straight from this plugin instead. Whichever setup you are on, the sharing image is the prepared one and its stated size matches the file. #### 5.11.4 * **Fix: articles now have a real sharing image.** Until now the plugin handed the article’s cover image to Facebook and LinkedIn exactly as it was. A cover is not a sharing image: one article’s cover was a tall 1024×1536 portrait, which does not fit the wide card those networks show, and another was a 2.9 MB image whose real size disagreed with what the page claimed. Both are reasons a network quietly falls back to no image at all. The plugin now prepares a proper 1200× 630 sharing image during the sync and hands that over instead, with its true dimensions. Existing articles get one on the next sync, without needing an edit. #### 5.11.3 * **Fix: link previews on Facebook, LinkedIn and WhatsApp.** In sync mode the article is a real WordPress post, so your SEO plugin already publishes a preview image and the plugin published a second one on top of it. The two disagreed about the image size, and scrapers that trust the first one reported no image at all. The plugin now leaves the preview image to your SEO plugin on synced posts. * **Fix: the preview image size is no longer guessed.** The plugin declared every preview image as 1200×630 pixels without ever measuring it. That was wrong for practically every article, which is what made social networks re-fetch or skip the image. The real size is now read from the media library, and when it cannot be determined the plugin says nothing and lets the network measure the file itself. * **Fix: articles are filed under their real author.** Synced articles were owned by the administrator account, so the REST API, oEmbed and the articles list in wp-admin all showed “admin” while the article page itself showed the correct byline. Each writer now gets their own author record. These records have no role and no usable password, so they cannot sign in; they exist only so WordPress knows who wrote the article. To keep everything on the administrator account instead, add `add_filter('launchmind_create_author_users', '__return_false');` to your theme. #### 5.11.2 * **Fix: existing articles now get their category and SEO fields too.** The pillar category and the SEO plugin fields introduced in 5.11.0 were only written when an article’s content had changed, so articles already on your site kept their empty category and empty focus keyphrase and the feature looked broken. Those fields are now kept current on every run, whether the text changed or not. #### 5.11.1 * **Fix: clicking Launchmind opens the dashboard again.** Adding the articles list under the Launchmind menu in 5.11.0 pushed it to the top, and WordPress sends a click on a parent menu to whatever sits first. That made the settings unreachable. Dashboard is back on top, with Articles below it. #### 5.11.0 * **Fix: you can now actually edit a synced article.** Opening one in the WordPress editor was blocked by a permission setting left over from when these articles were not real posts yet. Even an administrator could not edit them. They behave like any other post now. * **New: articles are filed under their content pillar as a category.** Your articles are already grouped into topical clusters on the Launchmind side, but that grouping never reached WordPress, so the category column sat empty. Each article now joins the category for its pillar, which gives you real archive pages and breadcrumbs. A category you assigned yourself is never removed. * **New: your SEO plugin’s fields are filled in.** The focus keyphrase, meta description and SEO title are written to Yoast and Rank Math from what we already know, so you stop seeing a red dot on every article for a field that was simply empty. Anything you filled in by hand is left alone. * **Keyword tag archives are kept out of search results.** The tags on your articles are search terms rather than a real taxonomy, and each article carries most of the same ones, so those archive pages end up nearly identical and compete with your actual articles. Tag archives that contain only Launchmind articles are now marked noindex (links are still followed). Tags you also use on your own posts are untouched, and category archives stay indexable. #### 5.10.0 * **In Sync mode your blog overview now comes from your own database too.** Until now the listing was fetched from Launchmind on every page load, even in Sync mode. That meant the overview could show articles that had not been imported yet (clicking one gave a 404), the links carried a language parameter that no longer did anything, and the overview stopped working if the connection to Launchmind ever went away. Now the listing and the articles come from the same place: yours. That also means your blog overview joins WordPress search, categories and theme loops, which it could not before. * **New: an Articles list in the admin.** In Sync mode your imported articles now appear under Launchmind as a normal WordPress list, with filters, quick edit and bulk actions. So you can set one or a hundred of them to draft whenever you want. The sync respects that: a post you set to draft yourself is flagged and never republished. * **Safety rail on reconciliation.** The sync drafts articles that disappeared on the platform. It will now refuse to do that when a run reports zero articles while your site holds many, because “I saw nothing” is never a good enough reason to unpublish … ## Meta * Version **6.4.0** * Last updated **2 hours ago** * Active installations **Fewer than 10** * WordPress version ** 5.8 or higher ** * Tested up to **6.9.10** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/launchmind-blog/) * Tags * [AI](https://wol.wordpress.org/plugins/tags/ai/)[articles](https://wol.wordpress.org/plugins/tags/articles/) [blog](https://wol.wordpress.org/plugins/tags/blog/)[content](https://wol.wordpress.org/plugins/tags/content/) [seo](https://wol.wordpress.org/plugins/tags/seo/) * [Advanced View](https://wol.wordpress.org/plugins/launchmind-blog/advanced/) ## Ratings 5 out of 5 stars. * [ 3 5-star reviews ](https://wordpress.org/support/plugin/launchmind-blog/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/launchmind-blog/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/launchmind-blog/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/launchmind-blog/reviews/?filter=2) * [ 0 1-star reviews ](https://wordpress.org/support/plugin/launchmind-blog/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/launchmind-blog/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/launchmind-blog/reviews/) ## Contributors * [ launchmind ](https://profiles.wordpress.org/launchmind/) ## Support Issues resolved in last two months: 1 out of 1 [View support forum](https://wordpress.org/support/plugin/launchmind-blog/)