Plumber schema markup: an evidence-backed guide

Schema.org includes a Plumber type. That does not mean a plumbing website is safe after changing one word in a generic LocalBusiness template.

A useful plumber graph still depends on business identity, visible facts, page purpose, existing markup, and delivery. The goal is not to fill every possible property. The goal is to describe the right business accurately and keep that description correct. For the wider operating model, use the structured-data resource library.

Start with the entity, not the template

Ask what the page represents:

• the plumbing company as a whole;
• one physical location;
• a service-area business;
• a specific service page, such as drain cleaning or water-heater repair;
• an informational article.

The company or location may be a Plumber. A service page does not become another duplicate plumbing company. It can link its WebPage and service description back to the same stable business identity.

Facts that need strong evidence

Business name

Use the real public brand or approved legal name. Do not turn “Mitchell Plumbing” into “Best Emergency Plumber in Austin” inside structured data unless that is genuinely the visible, verified business name—which it usually is not.

Phone number

Use a current public business number. If the header, footer, contact page, and existing markup disagree, the conflict needs resolution. Choosing the first number a crawler encounters is not safe.

Address and service area

Some plumbers operate from a public storefront; others travel to customers and do not display a home address. Do not invent or expose an address to complete markup. Service-area facts should come from customer confirmation or an authorized business source, not a geocoding guess.

Hours and emergency availability

“24/7 emergency service” is a business claim. Publish it only when the visible site and customer confirmation support it. Do not translate an after-hours voicemail or a single emergency-service page into round-the-clock opening hours automatically.

Services

Plumbing sites often mention drain cleaning, leak repair, sewer work, repiping, water heaters, or gas lines. A crawler may detect those phrases, but publication should respect page context and the actual services the business approved. Never add prices, availability, licenses, or guarantees from inference.

Ratings and reviews

Do not copy a star count from a badge and publish an aggregate rating without confirming the source, scope, freshness, and applicable policies. Google restricts self-serving review markup for organizations and local businesses. A safe system may detect and advise on the issue rather than generate it.

Use a coherent graph shape

For a single-location plumbing site, a coherent page often connects:

• one stable Plumber business identity;
• the WebSite published by that business;
• the current WebPage as part of that site;
• a visible breadcrumb when one exists;
• page-specific information linked back to the same business.

The exact properties depend on supported evidence. A shorter accurate graph is better than a complete-looking graph with guessed hours, coordinates, ratings, or service areas.

Watch for WordPress collisions

Many plumbing sites already have schema from a theme, SEO plugin, local SEO add-on, review widget, or page builder. Before adding new JSON-LD:

1. Inventory every existing block on the served page.
2. Identify which system owns each block.
3. Compare business names, URLs, phone numbers, addresses, and @id values.
4. Avoid silently deleting valid origin markup.
5. Decide whether to link, merge, suppress at the source, or pause for review.

Adding another “perfect” Plumber object can make the overall graph worse if it conflicts with what is already there.

Validate what you can actually prove

Use separate checks for safe JSON, Schema.org vocabulary, applicable Google feature requirements, and the live served output. Then keep monitoring after site changes.

Correct markup does not guarantee a rich result, ranking, traffic, or new plumbing jobs. What a good operating system can guarantee is narrower: it will not knowingly publish unsupported facts, it will apply the declared validation rules, and it will verify what the live page serves.