Schema markup is the structured data code embedded in your website that tells search engines and AI engines exactly what your business does, who it serves, and how it works. Most websites have none of it. The ones that do consistently outperform competitors on both Google rich results and AI citations.
Here is what schema is, why it matters, and copy-paste examples for the schemas your site probably needs.
What schema markup is
Schema is a vocabulary developed by Schema.org (a collaboration between Google, Microsoft, Yahoo, and Yandex) for describing web content in a machine-readable way. The most common implementation is JSON-LD: a small block of JSON code embedded in the <head> of a page.
Without schema, search engines have to infer what your page is about from prose. With schema, they know explicitly.
A simplified example:
With schema: a structured block of JSON that explicitly says: type = Dentist, name = X, address = Y, services = [Z, A, B], opening hours = C. Google knows exactly what it is looking at.
Why schema matters in 2026
1. Rich results on Google
Schema enables rich results: enhanced search listings with star ratings, FAQ dropdowns, recipe details, event dates, product prices, and more. Rich results typically get 30 to 100% higher click-through rates than standard blue-link results.
2. AI engine understanding
ChatGPT, Perplexity, Claude, and Google AI Overviews all parse structured data to understand what businesses do. Schema is one of the strongest signals an AI engine has for confidently citing a business in an answer.
3. Knowledge Graph entry
For brands, schema is a key signal toward getting a Knowledge Graph panel in Google search (the box that appears on the right side for known entities). The Knowledge Graph is built from structured data, including yours.
4. Local SEO
LocalBusiness schema is the single biggest on-page signal for local rankings outside of Google Business Profile. Without it, you are missing a major local ranking factor.
The schemas your site probably needs
1. Organization schema (homepage and most other pages)
Describes your business as an entity. Goes on the homepage and inherits across the site.
Critical fields:
- name: official business name
- alternateName: brand variations (rank-day, rank day, etc.)
- url: canonical homepage URL
- logo: URL to logo image (recommend 1080×1080 or larger)
- description: 2 to 3 sentence summary
- founder: the founder's name
- foundingDate: year founded
- sameAs: array of social profile URLs (LinkedIn, Twitter, etc.)
- contactPoint: phone, email, customer service hours
2. LocalBusiness schema (for businesses with physical locations or service areas)
Extends Organization with location-specific fields:
- address (streetAddress, addressLocality, postalCode, addressCountry)
- geo (latitude, longitude)
- openingHoursSpecification (per day)
- priceRange ($ to $$$$)
- areaServed (cities or regions served)
- telephone
For specific business types, use the more specific subtype. Dentist instead of LocalBusiness for a dental clinic. LegalService for a law firm. Restaurant for a restaurant. Schema.org has hundreds of specific types.
3. Service schema (for each service page)
Apply on each service page describing what that page covers.
- serviceType: the specific service
- provider: reference to your Organization
- areaServed: where the service is available
- description: what the service includes
- offers: pricing if applicable
4. FAQPage schema (on FAQ pages and pages with Q&A sections)
Marks up question-and-answer content so Google can show the questions as expandable rich results.
Each Q&A pair becomes a Question entity with an acceptedAnswer.
5. Article schema (on every blog post)
Identifies the page as an article with publication metadata.
- headline: post title
- description: post description
- datePublished, dateModified
- author: Person object with name
- publisher: Organization object
- mainEntityOfPage: URL of the post
6. BreadcrumbList schema (on all interior pages)
Shows the page hierarchy. Helps Google display breadcrumb navigation in search results.
7. Product schema (on product or pricing pages)
For e-commerce products, but also relevant for service businesses with productised offerings.
- name, description, image
- offers (Offer object with price, priceCurrency, availability)
- aggregateRating (if you have reviews to surface)
How to add schema to your site
If you use WordPress
Plugins handle most schema. Recommended: RankMath (free), Yoast SEO (free), or Schema Pro (paid). Configure them to apply the right schemas to the right page types.
Drawback: plugins often inject schema after JavaScript loads, which some tools cannot detect even though Google can read it.
If you use Webflow
Schema goes in the <head> via custom code per page. Webflow's CMS Collection variables can populate the JSON-LD dynamically.
If you use Next.js (like Rankday)
Inject JSON-LD via a <script type="application/ld+json"> tag in the layout or page component. Use template strings or JSON.stringify to keep the schema typed and maintainable.
If you build manually
Add the JSON-LD block to the <head> of each page. Many developers prefer to centralise it in a template that pulls dynamic data per page.
How to validate schema
Two tools to test your schema:
- Google Rich Results Test: at search.google.com/test/rich-results. Tells you if your schema is valid and what rich results it qualifies for.
- Schema.org Validator: at validator.schema.org. Validates schema against the broader specification, not just Google's subset.
Run every schema through both. Fix any errors before relying on the markup to drive results.
Common schema mistakes
- Schema doesn't match visible content. If your schema says "ratings: 4.9 stars based on 247 reviews" but those reviews are not visible on the page, Google will eventually penalise you.
- Wrong type used. Marking a service page as a Product, or vice versa. Use the most specific applicable type.
- Missing required fields. Some schema types require specific fields. Missing them invalidates the markup.
- Schema applied to wrong pages. FAQPage schema on a service page that does not have an FAQ section. Article schema on a homepage. Mismatches confuse search engines.
- Fake reviews schema. Schema marking up reviews that do not actually exist. Detected by Google and results in a manual penalty.
What Rankday does with schema
Every Rankday-built site includes the full schema stack from day one:
- Organization or LocalBusiness on the homepage and layout
- WebSite schema for brand entity recognition
- Service schema on each service page
- FAQPage schema on FAQ pages
- Article schema on all blog posts
- BreadcrumbList schema on interior pages
- Person schema for the founder where appropriate
Schema is part of the technical foundation, not an add-on. We apply it before any content goes live so search engines and AI engines understand your business from the first crawl. See the 90-day breakdown or how schema feeds into AI citation.