[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f0uWy6oOujKVkO6128jcjK-HONf7x-4cZn7Yt9AS-Igc":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":23,"download_link":24,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":37,"analysis":143,"fingerprints":200},"yopress","YoPress","0.2.2","Jason Stallings","https:\u002F\u002Fprofiles.wordpress.org\u002Foctalmage\u002F","\u003Cp>Instructions:\u003C\u002Fp>\n\u003Cp>Signup for an API key at \u003Ca href=\"http:\u002F\u002Fyoapi.justyo.co\" rel=\"nofollow ugc\">yoapi.justyo.co\u003C\u002Fa>, for “Callback URL” put in your homepage with a trailing slash.\u003C\u002Fp>\n\u003Cp>Put your API key in the YoPress settings and hit save changes.\u003C\u002Fp>\n\u003Cp>Then tell your visitors to Yo your website’s username, or use \u003Ca href=\"http:\u002F\u002Fbutton.justyo.co\" rel=\"nofollow ugc\">button.justyo.co\u003C\u002Fa> to generate a button.\u003C\u002Fp>\n\u003Cp>Now when you publish a new post your visitors will get a Yo with the link!\u003C\u002Fp>\n","Yo your subscribers when you publish a new post!",10,1545,100,1,"2014-11-11T06:50:00.000Z","3.9.40","3.6.0","",[20,21,22],"api","notifications","yo","http:\u002F\u002Fjason.stallin.gs\u002Fyopress","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fyopress.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":25,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},"octalmage",4,50,30,84,"2026-04-04T06:06:18.349Z",[38,60,81,107,126],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":48,"num_ratings":32,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":18,"download_link":59,"security_score":13,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"retrigger-notifications-gravity-forms","Retrigger Notifications Gravity Forms","1.3","wpspin","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpspin\u002F","\u003Cp>\u003Cstrong>Retrigger Notifications Gravity Forms\u003C\u002Fstrong> lets you manually re-send Gravity Forms entry data to external Zapier and Webhook API feeds — directly from the WordPress admin, without resubmitting the form.\u003C\u002Fp>\n\u003Cp>Whether a webhook failed silently, Zapier missed a trigger, or you simply need to push historical entries to a new integration, this plugin has you covered.\u003C\u002Fp>\n\u003Ch3>🔄 What It Does\u003C\u002Fh3>\n\u003Cp>When Gravity Forms sends entry data to Zapier or Webhooks, things don’t always go right. Endpoints go down, APIs timeout, and integrations break. Instead of asking users to resubmit, this plugin lets you \u003Cstrong>retrigger the feed\u003C\u002Fstrong> for any entry — individually or in bulk.\u003C\u002Fp>\n\u003Ch3>✅ Use Cases\u003C\u002Fh3>\n\u003Col>\n\u003Cli>\u003Cstrong>🔁 Resend failed Zapier triggers\u003C\u002Fstrong> — A Zap didn’t fire? Retrigger it from the entry detail page without asking the user to resubmit.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>🌐 Resend failed Webhook deliveries\u003C\u002Fstrong> — Push entry data again to your Webhook endpoint when the first attempt failed or timed out.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>📦 Bulk resend entries to Zapier\u003C\u002Fstrong> — Select multiple entries from the Entries list and resend them all to Zapier feeds in one action.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>📦 Bulk resend entries to Webhooks\u003C\u002Fstrong> — Select multiple entries and push them all to Webhook endpoints at once.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>🐛 Debug API integrations\u003C\u002Fstrong> — Use the built-in test endpoint and GF logging to troubleshoot why data isn’t reaching your external service.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>🔗 Connect a new Zapier integration to old entries\u003C\u002Fstrong> — Set up a new Zap and retrigger historical entries so they flow into the new workflow.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>🔗 Connect a new Webhook to old entries\u003C\u002Fstrong> — Added a new Webhook feed? Push past entries through it without resubmission.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>🛠️ Test Zapier\u002FWebhook setup during development\u003C\u002Fstrong> — Quickly retrigger entries while building and testing your automation pipeline.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>📊 Sync data after downtime\u003C\u002Fstrong> — If your external service was down during form submissions, retrigger all affected entries once it’s back online.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>🔍 Verify data delivery\u003C\u002Fstrong> — Retrigger a single entry and check GF logs to confirm data was sent and received correctly.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>⚙️ Settings & Usage\u003C\u002Fh3>\n\u003Cp>This plugin works seamlessly within the existing Gravity Forms interface — no separate settings page required.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Single Entry Resend:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Go to \u003Cstrong>Forms \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Entries\u003C\u002Fstrong> in your WordPress admin.\u003C\u002Fli>\n\u003Cli>Click on any entry to open the \u003Cstrong>Entry Detail\u003C\u002Fstrong> page.\u003C\u002Fli>\n\u003Cli>In the right sidebar, you’ll see \u003Cstrong>“Resend Zapier Feeds”\u003C\u002Fstrong> and\u002For \u003Cstrong>“Resend Webhook Feeds”\u003C\u002Fstrong> panels.\u003C\u002Fli>\n\u003Cli>Check the feeds you want to retrigger.\u003C\u002Fli>\n\u003Cli>Click the \u003Cstrong>Resend\u003C\u002Fstrong> button. Done!\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Bulk Resend:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Go to \u003Cstrong>Forms \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Entries\u003C\u002Fstrong> and select the entries you want to resend.\u003C\u002Fli>\n\u003Cli>Choose \u003Cstrong>“Resend Zapier Feeds”\u003C\u002Fstrong> or \u003Cstrong>“Resend Webhook Feeds”\u003C\u002Fstrong> from the \u003Cstrong>Bulk Actions\u003C\u002Fstrong> dropdown.\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Apply\u003C\u002Fstrong>. Confirm the action in the popup dialog.\u003C\u002Fli>\n\u003Cli>All selected entries will be resent to the configured feeds.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Debugging:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable \u003Cstrong>Gravity Forms Logging\u003C\u002Fstrong> under Forms \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Logging.\u003C\u002Fli>\n\u003Cli>Use the built-in test endpoint (\u003Ccode>\u002Fwp-json\u002Fgf\u002Fv1\u002Ftest-webhook-api\u003C\u002Fcode>) to verify webhook delivery.\u003C\u002Fli>\n\u003Cli>All retrigger operations are logged to the GF debug log.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>🧩 Works Great With These Plugins\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.gravityforms.com\u002F\" rel=\"nofollow ugc\">Gravity Forms\u003C\u002Fa>\u003C\u002Fstrong> — Required. The form plugin this addon extends.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.gravityforms.com\u002Fadd-ons\u002Fzapier\u002F\" rel=\"nofollow ugc\">Gravity Forms Zapier Add-On\u003C\u002Fa>\u003C\u002Fstrong> — Required for Zapier retrigger features.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.gravityforms.com\u002Fadd-ons\u002Fwebhooks\u002F\" rel=\"nofollow ugc\">Gravity Forms Webhooks Add-On\u003C\u002Fa>\u003C\u002Fstrong> — Required for Webhook retrigger features.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.gravitykit.com\u002Fproducts\u002Fgravityview\u002F\" rel=\"nofollow ugc\">GravityView\u003C\u002Fa>\u003C\u002Fstrong> — Display entries on the frontend; use Retrigger to fix API issues behind the scenes.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fgravitywiser.com\u002F\" rel=\"nofollow ugc\">Gravity Perks\u003C\u002Fa>\u003C\u002Fstrong> — Advanced Gravity Forms snippets and utilities that complement this plugin.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fgravityflow.io\u002F\" rel=\"nofollow ugc\">Gravity Flow\u003C\u002Fa>\u003C\u002Fstrong> — Workflow automation for Gravity Forms; retrigger feeds at any workflow step.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwp-webhooks.com\u002F\" rel=\"nofollow ugc\">WP Webhooks\u003C\u002Fa>\u003C\u002Fstrong> — Extend your webhook capabilities beyond Gravity Forms.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fzapier.com\u002F\" rel=\"nofollow ugc\">Zapier\u003C\u002Fa>\u003C\u002Fstrong> — The automation platform this plugin integrates with for retriggering Zaps.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.make.com\u002F\" rel=\"nofollow ugc\">Make (formerly Integromat)\u003C\u002Fa>\u003C\u002Fstrong> — Use with Gravity Forms Webhooks to push data to Make scenarios.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.gravityforms.com\u002Fadd-ons\u002Fsmtp\u002F\" rel=\"nofollow ugc\">Gravity SMTP\u003C\u002Fa>\u003C\u002Fstrong> — Reliable email delivery alongside your retriggered API feeds.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>📋 Requirements\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>WordPress 4.0 or higher\u003C\u002Fli>\n\u003Cli>Licensed \u003Cstrong>Gravity Forms\u003C\u002Fstrong> plugin (active)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Zapier Add-On\u003C\u002Fstrong> enabled (for Zapier features)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Webhooks Add-On\u003C\u002Fstrong> enabled (for Webhook features)\u003C\u002Fli>\n\u003C\u002Ful>\n","Resend Gravity Forms entry data to Zapier and Webhook feeds with one click -- no need to resubmit the form.",1000,6180,90,"2026-02-12T20:35:00.000Z","6.9.4","4.0.0","7.0",[54,55,56,57,58],"gravity-forms","gravity-forms-addon","resend-notifications","webhooks","zapier","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fretrigger-notifications-gravity-forms.1.3.zip",{"slug":61,"name":62,"version":63,"author":64,"author_profile":65,"description":66,"short_description":67,"active_installs":46,"downloaded":68,"rating":13,"num_ratings":69,"last_updated":70,"tested_up_to":71,"requires_at_least":72,"requires_php":73,"tags":74,"homepage":18,"download_link":79,"security_score":80,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"wp-rest-yoast-meta","WP REST Yoast Meta","2025.1.0","Acato","https:\u002F\u002Fprofiles.wordpress.org\u002Facato\u002F","\u003Cp>\u003Cem>This plugin is no longer updated, but is open for adoption\u003C\u002Fem>\u003Cbr \u002F>\nAs of Yoast SEO version 16.7 the functionality provided by this plugin is now \u003Ca href=\"https:\u002F\u002Fdeveloper.yoast.com\u002Fcustomization\u002Fapis\u002Frest-api\u002F\" rel=\"nofollow ugc\">part of the Yoast SEO plugin\u003C\u002Fa> itself. This plugin will no longer be updated, but is open for adoption. If you are interested in adopting this plugin, please contact the authors.\u003C\u002Fp>\n\u003Cp>Are you using WordPress for a headless set-up, using the WP REST API? And would you like to use the Yoast SEO plugin just like you would for any other project? This plugin adds the meta tags generated by the Yoast SEO plugin to the WP REST API output, allowing your headless set-up to implement them. Also when you are using Yoast SEO Premium you have the option to retrieve redirects throught the API: this plugin adds a custom endpoint (\u003Ccode>\u002Fwp-rest-yoast-meta\u002Fv1\u002Fredirects\u003C\u002Fcode>) to provide those redirects in a JSON format. Since Yoast 11.0 JSON LD Schema.org data is also supported and is now also available through the WP REST API when using this plugin.\u003C\u002Fp>\n\u003Ch3>Installation from within WordPress\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Visit ‘Plugins > Add New’ (or ‘My Sites > Network Admin > Plugins > Add New’ if you are on a multisite installation).\u003C\u002Fli>\n\u003Cli>Search for ‘WP REST Yoast Meta’.\u003C\u002Fli>\n\u003Cli>Activate the WP REST Yoast Meta plugin through the ‘Plugins’ menu in WordPress.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Installation manually\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Upload the \u003Ccode>wp-rest-yoast-meta\u003C\u002Fcode> folder to the \u003Ccode>\u002Fwp-content\u002Fplugins\u002F\u003C\u002Fcode> directory.\u003C\u002Fli>\n\u003Cli>Activate the WP REST Yoast Meta plugin through the ‘Plugins’ menu in WordPress.\u003C\u002Fli>\n\u003C\u002Fol>\n","Adds meta tags as generated by Yoast SEO to the WP REST API. And adds a custom endpoint to retrieve all redirects as they are set in Yoast SEO Premium …",31743,6,"2025-01-23T09:31:00.000Z","5.7.15","4.7","5.4",[75,20,76,77,78],"adopt-me","wp-rest","wp-rest-api","yoast","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-rest-yoast-meta.2025.1.0.zip",92,{"slug":82,"name":83,"version":84,"author":85,"author_profile":86,"description":87,"short_description":88,"active_installs":89,"downloaded":90,"rating":91,"num_ratings":92,"last_updated":93,"tested_up_to":94,"requires_at_least":95,"requires_php":18,"tags":96,"homepage":102,"download_link":103,"security_score":104,"vuln_count":105,"unpatched_count":26,"last_vuln_date":106,"fetched_at":28},"contact-forms","Contact Forms by Cimatti","1.9.13","cimatti","https:\u002F\u002Fprofiles.wordpress.org\u002Fcimatti\u002F","\u003Cp>Forms are an essential component of any website. Contact Forms by Cimatti is the culmination of years of experience building and developing business websites of all types. Our plugin focuses on simplicity and power, it captures, stores and helps to classify contacts and leads according to their lead status. It’s ideal for single-language and multilingual sites, simple blogs, or complex WordPress-powered Content Management Systems. If your website handles a considerable amount of contacts and you need to make diverse forms our plugin is an excellent choice.\u003C\u002Fp>\n\u003Ch4>Select, Configure, and Embed Forms\u003C\u002Fh4>\n\u003Cp>Choose the fields you require, customize on-screen messages and email responses, preview, test, and effortlessly embed forms into your posts, pages, or custom content types using shortcodes or the built-in TinyMCE button.\u003C\u002Fp>\n\u003Ch4>Create Forms for Any Purpose\u003C\u002Fh4>\n\u003Cp>Create as many forms as you need. Design landing pages, contact pages, invitations, job application forms with curriculum upload, customer request forms, spare part requests, and more. Utilize the “Clone” feature to avoid “reinventing the wheel” when creating new forms.\u003C\u002Fp>\n\u003Ch4>Ready-to-Use Features\u003C\u002Fh4>\n\u003Cp>Contact Forms by Cimatti has commonly used fields like First Name, Last Name, Address, Province, Country, Telephone, Email, Captcha, and default success messages and email notifications. Simply create a drag-and-drop form, save it, go to a post or page, and click the orange “C” icon in the WYSIWYG editor to insert a contact form into the post or page content.\u003C\u002Fp>\n\u003Ch4>Easy to Use for Beginners\u003C\u002Fh4>\n\u003Cp>These features make it effortless for first-time users, but the plugin’s fast learning curve will soon entice you to explore its advanced features.\u003C\u002Fp>\n\u003Ch4>Craft Superior Forms\u003C\u002Fh4>\n\u003Cp>Don’t leave anything to chance; fine-tune the entire form submission process.\u003C\u002Fp>\n\u003Ch4>Create Reusable Fields\u003C\u002Fh4>\n\u003Cp>Build custom fields to reuse multiple times, starting with 20 available field types, including Text Field, Text Area, Email, Autoreply Email, Checkbox, Checkbox Group, Radio Buttons, Select, Multiple Select, Hidden Value, File Upload, Captcha, Custom HTML, Password, and more.\u003C\u002Fp>\n\u003Ch4>Customize Forms to Perfection\u003C\u002Fh4>\n\u003Cp>Apply visual styles to your forms using options in the “Appearance” tab. Select colors, margins, button styles, and more.\u003C\u002Fp>\n\u003Ch4>Custom Messages for Success\u003C\u002Fh4>\n\u003Cp>Each form can have its own unique online success message. So, when a form is completed, you can provide access to a file download link, coupon information, or simply a message to confirm that the form was submitted correctly.\u003C\u002Fp>\n\u003Ch4>Email Notifications for Administrators and Visitors\u003C\u002Fh4>\n\u003Cp>Send email notifications to administrators, including tracking information like visitor IP, referrer, date and time of form submission, and other user properties (for a full list, see the Beginners’ Guide). Send an email notification to the visitor as further confirmation that the form was filled in correctly. All email notifications can be tested in the Preview\u002FTest Tab before publishing.\u003C\u002Fp>\n\u003Ch4>Data Collection and Excel Export\u003C\u002Fh4>\n\u003Cp>All submitted data is securely stored in your WordPress database. Contacts received can be easily categorized into lead status categories and spam and tests can be easily discarded. Add notes on each contact received to keep track.\u003C\u002Fp>\n\u003Cp>All contact data received can be filtered, searched, and exported to Excel at any time. You can export all the data or just the data you need. The Advanced Excel Export option allows you to export to a file with ready-to-use filtering options.\u003C\u002Fp>\n\u003Cp>Contact Forms also includes a tracking graph in its Dashboard that displays the performance of all or each of your website forms over time.\u003C\u002Fp>\n\u003Ch4>Developer-Friendly API\u003C\u002Fh4>\n\u003Cp>Contact Forms by Cimatti includes an API to assist developers in customizing and adding their own features. WordPress Filters are used to customize forms during generation, to check and validate submitted form values, to execute custom code using sent data, and to add custom tokens for messages. Read the documentation on our site for more information.\u003Cbr \u002F>\nPowerful PHP Form Builder Class\u003Cbr \u002F>\nContact Forms by Cimatti utilizes a PHP form builder class to generate the forms, ensuring robust and efficient form creation and management.\u003C\u002Fp>\n","Create and publish forms in your WordPress website with drag and drop. Contact forms, landing page forms, invitations, and more.",700,79288,88,16,"2025-11-14T11:57:00.000Z","6.8.5","3.5",[97,98,99,100,101],"contact-form","email-notifications","form-api","form-builder","lead-generation","https:\u002F\u002Fwww.cimatti.it\u002Fen\u002Fwordpress-plugins\u002Fcontact-forms\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontact-forms.zip",91,11,"2025-06-02 00:00:00",{"slug":108,"name":109,"version":110,"author":111,"author_profile":112,"description":113,"short_description":114,"active_installs":115,"downloaded":116,"rating":26,"num_ratings":26,"last_updated":117,"tested_up_to":118,"requires_at_least":119,"requires_php":18,"tags":120,"homepage":124,"download_link":125,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"wp-api-yoast-meta","WP API Yoast SEO","1.2.0","ChazUK","https:\u002F\u002Fprofiles.wordpress.org\u002Fchazuk\u002F","\u003Cp>Returns Yoast post or page metadata in a normal post or page request. Stores the metadata in the yoast_meta field of the returned data.\u003C\u002Fp>\n","Returns Yoast post or page metadata in a normal post or page request.",600,8182,"2016-07-29T12:02:00.000Z","4.5.33","4.4",[121,122,123,78],"rest","seo","wp-api","https:\u002F\u002Fgithub.com\u002FChazUK\u002Fwp-api-yoast-seo","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-api-yoast-meta.zip",{"slug":127,"name":128,"version":129,"author":130,"author_profile":131,"description":132,"short_description":133,"active_installs":134,"downloaded":135,"rating":13,"num_ratings":136,"last_updated":137,"tested_up_to":71,"requires_at_least":72,"requires_php":138,"tags":139,"homepage":141,"download_link":142,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"rest-api-head-tags","REST API – Head Tags","1.2.1","frontity","https:\u002F\u002Fprofiles.wordpress.org\u002Ffrontity\u002F","\u003Cp>This plugin adds all the tags in the head section of a website to WordPress REST API responses.\u003C\u002Fp>\n\u003Cp>It is perfect if you are using WordPress for a headless set-up and would like to add the \u003Cstrong>meta tags\u003C\u002Fstrong> generated by your \u003Cstrong>WordPress SEO plugin\u003C\u002Fstrong> (like Yoast SEO or All-in-One SEO Pack) to the WordPress REST API output.\u003C\u002Fp>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cp>This package depends on the \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fbook.dom.php\" rel=\"nofollow ugc\">PHP DOM library\u003C\u002Fa>. Most PHP environments have it by default so you don’t have to worry about that.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>In case you get some errors regarding this dependency make sure you have this library installed (you can take a look at this \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ffrontity\u002Fwp-plugins\u002Fissues\u002F35\" rel=\"nofollow ugc\">thread\u003C\u002Fa> in the code repository).\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>Compatibility\u003C\u002Fh4>\n\u003Cp>This plugin is compatible and works out of the box with some of the most popular WordPress SEO plugins. These are the ones that we tested:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwordpress-seo\u002F\" rel=\"ugc\">Yoast SEO\u003C\u002Fa> – (up to 13.5)\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fall-in-one-seo-pack\u002F\" rel=\"ugc\">All in One SEO Pack\u003C\u002Fa> – (up to 3.4.2)\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Falleyinteractive\u002Fwp-seo\" rel=\"nofollow ugc\">WP SEO\u003C\u002Fa> –\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Are you using a different SEO plugin and want to know if it’s compatible? Feel free to ask in our \u003Ca href=\"https:\u002F\u002Fcommunity.frontity.org\u002F?utm_source=plugin-repository&utm_medium=readme&utm_campaign=rest-api-head-tags-plugin\" rel=\"nofollow ugc\">community forum\u003C\u002Fa>. If you tested any other plugin, please let us know as well so we can update the list.\u003C\u002Fp>\n\u003Ch3>How to use this plugin\u003C\u002Fh3>\n\u003Ch4>Entities with head tags\u003C\u002Fh4>\n\u003Cp>The plugin has been developed to include the head_tags field to the REST API response of most of the WordPress core entities:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Posts, pages, attachments and custom post types.\u003C\u002Fli>\n\u003Cli>Post types: for archive pages.\u003C\u002Fli>\n\u003Cli>Categories, tags and custom taxonomies.\u003C\u002Fli>\n\u003Cli>Authors.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>In a Frontity project\u003C\u002Fh4>\n\u003Cp>If you are using \u003Ca href=\"https:\u002F\u002Ffrontity.org?utm_source=plugin-repository&utm_medium=readme&utm_campaign=rest-api-head-tags-plugin\" rel=\"nofollow ugc\">Frontity\u003C\u002Fa>, you just have to install the \u003Ca href=\"https:\u002F\u002Fdocs.frontity.org\u002Fapi-reference-1\u002Ffrontity-head-tags?utm_source=plugin-repository&utm_medium=readme&utm_campaign=rest-api-head-tags-plugin\" rel=\"nofollow ugc\">@frontity\u002Fhead-tags package\u003C\u002Fa> and \u003Cstrong>it will work automatically\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch4> In a different project\u003C\u002Fh4>\n\u003Cp>You need to understand better how it works and \u003Cstrong>add the data manually\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>\u003Cem>How to fetch the head_tags field manually\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>You have to get each entity from its respective REST API endpoint. For example: for fetching the posts, you should go to \u003Ccode>\u002Fwp-json\u002Fwp\u002Fv2\u002Fposts&id=123\u003C\u002Fcode> endpoint; for fetching the categories, you have to go to \u003Ccode>wp-json\u002Fwp\u002Fv2\u002Fcategories&id=123\u003C\u002Fcode>, and for custom post types or custom taxonomies, it would be a different url in each case.\u003C\u002Fp>\n\u003Cp>In the case of the homepage, it’s less intuitive and you should go to \u003Ccode>\u002Fwp-json\u002Fwp\u002Fv2\u002Ftypes\u002Fpost\u003C\u002Fcode>. As previously said, each entity has a different endpoint so if you aren’t familiar with this, you should check out the \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Frest-api\u002Freference\u002F\" rel=\"nofollow ugc\">WordPress REST API reference\u003C\u002Fa> for more information.\u003C\u002Fp>\n\u003Cp>Inside each endpoint, it will be a new field named \u003Cem>head_tags\u003C\u002Fem>, which will be an array of objects representing the tags that WordPress would normally include inside the html head element. These objects have the properties \u003Ccode>tag\u003C\u002Fcode>, \u003Ccode>attributes\u003C\u002Fcode> and \u003Ccode>content\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>For example for these HTML tags:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Ctitle>Hello wordl! - My Site\u003C\u002Ftitle>\n\u003Cmeta name=\"robots\" content=\"max-snippet:-1, max-image-preview:large, max-video-preview:-1\">\n\u003Clink rel=\"canonical\" href=\"\u003Chttps:\u002F\u002Ftest.frontity.org\u002F>\" \u002F>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This would be the content of the head_tags field:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\"head_tags\": [\n  {\n    \"tag\": \"title\",\n    \"content\": \"Hello world! - My Site\"\n  },\n  {\n    \"tag\": \"meta\",\n    \"attributes\": {\n      \"name\": \"robots\",\n      \"content\": \"max-snippet:-1, max-image-preview:large, max-video-preview:-1\"\n    }\n  },\n  {\n    \"tag\": \"link\",\n    \"attributes\": {\n      \"rel\": \"canonical\",\n      \"href\": \"\u003Chttps:\u002F\u002Ftest.frontity.org\u002F>\"\n    }\n  }\n]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Settings\u003C\u002Fh3>\n\u003Cp>The settings of this plugin are really simple.\u003C\u002Fp>\n\u003Ch4>Purge cache\u003C\u002Fh4>\n\u003Cp>In order to not affect the performance of your site, the head_tags field is cached for all your responses. Each time you update a post\u002Fpage\u002Fcpt or a taxonomy, the cache for that entity will be purged automatically. In case you make global changes (i.e. your permalinks or your global Yoast settings) use the Purge button to clean the whole cache.\u003C\u002Fp>\n\u003Ch4> Enable output\u003C\u002Fh4>\n\u003Cp>By default, the head_tags field is included in the common endpoint of each entity. You can configure it so it doesn’t appear by default and to be shown when you include the head_tags=true query.\u003C\u002Fp>\n\u003Cp>For example, with the output disabled, https:\u002F\u002Ftest.frontity.org\u002Fwp-json\u002Fwp\u002Fv2\u002Fposts won’t show the head_tags field unless you have the query \u003Ccode>?head_tags=true\u003C\u002Fcode> at the end.\u003C\u002Fp>\n\u003Ch4>Skip cache\u003C\u002Fh4>\n\u003Cp>In case you want to skip the cache, you can do so by adding to the query the  parameter \u003Ccode>skip_cache\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>There are some cache plugins for the REST API which also use the same parameter. In case you want to ignore the cache for the REST API call but not for the head tags, you can use \u003Ccode>skip_cache&head_tags_skip_cache=false\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch3>Problems and Questions\u003C\u002Fh3>\n\u003Cp>If you have any trouble with the REST API – Head Tags, you can check out \u003Ca href=\"https:\u002F\u002Fdocs.frontity.org\u002Ffrontity-plugins\u002Frest-api-head-tags?utm_source=plugin-repository&utm_medium=readme&utm_campaign=rest-api-head-tags-plugin\" rel=\"nofollow ugc\">our docs\u003C\u002Fa> or join our \u003Ca href=\"https:\u002F\u002Fcommunity.frontity.org\u002F?utm_source=plugin-repository&utm_medium=readme&utm_campaign=rest-api-head-tags-plugin\" rel=\"nofollow ugc\">community forum\u003C\u002Fa> and let us know. We’ll be happy to help!\u003C\u002Fp>\n\u003Cp>Bug reports for REST API – Head Tags plugin are welcomed in \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ffrontity\u002Fwp-plugins\" rel=\"nofollow ugc\">our repository\u003C\u002Fa> on GitHub. Before opening an issue, please be sure to review the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ffrontity\u002Ffrontity\u002Fblob\u002Fdev\u002FCONTRIBUTING.md\" rel=\"nofollow ugc\">contributing guidelines\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>More Information\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdocs.frontity.org\u002F#what-is-frontity?utm_source=plugin-repository&utm_medium=readme&utm_campaign=rest-api-head-tags-plugin\" rel=\"nofollow ugc\">About Frontity Framework\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fblog.frontity.org\u002Fseo-for-headless-wordpress-themes\u002F?utm_source=plugin-repository&utm_medium=readme&utm_campaign=rest-api-head-tags-plugin\" rel=\"nofollow ugc\">Guide on SEO for Headless WordPress Themes\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Follow Frontity on \u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Ffrontity\" rel=\"nofollow ugc\">Twitter\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ffrontity\u002Ffrontity\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Get help on the \u003Ca href=\"https:\u002F\u002Fcommunity.frontity.org\u002F?utm_source=plugin-repository&utm_medium=readme&utm_campaign=rest-api-head-tags-plugin\" rel=\"nofollow ugc\">Frontity Community Forum\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Adds all the meta tags of the head section to WordPress REST API responses, including the ones generated by SEO plugins like Yoast or All in One SEO.",200,18122,2,"2021-03-26T17:08:00.000Z","5.6",[20,140,121,122,78],"meta","http:\u002F\u002Fgithub.com\u002Ffrontity\u002Fwp-plugins","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frest-api-head-tags.zip",{"attackSurface":144,"codeSignals":172,"taintFlows":184,"riskAssessment":185,"analyzedAt":199},{"hooks":145,"ajaxHandlers":168,"restRoutes":169,"shortcodes":170,"cronEvents":171,"entryPointCount":26,"unprotectedCount":26},[146,152,156,160,164],{"type":147,"name":148,"callback":149,"file":150,"line":151},"action","admin_menu","yopress_create_menu","YoPress.php",12,{"type":147,"name":153,"callback":154,"file":150,"line":155},"draft_to_publish","yopress_do_once_on_publish",13,{"type":147,"name":157,"callback":158,"file":150,"line":159},"init","yopress_create_subscribers_list",14,{"type":147,"name":161,"callback":162,"file":150,"line":163},"plugins_loaded","yopress_pageload",15,{"type":147,"name":165,"callback":166,"file":150,"line":167},"admin_init","register_yopress_settings",95,[],[],[],[],{"dangerousFunctions":173,"sqlUsage":174,"outputEscaping":176,"fileOperations":26,"externalRequests":14,"nonceChecks":26,"capabilityChecks":26,"bundledLibraries":183},[],{"prepared":26,"raw":26,"locations":175},[],{"escaped":26,"rawEcho":136,"locations":177},[178,181],{"file":150,"line":179,"context":180},125,"raw output",{"file":150,"line":182,"context":180},144,[],[],{"summary":186,"deductions":187},"The yopress v0.2.2 plugin exhibits a generally positive security posture based on the static analysis, with no identified vulnerabilities in its attack surface, dangerous functions, or SQL queries. The absence of known CVEs and historical vulnerabilities further contributes to this perception.  However, a significant concern arises from the complete lack of output escaping, meaning all data being displayed to users could potentially be rendered in an unsafe manner, opening the door to cross-site scripting (XSS) attacks.  Additionally, the presence of external HTTP requests without any clear context or security checks is a potential, albeit undefined, risk. The lack of any nonces or capability checks for its (limited) entry points, combined with the unescaped output, presents a notable weakness.",[188,191,194,197],{"reason":189,"points":190},"0% output escaping",8,{"reason":192,"points":193},"External HTTP request without context",3,{"reason":195,"points":196},"No nonce checks",5,{"reason":198,"points":196},"No capability checks","2026-03-17T00:21:47.189Z",{"wat":201,"direct":206},{"assetPaths":202,"generatorPatterns":203,"scriptPaths":204,"versionParams":205},[],[],[],[],{"cssClasses":207,"htmlComments":208,"htmlAttributes":209,"restEndpoints":210,"jsGlobals":211,"shortcodeOutput":212},[],[],[],[],[],[]]