AI crawlers allowed in robots.txt
Settings → Content → Pages → the domain, then the Robots.txt tab. HubSpot keeps one robots.txt per connected domain, so check the one that matches the site being graded.
Site platforms
HubSpot CMS gives you everything you need for these checks and buries each of it somewhere different. robots.txt is per connected domain, root files come out of Design Manager, and schema goes in a template — three separate places, none of which are where you would look first.
The trap specific to HubSpot is the per-domain robots.txt. Sites with a marketing domain, a blog subdomain and a landing-page domain have three of them, and fixing the one you happened to open does nothing for the domain that was actually failing.
How we recognise it: the HubSpot tracking script, pages on hs-sites.com, or assets on HubSpot's CDN. Run the free readiness check and the fixes it gives you are the HubSpot CMS ones below.
Settings → Content → Pages, then pick the domain from the list before opening the Robots.txt tab. On a multi-domain portal this is the difference between fixing the problem and editing a file nobody fetches.
Settings → Content → Pages → Templates → site header HTML. HubSpot emits no Organization schema on its own, so this is not an override — it is the only one on the site.
Site header HTML
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your company",
"url": "https://yourdomain.com",
"sameAs": ["https://www.linkedin.com/company/yourcompany"]
}
</script>Create it as a file rather than a page, and publish it to the root of the domain being checked. A page slugged llms.txt renders as HTML and reads as absent.
CueScout runs eight checks on whether an answer engine can read a site at all. These are the ones whose answer is different on HubSpot CMS — the rest are the same everywhere.
Settings → Content → Pages → the domain, then the Robots.txt tab. HubSpot keeps one robots.txt per connected domain, so check the one that matches the site being graded.
Design Manager → create a new file → llms.txt, then publish it to the domain root. HubSpot serves files from the manager at the path you give them.
Settings → Content → Pages → Templates → the site header HTML, or the individual template's head. HubSpot generates no Organization schema of its own.
These describe HubSpot CMS’s own settings, which move without warning us. Last checked against the product on 2026-08-14.
No. The checks are HTTP requests against your public pages, so there is nothing to install and no portal access involved.
Usually because the fix landed on a different connected domain. HubSpot keeps one robots.txt per domain and the site being graded may not be the one you edited.
They can be, and they mostly are not, for a reason unrelated to HubSpot: a landing page written to convert a click rarely answers a question in the form somebody asked it. The pages that get quoted explain something.
WordPress
The virtual robots.txt, the Yoast and Rank Math settings that produce sameAs, and where llms.txt goes.
Site platformsWebflow
The robots.txt setting that only works on a custom domain, where JSON-LD goes, and why /llms.txt needs a proxy.
Site platformsNext.js
app/robots.ts, a route handler for llms.txt, JSON-LD in the layout, and the client-component trap.
The readiness check is free, needs no signup, and takes about half a minute. It works out what your site is built on and gives you the fixes written for it.