Black Friday30% off your first year on yearly plans with30% off yearly · . Ends 1 Dec.See pricing

How to Add Schema Markup to Framer (Without Writing a Single Line of Code)

Framer has no native schema UI, so every JSON-LD block has to be hand-coded. Here's what schema matters, how to add it, and how to skip the manual work.

7 Seers

RankFrame team

Makers of RankFrame, by 7 Seers

·

·

11 min read

Cover image for How to Add Schema Markup to Framer (Without Writing a Single Line of Code)

What Is Schema Markup and Why Does It Matter?

Search engines are very good at reading words on a page, but they often need help understanding what those words mean. Schema markup is a standardized vocabulary (defined at schema.org and supported by Google, Bing, and other engines) that lets you annotate your content with machine-readable labels: “this is an article,” “this is a recipe,” “this is an FAQ.”

The practical payoff is rich results in Google Search. Rich results are enhanced SERP listings that show star ratings, FAQ dropdowns, event dates, job post details, recipe images, and more directly below the blue link. They make your listing physically larger and more informative than a standard result, which consistently drives higher click-through rates.

Schema and Google Rankings

Schema markup is not a direct ranking factor. Google has confirmed it does not use structured data to boost a page’s position in core organic results. What schema does is make pages eligible for rich results, and rich results generally improve CTR. Higher CTR on your organic listings can signal engagement quality to Google’s systems over time.

The Three Implementation Formats

Schema.org supports three formats: JSON-LD, Microdata, and RDFa. Google recommends JSON-LD for all new implementations. It lives in a script tag in your page head, completely separate from your HTML structure, which makes it far easier to manage, update, and validate.

How Framer Handles Schema Markup Natively

Framer provides two places to inject custom code: Site Settings (applies to every page) and page-level Custom Code (applies to one page). Both support a Head field where you can paste raw HTML, including script blocks with type=”application/ld+json”. That is the full extent of Framer’s native schema support.

Framer has no schema form, no field validation, no schema type selector, and no automation. Every schema snippet must be written by hand and pasted manually. A single typo in a JSON-LD block renders the entire schema unreadable by Google.

How to Add Schema Manually to a Framer Page

Step 1: Write your JSON-LD script using a reference from schema.org. For example, an Article schema requires at minimum headline, author, datePublished, and publisher.

Step 2: Open your page in the Framer editor. Click the page name in the left panel and select Page Settings. Scroll to Custom Code, then paste your script into the Head section.

Step 3: Publish your site, then test the live URL in Google’s Rich Results Test to confirm the schema is parsed correctly.

Why Manual Schema Breaks Down at Scale

  • Every page needs a separate script. There is no templating mechanism for CMS pages in Framer’s custom code fields.

  • Errors compound silently. A missing comma or incorrect property name produces no visible error on the page but breaks schema detection entirely.

  • Updates are fragile. Changing your business name or logo URL means updating every page’s schema individually.

Every Schema Type That Matters for Framer Sites

Organization (Supported by RankFrame)

Describes a business or organization: name, URL, logo, contact information, social profiles, and founding details. Every business or agency website should have Organization schema on the homepage. Rich results: contributes to Google’s Knowledge Panel, sitelinks display, and brand entity recognition.

Person (Supported by RankFrame)

Describes an individual: name, job title, employer, website, and social profiles. Use for freelancer portfolios, personal blogs, author pages, and consultant websites. Rich results: author attribution in article rich results, Knowledge Panel for notable individuals.

Article / BlogPosting / TechArticle / NewsArticle (Supported by RankFrame)

Describes a written piece of content. Use any page that is primarily a written article, post, or guide. Rich results: article headline, image, and date in Google Discover and Top Stories.

Service (Supported by RankFrame)

Describes a service offered by a business: name, description, provider, and area served. Use on individual service pages on agency, SaaS, or professional services websites.

Restaurant (Supported by RankFrame)

A subtype of LocalBusiness specifically for food service establishments. Includes cuisine type, menu, reservations, and price range.

Book (Supported by RankFrame)

Describes a book: title, author, ISBN, publisher, and description. Use on author websites, book landing pages, or any Framer page promoting a specific book.

LocalBusiness (Supported by RankFrame)

Describes a physical business location with address, phone, hours, and geographic coordinates. Rich results: Business Knowledge Panel, Google Maps integration, local pack listings.

Product (Supported by RankFrame)

Describes a product for sale, including price, availability, reviews, and brand. Rich results: price, availability badge, and star ratings in standard search results.

FAQPage (Supported by RankFrame)

