Your site plugin offers a dozen schema types. Selecting more types does not give a service business twelve new ways to appear in Google. Start with the facts on each page and the supported search feature you want the developer to implement.
Structured data supplies machine-readable information about a page. Google's introductory documentation says the markup should describe that page's visible content. A valid implementation can support eligibility for an applicable feature; it does not guarantee display.
Build a visible-content-to-markup map
The following example concerns a hypothetical maintenance business with an office, service pages, and an advice blog. A business without a customer-facing office should use its own truthful information rather than copy the example's location details.
| Page | Facts to confirm | Implementation decision |
|---|---|---|
| Business information page | Public name, applicable location information, phone, hours, and corresponding website details. | Review the current LocalBusiness guidance and choose a suitable type only when the required facts fit. |
| Published advice article | Headline, author, actual publication and modification dates, and representative image. | Review Article markup against the visible article and author information. |
| Service overview | Services actually offered, relevant coverage, and the inquiry path. | Describe truthful content. Do not invent a rich-result feature because a vocabulary permits a Service type. |
| Questions and answers | Answers customers can read on the page. | Keep useful answers for readers; do not sell them as a current Google FAQ rich-result tactic. |
The developer should retain the reference for each supported feature alongside the implementation. Google provides separate guides for LocalBusiness and Article. A schema vocabulary and Google's supported display features serve different purposes.
Remove promises based on old documentation
Google stopped showing FAQ rich results starting May 7, 2026 and removed the feature documentation in June. Its Search documentation updates record that change. A service business can still publish helpful questions and answers, but the team should revise proposals that promise Google FAQ rich results.
Apply that check to other claims too. Ask the provider to name the supported feature and link its current requirements. Do not accept a screenshot of another site's search result as proof that your page qualifies.
Validate one representative page before scaling
Ask the developer to implement one article, then inspect the live page with the Rich Results Test. Record the tested URL, detected type, errors, and warnings. The team should distinguish a critical missing property from a recommended property it cannot truthfully supply.
Compare the detected values with the reader's view. If the article says Luke Thompson wrote it but the markup names the site administrator, correct the author relationship. If the developer uses the build date as the publication date, replace it with the article's actual first-publication date.
Test an article after a substantive edit as well. The page and markup should reflect its legitimate modification date while retaining the original publication date. A deployment that changes navigation should not turn the entire archive into newly published articles.
Then review a second page using the same template. A hardcoded author or image may pass on the first example and misdescribe the next article. Compare the two detected outputs before enabling the template across the archive.
Give the implementer a short acceptance record
- Page and type: Identify the exact live URL and chosen markup.
- Visible facts: Link each important field to the page content or legitimate business record.
- Validation: Attach the current test result and unresolved issues.
- Release owner: Name who updates the template when the content or feature guidance changes.
Do not fabricate reviews, ratings, locations, authors, or results to complete a schema field. Where your business cannot supply a required fact, revisit the implementation choice instead of creating the fact.
Use our technical SEO checklist for broader page acceptance. The Ops Guide's SEO services can help connect accurate content, technical implementation, and the customer inquiry path.

