Connect Your Platform
The structured-data, social-preview and citation fields HarperFlow writes into your collection, and how to bind them in Webflow.
Alongside the article itself, HarperFlow computes a set of fields that exist purely to make each post easier for search engines and AI answer engines to read. They're written into your collection like any other field, so you can bind them in the Designer yourself — no app, no custom code permissions, nothing to install.
| Field | What it holds |
|---|---|
| Article Schema | The article's Article structured data, as JSON. |
| OG Title | The title social platforms and AI crawlers should show. |
| OG Description | The one-line description they should show with it. |
| OG Image | The image they should show with it. |
| Canonical URL | The article's own live URL, so duplicates elsewhere don't compete with it. |
| Word Count | How many words the published article actually runs to. |
| Sources | The outbound citations the article links to, as a list. |
| Related Articles | The links to your own posts that the article weaves in. |
| Author Snapshot | The byline, as plain text. |
| TLDR | Your key takeaways as a single paragraph, for a lede under the headline. |
Every one is optional. If a field isn't in your collection, or an article genuinely has nothing to put in it — no featured image, no outbound citations — HarperFlow leaves it out rather than writing something empty.
Article Schema holds bare JSON, deliberately without a <script> wrapper — Webflow strips <script> from Rich Text fields, and you need the tag to live in your template rather than in your data. To use it:
Open your blog's collection template page in the Designer.
Drag in an HTML Embed.
Set its contents to:
<script type="application/ld+json">
</script>
Put your cursor between the tags and add the Article Schema field from the CMS field picker.
Publish.
Every article then serves its own valid structured data in the page's raw HTML — which matters, because most AI crawlers read raw HTML and never run JavaScript.
<link rel="canonical" href="…"> tag in the page's custom code, or bind it in page settings if your plan includes that.The Connector applies a template that binds all of this for you in a click, so you don't need to do any of the above. These fields exist so that everything still works if you'd rather set your template up by hand.