Marks up a page that contains a list of question-and-answer pairs. Google stopped showing FAQ rich results on 7 May 2026, but the schema is still valid and AI search reads it.

HowTo

Describes a step-by-step guide or tutorial. Google stopped showing HowTo rich results in September 2023, so RankFrame does not build HowTo schema.

BreadcrumbList (Supported by RankFrame)

Describes the hierarchical path from homepage to the current page. Rich results: breadcrumb trail displayed below the page title in search results.

Always validate your schema before publishing using Google’s Rich Results Test or the Schema.org Validator. RankFrame supports Article and BlogPosting, Product, Event, Recipe, JobPosting, Course, VideoObject, LocalBusiness, FAQPage, Organization, ProfilePage, Book, BreadcrumbList and more.

How RankFrame Solves the Framer Schema Problem

RankFrame is the only native SEO plugin built specifically for Framer. It lives inside the Framer editor as a plugin, which means you never need to leave the canvas to manage schema. Everything happens through a visual interface, no JSON-LD knowledge required.

Schema on Every Page

Inside the RankFrame plugin, open Optimise, then Schema. RankFrame adds its Schema component to your pages, invisible on your site, and you can add free schema to every page in one go, built from each page’s title, description and address. When you want more, Add AI schema to all pages reads each published page and adds every schema type it supports, for 3 credits a page, only when it adds something. Check each page with See it like Google, use Fix to fill missing fields, then publish your Framer site. No manual JSON, no risk of syntax errors, no template maintenance.

Schema for CMS Collections

For CMS sites, RankFrame adds one schema field to each collection. Schema built from your CMS fields is free, and AI schema uses 2 credits an item, only when it adds something. This is particularly useful for Framer CMS sites where a blog collection might have 50 or 100 posts, and it works with your sitemap as it is.

Schema Types Currently Supported

Schema Type

Status

Best For

Organization

Available

Business homepages, agencies

Person

Available

Portfolios, personal brands

Article

Available

Editorial content

BlogPosting

Available

Blog posts

TechArticle

Available

Technical guides, documentation

NewsArticle

Available

News and press content

Service

Available

Service pages

Restaurant

Available

Food service businesses

Book

Available

Book landing pages

HowTo

Not built (Google ended HowTo rich results)

Tutorials, guides

FAQPage

Available

FAQ sections

Product

Available

Product and pricing pages

LocalBusiness

Available

Local businesses

BreadcrumbList

Available

All internal pages

How to Validate Schema Markup Before Going Live

Adding schema markup that contains errors is, in practical terms, the same as adding no schema at all. Google will silently ignore malformed or incomplete JSON-LD. Validation is not optional, it should be the final step every time you add or update schema on any Framer page.

Google’s Rich Results Test

The Rich Results Test is Google’s official tool for checking whether a page’s structured data qualifies it for specific rich result types. Enter a URL or paste raw HTML. The tool shows detected schema types, which fields are present, which are missing, and whether the page is eligible for each rich result format.

Common Schema Errors on Framer Sites

Error

Cause

Fix

JSON parse error

Missing comma, trailing comma, or unescaped quote in the JSON-LD block

Use a JSON linter or let RankFrame generate the script to guarantee valid syntax

Missing required field

A property required for rich results eligibility is absent

Add the required property; check Google’s rich result documentation for each type

Invalid date format

Date not in ISO 8601 format (YYYY-MM-DD)

Ensure all date values use the ISO 8601 format

Logo URL not accessible

The URL referenced in logo.url returns a 404 or requires authentication

Use a publicly accessible absolute URL for all image references

Schema injected in body instead of head

Custom code pasted in Framer’s body section rather than head

Ensure JSON-LD is placed in the Head custom code field in Framer page settings

Schema Markup Strategy for Framer Sites

Priority 1, Establish Entity (All Framer Sites)

Every Framer site should start here regardless of type or size. Add Organization or Person schema to your homepage first. This is the single highest-leverage schema action because it establishes your site’s core identity for Google.

Priority 2, Mark Up Your Primary Content Type

Once entity schema is in place, add schema to your primary content pages: BlogPosting or Article on every blog post, Service schema on each service page, LocalBusiness on the homepage or contact page for local businesses.

Priority 3, Add Navigation and Rich Result Enhancers

After primary content schema is complete, add BreadcrumbList to all internal pages and FAQPage to any page with a Q&A section.

Schema for Framer CMS Sites

Framer CMS sites present a unique challenge: you may have dozens or hundreds of dynamic pages generated from a collection. Framer’s page-level custom code does not apply to CMS collection item pages by default. RankFrame solves this with one schema field per collection: schema built from your CMS fields is free, and AI schema reads each item’s published page for 2 credits an item, so every item in your sitemap gets its own schema.

