How to Add Schema to Your HubSpot Website (and Why It Matters for AEO)

Jonathan Price // October 5, 2026

How to Add Schema to Your HubSpot Website (and Why It Matters for AEO)

Structured data gives search systems clearer context about your content

If you’ve read our Answer Engine Optimisation (AEO) playbook, you’ll know that search behaviour has already changed.

People increasingly discover, research and evaluate businesses through AI-powered search experiences as well as traditional search results. That makes it more important than ever that your website is clear, well structured and easy for both people and machines to understand.

Schema markup can help with that. It gives search engines a standardised description of the organisations, services, articles, products and other entities represented on a page.

But it is important to be precise about what schema does not do. It is not an AI-ranking hack, and adding structured data does not guarantee that ChatGPT, Google Gemini, Perplexity or another answer engine will cite your page. Google also does not require special schema to appear in AI Overviews or AI Mode.

Instead, think of schema as supporting infrastructure: useful technical SEO that reduces ambiguity, helps eligible search features and gives machines an explicit description of your content.

In this guide, we’ll show you how to add schema to a HubSpot website, how to choose useful schema types, how to generate JSON-LD safely, and how to validate what you publish.

What is schema markup?

Schema markup is a form of structured data. It uses a shared vocabulary from Schema.org to describe what a page contains and how the different entities on that page relate to one another.

For example, structured data can explicitly tell a search engine:

this entity is an Organization;
this page describes a Service;
this piece of content is a BlogPosting;
these links represent a BreadcrumbList;
this visible question-and-answer content is an FAQPage.

That does not replace good content, technical SEO, internal linking or a crawlable website. It complements them.

Google uses structured data to understand page content and to determine eligibility for certain search features. Other systems may also parse structured data, but you should avoid assuming that schema alone will improve AI citations or rankings.

The practical rule: use schema to describe what is genuinely on the page, not to make claims that the visible content does not support.

Step 1. Choose the right schema for the page

Not every page needs every kind of schema. Start with the entities and content types that are actually important to the page.

Schema type	Good fit for	What it helps describe
Organization	Homepage / about page	Your business identity, website, logo, contact details and official profiles.
Service	Core service pages	The service being offered, its provider and the market or area served.
Article / BlogPosting	Blog posts and guides	The article, author, publisher, dates and imagery.
BreadcrumbList	Pages with a clear hierarchy	Where the page sits within the structure of your site.
FAQPage	Pages containing genuine, visible FAQs	Question-and-answer content that is already visible to users. Do not expect commercial FAQ rich results from Google.
LocalBusiness	Relevant physical business locations	Location, contact and business information where a local business subtype is appropriate.

What about reviews and testimonials?

A case study or testimonial does not automatically mean you should add Review schema. Google has specific eligibility rules for review snippets, including restrictions around self-serving reviews for organisations and local businesses. Add review-related structured data only when the content genuinely fits the supported use case.

What about FAQ schema?

FAQPage still exists in Schema.org and can accurately describe visible FAQ content. However, Google now limits FAQ rich results primarily to well-known government and health sites, so most commercial websites should not implement FAQ schema expecting the old expandable FAQ search result.

The FAQ itself can still be valuable. Useful, page-specific questions and concise answers help users and make the content easier to understand. The structured data should simply describe what is already there.

Step 2. Generate JSON-LD safely

You do not need to hand-code every schema block. ChatGPT and other AI tools can be useful for drafting JSON-LD — but treat the output as code, not as a source of truth.

Give the model the factual information you want represented and tell it not to invent missing details.

Example prompt for Organisation schema

Generate valid JSON-LD using Schema.org Organization markup for Growth London. Use only the factual information I provide below. Include name, canonical website URL, description, logo, sameAs links and contact details where supplied. Do not invent missing values. Return the complete JSON-LD inside a <script type="application/ld+json"> tag, followed by a short checklist of any values I should verify before publishing.

ChatGPT will return something like:

💡 Always copy the schema exactly as-is, including the <script> tags.

Example prompt for Service schema

Generate valid JSON-LD using Schema.org Service markup for this HubSpot service page. Use the page copy I provide as the source of truth. Include serviceType, provider, areaServed and description where they are genuinely supported by the page. Do not invent awards, ratings, prices, locations or other facts. Return the complete JSON-LD inside a <script type="application/ld+json"> tag.

Before you publish anything AI-generated, check:

Does every factual value match the website?
Does the structured data describe content that is actually present on the page?
Are URLs canonical and current?
Are you using the correct Schema.org type and property names?
Have you removed anything the AI invented?

TIP: do not simply copy AI-generated schema without reviewing it. Structured data should be accurate, representative and maintained alongside the content it describes.

Step 3. Add schema to your page in HubSpot

