Lazy SEO vs REST API – Head Tags

The Lazy SEO plugin will automatically create exact match SEO keyword/location combinations for SEO title tags and meta descriptions that randomly rotate with each refresh using SEO best practices. In addition, if you check the box to replace h1’s, it will add an exact match h1 to the content, or replace the first one if it exists, with the same SEO keyword/location combo. Perfect for Small Business SEO. Have WooCommerce? Check out my Small Business eCommerce SEO extension! How to use: 1) Go to the Lazy SEO Settings page to change the default SEO keywords and locations!!! 2) Select whether you want to use the replace h1 Lazy SEO feature. This will replace the first h1 tag within the content of your page/post with the selected priority SEO keyword/location combo for that post for SEO purposes. If there is no SEO keyword priority, it will select a random keyword from your keyword list in the settings. Locations will only be used if selected as priority. If there is not an h1 tag to replace, a new one will be added at the top of the content. 3) Enter an integer for the number SEO keywords you want to use for the site. These SEO keywords will be used throughout the entire site to generate title tags, meta descriptions, and h1 tags (if selected). This is where the list of SEO keywords to focus on will be pulled from. 4) Enter in the SEO keywords. 5) Enter an integer for number geographic locations. These are used the same way as the SEO keywords but for many functions, if they are not set, no location will be assigned (e.g. meta descriptions and new h1 tags). 6) Enter in the geographic locations. 7) Focus pages/posts to SEO keyword and geographic locations through the drop down menu. If an SEO keyword is set, then it will always appear first in the title tag and appear in both the meta description and new h1 (if applicable). If a location is set, it will always be the geographic location used in all three modifications. If there is no geo graphic location used, the first section of the title tag will have a random geographic location, but there will be no geographic location used in either the meta description or new h1 (if applicable). 7a) If no SEO keyword is selected, then one will be assigned for you based on SEO keyword usage. Furthermore, if no location is selected AND no SEO keyword is selected, both will be assigned. However, if an SEO keyword has been selected, a location will NOT be selected and instead be random. To attempt to assign a new focus, select the empty (default) priority. 8) Never worry about fresh SEO content again.

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