Schema and multi-language sites

Schema follows each language: use Translate schema in Framer Localization to build each language’s schema: free when built from that language’s page details, or 3 credits a page per language with AI.

Google has retired several rich results since 2023, see Which Rich Results Does Google Still Show in 2026?. For CMS collections, see Schema for Every Framer CMS Item.

Manual vs. Automatic: Which Should You Use?

Factor

Manual (Custom Code)

RankFrame (Automatic)

Setup time

Fast for 1-2 pages

Fast for any number of pages

Maintenance

Manual update required on every content change

Rebuild when a page changes, then publish

CMS pages

Cannot individualize per CMS item

Per-item schema through the collection’s schema field

Duplicate risk

High if not tracked carefully

None (one schema per page, replaced on rebuild)

Schema types supported

Any (you write the JSON)

Article, Product, Event, Recipe, JobPosting, Course, LocalBusiness, FAQPage and more

JSON knowledge needed

Yes

No

Validation built in

No (use external tools)

Yes (See it like Google, with required and recommended fields)

Cost

Free

Paid plugin (7-day free trial)

Pitfalls of Manual JSON-LD Injection in Framer

Manual JSON-LD injection in Framer is viable for simple sites, but there are several pitfalls that cause problems for real-world implementations. Knowing these in advance saves significant debugging time.

Pitfall 1: Duplicate schema after republishing

This is the most common issue. If you paste a JSON-LD block into the Custom Code field, then later update the schema by pasting a new version, you may end up with two versions of the same schema type in the page head if you forgot to remove the old one. Google may process one, ignore one, or flag both as conflicting. Always view source after publishing to count your schema blocks.

Pitfall 2: Schema not updating when content changes

Static JSON-LD you paste into Custom Code does not update when you change the page’s content. If you change the headline of a blog post, update the article date, or switch authors, the schema still reflects the old values until you manually edit the Custom Code field. Over time, stale schema values create discrepancies between what Google sees in structured data and what users see on the page, which can reduce the quality score of your structured data.

Pitfall 3: Invalid JSON syntax

JSON has strict syntax requirements: every string must be in double quotes, trailing commas are not allowed, and the structure must be perfectly nested. A single syntax error in a JSON-LD block causes the entire schema block to fail silently. Googlebot will not report this as an error in the crawl report. You only discover it when you run the URL through the Rich Results Test and see nothing detected.

Before pasting JSON-LD into Framer, validate it at jsonlint.com to catch syntax errors. This takes 30 seconds and prevents hours of debugging.

Pitfall 4: Site Settings vs. Page Settings confusion

Framer has two Custom Code fields: one in Site Settings (applies to every page) and one in Page Settings (applies to a single page). Organization schema belongs in Site Settings, since it describes the overall brand. Article schema for a specific post belongs in that post’s Page Settings. Mixing these up results in Organization schema appearing on every page (harmless but redundant) or Article schema from one post appearing on all pages (actively harmful).

Pitfall 5: Forgetting to publish after saving Custom Code

This sounds obvious, but it trips up many Framer users. Changes to Custom Code are saved in the Framer editor but do not go live until you publish. If you add schema to a page and immediately test it with the Rich Results Test using the live URL, the schema will not be detected because the publish step has not happened yet. Always publish before testing.

Pitfall 6: Wrong content type for Custom Code

Framer’s Custom Code field accepts raw HTML, including script tags. The JSON-LD must be wrapped in a script tag with type=”application/ld+json”. Pasting just the JSON object without the script tag wrapper will not produce a valid schema block. Framer will not warn you about this. The JSON will appear as raw text in the page source rather than a recognized schema block.

Related features

Schema: Add schema to every page and CMS item, and see it like Google.

Frequently asked questions

Does Framer support schema markup natively?

Framer does not have a native schema markup UI. You can add JSON-LD scripts manually via Custom Code in page settings, but Framer provides no form-based interface, no field validation, and no automation for schema. RankFrame fills this gap by adding schema to every page and CMS item from inside the Framer editor.

What is the difference between JSON-LD and microdata for schema?
Which schema types does RankFrame currently support?
Can I add schema markup to Framer CMS pages?
Will adding schema markup improve my Framer site's Google rankings?
How do I validate schema on a Framer site?
What is the most important schema type for a Framer portfolio or agency site?
Can RankFrame generate schema for every page on my site?

Put this guide to work in Framer

RankFrame handles meta tags, schema, alt text and Google indexing from inside the Framer editor. Try every feature free for 7 days.