Schema Markup for Business Websites in India: Types, JSON-LD Examples & Testing Guide (2026)

When someone searches for a business, product, service, or useful information on Google, the search engine needs to understand what each website page represents.
A page may contain a company's name, address, services, products, contact information, reviews, or articles. Although search engines can interpret much of this information from page content, website owners can provide additional context through structured data.
This is where schema markup becomes useful.
Schema markup for business websites helps search engines understand the entities and information represented on a page. When implemented correctly, certain structured data types can also make eligible pages appear with enhanced search features, such as breadcrumbs, product information, or business details.
However, schema markup is frequently misunderstood. Adding structured data does not automatically improve rankings, guarantee rich results, or make a website appear in AI-generated answers.
In this guide, we explain how schema markup works, which types are useful for Indian businesses, how to implement JSON-LD examples, and how to test structured data correctly in 2026.
1. What Is Schema Markup?
Schema markup is structured data added to a website to describe the meaning of its content in a format that search engines and other systems can understand.
It uses vocabulary from Schema.org, a collaborative initiative that provides standard definitions for describing businesses, people, products, services, articles, events, and other entities.
For example, a business website may display the following information:
- Business name: Example Digital Solutions
- Website: https://example.com
- Email: contact@example.com
- Services: Website development and SEO
- Logo: A company logo image
A search engine can read the visible text, but structured data provides additional machine-readable information about the business and its properties.
Schema markup can describe:
- Organisations and businesses.
- Local business locations.
- Products and offers.
- Articles and blog posts.
- Website navigation.
- Events.
- People and authors.
- Other supported content types.
The objective is to describe the actual content accurately, not to add keywords or promotional claims that are not supported by the page.
2. How Does Schema Markup Work?
Schema markup uses structured properties to explain what a website contains.
For example, consider a business homepage.
Without structured data, search engines need to interpret the page's HTML and visible content to understand the business.
With appropriate Organization markup, the website can explicitly identify:
- The organisation's name.
- Its website URL.
- Its logo.
- Its contact details.
- Its social media profiles.
- Other relevant organisational information.
This provides a clearer description of the entity represented by the website.
What is JSON-LD?
JSON-LD stands for JavaScript Object Notation for Linked Data.
It is a format for expressing structured data using JSON.
Google recommends JSON-LD as a format for structured data because it can be added separately from the visible HTML content.
A typical JSON-LD block looks like this:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Digital Solutions",
"url": "https://example.com"
}
</script>
This example identifies an organisation and its website.
The information should accurately represent the business and be consistent with the content visitors can see.
Common formats for structured data
There are three commonly used formats:
1. JSON-LD
A separate script block containing structured data. It is generally the easiest format to maintain.
2. Microdata
Structured data added through HTML attributes within the visible page elements.
3. RDFa
A format that uses HTML attributes to describe relationships and structured information.
For most modern business websites, JSON-LD is a practical starting point.
3. Why Is Schema Markup Important for Business Websites?
Schema markup can help search engines interpret website content and determine whether a page is eligible for supported search enhancements.
It is useful for several reasons.
1. Helps search engines understand your business
Organization markup can identify the business name, logo, website, and relevant contact information.
This can help Google understand and distinguish your organisation from other entities with similar names.
2. Makes eligible pages suitable for rich results
Certain structured data types can support enhanced search appearances.
Examples include:
- Product information.
- Breadcrumb navigation.
- Article information.
- Local business details.
- Review snippets for eligible content.
Eligibility does not mean that Google will necessarily display the enhancement.
3. Provides clearer information about website pages
Different pages have different purposes.
For example:
- Homepage: Represents the organisation.
- Service page: Explains a service.
- Product page: Describes a product.
- Blog article: Provides editorial information.
- Contact page: Provides contact information.
Structured data can describe these page types more clearly.
4. Supports a better technical SEO foundation
Schema markup is one component of technical SEO.
It should work alongside:
- Crawlable website content.
- Proper page structure.
- Internal linking.
- Correct canonical URLs.
- XML sitemaps.
- Mobile usability.
- Website performance.
It should not be treated as a replacement for these fundamentals.
4. Types of Schema Markup Every Business Should Understand
Not every website needs every schema type.
The appropriate structured data depends on what the business offers and what each page contains.
Here are some important types to understand.
1. Organization Schema
Organization schema describes a company, agency, brand, or other organisation.
It is generally appropriate for a homepage or a page that describes the organisation.
It can include:
- Business name.
- Website URL.
- Logo.
- Description.
- Contact information.
- Social media profiles.
- Legal name, where applicable.
Example use case:
A digital agency wants to help search engines understand its official name, website, logo, and online profiles.
2. LocalBusiness Schema
LocalBusiness schema describes a business with a relevant physical business location.
It can provide information such as:
- Business name.
- Physical address.
- Telephone number.
- Opening hours.
- Geographic coordinates.
- Website URL.
- Other relevant business details.
Google recommends using the most specific LocalBusiness subtype that accurately describes the business.
For example, a restaurant, dental clinic, or hair salon may use a more specific subtype when appropriate.
Important: Do not invent an address or use an inaccurate location just to qualify for LocalBusiness markup. Google's LocalBusiness rich-result documentation requires a business name and address. Businesses operating without an eligible physical location should not fabricate one. Organization markup may be more appropriate for describing their business identity.
3. Article Schema
Article schema describes editorial content published on a website.
It is relevant to:
- Blog posts.
- News articles.
- Guides.
- Editorial publications.
Common properties include:
- Headline.
- Image.
- Author.
- Publication date.
- Modification date.
- Publisher.
For a business blog, Article or BlogPosting markup can help search engines understand the content and its publication details.
4. BreadcrumbList Schema
Breadcrumb schema describes a page's position within a website hierarchy.
For example:
Home → Blog → SEO Guide
Breadcrumbs help represent the relationship between the homepage, category, and individual article.
Google supports breadcrumb structured data for eligible search appearances.
5. Product Schema
Product schema describes products offered for sale or reviewed on a website.
Depending on the page and its purpose, it can include:
- Product name.
- Description.
- Image.
- Brand.
- Price.
- Availability.
- Reviews.
- Ratings.
Product structured data is particularly relevant to e-commerce businesses.
Google has different requirements for product snippets and merchant listings. Choose the format that matches the actual page and purchasing experience.
6. Service Schema
Service is a Schema.org type that can describe services offered by a business.
For example:
- Website development.
- SEO services.
- Mobile application development.
- Digital marketing.
- API integration.
It can help describe the subject of a service page, but it does not automatically qualify the page for a dedicated Google rich result.
Use it only when it accurately describes the visible service information.
7. Person and ProfilePage Schema
Person schema describes an individual, such as an author, professional, or team member.
ProfilePage markup can describe a page focused on a particular person or organisation profile.
These types may be relevant to websites that publish author profiles, professional biographies, or team information.
5. Schema Markup Examples: Practical JSON-LD Code
The following examples demonstrate how structured data can be implemented.
They are templates, not ready-to-publish markup. Replace all example details with accurate information from the actual website.
Example 1: Organization Schema
Use Organization markup to describe a business.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Digital Solutions",
"url": "https://example.com/",
"logo": "https://example.com/images/logo.png",
"description": "Digital solutions and website development services.",
"email": "contact@example.com",
"sameAs": [
"https://www.linkedin.com/company/example/",
"https://www.instagram.com/example/"
]
}
</script>
What to customise:
- Replace the example business name.
- Add the actual website URL.
- Use a publicly accessible logo URL.
- Add a genuine business description.
- Include only official social media profiles.
- Remove properties that do not apply.
Do not add a physical address unless it is accurate and appropriate to publish.
Example 2: LocalBusiness Schema
For a business with an eligible physical location, LocalBusiness markup may be appropriate.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Example Dental Clinic",
"url": "https://example.com/",
"telephone": "+91-XXXXXXXXXX",
"address": {
"@type": "PostalAddress",
"streetAddress": "Example Street",
"addressLocality": "Vadodara",
"addressRegion": "Gujarat",
"postalCode": "390001",
"addressCountry": "IN"
}
}
</script>
What to customise:
- Actual business name.
- Real business address.
- Valid phone number.
- Correct website URL.
- Appropriate LocalBusiness subtype, if one exists.
The address above is illustrative. Do not publish it as the address of a real business.
Example 3: Article Schema
Use Article or BlogPosting markup for a blog article.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Schema Markup for Business Websites in India",
"description": "A practical guide to structured data and JSON-LD.",
"image": [
"https://example.com/images/schema-markup-guide.webp"
],
"datePublished": "2026-11-16",
"dateModified": "2026-11-16",
"author": {
"@type": "Organization",
"name": "Example Digital Solutions"
},
"publisher": {
"@type": "Organization",
"name": "Example Digital Solutions",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/images/logo.png"
}
},
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/blog/schema-markup-guide"
}
}
</script>
What to customise:
- Actual article headline.
- Accurate description.
- Publicly accessible cover image.
- Correct publication and modification dates.
- Genuine author or publisher.
- Canonical article URL.
Do not use the current date as the publication date if the article was published earlier.
Example 4: BreadcrumbList Schema
Breadcrumb markup can describe the hierarchy of an article.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://example.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Blog",
"item": "https://example.com/blog"
},
{
"@type": "ListItem",
"position": 3,
"name": "Schema Markup Guide",
"item": "https://example.com/blog/schema-markup-guide"
}
]
}
</script>
Make sure the breadcrumb hierarchy reflects the actual navigation and page structure.
Example 5: Product Schema
For a product page, the markup may include product details and an offer.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Example Product",
"image": [
"https://example.com/images/example-product.webp"
],
"description": "Description of the actual product.",
"offers": {
"@type": "Offer",
"url": "https://example.com/products/example-product",
"priceCurrency": "INR",
"price": "1999",
"availability": "https://schema.org/InStock"
}
}
</script>
Use accurate product information. Price, currency, availability, and other offer details must match the actual product page.
Google's product rich-result requirements differ depending on whether the page is a product snippet or a merchant listing. Review the relevant documentation before deployment.
6. Where Should You Add Schema Markup on Your Website?
Schema should be added to the page or pages that it describes.
A practical implementation plan for a typical business website looks like this:
Homepage
Consider:
- Organization schema.
- WebSite information, where appropriate.
- LocalBusiness schema if the business genuinely qualifies.
About page
Consider:
- Organization information.
- Relevant Person or ProfilePage information, where appropriate.
Service pages
Consider:
- WebPage markup.
- Service descriptions using appropriate Schema.org types.
- BreadcrumbList markup where the page has a breadcrumb hierarchy.
Product pages
Consider:
- Product schema.
- Offer information.
- Merchant listing properties where eligible.
Blog posts
Consider:
- Article or BlogPosting schema.
- Author information.
- Publisher information.
- BreadcrumbList markup.
Contact page
Provide clear visible contact information and ensure it matches the relevant business information represented elsewhere on the website.
Do not copy the same complete schema block onto every page without considering what each page actually represents.
7. How to Add Schema Markup to WordPress Websites
WordPress users have several options for implementing structured data.
Method 1: Use an SEO plugin
Some WordPress SEO plugins provide structured data functionality.
Depending on the plugin and configuration, they may generate:
- Organization schema.
- Article schema.
- Breadcrumb markup.
- Website information.
- Product markup.
Review the generated output instead of assuming that every default setting is correct.
Method 2: Use a dedicated schema plugin
Dedicated schema plugins can provide additional control over schema types and properties.
Before installing one, check:
- Whether it supports the required schema types.
- Whether it generates valid JSON-LD.
- Whether it conflicts with your existing SEO plugin.
- Whether it allows page-specific configuration.
- Whether it receives security and compatibility updates.
Avoid installing multiple plugins that generate duplicate or conflicting structured data.
Method 3: Add JSON-LD manually
Developers can add JSON-LD directly to the website's HTML.
For WordPress, this may be done through:
- A custom theme implementation.
- A suitable custom plugin.
- A controlled code-injection solution.
- A page-specific implementation.
If you add custom code, make sure it is not overwritten by theme updates and does not duplicate markup generated by another plugin.
Method 4: Implement schema through custom development
For React, Next.js, and other custom websites, JSON-LD can be generated from reliable business and page data.
For example, a website can generate Article markup from its CMS fields.
Important considerations include:
- Use accurate source data.
- Generate the correct schema type for each page.
- Escape user-generated content safely.
- Avoid invalid JSON.
- Ensure the markup appears in the rendered page.
- Prevent duplicate schema blocks.
- Keep structured data consistent with visible content.
For custom websites, schema implementation should be part of the development and SEO planning process.
8. How to Test and Validate Schema Markup
Adding JSON-LD is not enough. You must test whether the website actually serves valid structured data.
Use these tools.
1. Google Rich Results Test
This tool checks whether a page contains structured data that Google supports for rich results.
It can help identify:
- Supported structured data types.
- Missing required properties.
- Invalid values.
- Critical errors.
- Warnings.
A page can contain valid Schema.org structured data without qualifying for a Google rich result. That distinction matters.
2. Schema.org Validator
This tool validates structured data against the Schema.org vocabulary.
It is useful for checking types and properties that may not be eligible for a Google rich result.
3. Google Search Console
Search Console can help website owners monitor supported rich-result reports, indexing, and search performance.
After publishing structured data:
- Open URL Inspection.
- Enter the live page URL.
- Check whether Google can access the page.
- Review the indexed or live test information.
- Inspect any available structured data enhancements.
- Request indexing when appropriate.
Remember that Google may take time to crawl and process changes.
4. Test the live website
Do not test only the code copied from your editor.
Test the actual published page because plugins, caching, rendering, and deployment settings may change the final output.
Check a sample of each important page template before applying the implementation sitewide.
9. Common Schema Markup Mistakes to Avoid
Incorrect structured data can be ignored by search engines or make pages ineligible for certain rich-result features.
Avoid these mistakes.
1. Adding inaccurate business information
The business name, contact details, address, and other properties should represent the actual business.
Never invent an office address to qualify for LocalBusiness markup.
2. Using schema types that do not match the page
Do not mark a blog article as a Product or a business homepage as an unrelated type.
Choose the type that accurately describes the content.
3. Marking up information that visitors cannot see
Structured data should represent the page's actual content.
Do not add fake prices, ratings, reviews, opening hours, or other details that are not supported by the visible page.
4. Adding fake review ratings
Do not create fictional ratings or mark up self-serving reviews to manipulate search appearance.
Google has specific review-snippet policies, including restrictions on self-serving reviews for LocalBusiness and Organization.
5. Duplicating schema markup
Multiple plugins or custom implementations may generate overlapping Organization, Article, or BreadcrumbList blocks.
Review the rendered page and establish which component or plugin is responsible for each type.
6. Ignoring required properties
Some Google rich-result features have required properties.
Check the official documentation for the exact schema type rather than copying code from an unrelated tutorial.
7. Treating warnings as automatic failures
A warning does not always mean that structured data is invalid.
Understand whether a property is required, recommended, or simply optional.
8. Forgetting to update structured data
If a product price, business phone number, logo, article title, or publication date changes, review the corresponding structured data.
It should not remain inconsistent with the visible page.
10. Does Schema Markup Improve Google Rankings?
This is one of the most common questions about structured data.
The direct answer is that adding schema markup is not a guaranteed ranking improvement.
Google explains that structured data can help it understand page content and make pages eligible for rich results. However, eligibility does not guarantee that a rich result will appear.
Schema markup should therefore be treated as a way to describe content and support eligible search appearances—not as a shortcut to higher rankings.
Your broader SEO strategy should still focus on:
- Helpful and relevant content.
- Proper website structure.
- Crawlability and indexability.
- Relevant internal links.
- Good page experience.
- Appropriate technical SEO.
- Genuine business information.
- Quality backlinks and reputation.
For more information, read Google Search Console in 2026: 12 Reports Every Business Website Should Monitor.
11. Does Schema Markup Help with AI Overviews and AI Search?
Structured data is often promoted as a special technique for appearing in AI-generated search results.
That claim needs to be treated carefully.
Google's current guidance states that there is no special schema.org markup required to appear in AI Overviews or AI Mode.
The same foundational SEO principles remain relevant:
- Make important content accessible to search engines.
- Publish helpful, reliable information.
- Use clear page structure.
- Maintain appropriate internal links.
- Keep structured data consistent with visible content.
- Ensure the website can be crawled and indexed.
Schema markup remains useful as part of a broader technical SEO implementation, especially for supported search features.
It should not be sold as an AI ranking hack.
Read our guide: How to Get Your Business Found on Google & AI Search in 2026.
12. Important 2026 Update: FAQ Schema and Google Rich Results
Older schema tutorials frequently recommend FAQPage markup as a way to display expandable questions and answers directly in Google Search.
That advice is outdated if it promises FAQ rich results.
Google stopped showing FAQ rich results in Search starting 7 May 2026 and subsequently removed the related feature documentation.
This does not mean that you should remove useful FAQ sections from your website.
FAQs can still help visitors understand products, services, pricing, and business processes.
However, do not implement FAQ schema expecting the former Google FAQ rich-result appearance or a ranking advantage.
Always check Google's current supported structured data gallery before choosing a schema type.
13. Schema Markup Checklist for Business Websites
Before publishing structured data, use this checklist.
Business information
- Business name is accurate.
- Website URL is correct.
- Logo URL is publicly accessible.
- Contact information is accurate.
- Social media profiles are official.
- Physical address is included only when appropriate and genuine.
Page-specific structured data
- Organization markup is relevant to the business page.
- LocalBusiness markup is used only when applicable.
- Article markup describes actual blog content.
- Product markup matches actual product information.
- Breadcrumb markup reflects the page hierarchy.
- Service descriptions accurately represent visible content.
Technical validation
- JSON-LD syntax is valid.
- Required properties are present for the intended rich-result feature.
- Structured data matches visible page content.
- No duplicate or conflicting markup is generated.
- Google Rich Results Test has been checked.
- Schema.org Validator has been checked where relevant.
- The live page has been inspected.
- Search Console is monitored after deployment.
Ongoing maintenance
- Business details are reviewed after changes.
- Product information remains accurate.
- Article dates are maintained correctly.
- Broken image URLs are corrected.
- Plugin and theme updates are reviewed.
- Structured data is retested after major website changes.
Frequently Asked Questions
1. What is schema markup in SEO?
Schema markup is structured data added to a website to describe its content using standard vocabulary from Schema.org. It helps search engines interpret information about businesses, products, articles, services, and other entities.
2. Which schema markup is best for a business website?
It depends on the website. Organization markup is useful for describing a business entity, LocalBusiness is relevant for eligible physical business locations, Article is useful for blog posts, and BreadcrumbList describes website navigation. E-commerce websites may also benefit from Product markup.
3. Is JSON-LD better than Microdata?
JSON-LD is generally the recommended starting point for Google structured data because it can be maintained separately from the visible HTML content. Microdata and RDFa are also structured data formats.
4. Does schema markup guarantee rich snippets?
No. Valid structured data can make a page eligible for certain rich results, but Google decides whether to display them. There is no guarantee.
5. Can I add multiple schema types to one page?
Yes, when each type accurately describes the content and the relationships between the entities are represented correctly. Avoid unnecessary duplication and conflicting markup.
6. Does every business need LocalBusiness schema?
No. LocalBusiness markup is intended for businesses with relevant physical business information. Do not invent an address to use it. Organization markup may be more suitable for businesses that operate online without an eligible physical location.
7. Can I add schema markup without coding?
Yes. Some CMS plugins and structured data tools can generate JSON-LD without requiring manual coding. You should still inspect and validate the generated output.
8. Does schema markup help websites appear in AI Overviews?
Google does not require special schema markup for AI Overviews or AI Mode. Structured data remains useful for supported search features, while foundational SEO and helpful content remain important.
9. Is FAQ schema still useful in 2026?
FAQ content remains useful for visitors, but Google stopped showing FAQ rich results in Search from 7 May 2026. Do not add FAQ markup expecting the old expandable search-result feature.
10. How often should schema markup be checked?
Check it after major website updates, changes to business information, CMS or plugin changes, and new page templates. Also review Search Console reports and test important live URLs periodically.
Final Thoughts
Schema markup is a useful part of modern website development and technical SEO when it is implemented accurately.
For Indian businesses, the best approach is to begin with the information that matters most: business identity, relevant location details, website structure, products, services, and published content.
Choose the appropriate schema type for each page, use JSON-LD where practical, validate the implementation, and keep the structured data consistent with what visitors can actually see.
Do not add unnecessary markup just because a tutorial recommends it. A smaller, accurate implementation is better than a large collection of incorrect schema blocks.
Need help implementing schema markup on your business website?
Arctis Digital provides website development, SEO, technical optimisation, API integration, and custom web solutions.
Visit Arctis Digital or contact our team to discuss your website requirements.
Official References and Useful Resources
- Google Search Central – Understand How Structured Data Works
- Google Search Central – Organization Structured Data
- Google Search Central – Local Business Structured Data
- Google Search Central – Article Structured Data
- Google Search Central – Breadcrumb Structured Data
- Google Search Central – Structured Data Supported by Google
- Google Search Central – General Structured Data Guidelines
- Google Search Central – AI Features and Your Website
- Google Rich Results Test
- Schema.org Validator
Related Guides from Arctis Digital
- Google Search Console in 2026: 12 Reports Every Business Website Should Monitor
- How to Rank Your Business on Google Maps in 2026: Local SEO Guide
- How to Get Your Business Found on Google & AI Search in 2026
- Core Web Vitals for Business Websites in India: LCP, INP & CLS Guide (2026)
- Website Accessibility Checklist for Indian Businesses
- Website Development Agreement Checklist for Indian Businesses
