LocalBusiness Schema in 2026: JSON-LD Checklist for Delhi NCR Service Websites

Quick answer: LocalBusiness schema markup is structured data that describes a genuine business location and helps search engines interpret facts such as its name, address, contact details, website and opening hours. In 2026, service businesses should combine accurate LocalBusiness or Organization JSON-LD with appropriate Service and BreadcrumbList markup, validate it on the public page, and avoid claiming that schema guarantees Google Maps rankings or AI citations. For a business operating across Delhi, Noida, Gurugram or Ghaziabad, the markup must describe where it really operates, not invented offices.

Updated: 30 October 2026. This implementation guide focuses on the technical questions that a general local SEO strategy for Delhi businesses cannot cover in detail: which schema types to use, how to connect them, where to place the code, and what Google actually supports.

What is LocalBusiness schema, and does it improve local SEO?

Schema markup is a machine-readable description of information that people can also see on a webpage. LocalBusiness is a type from Schema.org. Google documents a specific set of LocalBusiness properties for eligible local business search features. It does not replace an accurate Google Business Profile, useful service pages, legitimate reviews or proximity to the searcher.

Think of schema as a consistency layer. If your contact page says that your office is in Nehru Place, your structured data should describe the same real office. If you visit customers in Noida but have no branch there, mark that as a genuine service area where relevant; do not add a fabricated Noida street address. This distinction matters for agencies, consultants, technicians, home-service providers and multi-location companies across Delhi NCR.

What changed in structured data guidance in 2026?

Two details matter when planning schema work today. First, Google deprecated FAQ rich results in May 2026 and removed the corresponding documentation in June 2026. You should still write helpful FAQs for readers and voice-style queries, but do not sell FAQPage markup as a way to obtain a Google FAQ rich result. Second, Google stopped showing breadcrumb trails in its mobile search result URL display in January 2025, while continuing to support breadcrumb markup for desktop results and page understanding. These are presentation changes, not reasons to abandon useful on-page answers or logical navigation.

Google’s documentation also distinguishes schema vocabulary from Google-specific search features. A valid Service type in Schema.org does not automatically mean Google offers a dedicated Service rich result. Likewise, valid markup does not guarantee enhanced snippets, indexing, ranking positions or visibility in AI answers.

Which schema types belong on which page?

Page	Appropriate markup	Purpose and caution
Home or about page	Organization or applicable LocalBusiness subtype	Define the real business entity once consistently; use the most specific legitimate type.
Physical office/contact page	LocalBusiness, PostalAddress, optional openingHoursSpecification	Use only verified public business information and an actual operating location.
Individual service page	Service with provider and areaServed; BreadcrumbList	Describe the service shown on the page; Service is vocabulary, not a guaranteed Google rich-result feature.
Educational blog article	BlogPosting or Article; BreadcrumbList	Use accurate headline, date, author and image if your frontend actually outputs them.
Separate real branch page	Location-specific LocalBusiness	Only for genuine branches with distinct real-world details, not doorway pages.
Visible FAQ section	Clear HTML questions and answers	Useful for users and answer engines; Google FAQ rich results are discontinued.

Step 1: verify the business facts before writing JSON-LD

Start with a simple source-of-truth sheet. Record the legal or public trading name, canonical website URL, real location, public phone number, opening hours, service categories and geographic coverage. Confirm each field against the website, signage, customer-facing documents and the actual Google Business Profile where applicable. A service-area business that hides its address on its profile should not expose a private residential address through schema merely to satisfy a template.

• Name: use the business’s actual public name, without adding search keywords.
• Address: use a genuine public operating address only when appropriate and accurate. Google documents address as required for LocalBusiness rich-result eligibility.
• Telephone: use the real public contact number, ideally in international format.
• URL: link to the correct canonical location or organization page.
• Hours: publish opening hours only when you can maintain them, including seasonal changes.
• Area served: describe areas where the service is actually available; do not imply branches exist everywhere.

If there is no suitable public location to describe, consider Organization and Service markup rather than inventing a PostalAddress. A legitimate service area is not a license to invent local offices.

Step 2: use a clean LocalBusiness JSON-LD example

