"Please add structured data." If you've seen this instruction in Genview's improvement suggestions or site diagnosis and weren't sure what to do — this page is for you. We'll walk through what Schema is, why it matters, and how to add it, with concrete examples from the ground up.
What is Schema?
Schema is machine-readable description text that tells AI and search engines exactly what a page is about.
Say your site has a FAQ page. A human reader immediately understands it's a list of questions and answers. But AI and search engines can't always reliably determine from text alone whether a page is a FAQ, a column article, or a product description.
That's where Schema comes in. By adding Schema, you make it easier for AI and search engines to understand information like "This page is a FAQPage. The first question is X and the answer is Y."
The page humans read
Schema (machine-readable description)
FAQ Q. How much does it cost? A. From ¥11,800/month.
"This page is a FAQPage. The question is 'How much does it cost?' and the answer is 'From ¥11,800 per month.'"
← Read by humans
← Easier for AI to parse
Schema is written in a format called JSON-LD and embedded in the HTML of your page. It's invisible to visitors — only AI and search engines read it.
Why does Schema matter?
AI determines "who this company is, what they're strong at, and when to recommend them" from enormous amounts of information. Schema acts as your official introduction — helping AI make that determination more accurately.
Without Schema, AI reads your page text and interprets it on its own. It often gets things right, but ambiguous parts get filled in through inference. When those inferences are wrong, AI may introduce your brand in the wrong context or miss key information.
Without Schema
AI reads the text and makes its best guess about who you are. It often gets things right, but gaps get filled in through inference.
With Schema
"This company is an Organization providing a GEO SaaS tool. Their pricing is X and their FAQ covers Y." Structured information reduces AI's room for misinterpretation.
This matters for SEO too, but it's even more important for GEO. AI generates responses based on a holistic understanding of your brand — so providing accurate structured information has a direct impact on how AI recognizes and describes you.
What happens without Schema?
Your site won't be completely invisible without Schema. But these kinds of problems are more likely to occur.
Inconsistent company descriptions
Without Organization Schema, AI interprets your company from each individual page. If pages say different things, AI's understanding becomes inconsistent.
FAQ content less likely to be cited
Without FAQPage Schema, AI has a harder time recognizing content as question-and-answer pairs, reducing the chances your FAQ gets referenced in response to user questions.
Author expertise harder to communicate
Without Person Schema, it's harder for machines to understand who wrote the content and what expertise they bring. Schema helps communicate author information more clearly.
Service type harder to convey
Without SoftwareApplication or Service Schema, it becomes harder for AI to accurately understand whether you offer a SaaS product, consulting, or something else entirely.
Where does Schema go?
Schema is embedded in your page HTML as a <script type="application/ld+json"> block, placed inside the <head> or <body> tag.
Example (FAQPage Schema)
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "How much does it cost?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Plans start from ¥11,800/month (Standard plan)."
}
}]
}
</script>
Nothing is displayed to visitors. Only AI and search engines read it.
Add Schema per page
Organization Schema goes on your homepage, FAQPage Schema on your FAQ page, Article Schema on blog posts — each embedded in the relevant page's HTML. Multiple Schema types can be added to a single page.
How do you add Schema?
There are three main ways to add Schema.
Method
Best for
①
Paste directly into HTML
Anyone who can edit page HTML directly. WordPress users can add it via a Custom HTML block or by editing the theme's head section.
②
Deploy via GTM (Google Tag Manager)
Sites where direct HTML editing is difficult. GTM lets you deploy Schema to specific target pages. FAQPage, Article, Product, and similar types need to be scoped to the correct page types — not deployed site-wide.
③
Auto-generate with a tool and paste
Anyone who doesn't want to write code manually. Genview's structured data feature auto-generates JSON-LD based on your page information — copy, paste, and you're done.
If writing code yourself, refer to the official Schema.org specifications or use Genview's generation feature. After adding Schema, use Google's Rich Results Test to verify it's being read correctly.
Genview's Schema priority ranking
Schema.org has hundreds of Schema types, but you don't need all of them. From a GEO perspective, we recommend organizing priorities into the following four tiers.
An important note for GEO
Even Schema types that don't appear in Google's Rich Results may still be used by AI to understand page content. "Doesn't show in Rich Results = unnecessary" is not accurate from a GEO perspective. Schema priorities differ between SEO and GEO.
S Rank — Recommended for almost all sites
Schema
Target page
GEO purpose
Organization
All sites, company info, homepage
Identify the organization behind the site
WebSite
Homepage, site-wide
Identify the site's name and URL
WebPage
General pages
Identify a page's existence, name, and description
BreadcrumbList
Key pages except homepage
Clarify site hierarchy
Article / BlogPosting
Articles, columns
Identify article, author, publish date, and publisher
The foundation of GEO. Prioritize Organization, WebSite, BreadcrumbList, and Article above all. WebPage is a supporting Schema for general pages — use it alongside more specific types like FAQPage, Article, or SoftwareApplication based on the page's content.
A Rank — Strongly recommended for GEO, SaaS, and B2B sites
Schema
Target page
GEO purpose
SoftwareApplication
Product top page, feature pages
Identify as a SaaS tool
Service
Service overview pages
Define the services offered
FAQPage
FAQ pages, FAQ sections
Mark question-and-answer pairs explicitly
Person
Author pages, team pages, article bylines
Identify who wrote it and who is involved
DefinedTerm
Individual glossary entries
Define specialist terminology
DefinedTermSet
Glossary index pages
Identify the glossary as a whole
For a GEO tool like Genview, A Rank Schema is also important. SoftwareApplication, FAQPage, Person, and DefinedTerm in particular are worth adding.
B Rank — Recommended depending on page content
Schema
Target page
When to use
CollectionPage
Index pages, category pages
Article lists, feature lists, glossary lists
AboutPage
Company overview, team, mission
Company or operator description pages
ProfilePage
Individual profile pages
Detailed introduction of a single author or supervisor
Product
Pricing and plan pages
When explicitly presenting pricing and plans as a product
Offer
Pricing pages, plan introductions
When explicitly presenting price, free trial, or terms
Review / AggregateRating
Pages with published reviews
Only when actual reviews are visible on the page
Product and Offer can work for B2B SaaS, but there's risk if they don't match what's actually displayed on the pricing page. Review-type Schema should only be used when real reviews are visible on the page.
C Rank — No need to add unless applicable
Schema
Reason
HowTo
Rich Results value has declined; not essential from a GEO perspective either
Event
Only if you host seminars or webinars
VideoObject
Only if video is embedded on the page
LocalBusiness
Not needed unless you have a physical location or serve a local area
JobPosting
Only if you have active job listings on a recruitment page
Course
Not needed unless you offer educational courses
Using Schema for GEO with Genview
Schema matters — but figuring out which pages need which Schema types, then writing the correct code, takes real effort. Genview's structured data feature auto-generates JSON-LD based on your page information. Copy, paste, and it's done.
After generating, the verification feature shows errors and warnings, with a direct link to Google's Rich Results Test. "Which Schema is missing?" is answered by Site Diagnosis — so the full flow is: diagnose → generate → add → verify.