REST API – Head Tags vs WPGraphQL Smart Cache

This plugin adds all the tags in the head section of a website to WordPress REST API responses. It is perfect if you are using WordPress for a headless set-up and would like to add the meta tags generated by your WordPress SEO plugin (like Yoast SEO or All-in-One SEO Pack) to the WordPress REST API output. Requirements This package depends on the PHP DOM library. Most PHP environments have it by default so you don’t have to worry about that. In case you get some errors regarding this dependency make sure you have this library installed (you can take a look at this thread in the code repository). Compatibility 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: Yoast SEO – (up to 13.5) All in One SEO Pack – (up to 3.4.2) WP SEO – Are you using a different SEO plugin and want to know if it’s compatible? Feel free to ask in our community forum. If you tested any other plugin, please let us know as well so we can update the list. How to use this plugin Entities with head tags The plugin has been developed to include the head_tags field to the REST API response of most of the WordPress core entities: Posts, pages, attachments and custom post types. Post types: for archive pages. Categories, tags and custom taxonomies. Authors. In a Frontity project If you are using Frontity, you just have to install the @frontity/head-tags package and it will work automatically. In a different project You need to understand better how it works and add the data manually. How to fetch the head_tags field manually You have to get each entity from its respective REST API endpoint. For example: for fetching the posts, you should go to /wp-json/wp/v2/posts&id=123 endpoint; for fetching the categories, you have to go to wp-json/wp/v2/categories&id=123, and for custom post types or custom taxonomies, it would be a different url in each case. In the case of the homepage, it’s less intuitive and you should go to /wp-json/wp/v2/types/post. As previously said, each entity has a different endpoint so if you aren’t familiar with this, you should check out the WordPress REST API reference for more information. Inside each endpoint, it will be a new field named head_tags, 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 tag, attributes and content. For example for these HTML tags: Hello wordl! - My Site " /> This would be the content of the head_tags field: "head_tags": [ { "tag": "title", "content": "Hello world! - My Site" }, { "tag": "meta", "attributes": { "name": "robots", "content": "max-snippet:-1, max-image-preview:large, max-video-preview:-1" } }, { "tag": "link", "attributes": { "rel": "canonical", "href": " " } } ] Settings The settings of this plugin are really simple. Purge cache 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/page/cpt 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. Enable output 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. For example, with the output disabled, https://test.frontity.org/wp-json/wp/v2/posts won’t show the head_tags field unless you have the query ?head_tags=true at the end. Skip cache In case you want to skip the cache, you can do so by adding to the query the parameter skip_cache. 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 skip_cache&head_tags_skip_cache=false. Problems and Questions If you have any trouble with the REST API – Head Tags, you can check out our docs or join our community forum and let us know. We’ll be happy to help! Bug reports for REST API – Head Tags plugin are welcomed in our repository on GitHub. Before opening an issue, please be sure to review the contributing guidelines. More Information About Frontity Framework Guide on SEO for Headless WordPress Themes Follow Frontity on Twitter and GitHub Get help on the Frontity Community Forum

Do you want your API data fast or accurate? With WPGraphQL Smart Cache, you can have both. WPGraphQL Smart Cache is a free, open-source WordPress plugin that provides support for caching and cache invalidation of WPGraphQL Queries. To get the most out of this plugin, we recommend using GET requests with Network Caching, which requires your WordPress install to be on a supported host. Note: WPGraphQL Smart Cache is now part of the WPGraphQL monorepo. All releases, issues, and discussions are managed in the main repository. BREAKING CHANGES: We may make breaking changes in the future to improve functionality and experience. If we do, we will use semver to do so. Pay attention to release notes and upgrade notices before updating. Video Overview Docs Overview Quick Start Features Network Cache Object Cache Persisted Queries Cache Invalidation Extending / Customizing Functionality FAQ and Troubleshooting Known Issues Providing Feedback Upgrading It is recommended that anytime you want to update WPGraphQL Smart Cache that you get familiar with what’s changed in the release. WPGraphQL Smart Cache publishes release notes on GitHub. Look for releases tagged with wp-graphql-smart-cache/v*. WPGraphQL Smart Cache will follow Semver versioning. The summary of Semver versioning is as follows: MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards compatible manner, and PATCH version when you make backwards compatible bug fixes. You can read more about the details of Semver at semver.org Privacy Policy WPGraphQL Smart Cache uses Appsero SDK to collect some telemetry data upon user’s confirmation. This helps us to troubleshoot problems faster & make product improvements. Appsero SDK does not gather any data by default. The SDK only starts gathering basic telemetry data when a user allows it via the admin notice. We collect the data to ensure a great user experience for all our users. Integrating Appsero SDK DOES NOT IMMEDIATELY start gathering data, without confirmation from users in any case. When you opt in, each telemetry request is sent to Appsero and a duplicate is sent in a non-blocking request to WPGraphQL-operated infrastructure at https://telemetry.wpgraphql.com (the same categories of data as described for Appsero below). Learn more about how Appsero collects and uses this data.