The following is an illustrative template, not the verified details of Keshav Enterprises or another real company. Replace every example value, choose the most specific applicable subtype, and remove unsupported properties before publishing. The example is escaped as code so it will not be mistaken for live markup on this article.

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "@id": "https://example.com/#business",
  "name": "Example Service Company",
  "url": "https://example.com/",
  "telephone": "+91-XXXXXXXXXX",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "VERIFIED PUBLIC ADDRESS",
    "addressLocality": "New Delhi",
    "addressRegion": "Delhi",
    "postalCode": "VERIFIED PIN",
    "addressCountry": "IN"
  },
  "areaServed": [
    {"@type": "Place", "name": "Delhi"},
    {"@type": "Place", "name": "Noida"}
  ]
}

For a multi-location brand, a separate real branch may need its own unique entity identifier and contact details. Do not copy one branch’s phone, address and map coordinates across every city page. For an online-only consultancy without a customer-facing location, the Organization type may be a more accurate starting point.

Step 3: connect service pages to the real provider

A Service schema node can describe a specific service such as website development, technical SEO or AC repair. The useful properties include serviceType, provider and areaServed. Reuse the provider’s stable @id so the relationship is explicit. The example below describes a fictional service page; it does not promise a special Google result.

{
  "@context": "https://schema.org",
  "@type": "Service",
  "@id": "https://example.com/services/technical-seo/#service",
  "name": "Technical SEO Audit",
  "serviceType": "Technical SEO",
  "provider": {"@id": "https://example.com/#business"},
  "areaServed": [
    {"@type": "Place", "name": "Delhi NCR"}
  ],
  "url": "https://example.com/services/technical-seo/"
}

The page itself should explain what the service includes, who it suits, deliverables, location coverage, expected process and how a visitor can enquire. Schema cannot compensate for an empty landing page. If you are building those pages, review a proper technical and local SEO service scope before multiplying city pages.

Step 4: add BreadcrumbList to support clear site hierarchy

Breadcrumbs show where a page sits within your information architecture. On a typical service site, a visitor might follow Home → Services → Local SEO. The visible navigation and structured data should tell the same story. A sample list is:

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {"@type": "ListItem", "position": 1,
     "name": "Home", "item": "https://example.com/"},
    {"@type": "ListItem", "position": 2,
     "name": "Services", "item": "https://example.com/services/"},
    {"@type": "ListItem", "position": 3,
     "name": "Local SEO"}
  ]
}

Google’s mobile results no longer display breadcrumb trails in the visible URL element, but it still supports breadcrumb structured data for desktop. Keep breadcrumbs useful for human navigation rather than implementing them solely for a search snippet.

Step 5: avoid duplicate schema on WordPress, Elementor and Next.js

On a WordPress or Elementor site, first inspect what the theme and SEO plugin already output. Adding a second LocalBusiness node with different names or addresses can create conflicting information. Prefer one maintained organization identity and page-specific service or article data. Use a plugin’s documented structured-data settings or a controlled template implementation; do not paste scripts into every content block without checking the rendered result.

On a Next.js or React frontend backed by WordPress, the public React page is the page that Google crawls. Do not assume JSON-LD saved in the WordPress editor automatically appears in the Next.js HTML. Check the rendered source and ensure that the frontend outputs the intended JSON-LD with a stable @id, accurate canonical URL and visible content. If the frontend builds statically or caches data, the schema must update when the underlying page information changes. This is also why technical website development and SEO need to be coordinated.

Where a schema object is rendered dynamically, serialize trusted data safely and avoid introducing user-supplied HTML into a script block. For multiple pages, a central data source for the organization and service areas is easier to maintain than dozens of hand-copied fragments.

Step 6: validate what Google can actually fetch

There are two distinct checks. The Schema Markup Validator checks general Schema.org vocabulary. Google’s Rich Results Test checks supported Google search features. A Service node can validate as Schema.org vocabulary without appearing as a special Google rich-result type. Neither tool proves that Google has indexed the page.

1. Open the exact public, canonical URL in a browser without signing in.
2. Inspect the rendered HTML and confirm there is one accurate organization or business identity.
3. Run the Schema Markup Validator and resolve vocabulary errors.
4. Run Google’s Rich Results Test for supported features.
5. Use Google Search Console URL Inspection to check crawling, canonical selection and indexing status.
6. Compare the structured data with the visible page, Google Business Profile and contact details.
7. Recheck after changing addresses, business hours, service areas, URL structure or frontend templates.

