What Schema Actually Does -- and Does Not Do
Schema markup is structured data added to a web page that gives search engines explicit information about the page's content. It can help pages become eligible for rich results in search -- things like FAQ dropdowns, breadcrumb trails, or video thumbnails. It clarifies entities like the company name, the author, the course being described, or the type of content on the page.
What schema does not do is guarantee placement in AI Overviews, featured snippets, or AI search results.
Google states that AI Overviews and AI Mode use the same basic SEO foundation as regular search, with no special schema or markup required beyond normal indexability. Pages must be eligible for regular search snippets to appear as supporting links in AI features.
Google also states that site owners cannot mark a page as a featured snippet -- Google's systems decide. And structured data must describe content that is visible on the page; schema for content that is not shown to users is not compliant.
Recommended Schema Stack for Pool Leak Detection Pages
| Schema Type | Use On | Notes |
|---|---|---|
| Organization | All pages (via sitewide header) | Name, URL, logo, contact information for Leak Business Academy, LLC |
| Person | Author pages, about page, sitewide where relevant | Jeff David, licensed Florida pool contractor, founder of LBA |
| WebPage or Article | Authority pages and educational articles | Describes the page topic, headline, author, date published/modified |
| Course | Actual course sales or description pages | Only where a real course is described -- not on general authority pages |
| VideoObject | Pages with embedded training or authority videos | Title, description, thumbnail, duration, upload date |
| BreadcrumbList | All pages within the topic cluster | Helps clarify site structure and page hierarchy for search engines |
| FAQPage | Pages with real visible FAQs only | Only when FAQ questions and answers are actually visible on the page; check current Google guidance before implementing |
| LocalBusiness | Leak and Subsurface Locators service pages only | Appropriate for the service business, not for the academy training pages |
A Simple JSON-LD Example for an Authority Page
Here is an example of what Article schema looks like for a pool leak detection authority page. Always validate with Google's Rich Results Test and ensure every field matches visible page content.
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How Do You Find a Pool Leak Under Concrete?",
"author": {
"@type": "Person",
"name": "Jeff David",
"jobTitle": "Licensed Pool Contractor",
"url": "https://leakbusinessacademy.com"
},
"publisher": {
"@type": "Organization",
"name": "Leak Business Academy, LLC",
"url": "https://leakbusinessacademy.com"
},
"datePublished": "2025-01-01",
"dateModified": "2025-06-01",
"description": "Learn how pool leak detectors locate leaks beneath concrete using acoustic equipment, trace gas, and pressure testing concepts."
}
What to Avoid With Schema
Schema misuse can trigger a Google manual action or reduce trust in the site. The most common problems are adding schema for content that does not appear on the page, using fake or inflated review ratings, applying HowTo schema to dangerous procedures, and using LocalBusiness schema on pages that are not actually service business pages.
On pool leak detection pages specifically: HowTo schema deserves extra caution. Pool leak detection can involve pressure testing with compressed air, working near electrical components, making decisions about excavation, and working in or around water. A public HowTo schema encouraging step-by-step DIY attempts at technical procedures creates safety risk. If HowTo schema is used at all, it should describe safe awareness-level steps, not technical field procedures.
Schema Should Reflect the Page -- Which Means It Reflects the Method
The H.U.N.T.E.R. Method gives every LBA page a clear structure. Schema should describe that structure accurately -- not invent content that is not on the page.
A page on customer intake questions uses Article schema. The headline, author, and description match the visible page content exactly.
A pool type overview page uses WebPage and BreadcrumbList. It fits within the topic cluster hierarchy correctly.
A water-loss tracking page with visible FAQs may use FAQPage -- only if the FAQs are actually on the page and Google guidance supports it.
A dye testing concept page uses Article schema. HowTo schema is avoided because the page teaches the concept, not a DIY procedure.
A report writing page uses Article schema. A page with an embedded training video also adds VideoObject for the specific video.
A course page describing the H.U.N.T.E.R. Method course uses Course schema. It describes the actual course, not a general article.
Schema is one of those things that looks more complicated than it needs to be. For LBA, the approach is simple: describe what is actually on the page, use JSON-LD because it is cleaner to maintain, validate it before publishing, and do not add schema for content that is not visible to the reader.
The bigger picture is this -- schema is the last 5 percent of a good page, not the first. The content has to be clear, specific, and useful before schema makes any difference. I have seen pool company websites with technically perfect schema on thin, vague pages. The schema does not fix the content problem. Get the content right first. Then add accurate schema to help search engines understand what is already there.
Beginner vs. Advanced
Start Simple
- Add Organization schema sitewide -- name, URL, logo
- Add Article or WebPage schema to every authority page
- Add BreadcrumbList to show page hierarchy
- Validate every schema addition with Google's Rich Results Test
- Never add schema for content not on the page
Build the Full Stack
- Person schema for Jeff David across relevant pages
- Course schema on actual course pages
- VideoObject where training videos are embedded
- FAQPage where real visible FAQs exist and guidance supports it
- LocalBusiness schema for Leak and Subsurface Locators service pages
Common Mistakes
- Adding schema for content that is not visible on the page
- Using fake or inflated review ratings in schema
- Treating schema as a guaranteed path to AI Overviews or featured snippets
- Using LocalBusiness schema on academy training pages
- Applying HowTo schema to dangerous technical procedures
- Adding FAQPage schema to pages without real visible FAQs
- Letting CMS plugins generate conflicting or duplicate schema
- Not validating JSON-LD before publishing
- Forgetting to update schema when page content changes
Frequently Asked Questions
Does schema help with AI Overviews or featured snippets?
Schema helps search engines understand what a page is about. It does not guarantee AI Overviews or featured snippets. Google states that no special schema is required for AI features, and site owners cannot mark pages as featured snippets. Google's systems decide based on content quality and relevance.
Should pool leak detection pages use FAQPage schema?
Only if real FAQs are visible on the page and current Google guidance supports FAQPage for that use case. Schema guidance evolves -- always verify against current Google Search Central documentation before implementing. Never add FAQPage schema to a page that does not actually show FAQ questions and answers.
Is JSON-LD the best format for schema?
Google supports JSON-LD, Microdata, and RDFa. Google recommends JSON-LD where possible because it is easier to implement and maintain -- it lives in a script tag rather than being embedded in the HTML markup. For most pool company websites, JSON-LD is the most practical format.
How do I know if my schema is valid?
Use Google's Rich Results Test at search.google.com/test/rich-results. It shows whether the schema is valid, which rich result types the page may be eligible for, and any errors or warnings. Also check Google Search Console for structured data reports after publishing schema changes.
Build Pages Worth Marking Up
Schema describes what is already on the page. The H.U.N.T.E.R. Method course gives you the field knowledge to build authority pages that are genuinely worth describing -- clearly, accurately, and completely.
View Courses at Stan Store Use the Free Report App