After a schema is generated, you add it to your live page. SuperSchema gives you two ways to do that, and both put the same JSON-LD on your page: paste the generated block into your page's <head>, or push it directly into HubSpot. Pick whichever fits how your site is built. If you would rather be walked through it, the Page Setup wizard takes a single page all the way from generating schema to deploying, verifying, and (on paid plans) monitoring it.
Your two deploy paths #
- Copy-paste into your <head>
- Copy the generated block from SuperSchema and paste it into the <head> of the page you generated it for. This works on every platform: WordPress, Shopify, Webflow, custom HTML, or anything else that lets you edit head code. It is the universal option.
- Deploy to HubSpot
- If you use HubSpot, connect your portal and push schema straight into a blog post, page, landing page, or knowledge article. No copy-paste, and SuperSchema places the block for you. The button reads "Deploy to HubSpot" (and "Redeploy to HubSpot" once a page has already been deployed).
The Page Setup wizard #
Page Setup is the guided flow for taking one page from nothing to fully set up. It moves through a clear sequence and shows your progress as a stepper at the top:
- Generate: SuperSchema reads the page and generates the right schema type(s), each with its own quality score.
- Deploy: ship the block to your page, either by copying it for your <head> or by pushing it to HubSpot.
- Verify: SuperSchema fetches the live page and confirms your schema is actually there and matches the version it generated.
- Monitor (paid plans): keep the page under watch so you are alerted if the schema drifts, breaks, or disappears.
Which one should you use? #
| Your setup | Best path |
|---|---|
| You use HubSpot for the page | Deploy to HubSpot for a one-click push. |
| WordPress, Shopify, or Webflow | Copy-paste into the head, using the platform guide for where each one keeps its head code. |
| Custom HTML or any other CMS | Copy-paste into the head. |
| Not sure | Copy-paste into the head. It works everywhere. |
What the deployed block looks like #
However you deploy, SuperSchema wraps your JSON-LD in two HTML comment markers. Leave them in place: they are how SuperSchema recognizes which exact version is live when it verifies and monitors the page. Removing them does not break your schema for search engines, but it does stop SuperSchema from tracking it.
<!-- SuperSchema v="2" id="..." ts="..." types="..." -->
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "..."
}
</script>
<!-- /SuperSchema -->