If a page is not indexed, structured data alone is not the fix. Diagnose rendering, robots directives, canonicals, sitemaps and content quality first. Local schema is one component of the broader local SEO process.

Common LocalBusiness schema mistakes in Delhi NCR

• Fake locations: publishing a Delhi, Noida and Gurugram address when only one office exists.
• Wrong type: labeling every professional service as a storefront or restaurant.
• Contradictory details: different names, hours or phone numbers in HTML, structured data and business profiles.
• Unsupported ratings: adding invented star scores or self-serving review markup to manufacture rich snippets.
• Duplicate JSON-LD: separate plugins and hard-coded templates output conflicting business entities.
• Hidden claims: marking up services, branches or prices that visitors cannot find on the page.
• Wrong domain: WordPress backend URLs appear in the markup even though the canonical public site is React.
• FAQ expectations: promising FAQ rich results after Google’s 2026 retirement of that feature.

Does structured data help AI search, voice search or GEO?

Clear structured data can make business facts easier for systems to interpret, but no schema type guarantees a citation in an AI answer. AI-search readiness is better treated as an evidence problem: maintain a crawlable page, use accurate organization and service information, explain the service in plain language, show real location coverage, and keep public facts consistent. A voice-style question such as “Who offers technical SEO audits near Nehru Place?” needs a useful, accessible answer on the site, not a pile of repeated keywords.

Use descriptive headings, direct answers, useful comparisons and honest service boundaries. Keep your Google Business Profile accurate and ensure your Delhi local SEO foundation is sound. If you need technical help aligning a headless frontend with its metadata, request a website and SEO review.

Seven-day implementation checklist

1. Day 1: inventory live pages, existing schema and current Google Business Profile facts.
2. Day 2: confirm the real organization identity, public address, service areas and contact details.
3. Day 3: select the correct Organization or LocalBusiness subtype; establish a stable @id.
4. Day 4: implement service-specific nodes and meaningful breadcrumb navigation.
5. Day 5: test WordPress and the actual React frontend for duplicate or missing markup.
6. Day 6: validate the public URLs, fix mismatches and inspect canonical/indexability signals.
7. Day 7: document the owner of each data field and schedule checks after business or website changes.

Frequently asked questions

What is the best schema for a local service business?

Use the most specific accurate LocalBusiness subtype for a genuine public business location, or Organization when a location-based type would misrepresent the operation. Add Service markup on pages that explain individual services.

Does LocalBusiness schema make my company rank in Google Maps?

No. It can clarify business information but cannot guarantee Maps placement. Local results depend on relevance, distance and prominence, along with other signals.

Can I list Noida as an area served without an office there?

Yes, if you genuinely serve customers in Noida. Do not claim a Noida street address or separate branch that does not exist.

Is an address required for LocalBusiness rich results?

Google’s LocalBusiness documentation lists address as a required property for that feature. Do not invent or expose a private address merely to complete a schema template; choose markup appropriate to your actual business.

Should every service page repeat the same LocalBusiness JSON-LD?

Use one consistent business identity and reference it from relevant service nodes. Avoid conflicting duplicates emitted by multiple plugins or templates.

Do FAQ schema snippets still work in Google in October 2026?

Google deprecated FAQ rich results in May 2026. Keep visible FAQs because they help readers, but do not expect an FAQ rich-result display from FAQPage markup.

Is Service schema a guaranteed Google rich result?

No. Service is a Schema.org vocabulary type, not a promise of a dedicated Google rich-result feature. Validate both general vocabulary and Google-supported features separately.

Where should JSON-LD go on a headless WordPress and Next.js website?

It must appear in the public frontend page that search engines fetch, not only in the WordPress admin or REST API. Confirm it in rendered HTML alongside the correct canonical URL.

Official references and next step

This guide follows Google’s LocalBusiness documentation, Organization markup guidance, structured-data policies, Schema.org’s Service definition and Google Search’s 2026 documentation changelog. Verify the current documentation before deploying to production.

Need a schema audit for a Delhi NCR business? Keshav Enterprises can review the real website structure, public business facts, schema output, indexability and service-page architecture. Share your website and requirements for a practical review rather than a ranking guarantee.