On this page10 sections

Plan the data before writing JSON-LD
A maintainable implementation starts with a small set of accurate records: the business, its services, its pages, and its authors. Before adding markup, write down the business name, public contact details, actual services, opening hours, and the places served. Each record should have an owner who can correct it when the underlying facts change. Do not invent a staffed address for a city where the business only travels to customers.
This guide is for the person implementing or reviewing the code. For an introduction, read what schema markup means.
Give entities stable identifiers
Use a stable identifier for the organization so service and article data can refer to the same publisher or provider. Keep page URLs canonical and consistent. Avoid producing a separate business identity every time a template renders.
Here is a local business JSON-LD example showing a service relationship. Replace the example values with actual visible facts:
{
"@context": "https://schema.org",
"@type": "Service",
"@id": "https://example.com/services/drain-cleaning#service",
"name": "Drain cleaning",
"url": "https://example.com/services/drain-cleaning",
"provider": {
"@id": "https://example.com/#organization"
},
"areaServed": {
"@type": "City",
"name": "Boise"
}
}
This example describes a service. It does not establish an office, verify credentials, or promise a particular Google result. Publish the referenced organization record using accurate information. For a quick starting block that already uses the right LocalBusiness subtype for your trade, try the free local business schema generator; it runs in the browser and flags missing required fields before you wire the values into shared templates.
Map the facts to the right pages
Keep the business identity consistent across the site. Give distinct services their own descriptions where there is enough useful information to justify a page. Identify the actual provider. Do not create empty pages solely to hold markup.
For articles, use the real author and publication date. Change the modified date when you make a substantive update, not every time the website builds. For breadcrumbs, use the visitor's actual navigation path.
Keep shared values in one place
Pull the business name, public URL, and contact details from a maintained configuration. Generate article data from the same record that supplies the visible title, author, and dates. Generate an offer from the same pricing policy used by the page.
Avoid copying a block of markup into dozens of pages and editing each separately. That makes missed updates harder to detect.
Serialize safely
Use a proper JSON serializer rather than building JSON from string concatenation. When embedding JSON in a script element, use the application's safe JSON-LD serialization helper so user-controlled text cannot terminate the script element.
Validate the resulting document, including values that contain quotation marks, angle brackets, or line breaks.
Review these LocalBusiness schema fields before launch
| Field | Check |
|---|---|
| Name | Matches the business or service shown on the page |
| URL | Points to the canonical public page |
| Contact details | Current and appropriate for public display |
| Service area | Describes real coverage without implying invented offices |
| Price | Agrees with the visible offer and payment terms |
| Images | Relevant, available, and used with permission |
| Dates | Reflect publication and meaningful updates |
| Provider | Identifies the business delivering the service |
If pricing changes in one place while markup keeps an old amount, the website sends conflicting information.
Test content, syntax, and eligibility separately
How to validate structured data: treat the facts, the syntax and any Google feature as three separate checks.
- Compare the facts against the visible page.
- Check that referenced URLs and images resolve.
- Validate the schema vocabulary and JSON syntax.
- Check any supported Google feature against its specific requirements.
- Inspect the deployed page after release.
Google's structured data introduction distinguishes markup from supported search presentation. Do not interpret a syntax pass as guaranteed eligibility or performance.
Validate a sample before applying a template everywhere
Check one page of each type first. Compare its rendered content, canonical URL, and JSON-LD. Fix the shared template before generating the rest.
Use the Rich Results Test for supported Google features and the Schema Markup Validator for schema syntax. Check the deployed URL as well as local code: configuration can change what gets served.
Avoid outdated feature promises
Does Google still show FAQ rich results? No. On May 7, 2026, Google stopped showing FAQ rich results in Search and added a notice saying so to its FAQPage structured data documentation. FAQ content can still help customers decide, so keep questions and answers that are useful. Do not sell FAQPage markup as a listing upgrade.
Do not promise review stars for testimonials either. Self-serving LocalBusiness and Organization reviews are excluded from Google's review-star feature, including when a business embeds a third-party review widget. Refer to the review snippet policy.
Neither correct schema nor a validation pass guarantees a search position.
Assign maintenance responsibility
Decide who updates hours, phone numbers, offers, services, and author records. Update markup alongside those business details, and put schema checks into the same workflow as visible content changes. Keep representative URLs in a release checklist so template changes get checked consistently. A maintenance plan should name these responsibilities rather than promise an unspecified search boost.
The webIQ custom build scope explains how this fits into the broader website setup. If you build your own site with webIQ Self-Service, free to build, it sets your pages up for Google and AI search for you.
Visible questions come first and markup second; see writing FAQs for service pages for the questions worth answering.
Frequently Asked Questions
Is FAQ schema still worth adding?
It no longer produces an FAQ rich result in Google Search. Valid markup is not harmful, and it still describes the page for any tool that reads schema, so keep it only where the page has a genuine, visible FAQ. Never add it to text the visitor cannot see.
Can I get review stars for my own business in search results?
Not from reviews on your own site. Google excludes self-serving reviews of a LocalBusiness or Organization from review stars, even when they come from an embedded third-party widget.
Does structured data improve my rankings?
Not by itself. It helps search engines read the facts on a page and can make a page eligible for some features. Rankings depend on whether the page is useful and relevant.
Follow webIQ on Google
Add webIQ as a preferred source and Google will show more of our guides when you search. It takes one tap, and you can undo it any time from the same screen.
Make webIQ a preferred source