The Viking StackKnowledge Base

Add custom JSON-LD or other head code manually

Use the tracking/header code fields to paste hand-written JSON-LD or any other head code, site-wide or per page, and validate it before you rely on it.

8 min readadvancedUpdated September 9, 2026

The AI schema generator (see Generate schema markup with AI) covers the vast majority of what a business page needs. But sometimes you want something more specific than the generator produces, you're pasting in markup a developer or agency wrote for you, or you need head code that isn't schema at all — a verification meta tag, a third-party tool's snippet. For all of that, the platform gives you a direct header/footer code field. This article covers when to use it and how to avoid breaking your page.

Note: This is an advanced/optional path. If the AI generator already covers your schema needs, you don't need this article — go to Generate schema markup with AI instead.

Where it lives

Custom code fields exist at two levels, and which one you use depends on the scope of what you're adding:

  • Site-wide / funnel-wide: open your funnel or website's Settings, and look for the Tracking Code (sometimes labeled Head tracking code / Footer tracking code) section. Anything pasted here loads on every page and step in that funnel or website.
  • Page-level: open the individual page's editor and look for its own custom code or SEO settings area, if your page template exposes one separately from the funnel/website-wide setting.

Screenshot coming soon

Funnel Settings with the Tracking Code section open, showing Head tracking code and Footer tracking code fields

Warning: Anything pasted into a site-wide tracking code field applies to every page in that funnel or website — including ones where it doesn't make sense. Site-wide is the right place for things like Organization schema (true everywhere) or a verification tag. It's the wrong place for page-specific schema like a single Product listing, which belongs only on that product's page.

When to add JSON-LD manually instead of using the AI generator

  • You already have markup written by a developer, SEO consultant, or generated by an outside tool, and you just need to place it.
  • You want a schema type or property the AI generator doesn't produce well, and you're comfortable editing JSON-LD directly.
  • You're adding something that isn't schema at all — a Google Search Console verification meta tag, an analytics or ad-platform verification script, a font preconnect, or another head-level snippet.

How to add it

  1. Write or obtain your JSON-LD, wrapped in a <script> tag:
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Software Co.",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png"
}
</script>
  1. Open Settings > Tracking Code for the funnel or website (or the page-level custom code field, if you're scoping it to one page).
  2. Paste the full snippet — including the <script> tags — into the Head tracking code field if it needs to load in the page <head> (this is where JSON-LD and verification tags normally go). Use the footer field only for scripts that specifically need to load after the page content, like some analytics tags.
  3. Save, then publish the page or funnel. Custom code, like schema from the AI generator, doesn't go live until the page is published.

Tip: If you're adding more than one JSON-LD block, each needs its own <script type="application/ld+json">...</script> wrapper. Don't try to combine multiple schema objects into a single script tag unless you're deliberately using a JSON array — get this wrong and the whole block can fail to parse.

Avoiding conflicts with the AI schema generator

If you use both the AI generator (for page-specific schema) and manual head code (for site-wide schema), keep them from overlapping:

  • Don't generate LocalBusiness schema with the AI tool on every page and also paste Organization schema site-wide with near-identical information — pick one layer for identity-level facts (site-wide) and use the AI generator for page-specific facts (a particular service, a particular FAQ).
  • If you ever remove or replace AI-generated schema on a page, double check you haven't left a stale duplicate sitting in the page's own custom code field too.

Validate before you trust it

Manual code doesn't get the same automatic "Validate and Save" check the AI generator gives you, so verify it yourself:

  1. Publish the page.
  2. Paste the live page URL into Google's Rich Results Test (search.google.com/test/rich-results) to confirm Google can parse it and see which rich-result types it's eligible for.
  3. For schema types Google's tool doesn't check, use the Schema Markup Validator (validator.schema.org), which validates against the full schema.org vocabulary.
  4. Check your browser's developer console on the live page for any script errors — a malformed <script> tag can silently fail or, worse, break other scripts on the page.

Warning: A syntax error in hand-written JSON-LD (a missing comma, an unescaped quote) won't usually break your page's visible design, but it will make the schema invisible to search engines and AI assistants — it just silently fails. Always validate after publishing, not just after saving.

What done looks like

  • Your custom code is placed at the right scope — site-wide for identity-level facts, page-level for anything specific to one page.
  • The page is published, not just saved.
  • Google's Rich Results Test or the Schema Validator shows the markup parsing without errors.
  • You've checked for duplicate or conflicting schema between manual code and anything the AI generator already added.

Frequently asked questions

Can I use manual head code and the AI schema generator on the same page?

Yes — they don't conflict as long as you're not duplicating the same facts in both places. Many sites use site-wide Organization or WebSite schema via manual code, plus page-specific schema (FAQPage, Product) via the AI generator on individual pages.

Where do verification tags for tools like Google Search Console go?

The same head tracking code field. Paste the verification meta tag exactly as the tool gives it to you, save, and publish — then confirm verification on the tool's side.

I pasted code and nothing changed. What's wrong?

The two most common causes: the page wasn't published after saving, or the code has a syntax error that's silently failing. Check both, then run the live URL through a validator to confirm.

Is there a limit to how much code I can add?

The field itself doesn't impose a practical limit for typical use, but loading a large amount of script — especially in the head — can slow page load. Keep it to what you actually need; see page-speed guidance touched on in the overview.