@frontity/head-tags
package instead. In this case you will also need the REST API Head Tags plugin.@frontity/yoast
package to your project:NOTE: This package requires the Yoast SEO plugin (v14.0 or above) to be installed and activated on the WordPress site in order to function.
frontity.settings.js
state.yoast.renderTags
<Html2React>
component which is used to render the meta tags can be processor intensive.<title>
tag continues to be rendered in the client while the site is being navigated so that the current page/post title will be displayed in the browser tab. Althougth the <Html2React>
is processor intensive it is not used to render the title tag, so client-side performance will not be impacted.state.yoast.transformLinks
false
.ignore
base
@frontity/yoast
package also requires two Frontity parameters in order to work:state.frontity.url
: The URL of your site. Usually defined in the frontity.settings.js
file.state.source.url
: The WordPress API that is the source of your data. Defined at @frontity/wp-source.@frontity/yoast
package adds the Yoast meta to pages, and to single posts and CPTs. In order to have the Yoast SEO meta on post/CPT archive pages the following PHP code snippet should be added to the WordPress installation. It can be added either in the active theme's functions.php
file or by using a plugin such as Code Snippets.yoast_meta
field for post/CPT archives β in the REST API responses. It adds the type
property inside the \_links
field of post entities when the ?_embed=true
query parameter is used.Note: Frontity always uses the?_embed=true
query parameter when making requests to the WP REST API.
@frontity/yoast
package.