HubSpot integration =================== Connect your HubSpot portal once, map it to the domains it hosts, then push schema and AI-readable files straight into your blog posts, pages, and landing pages with one click. No copy-paste, no touching HubSpot code. Category: Integrations | Last updated: 2026-07-07 The HubSpot integration lets SuperSchema write schema directly into your HubSpot content instead of you copying JSON-LD and pasting it into head HTML by hand. You connect your portal once, tell SuperSchema which domains that portal hosts, then use the "Push to HubSpot" button on any generated schema. SuperSchema finds the matching blog post, page, or landing page and adds the schema (and your AI-readable files) to that content's head HTML. It works for one page or for an entire monitored site. BEFORE YOU START - You need a HubSpot account with CMS access. Pushing schema into pages and blog posts requires Marketing Hub Professional or Enterprise, or CMS Hub Professional or Enterprise. - Knowledge Base articles are separate: pushing to them requires Service Hub Professional or Enterprise, and you have to grant the optional Knowledge Base permissions when you connect (see below). - You connect at the portal level. One SuperSchema account can connect several HubSpot portals, and each portal is mapped to the domains it hosts. CONNECT YOUR HUBSPOT ACCOUNT 1. Open the HubSpot page in SuperSchema. 2. Click "Connect HubSpot Account". 3. You are sent to HubSpot to review the requested permissions. Log in if needed and choose the account (portal) you want to connect. 4. Approve the permissions. HubSpot sends you back to SuperSchema and your portal appears on the HubSpot page. SuperSchema requests two required permissions, "content" (read and write access to your CMS pages and blog posts, which is where schema is injected) and "oauth" (the standard sign-in permission). It also asks for optional Knowledge Base permissions. Those are optional because they only work on Service Hub Professional or Enterprise, so granting or skipping them never blocks the core connection. Note: HubSpot authorization codes expire about 60 seconds after you approve. If you refresh the page, use the back button, or stall on the HubSpot screen, the connection can fail with an expired-code error. If that happens, just click "Connect HubSpot Account" again and move through the screens without pausing. ASSOCIATE A DOMAIN WITH YOUR PORTAL SuperSchema matches a schema to HubSpot content by URL, so it needs to know which domains live in which portal. If you only have one portal, associating your domain also flips the portal to "ready" for one-click deploys. 1. On the HubSpot page, find your connected portal. 2. In the "Associated Domains" section, click "Add Domain" (or "Add Domain to Complete Setup" if none is mapped yet). 3. Enter the domain that this HubSpot portal hosts. You can paste a full URL or just the domain; SuperSchema strips the protocol and path for you. 4. Click Add. The domain now shows under that portal. Tip: A portal is only ready for one-click deploys once it is active and has at least one associated domain. Until then you may see a "Domain Not Associated" warning when you try to push. Associating the domain clears it. PUSH SCHEMA TO HUBSPOT Once a portal is connected and its domain is associated, you can push from a couple of places. The button label depends on where you are: "Push to HubSpot" on a generated schema, and "Deploy to HubSpot" (or "Redeploy to HubSpot" after the first deploy) in the monitoring deploy step. 1. Generate schema for a URL, or open an existing one from your Library. 2. Click "Push to HubSpot" (its tooltip reads "Push schema and AI-readable files to HubSpot"). If the button is greyed out, the portal is not connected or not active yet; the tooltip will read "Connect HubSpot first". 3. SuperSchema opens the content matcher and looks up the matching HubSpot content by URL. It searches your blog posts, pages, landing pages, and (if enabled) Knowledge Base articles. 4. Pick the matching content, or search by title, or paste the HubSpot URL directly if it is not in the list. 5. Click "Confirm & Push Schema". SuperSchema adds the JSON-LD to that content's head HTML, keeping any head HTML that was already there. What gets written: SuperSchema extracts the valid JSON-LD from your schema and injects it into the head HTML of the matched HubSpot content. Existing head HTML is preserved, not overwritten. Content types it can match: Blog posts, site pages, landing pages, and Knowledge Base articles. Matching is by URL, so the URL you generated schema for has to line up with the content's live URL and domain. After a successful push: SuperSchema records the deployment so it can track that page for schema drift, and it refreshes its baseline shortly after so the next monitoring cycle does not misread your fresh schema as an unexpected change. WHICH HUBSPOT PLAN YOU NEED Pages and blog posts | Marketing Hub Pro/Enterprise or CMS Hub Pro/Enterprise | content (required) Landing pages | Marketing Hub Pro/Enterprise or CMS Hub Pro/Enterprise | content (required) Knowledge Base articles | Service Hub Professional or Enterprise | Knowledge Base permissions (optional) Note: If you did not grant the Knowledge Base permissions when you first connected, or your plan did not support them, SuperSchema shows an "Enable Knowledge Base Access" option in the content matcher so you can add just those permissions without disconnecting. MANAGING AND DISCONNECTING A PORTAL Validate: Click "Validate" on a portal to test the saved connection against HubSpot and refresh its status. Use this if a portal starts showing as inactive. Reconnect: If a connection cannot be validated, SuperSchema marks it inactive and shows a "Reconnect" action. Reconnecting re-runs the HubSpot approval and restores one-click deploy access. Disconnect: Click Disconnect, then confirm in the "Disconnect HubSpot Account" dialog. This deactivates the connection in SuperSchema. Schema you already pushed stays live in HubSpot; it is not removed. To push to that portal again you will need to reconnect and reassociate its domains. TROUBLESHOOTING Getting a "Domain Not Associated" warning: The portal is connected but the domain of the page you are pushing has not been mapped to it. Add the domain in the "Associated Domains" section, then push again. The content matcher cannot find your page: Matching is by URL, so the page URL and the HubSpot content URL (including domain) have to line up. Check that the right domain is associated with this portal, search by the content title, or paste the HubSpot URL directly into the matcher. Blog posts (or another type) could not be loaded: This is usually a temporary HubSpot hiccup. You can still switch to another content type, search, or paste the HubSpot URL directly, then try the failing type again in a moment. Connection showing as "Inactive": Click "Validate" to re-test and refresh it. If it stays inactive, the token was likely expired or revoked on HubSpot's side; use "Reconnect" to re-authorize. A push fails with a reconnect message: If you see "HubSpot connection expired or was revoked. Please reconnect HubSpot and try again." the saved token is no longer valid. SuperSchema deactivates the connection automatically; click "Reconnect HubSpot" and push again. A push fails with a permissions error: A message about permissions being denied means the connected token is missing a CMS permission for that action. Reconnect and make sure you approve all requested permissions, including the Knowledge Base ones if you are pushing to KB articles. Content not found in HubSpot: The message "Content not found in HubSpot. It may have been deleted or moved." means the page or post you selected no longer exists at that ID. Re-open the matcher and pick the current content. Note: HubSpot is one of several ways to get schema onto your site. If you are not on a supported HubSpot plan, you can still copy the schema and paste it into your head HTML by hand, or host AI-readable files. See the deployment options overview for the full picture. QUESTIONS THIS ANSWERS - How do I connect my HubSpot account to SuperSchema? - How do I push schema to a HubSpot blog post, page, or landing page? - What HubSpot permissions does SuperSchema ask for and why? - What is a domain association and why do I need one? - Why can the content matcher not find my HubSpot page? - Why does my HubSpot connection show as Inactive and how do I fix it? - Which HubSpot plan do I need to push schema? - Can I push schema to HubSpot Knowledge Base articles? - What happens to my schema if I disconnect HubSpot? - Why did my push to HubSpot fail?