AEO Schema Edits to Site Source Code#5044
Conversation
Added new description for organisation-level clarity. This will help with AEO targeting sameAs data and authority.
Added logo, description, founded year, and headquarters for FlowFuse.
Added social media and expertise details for Sumit Shinde. This will help for authority. Anyone who publishes should have this done to their profile - will do that in the second step.
Updated JSON-LD structured data for FlowFuse with new descriptions, ratings, and additional social media links.
Add in author resolution to prevent stubs and also added in additional details about the org.
Added HowTo schema for AEO targeting.
Updated the URL to use lowercase and modified Twitter creator meta tag logic to prevent empty emission.
KristopherLeads
requested review from
PabloFilomeno83,
Yndira-E and
sumitshinde-84
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| }, | ||
| "organization": { | ||
| "legalName": "FlowFuse Inc.", | ||
| "alternateName": ["Flow Fuse"], |
There was a problem hiding this comment.
why it has space in between?
There was a problem hiding this comment.
Wasn't this supposed to be "FlowForge"?
There was a problem hiding this comment.
It's so anyone that searches for Flow Fuse still finds FlowFuse.
…dcoding - Replace all hardcoded Organization fields in jsonld.njk with references to site.organization.* and site.baseURL - Add "FlowForge" to alternateName for pre-rebrand entity disambiguation - Remove description duplicate from site.organization (same as messaging.subtitle) - Revert companies/flowfuse.json to main state — schema fields added there were unused; the data now lives in site.json as single source of truth - Fix author sameAs rendering to use dump filter, eliminating empty lines Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
| ] | ||
| } | ||
| {% endif %} | ||
| {% if meta.howto %} |
There was a problem hiding this comment.
@KristopherLeads There's no documentation on how to use this. Could you add an entry to the handbook explaining:
- When to use it
- The full frontmatter structure (name, description, totalTime, tool, steps)
- How the url field works
- A complete example
Without this, authors won't know the feature exists and it'll never show up in the JSON-LD output.
There was a problem hiding this comment.
Will do - wanted to make sure this was in before as we discussed earlier. Just documenting here for the future.
|
Also reverted the fields added to Additional change: added "FlowForge" to |
Yndira-E
left a comment
Yndira-E
left a comment
There was a problem hiding this comment.
I'm approving, but this needs a follow up PR #5044 (comment)
3 participants
Description
This is a non-breaking relatively major change to the way we render blog posts on-site. This code does a handful of major things:
Checklist