SEO & AIO/GEO

Schema Markup Guide: FAQPage, LocalBusiness and Service Schema

By Lokesh Narwara · 2026-10-23 · 5 min read

Schema markup is structured data that tells search engines and AI systems exactly what a page is about: who you are, what you offer, where you operate and which questions you answer. For service businesses, a handful of schema types cover most needs. This guide explains the types that matter, shows a simple example, and walks through how to add, test and maintain structured data without breaking Google's rules.

What is schema markup?

Schema markup uses a shared vocabulary from schema.org to label the information on a page in a machine-readable way. Google recommends the JSON-LD format, which is a block of code placed in the page that describes the content without changing how it looks. Search engines use it to understand your pages and, in some cases, to show enhanced results. AI systems can use the same clear facts when summarizing your business.

Schema does not directly raise rankings and it does not guarantee rich results, but it reduces ambiguity, and ambiguity is expensive in search.

The schema types most service businesses need

• Organization or LocalBusiness: your name, logo, address, phone, hours, social profiles and founders. Use ProfessionalService for agencies and consultants.
• WebSite: your site name and URL.
• Service: each service page, with its name, description, provider and the area you serve.
• Article or BlogPosting: blog posts, with headline, author, publication date and image.
• Person: founders and authors, linked to your organization.
• BreadcrumbList: the path to a page, which clarifies site structure.
• FAQPage: question-and-answer pairs that are visible on the page.

A simple JSON-LD example

Here is a trimmed example for an agency. Values must match what is shown on your site.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfessionalService",
  "name": "NRY Media",
  "url": "https://nrymedia.com",
  "telephone": "+919818085177",
  "areaServed": "United States",
  "founder": [
    { "@type": "Person", "name": "Lokesh Narwara" },
    { "@type": "Person", "name": "Deepak Kumar Jangid" }
  ]
}
</script>

Add the code to the head or body of the page, or generate it through your CMS or an SEO plugin.

FAQ schema: what to expect in 2026

Google limited FAQ rich results to a small set of authoritative sites, so most businesses will not see expandable FAQs in search results. FAQ schema is still harmless when used properly and can help systems understand your question-and-answer content. The rules are simple: only mark up questions and answers that are visible on the page, keep answers honest and do not use FAQ markup for advertising.

Google's rules for structured data

• Markup must describe content that users can see on the page.
• Do not mark up misleading, hidden or irrelevant content.
• Use accurate information, including prices, ratings and dates. Fake reviews or inflated ratings can lead to manual actions.
• Follow the required properties for each type shown in Google's documentation.
• Do not add review or rating markup for yourself on your own pages unless it follows Google's guidelines for self-serving reviews.

How to add schema step by step

• List your page types: home, service, blog, about, contact.
• Choose the schema types for each page and gather accurate details.
• Write JSON-LD or use a trusted plugin or tag manager template.
• Include an id for your organization and reference it from other types, so entities connect.
• Publish, then test each page type.

How to test and monitor

Use Google's Rich Results Test to check eligibility for rich results and the Schema Markup Validator to check general validity. In Google Search Console, open the Enhancements reports to see errors and warnings over time. Re-test after redesigns, plugin updates or content changes, because broken templates often remove or corrupt structured data silently.

Which schema goes on which page

• Home page: Organization or ProfessionalService, WebSite and BreadcrumbList.
• Service pages: Service, BreadcrumbList and, if useful, visible FAQs with FAQPage.
• Blog posts: BlogPosting or Article, Person for the author and BreadcrumbList.
• About page: Person entries for founders, linked to the organization.
• Contact page: ContactPage with your real phone, email and address.

Keep the organization details identical across all pages so that search engines see one consistent entity.

Schema and AI search

Structured data gives AI systems clean, labeled facts about your business, such as your name, services, area served and founders. It does not guarantee that you will be cited, but it reduces the chance of being misunderstood or confused with a similarly named company. Combine schema with answer-first content, consistent profiles and genuine reviews to make your brand easy to recognize and trust.

A simple schema maintenance checklist

• After every redesign, re-test one page of each type.
• Update phone numbers, addresses, hours and founders whenever they change.
• Remove schema for services or pages that no longer exist.
• Check Search Console enhancement reports monthly for new errors.
• Keep a short document listing which schema types you use and where, so future developers do not break them.

Schema do's and don'ts

• Do keep schema in JSON-LD and match the visible page content exactly.
• Do reference your organization with a consistent identifier across pages.
• Don't mark up content that is hidden, outdated or invented.
• Don't copy another company's schema without changing every detail.
• Don't expect schema alone to rescue weak content or slow pages.

Common schema mistakes

• Marking up content that is not visible on the page.
• Leaving old phone numbers, addresses or names in the code.
• Duplicate or conflicting schema from a theme and a plugin.
• Using the wrong type, for example LocalBusiness for a purely online business with no public location, when ProfessionalService or Organization fits better.
• Adding fake reviews or ratings, which violates guidelines.