{"id":407135,"date":"2026-11-21T09:35:22","date_gmt":"2026-11-21T09:35:22","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/clearyvo-database-cleanup-action-scheduler-autoload-orphaned-data\/"},"modified":"2026-11-21T09:35:00","modified_gmt":"2026-11-21T09:35:00","slug":"clearyvo-database-cleanup","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/clearyvo-database-cleanup\/","author":23590642,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"0.8.6","stable_tag":"0.8.6","tested":"7.1.5","requires":"6.2","requires_php":"7.4","requires_plugins":null,"header_name":"Clearyvo Database Cleanup \u2013 Optimize Database, Autoload & Orphaned Data","header_author":"Clearyvo","header_description":"Clean up and optimize the WordPress database: Action Scheduler tables, autoloaded options, orphaned meta, revisions and leftovers of removed plugins, each named by the plugin that left it. Free, no limits.","last_updated":"2026-11-21 09:35:00","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"https:\/\/clearyvo.com\/","rating":0,"author_block_rating":0,"active_installs":0,"downloads":24,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"0.8.6":{"tag":"0.8.6","author":"kishollo001","date":"2026-11-21 09:35:00","revision":3815051}},"upgrade_notice":{"0.8.6":"<p>Fixes the daily background-task cleanup after reactivation. Settings and data are unchanged.<\/p>","0.8.5":"<p>New plugin name. Settings and data are unchanged.<\/p>","0.8.4":"<p>Shared Clearyvo framework 3.7.4. Settings and data are unchanged.<\/p>","0.8.3":"<p>Shared Clearyvo framework 3.7.3. Settings and data are unchanged.<\/p>","0.8.2":"<p>Small text change on the results page.<\/p>","0.8.1":"<p>Shared Clearyvo framework 3.7.1 (security hardening of the shared menu). Settings and data are unchanged.<\/p>","0.8.0":"<p>Safer leftover detection (add-ons and must-use plugins are recognised, nothing pre-ticked) and safer term relationship cleanup. Recommended update.<\/p>","0.7.1":"<p>Unified Clearyvo interface and Export CSV. The scan, the cleanup and all stored data are unchanged.<\/p>","0.6.3":"<p>Framework update: when several Clearyvo plugins contain this checker, only the newest copy runs. Grouped Site Toolkit menu. Settings and results are unchanged.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3815051,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3815051,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3815051,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3815051,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.8.6"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Database cleanup overview: what is safe to remove, what needs review, autoloaded options and plugins that left data behind.","2":"Clutter and orphans \u2013 expired transients, orphaned meta, spam, revisions \u2013 with safe items pre-ticked and cleaned in one click.","3":"Leftovers of removed plugins and the largest autoloaded options, with the plugin that owns each one."}},"plugin_section":[],"plugin_tags":[225911,1328,4655,17806,9568],"plugin_category":[],"plugin_contributors":[290083],"plugin_business_model":[],"class_list":["post-407135","plugin","type-plugin","status-publish","hentry","plugin_tags-action-scheduler","plugin_tags-autoload","plugin_tags-clean-database","plugin_tags-database-cleanup","plugin_tags-wp_options","plugin_contributors-kishollo001","plugin_committers-kishollo001"],"banners":{"banner":"https:\/\/ps.w.org\/clearyvo-database-cleanup\/assets\/banner-772x250.png?rev=3815051","banner_2x":"https:\/\/ps.w.org\/clearyvo-database-cleanup\/assets\/banner-1544x500.png?rev=3815051","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/clearyvo-database-cleanup\/assets\/icon-128x128.png?rev=3815051","icon_2x":"https:\/\/ps.w.org\/clearyvo-database-cleanup\/assets\/icon-256x256.png?rev=3815051","generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p><strong>Clearyvo Database Cleanup cleans up your WordPress database safely and shows which plugin left each piece of junk behind.<\/strong><\/p>\n\n<p>A WordPress database grows with every plugin you try. Uninstalled plugins leave their settings in wp_options, some of them autoload on every page view, WooCommerce fills the Action Scheduler tables (actionscheduler_actions, actionscheduler_logs) with hundreds of thousands of finished tasks, and revisions, orphaned post meta and expired transients pile up. A large database makes backups slower, and large autoloaded options slow down every page.<\/p>\n\n<p>Clearyvo Database Cleanup is for site owners, WooCommerce shops and agencies who want a clean database without guessing which rows are safe to delete. It scans the database, names the plugin or theme behind each item, and removes only what you tick. Everything is free: no limits, no account, no locked features.<\/p>\n\n<h4>What it checks<\/h4>\n\n<ul>\n<li><strong>Leftovers of removed plugins and themes<\/strong> \u2013 options grouped by the plugin that created them, with size.<\/li>\n<li><strong>Autoload bloat<\/strong> \u2013 the largest options that load on every page view, with their owner and status (active, inactive, not installed). WordPress Site Health warns above 800 KB.<\/li>\n<li><strong>Orphaned data<\/strong> \u2013 post, comment, term and user meta whose parent no longer exists; term relationships pointing to deleted posts.<\/li>\n<li><strong>Background tasks (Action Scheduler)<\/strong> \u2013 WooCommerce and many other plugins queue their work in the actionscheduler tables, which often grow to hundreds of thousands of rows. Remove finished, canceled and failed tasks older than 7 days with their log lines, and orphaned logs. See which hooks create the most tasks, and whether the queue is running at all (tasks more than an hour late usually mean WP-Cron does not run). Optional automatic daily cleanup.<\/li>\n<li><strong>Clutter<\/strong> \u2013 post revisions, old auto-drafts, spam and trashed comments, trashed posts, expired transients, oEmbed caches, duplicate post meta.<\/li>\n<li><strong>Tables<\/strong> \u2013 every table of the site with owner, approximate rows, size and overhead.<\/li>\n<li><strong>Settings check<\/strong> \u2013 revision limit and trash period.<\/li>\n<li><strong>Database score<\/strong> \u2013 a Site health score from the space that is safe to clean, autoload size and the number of leftover plugins.<\/li>\n<\/ul>\n\n<h4>How cleaning works<\/h4>\n\n<ul>\n<li>Scanning only reads the database.<\/li>\n<li>Safe items are pre-ticked; items that remove history or trash contents are left for you to decide.<\/li>\n<li>Posts, revisions and comments are deleted through WordPress core functions, so other plugins are notified and caches stay consistent.<\/li>\n<li>Cleanup runs in small batches, so it does not time out on large sites.<\/li>\n<li>For autoload, the plugin only turns autoload off; the value itself is kept.<\/li>\n<li>Core options are never touched.<\/li>\n<li>Dropping tables is not offered, because a wrong guess cannot be undone.<\/li>\n<\/ul>\n\n<h4>Why Database Cleanup?<\/h4>\n\n<ul>\n<li><strong>It tells you whose junk it is<\/strong> \u2013 every option and table is attributed to a plugin or theme, with its status, so you remove leftovers of plugins you deleted and leave the rest alone.<\/li>\n<li><strong>Action Scheduler cleanup included, free<\/strong> \u2013 the tables that make many WooCommerce databases huge, with an optional daily cleanup.<\/li>\n<li><strong>Careful by default<\/strong> \u2013 read-only scan, nothing unknown pre-ticked, core options excluded, no table drops.<\/li>\n<li><strong>Works on shared hosting<\/strong> \u2013 small batches, no time-limit errors.<\/li>\n<\/ul>\n\n<h4>Free and Pro<\/h4>\n\n<p>Everything in Database Cleanup is free, with no limits. Clearyvo Pro, the all-in-one plugin of the family, contains this checker too; Database Cleanup has no Pro-only features.<\/p>\n\n<h4>For AI assistants and automation<\/h4>\n\n<p>On WordPress 6.9 and newer the results are available as read-only abilities (WordPress Abilities API): <code>clearyvo\/database-cleanup-summary<\/code>, <code>clearyvo\/database-cleanup-background-tasks<\/code> and <code>clearyvo\/site-health<\/code>. With the MCP Adapter plugin, an AI assistant such as Claude or ChatGPT can read them. Nothing can be deleted that way, and only administrators can use them.<\/p>\n\n<h4>Part of the Clearyvo family<\/h4>\n\n<p>Focused plugins that each check one part of your site and share one Site Toolkit menu with a Site health score: media cleanup, disk space, backups, broken links, SEO, speed and more. The free Site Toolkit plugin is the dashboard: one Site health score and one-click install of every checker. Clearyvo Pro contains every checker; when it is installed, this plugin's settings and results are shared with it. More at <a href=\"https:\/\/wp-sitechecker.com\/\">wp-sitechecker.com<\/a>.<\/p>\n\n<h4>External services<\/h4>\n\n<p>None. The scan and the cleanup run on your own server and database; nothing is sent anywhere.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install and activate the plugin.<\/li>\n<li>Open Database Cleanup in the admin menu (under Site Toolkit when other Clearyvo plugins are installed).<\/li>\n<li>Click \"Scan database\", review the results, make a backup, then click \"Clean selected\".<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"how%20do%20i%20clean%20up%20and%20optimize%20the%20wordpress%20database%3F\"><h3>How do I clean up and optimize the WordPress database?<\/h3><\/dt>\n<dd><p>Open Database Cleanup and click \"Scan database\". The scan only reads. Make a database backup, check the list (safe items are pre-ticked), then click \"Clean selected\". Only rows you tick are changed and core options are excluded. The work runs in small batches, so it finishes on shared hosting too.<\/p><\/dd>\n<dt id=\"how%20do%20i%20reduce%20autoloaded%20options%20when%20wp_options%20is%20too%20large%3F\"><h3>How do I reduce autoloaded options when wp_options is too large?<\/h3><\/dt>\n<dd><p>The scan lists the largest autoloaded options with the plugin that owns them, and whether that plugin is still installed. For options of removed plugins, delete them under \"Leftovers\". For others, you can turn autoload off: the value stays, it is just no longer loaded on every page view. WordPress Site Health warns when autoloaded options exceed 800 KB.<\/p><\/dd>\n<dt id=\"how%20do%20i%20clean%20the%20action%20scheduler%20tables%20%28actionscheduler_actions%2C%20actionscheduler_logs%29%3F\"><h3>How do I clean the Action Scheduler tables (actionscheduler_actions, actionscheduler_logs)?<\/h3><\/dt>\n<dd><p>Run a scan. If the site has Action Scheduler (WooCommerce, WP Mail SMTP, Rank Math and many others include it), the scan lists finished, canceled and failed tasks older than 7 days and orphaned log lines. Finished and canceled tasks are pre-ticked; failed ones are left for you, because their log explains what went wrong. Pending and running tasks are never touched. To keep the tables small, switch on \"Clean background tasks automatically every day\" in Settings.<\/p><\/dd>\n<dt id=\"why%20are%20there%20thousands%20of%20pending%20background%20tasks%3F\"><h3>Why are there thousands of pending background tasks?<\/h3><\/dt>\n<dd><p>If tasks are more than an hour late, the queue is not running. Usually WP-Cron does not fire: the site has little traffic, or DISABLE_WP_CRON is set without a server cron job calling wp-cron.php. The scan shows this in the Settings check.<\/p><\/dd>\n<dt id=\"how%20do%20i%20remove%20leftover%20data%20from%20deleted%20plugins%3F\"><h3>How do I remove leftover data from deleted plugins?<\/h3><\/dt>\n<dd><p>Look at \"Leftovers\": options of plugins and themes that are no longer installed, grouped by plugin, with their size. They are not pre-ticked: the owner is judged by the option names, so tick a plugin only when you are sure you removed it for good. If you reinstall it later, it starts with default settings. Tables of removed plugins are listed under Tables with their owner, but they are never dropped by this plugin.<\/p><\/dd>\n<dt id=\"how%20does%20it%20know%20which%20plugin%20left%20an%20option%20behind%3F\"><h3>How does it know which plugin left an option behind?<\/h3><\/dt>\n<dd><p>It compares option and table names with the prefixes used by installed plugins and themes, and with a built-in list of well-known plugins. Options of themes are matched exactly (theme_mods_). Must-use plugins and drop-ins count as installed, and options that may belong to an installed add-on of the same family (for example Jetpack Boost for Jetpack) are not called leftovers. Anything it cannot attribute is shown as \"Unknown\". Nothing in this list is pre-ticked.<\/p><\/dd>\n<dt id=\"does%20it%20optimize%20database%20tables%20%28optimize%20table%29%3F\"><h3>Does it optimize database tables (OPTIMIZE TABLE)?<\/h3><\/dt>\n<dd><p>No. The Tables view shows every table with its size and overhead, but the plugin does not run OPTIMIZE TABLE itself. It optimizes the database by removing junk rows and by turning off autoload for large options, which is what makes a real difference to backups and page loads.<\/p><\/dd>\n<dt id=\"will%20it%20make%20my%20site%20faster%3F\"><h3>Will it make my site faster?<\/h3><\/dt>\n<dd><p>Smaller autoloaded options speed up every page view, because WordPress loads them on each request. Removing old rows mostly makes the database and its backups smaller and faster to work with; the effect on page speed depends on the site.<\/p><\/dd>\n<dt id=\"is%20it%20really%20free%3F%20does%20it%20work%20on%20multisite%3F\"><h3>Is it really free? Does it work on multisite?<\/h3><\/dt>\n<dd><p>Yes, every feature is free, including the Action Scheduler cleanup and the automatic daily cleanup, with no usage limit and no account. On multisite it scans the current site's tables; orphaned user meta is skipped there because users are shared across the network.<\/p><\/dd>\n<dt id=\"what%20is%20the%20%2Fwp-json%2Fclearyvo%2Fv1%2Fapp%2F%20address%3F\"><h3>What is the \/wp-json\/clearyvo\/v1\/app\/ address?<\/h3><\/dt>\n<dd><p>A read-only REST route for the Clearyvo Site Inspector Mac app. It shows the Site health score of the Clearyvo plugins to a signed-in administrator (for example with a WordPress Application Password) and changes nothing. It sends nothing anywhere: the app asks, the site answers.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>0.8.6<\/h4>\n\n<ul>\n<li>Fixed: the daily background-task cleanup is scheduled again after the plugin is deactivated and reactivated (it showed as on but did not run).<\/li>\n<li>Fixed: \"Last run\" counts the removed log lines too.<\/li>\n<li>Fixed: switching autoload off accepts only options shown on the results page; this plugin's own settings are no longer listed.<\/li>\n<li>Faster duplicate post meta cleanup when post IDs have large gaps.<\/li>\n<li>Uninstall also removes the resume point of an interrupted duplicate cleanup.<\/li>\n<li>Shared Clearyvo framework 3.7.5: CSV export without file functions, sanitised query names in filter links, every assembled block printed through wp_kses(), the \"moved into the Clearyvo menu\" notice only on the Plugins screen and the Clearyvo page.<\/li>\n<\/ul>\n\n<h4>0.8.5<\/h4>\n\n<ul>\n<li>Plugin name: \"Clearyvo Database Cleanup \u2013 Optimize Database, Autoload &amp; Orphaned Data\".<\/li>\n<\/ul>\n\n<h4>0.8.4<\/h4>\n\n<ul>\n<li>Plugin name without the name of another project.<\/li>\n<li>Shared Clearyvo framework 3.7.4: the \"moved into the Clearyvo menu\" notice shows only on the Dashboard, the Plugins screen and the Clearyvo page; the redirect of old page addresses passes on only sanitised query names; one unneeded core include removed.<\/li>\n<li>Every PHP file stops when it is loaded outside WordPress.<\/li>\n<\/ul>\n\n<h4>0.8.3<\/h4>\n\n<ul>\n<li>Shared Clearyvo framework 3.7.3: the pointers to other Clearyvo plugins (\"Get it\", \"Install\", \"More from Clearyvo\") only name plugins that are already in the WordPress.org plugin directory.<\/li>\n<\/ul>\n\n<h4>0.8.2<\/h4>\n\n<ul>\n<li>The backup warning above the results no longer links to another plugin.<\/li>\n<\/ul>\n\n<h4>0.8.1<\/h4>\n\n<ul>\n<li>Shared Clearyvo framework 3.7.1, the same as in the other Clearyvo plugins: the plugin installer of the shared menu installs only packages from WordPress.org and checks permissions before reading the request; \"Hide for 30 days\" and the review prompt check the nonce and permissions first; uninstall also removes the \"Hide for 30 days\" user setting and the cached WordPress.org data of the shared menu.<\/li>\n<\/ul>\n\n<h4>0.8.0<\/h4>\n\n<ul>\n<li>Leftovers: must-use plugins and drop-ins count as installed; options that an installed add-on of the same plugin family may use (Jetpack Boost, Secure Custom Fields, Event Tickets, BuddyBoss \u2026) are no longer called leftovers. Leftovers are never pre-ticked and count as \"to review\", not as safe.<\/li>\n<li>Orphaned term relationships: only taxonomies of posts are checked, so user and group taxonomies are never touched.<\/li>\n<li>Autoload: only options listed by the scan can be changed.<\/li>\n<li>Duplicate post meta is cleaned in post ID ranges, so large sites do not time out.<\/li>\n<li>Shared Clearyvo framework 3.6.2.<\/li>\n<\/ul>\n\n<h4>0.7.1<\/h4>\n\n<ul>\n<li>Security: all database queries are fully prepared, including the Action Scheduler cleanup.<\/li>\n<li>The shared Clearyvo framework loads WordPress admin include files only when their functions are missing.<\/li>\n<\/ul>\n\n<h4>0.7.0<\/h4>\n\n<ul>\n<li>Unified Clearyvo interface: the shared Clearyvo layout of every checker, with Overview and Settings views. Summary cards (Score, database size, safe to remove, needs review, autoloaded options, plugins that left options) also show the last scan on later visits; one \"Scan database\" button with a progress bar while the scan runs; results as tables with Status pills; a \"How it works\" card.<\/li>\n<li>New: Export CSV of the tables, the autoloaded options and the leftovers; a filter for the tables by owner status. The daily background-task cleanup moved to Settings (with the CSV separator).<\/li>\n<li>Plugins screen: the link is called \"Open\".<\/li>\n<li>Unchanged: the scan, the cleanup and all stored data.<\/li>\n<li>Shared Clearyvo framework 3.3.0: number columns line up, code names such as hooks and file names no longer break letter by letter on phones and long filter choices stay compact.<\/li>\n<\/ul>\n\n<h4>0.6.3<\/h4>\n\n<ul>\n<li>Shared Clearyvo framework 3.2.0: when several installed Clearyvo plugins contain this checker (this plugin, Site Toolkit), only the newest copy runs; an older plugin that keeps its own copy is named in an \"Update\" notice.<\/li>\n<li>Site Toolkit menu: one entry per topic, the checkers of a topic as tabs. Site health shows a \"Fix these first\" list.<\/li>\n<li>Uninstall keeps the data while another installed plugin still uses it, and cleans every site of a multisite network.<\/li>\n<li>The interface stays English with every combination of Clearyvo plugins.<\/li>\n<\/ul>\n\n<h4>0.6.2<\/h4>\n\n<ul>\n<li>Shared Clearyvo framework 2.5.0: built on 2.3.2 (the order of the SEO group in the menu), with the abilities of 2.4.0, and the new Cron Checker and Permalink Checker in the family list.<\/li>\n<li>The new Clearyvo Cron Checker and Permalink Checker are recognised as part of the family (their settings are not shown as leftovers).<\/li>\n<\/ul>\n\n<h4>0.6.1<\/h4>\n\n<ul>\n<li>Readme: clearer description of what the plugin cleans, and answers to common questions about database cleanup, autoload and Action Scheduler.<\/li>\n<\/ul>\n\n<h4>0.6.0<\/h4>\n\n<ul>\n<li>New: Background tasks (Action Scheduler). Removes finished, canceled and failed tasks older than 7 days together with their log lines, and orphaned log lines, in batches. Pending and running tasks are never touched. Shows tasks by status, the hooks that create the most tasks, and whether the queue is late or stuck. Free, no limits.<\/li>\n<li>New: optional automatic daily cleanup of finished and canceled background tasks (failed ones are kept for review).<\/li>\n<li>New: oEmbed caches in post meta, and duplicate post meta (same post, key and exact value; one copy stays). Duplicates are compared byte for byte, so values that differ only in letter case are kept.<\/li>\n<li>New: read-only abilities for the WordPress Abilities API (WordPress 6.9+): clearyvo\/database-cleanup-summary and clearyvo\/database-cleanup-background-tasks. AI assistants can read the results through the MCP Adapter; nothing can be deleted that way.<\/li>\n<li>Shared Clearyvo framework 2.4.0: the \"clearyvo\" ability category and clearyvo\/site-health.<\/li>\n<li>Fix: the version shown inside the plugin matches the plugin version again (it showed 0.5.4).<\/li>\n<\/ul>\n\n<h4>0.5.5<\/h4>\n\n<ul>\n<li>Shared Clearyvo framework 2.3.1: the SEO checker is listed as Clearyvo SEO (formerly Image Alt &amp; SEO) everywhere, whichever Clearyvo plugin loads the framework.<\/li>\n<\/ul>\n\n<h4>0.5.4<\/h4>\n\n<ul>\n<li>Database: every query goes through $wpdb-&gt;prepare(), with %i placeholders for table names.<\/li>\n<\/ul>\n\n<h4>0.5.3<\/h4>\n\n<ul>\n<li>New icons: one design for the whole Clearyvo family, with a colour per group of checkers.<\/li>\n<\/ul>\n\n<h4>0.5.2<\/h4>\n\n<ul>\n<li>The other checkers in the shared menu have their new names (SSL Checker, Security Checker, Indexing Checker and the rest).<\/li>\n<\/ul>\n\n<h4>0.5.1<\/h4>\n\n<ul>\n<li>The plugin links point to wp-sitechecker.com again, until the site has moved to clearyvo.com.<\/li>\n<\/ul>\n\n<h4>0.5.0<\/h4>\n\n<ul>\n<li>New: read-only connection for the Clearyvo Site Inspector Mac app (Site health as data, for administrators with an Application Password).<\/li>\n<\/ul>\n\n<h4>0.4.1<\/h4>\n\n<ul>\n<li>Links to the new home of the Clearyvo WordPress plugins: clearyvo.com\/wordpress.<\/li>\n<\/ul>\n\n<h4>0.4.0<\/h4>\n\n<ul>\n<li>First release under the Clearyvo name (folder and text domain: clearyvo-database-cleanup). Settings and results of the earlier versions are kept; activating this plugin switches the earlier copy off.<\/li>\n<\/ul>","raw_excerpt":"Clean up and optimize the WordPress database: Action Scheduler tables, autoloaded options, orphaned meta, revisions and plugin leftovers.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/407135","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=407135"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/kishollo001"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=407135"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=407135"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=407135"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=407135"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=407135"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=407135"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}