Hi HubSpot Community, as search user behaviour shifts toward AI-driven engines (SearchGPT, Perplexity, Google Overviews), we’re evaluating how to structure blog content and landing pages hosted on HubSpot CMS for better AI citation. Traditionally, we’ve focused heavily on standard on-page SEO schema and topic clusters within Marketing Hub. However, GEO seems to demand more direct, entity-focused formatting and structured data. For those managing content strategy on HubSpot CMS: 1. Are you making structural changes to your rich-text modules or header hierarchies specifically for AI engine indexing? 2. Has anyone successfully integrated schema markups beyond standard HubSpot defaults for better visibility? Would love to hear how other growth teams and agencies are adapting their HubSpot content stack for 2026. Best,
Hi @proxdigital and welcome, we are delighted to have you here!
Great questions, thanks for asking the Community!
To start with, I’d like to share these resources that can help:
- AI Search Sensor | AI Visibility Trends, Data, and Updates
- HubSpot Academy | Become an Expert in AI Search
- SEO in the Age of AI Learning Path
Now, I’d love to put you in touch with our Top Experts: Hi @Anton, @MichaelMa and @Mike_Eastwood do you have any insights to share with @proxdigital, please?
Thanks so much and wishing you a brilliant day!
Bérangère
Hi @proxdigital,
the fact that you’re putting a lot of effort into classic SEO is great, as it’s still the most important aspect for GEO.
GEO/AEO optimization is nice, but not in a way like “omg… GPT doesn’t see us, because we don’t optimize our content for it”. Personally I’d say it might be responsible for 5-10% overall.
In terms of implementing Schema markup beyond standard HubSpot - yes, done it several times as I offer such services to my clients to have much more control over the generated Schema markup per page and page type.
As for rich-text, my personal opinion on this is: It’s a double-edged sword and I’m always restricting it in functionality to
- improve UX and ease of use
- improve Design Guidelines conformity
- and a few other topics
For instance: Why would you need a table in something like an accordion content element.
Furthermore - one thing I’m always disabling is everything that has to do with fonts and font styles.
For one simple reason: many content editors will use H-tags for the styling, not for the actual structure.
hope this helps
best,
Anton