Start with the page's visible facts
List the business name, public contact details, page purpose, and any prices or dates a visitor can read. Then compare those facts with the structured data. A valid code block can still describe the wrong company, an old price, or an outdated article.
Google supports several formats and generally recommends JSON-LD. Its documentation explains that markup should describe the page where it appears and reflect information available to visitors. See Google's introduction to structured data.
Choose the type that fits the content
- Organization or an appropriate LocalBusiness type: describe the actual business and public details. Do not invent an office or location to target another city.
- BreadcrumbList: describe the navigation path to the page.
- Article or BlogPosting: describe an article, its author, and genuine publication and revision dates.
- Service: describe a service. A Schema.org type's existence does not mean Google offers a dedicated rich result for it.
- Product or Offer: use only when the page and applicable guidelines support that description. Keep price conditions visible.
Choose supported Google search features using Google's current documentation. Do not add unrelated types just to increase the number of code blocks.
Review stars require more than real testimonials
A genuine testimonial does not automatically qualify a business's own page for Google review stars. Google's LocalBusiness and Organization review rules exclude self-serving reviews, including reviews displayed through a third-party widget on the reviewed business's site. See the review snippet guidelines.
Keep useful testimonials visible when you have permission to publish them. Do not turn them into unsupported rating markup or invent a rating count.
Keep FAQ content useful without promising dropdowns
Google retired FAQ rich results on May 7, 2026. FAQPage markup no longer produces that Google search feature. The questions and answers can still help visitors decide whether your service fits. See Google's retirement notice.
Google also says its AI features need no special AI markup. Use accurate content and accessible pages as the foundation; structured data does not secure a citation. Read Google's AI search guidance.
A practical check using RDS pricing
Our website build packages range from $600 to $5,000. Our $189 monthly plan covers maintenance, while search optimization starts at $289 per month. Those figures describe RDS pricing, not an industry average.
If a page describes an offer, check the amount, currency, billing period, and scope against the visible pricing page. A $189 maintenance offer must not appear in the code as a $189 SEO service. Apply the same check when changing a price or package.
Validate in three passes
- Check syntax and meaning. Parse the JSON-LD, confirm the type, and compare each claim with the visible page. A Schema.org validator checks vocabulary; it does not promise a Google feature.
- Check Google's supported features. Use the Rich Results Test. Review errors and warnings in context. A result with no supported items can be expected for a type without a Google rich result.
- Check the published page. Inspect the actual URL after deployment. Confirm the markup survived the build and that crawling and indexing are allowed. Search Console can show what Google last fetched.
Repeat the relevant checks when templates, plugins, prices, or business details change. Assign someone to update both the page and its markup.
Connect markup to the rest of the website
Structured data does not replace service explanations, internal links, or a working inquiry form. Our Phoenix web design service covers the website itself, while search optimization addresses ongoing search work. The local SEO guide explains how business details fit into the broader process.
Frequently asked questions
Does valid schema guarantee a rich result?
No. Eligibility depends on the page, supported feature, and policies. Google decides whether to display an enhanced result.
Should I add every available schema type?
No. Add types that accurately describe visible content and keep them maintained. More markup does not establish better search performance.
Can a plugin handle schema for me?
A plugin can generate markup, but someone still needs to verify its facts, check for duplicate or conflicting output, and test the published page.
Rytell