Connect HubSpot content operations to measurable AI visibility.
Review topic clusters, templates, canonicals, structured data, domain mapping and rendered content across HubSpot-hosted pages.
Five checks before content optimization begins.
Fix access, duplication and rendering problems before interpreting weak AI visibility as a content-only issue.
How these things actually work on HubSpot
Generic advice stops being useful at the point where you have to click something. Each row below is the mechanism on this platform, linked to the vendor documentation it came from.
| robots.txt | An admin setting, not a file: Settings, Content, Pages, pick the domain, then the SEO and Crawlers tab. Rules are per domain, and only domains actually connected to HubSpot can be governed this way. HubSpot system domains containing hs-sites are permanently no-index regardless of what you write there. Platform documentation |
|---|---|
| Structured data | HubSpot documents no automatic schema.org emission. The supported route is writing JSON-LD in the template inside the require_head HubL tag, which relocates it into the head, populated from HubL variables such as the title, featured image and publish date with the datetimeformat filter for ISO dates. Per-page one-offs go in the page’s Head HTML field. Platform documentation |
| Sitemap | Only partly automatic. Website pages and blog posts are added to /sitemap.xml on their own, but landing pages are not — you add each one by hand under Content, Domains and URLs, Sitemap. Edits can take up to thirty minutes to propagate, and removing a URL from the sitemap does not deindex it. Platform documentation |
| /llms.txt | HubSpot has no documented mechanism for serving an arbitrary static file at the domain root: File Manager assigns generated URLs under /hubfs/. Of the available workarounds, a page or coded template whose slug is literally llms.txt resolves at the root but is served as text/html rather than text/plain, and a reverse proxy in front of HubSpot is the reliable option. Do not rely on a redirect from /llms.txt, because control-file fetchers commonly do not follow one. Platform documentation · help centre blocks our fetcher; read from the linked article rather than tested by us |
| Rendering | HubL templates are evaluated on the server, so page and blog body content arrives as complete HTML. Forms, CTAs and chat are embedded and populate client-side, which means any offer text living inside a form is invisible to a crawler that does not run JavaScript. Membership-gated content is withheld before authentication. Platform documentation |
| The gotcha | If you use HubSpot site search, robots.txt must explicitly allow HubSpotContentSearchBot as its own group. A robots.txt tightened for AI or SEO reasons with a blanket disallow will silently break on-site search, because HubSpot’s own indexer is caught by the same rule. Platform documentation |
Do these three first
- In Settings, Content, Pages, SEO and Crawlers, check each connected domain separately, and give HubSpotContentSearchBot its own allow group if site search is in use. ↗
- Add every landing page you want crawled to the sitemap by hand, then reload /sitemap.xml after thirty minutes to confirm. ↗
- Wrap a JSON-LD Article block in require_head in the blog template so every post emits schema without per-post editing. ↗
Check implementation decisions against current HubSpot documentation.
HubSpot SEO knowledge base ↗A practical HubSpot GEO workflow.
Separate technical readiness, content evidence and continuous measurement.
Start with checks that do not consume AI tokens.
Questions teams ask before they start
Does a platform page mean InsightWonder edits the site automatically?
No. The page explains platform-specific checks and implementation paths. Write-back or app-based changes should be described only where a verified integration exists.
Are robots.txt and llms.txt enough for GEO?
No. They help with access and orientation, but useful answers still depend on clear content, structured evidence and credible external signals.
Should platform pages be published before examples exist?
No. Publish only after the page has platform-specific checks, executable steps and a real or complete example.
Does InsightWonder modify theme or template code?
No. Platform integrations use supported extension points rather than editing theme files directly.
Is a technical fix enough to get recommended?
Rarely. Access checks remove blockers, but whether a model names you still depends on clear content, structured evidence and credible external signals.
Can more than one site be connected?
Yes. Sites are separate measurement scopes under one account, so results stay comparable instead of being mixed together.
Turn AI visibility into a repeatable growth system.
Create a project, confirm your market and start measuring the questions that matter.