Add-On for Contact Form 7 to Notion vs REST API – Head Tags

Connect the popular WordPress plugin Contact Form 7 to Notion. This add-on enables you to integrate Contact Form 7 forms so that when users submit a form entry, the entries get directly added to Notion. You can link any field type including custom fields and add information to your Notion database. Features Set up the connection with Notion Some simple steps to follow (only once) A new Notion tab shows up in your form settings Choose the destination database you want Make your Notion page visible to the integration For each form, select the database where you want to send data Map your Contact Form 7 fields with Notion All major field types are supported Select the corresponding database field for each form field User-friendly and helpful plugin interface Dropdown lists for instant visualization of mapped fields Many tooltips to make things easier How does it work? How to use it? Create a form with at least an e-mail field (don’t forget the consent field) Go to Notion tab and check the box “Add form submissions to your database” to activate the connection Choose the Notion’s database in which the data should be added Map the fields of your Contact Form 7 form with your Notion’s columns Click on “Save settings” External services This plugin connects to the Notion API to send Contact Form 7 submissions to the Notion database selected in the plugin settings. It sends requests to https://api.notion.com/v1/ when an administrator configures the integration, loads available Notion databases or database properties, and when a visitor submits a connected Contact Form 7 form. Data sent to Notion can include the Notion integration token configured by the site administrator, selected database identifiers, mapped form field values, and uploaded file URLs when file fields are mapped. This data is sent only to create or retrieve the Notion records required for the configured integration. Notion service terms: https://www.notion.so/terms Notion privacy policy: https://www.notion.so/privacy Support If you need support, open a ticket on the Support. Troubleshooting Make sure you have created your database and columns in Notion before linking them to your form fields. If you don’t see it, wait 1 minute. Your Notion elements are cached for 60 seconds for optimal performance. Supported Fields: Title, Text, Number, URL, E-mail, Phone, Select, Multiple Select and Date

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