HubSpot supports adding code snippets to individual website pages, landing pages, blog posts and knowledge base articles.

In HubSpot, navigate to Content → Website Pages or Content → Landing Pages. For a blog post, navigate to Content → Blog.
Open the page or post you want to edit.
Open Settings and select Advanced.
Find Additional code snippets.
Paste the complete JSON-LD block into Head HTML.
Publish or update the content.

Your JSON-LD should include the script wrapper:

<script type="application/ld+json"> { ...your structured data... } </script>

Schema Example - HubSpot CMS

Once saved, the page contains machine-readable structured data alongside the human-readable content.

Pro tip for scaling schema in HubSpot

If you manage many similar pages, reusable HubSpot components can make structured data easier to maintain - but avoid outputting identical page-specific schema everywhere.

A sensible approach is to separate:

Site-level information, such as organisation identity, which can be managed centrally where appropriate.
Page-level information, such as a particular service, article or location, which should use values specific to that page.

For larger HubSpot sites, a developer can build a custom module or template logic that outputs JSON-LD dynamically from controlled HubSpot fields. That is much safer than manually copying the same hard-coded block across dozens of pages.

Step 4. Validate your schema

Validation is not one single test. We recommend three checks.

1. Schema.org Validator

Use the Schema.org Validator to check whether the structured data is valid against the Schema.org vocabulary.

2. Google Rich Results Test

Use Google’s Rich Results Test to see whether Google recognises any structured-data features that are eligible for Google Search enhancements.

Not every valid Schema.org type produces a Google rich result. For example, Service can be valid and useful structured data without being a standalone Google rich-result type.

3. Google Search Console URL Inspection

After publishing, use URL Inspection in Google Search Console to confirm that Google can crawl and render the live page. If you have made a significant update, you can also request re-indexing.

Warnings are not always problems. Fix genuine errors first, then review warnings to decide whether additional recommended properties are relevant and truthful for the page.

Step 5. Keep your structured data accurate

Structured data should evolve alongside the content and business information it describes.

Review it when you change:

company name, branding, logo or contact details;
service descriptions or markets served;
authors, dates or article content;
business locations;
the underlying visible FAQs or other marked-up content.

For larger sites, it is useful to keep a simple record of which schema types are being generated where, and whether they are manually maintained or produced dynamically by the HubSpot theme or module.

If you regenerate schema with ChatGPT after a major content change, repeat the same factual review and validation process before publishing it.

Where schema fits into AEO

Schema can support an AEO strategy, but it should not be confused with AEO itself.

Answer Engine Optimisation is the wider job of making your organisation and expertise easy to discover, understand, verify and cite across search and AI systems. That includes the quality and clarity of your content, strong entity signals, crawlability, authority, internal linking, relevant source material and useful page structure.

Schema contributes by making some of that meaning explicit in a standard format.

Organisation schema can make your core business identity and official properties explicit.
Service schema can describe the relationship between a service and its provider.
Article or BlogPosting schema can identify the author, publisher, dates and other article metadata.
FAQPage schema can accurately describe genuine FAQ content, but it should not be treated as a route to guaranteed AI citations or Google FAQ rich results.

That distinction matters. Google does not require special schema for its AI search experiences, and there is no reliable basis for promising that adding JSON-LD will make ChatGPT or another answer engine quote a page.

The case for schema is simpler and stronger: accurate structured data removes ambiguity and gives machines a clean, explicit description of important entities and content.

Keep the FAQ visible

If you use FAQPage markup, the questions and answers should also be visible on the page itself and genuinely useful to the reader.

At Growth London, we often build reusable HubSpot FAQ modules that match the website design and make it easy for content editors to maintain the visible content consistently.

Example FAQ modules:

Example HubSpot FAQ module

Conclusion: use schema for clarity, not as an AI shortcut

Schema markup is invisible to most visitors, but it gives search systems a clearer, more structured description of what your website contains.

For HubSpot users, implementation is relatively straightforward. The important part is choosing the right schema, keeping it aligned with the visible page, validating it properly and maintaining it as your content changes.

It will not replace useful content or guarantee AI visibility. But as part of a broader technical SEO and AEO approach, it is a practical way to reduce ambiguity and make the structure of your website more explicit.

At Growth London, we help teams improve HubSpot websites across content, technical SEO, structured data and AI search readiness.

If you’d like us to audit your HubSpot site and identify where structured data and broader AEO improvements would be most useful, get in touch.

🔗 Related reading

Answer Engine Optimisation (AEO): A Playbook for HubSpot Users

Getting Started with HubSpot

Get More Out of HubSpot

Services for Your

Spot the Gaps

All Services

How to Add Schema to Your HubSpot Website (and Why It Matters for AEO)

Structured data gives search systems clearer context about your content

What is schema markup?