English
Romana
If you run a service website and pinned your hopes on FAQPage schema for rich results in Google, here is the direct answer: that rich result no longer exists in Google Search as of May 7, 2026. The official documentation for it was fully retired on June 15, 2026. What actually works for a service business today is different — and that is exactly what this guide clarifies.
For consulting firms, local service providers, agencies and B2B service businesses, the correct 2026 priority is Organization, Service, LocalBusiness, BreadcrumbList and Review markup — combined with an on-page FAQ structure built for AI citation, not for a rich result that no longer exists.
This guide is written for service-website owners, in-house marketers and developers who need to prioritize technical effort correctly, without spending time on a schema type that no longer produces a visible result in Google Search.
What changed with FAQPage and why it matters for service websites
Many service-website guides and templates still recommend FAQPage schema as a "must-have" step for rich snippets. The 2026 reality is different.
- Since 2023, the FAQPage rich result had already been restricted to well-known government and health-related websites only.
- As of May 7, 2026, Google removed this feature entirely from Search, for every type of website.
- Google fully retired the dedicated FAQPage documentation on June 15, 2026.
For a service website, the practical consequence is direct: if development budget went into FAQPage markup with the sole goal of getting a rich snippet, that effort no longer delivers the expected outcome in classic Google Search. This is not an implementation error — it is a platform-level policy change from Google.
Which Schema.org types still produce visible results in Google in 2026
Not every schema type was affected. For a service website, several types remain relevant and can still produce visible elements in search results, when the on-page content supports them.
| Schema type | Status in Google Search (2026) | Relevance for a service website |
|---|---|---|
| FAQPage | Removed from rich results as of May 7, 2026 | No longer produces a snippet; useful only for content clarity and AI |
| Organization | Active | Priority — clarifies brand identity for Google |
| LocalBusiness | Active | Priority for services with a physical location or service area |
| Service | Active | Recommended on every dedicated service page |
| BreadcrumbList | Active | Useful on any site with multi-level category/service structure |
| Review / AggregateRating | Active, under strict conditions | Relevant only if reviews are real and verifiable on the page |
| Article / BlogPosting | Active | Useful for the blog or resources section of the service website |
HappyWeb's practical recommendation: allocate technical effort in the order shown in the table, not in the order generic tutorials happen to list schema types.
How to structure the data for a service website, step by step
Recommended structure for a typical service website, with a homepage, individual service pages and, optionally, a location page:
- Mark up the homepage with Organization, including name, logo, URL and official contact channels.
- If the business has a physical location or a clear service area, add LocalBusiness with address, hours and coverage area.
- Mark up each dedicated service page with Service, including the service name, provider (Organization) and area served, when relevant.
- Add BreadcrumbList on service pages, to clarify site hierarchy (e.g., Services > Category > Specific Service).
- If you have real, on-page visible reviews, add Review or AggregateRating, synced with the actual review source.
- For the blog section, use Article or BlogPosting, with clear author and publication date.
- Test each markup type with Rich Results Test before publishing.
On-page FAQ vs. FAQPage schema: what to keep and why
A short, direct answer to a common question in this space: you should keep a visible FAQ section on the page, even though FAQPage markup no longer produces a rich snippet in Google Search.
The reason is simple: FAQ content written clearly, with naturally phrased questions and concrete answers, remains easy to extract and cite for AI systems (AI Overviews, conversational assistants), regardless of the Schema.org markup used. The difference from 2023 is that FAQ content is no longer a rich-snippet tactic — it is a clarity tool for readers and for the AI systems summarizing the page.
- Keep FAQ content static and visible directly in the HTML, without JS toggles that hide the answer.
- Phrase questions exactly as your clients actually search (e.g., "How much does an SEO audit cost for a service website?"), not generically.
- Write the full answer in 2-4 self-contained sentences, without ambiguous references to other page sections.
- Do not add FAQPage markup out of habit — it has no impact on rich results in Google Search in 2026.
Practical implementation plan for a service website
A rough plan applicable to most small and mid-size service websites:
- First 30 days: Organization on the homepage, LocalBusiness (if applicable) and Service on the 3-5 most important service pages.
- 30-60 days: BreadcrumbList across all service pages, plus Review/AggregateRating if real reviews are available.
- 60-90 days: Article/BlogPosting for the resources section, a full review of existing markup and a final check in Search Console.
Minimum checklist before considering the implementation "done":
- Every service page has valid, tested Service markup.
- No properties are filled with information that is not visible on the page.
- The on-page FAQ is genuinely useful for readers, regardless of markup.
- The Enhancements report in Search Console shows no recurring critical errors.
Common mistakes on service websites and how to avoid them
| Common mistake | Real risk | Recommended mitigation |
|---|---|---|
| Spending time on FAQPage schema for a rich snippet | Technical effort with no visible result in Google Search since May 2026 | Redirect the effort to Service, LocalBusiness and BreadcrumbList |
| LocalBusiness markup with outdated address or hours | Confusion for users and search engines, lower trust | Sync the markup with real data from your Google Business Profile |
| Review/AggregateRating for reviews not actually visible on the page | Exclusion from rich result eligibility; risk of a manual action | Only display on the page exactly the reviews marked up in schema |
| One generic Service block for all of the company's services | Loss of granularity; Google cannot differentiate individual services | A distinct Service block for each real service page |
How to verify your implementation
Validation stays the same regardless of which schema type you choose: test before publishing and monitor continuously afterward.
- Rich Results Test — confirms whether the markup meets the required properties for the targeted rich result type, before publishing.
- Enhancements report in Search Console — shows, site-wide, how many pages have valid markup and which errors recur, after publishing.
- URL Inspection — useful to confirm an individual page's status after a significant content or markup change.
Sources last checked: July 12, 2026.
FAQ - Schema.org for Service Websites
1. Is it still worth implementing FAQPage schema on my service website?
It no longer produces a rich snippet in Google Search — the feature was fully removed as of May 7, 2026. You can keep FAQ content on the page for readers and AI systems, but stop allocating technical effort to FAQPage markup for rich-result purposes.
2. Which schema type should I implement first on a service website?
Organization on the homepage, followed by Service on each service page, and, if the business has a physical location or service area, LocalBusiness.
3. Do I need LocalBusiness if I work remotely with no visible physical location?
Not necessarily. If your services don't depend on a physical location or a served geographic area, Organization and Service correctly cover the technical need.
4. Do Google Business Profile reviews need to be separately marked up with Review schema?
Not automatically. Only mark up with Review or AggregateRating the reviews actually displayed on your page, synced with the real source — not imported reviews without verification.
5. How often should Schema.org implementation be reviewed on a service website?
A review every 90-180 days is a reasonable baseline, especially if Google announces changes to the schema types you use, as happened with FAQPage.
Conclusion
For a service website, the correct 2026 priority is no longer FAQPage schema, but Organization, Service, LocalBusiness and BreadcrumbList, backed by correctly marked-up real reviews. FAQ content remains valuable on the page, but for clarity and AI citation, not as a rich-snippet source in Google Search.
Want to check whether your service website's Schema.org implementation is current and correct? Let's discuss a technical audit. Read also our general Schema.org implementation guide or see our SEO optimization services.
Image generated with AI, used for illustrative purposes.
Write a comment