What Schema Markup Is and Why It Matters for Local Businesses
Schema markup is structured data code added to your website that tells search engines explicitly what your content means, not just what it says. Where a regular webpage might mention "480-555-1234," schema markup tags that number as a telephone for a specific business entity. Where a page lists Monday-Friday 8am-6pm, schema marks those as business hours in a machine-readable format.
For local service businesses, schema serves two purposes: it strengthens the entity signals that feed into Maps rankings and AI Overviews, and it enables rich results in organic search (star ratings, FAQ dropdowns, breadcrumbs) that increase click-through rate. Done correctly, it's one of the highest-ROI technical SEO tasks because it's a one-time implementation that produces compounding returns without requiring ongoing maintenance.
The reason most local businesses don't have it: schema has a reputation for being developer territory. It isn't. JSON-LD schema — the format Google recommends — is a self-contained script block that goes in your page's head section. If you can copy and paste and edit a few field values, you can implement schema on a Webflow site in under two hours with zero developer involvement.
— Chris Brannan, Local SEO Consultant, Gilbert AZ
LocalBusiness Schema: The Foundation
The LocalBusiness schema type (and its specific subtypes) is the most important schema implementation for any service business website. It creates a machine-readable business profile on your own domain that Google can use to corroborate your GBP data, resolve your business as a distinct entity in its knowledge graph, and determine what queries your business is relevant for.
The critical implementation detail is using the most specific subtype available. Don't use LocalBusiness if a specific subtype exists. Use Plumber for plumbing companies, HVACContractor for HVAC businesses, Dentist for dental practices, Attorney for law firms. Google's entity recognition is more confident when the @type is maximally specific. Use Schema.org's type hierarchy to find the most specific type applicable to your business.
Required Fields for LocalBusiness Schema
A complete LocalBusiness schema implementation includes: @context (schema.org), @type (your specific subtype), @id (your canonical homepage URL as a unique identifier), name (exactly matching your GBP business name), address with PostalAddress including streetAddress, addressLocality, addressRegion, and postalCode, telephone in E.164 format, openingHoursSpecification as an array, geo with GeoCoordinates for latitude and longitude, url (your canonical homepage), priceRange ($, $$, $$$, $$$$), and areaServed as an array of city names you serve.
The areaServed field is especially important for service area businesses and multi-city service providers. A Gilbert HVAC company that serves Gilbert, Chandler, Mesa, Queen Creek, and San Tan Valley should list all five cities in areaServed. This explicitly tells Google the geographic scope of the business, which feeds both Maps proximity signals and organic local search relevance for each city listed.
Arizona-Specific LocalBusiness Schema Example
Here's a complete LocalBusiness schema block for an Arizona plumbing SAB as a JSON-LD reference:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Plumber",
"@id": "https://yoursite.com",
"name": "Desert Pro Plumbing",
"url": "https://yoursite.com",
"telephone": "+14805551234",
"priceRange": "$$",
"areaServed": ["Gilbert", "Chandler", "Mesa", "Queen Creek", "San Tan Valley"],
"address": {
"@type": "PostalAddress",
"addressLocality": "Gilbert",
"addressRegion": "AZ",
"postalCode": "85296",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 33.3528,
"longitude": -111.7890
},
"hasCredential": {
"@type": "EducationalOccupationalCredential",
"credentialCategory": "ROC License",
"name": "Arizona ROC #CR-37 123456"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
"opens": "07:00",
"closes": "18:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Saturday",
"opens": "08:00",
"closes": "14:00"
}
]
}
</script>
Key Arizona-specific notes: the hasCredential block is where your ROC license number goes — this is the verifiable expertise signal that differentiates a licensed Arizona contractor from an unlicensed one in Google's entity graph. For SABs with no public address, omit the streetAddress and use only addressLocality, addressRegion, and postalCode to avoid entity confusion from an address that doesn't match GBP.
Service Schema: Telling Google What You Do
Adding Service schema to each individual service page explicitly connects your service offerings to the business entity. A plumbing company's water heater page with Service schema (serviceType: "Water Heater Replacement", provider: your LocalBusiness @id, areaServed: ["Gilbert", "Chandler", "Mesa", "Queen Creek"]) tells Google precisely what service is offered, by whom, and where.
Service schema on location-specific pages is particularly powerful. A page about pool service in Mesa with Service schema specifying areaServed as Mesa creates an explicit machine-readable signal that matches "pool service Mesa" queries with high confidence. This is the schema pattern that supports both Maps pack rankings and organic local rankings most directly.
For businesses with multiple service pages, the implementation pattern is: one Service schema block per page, with the serviceType matching the primary service covered by that page, the provider referencing the LocalBusiness @id from the homepage, and areaServed listing the cities served by that particular service.
FAQPage Schema: The AI Overview Gateway
FAQPage schema is the highest-leverage schema implementation for AI Overview citation visibility. Pages with FAQPage schema appear in Google's AI Overviews at approximately 2.8x the rate of equivalent pages without it. For a local service business trying to appear in AI-generated local recommendations, this is non-negotiable.
The implementation is straightforward: wrap your Q&A content in FAQPage schema with Question and acceptedAnswer types for each question-answer pair. Every service page with a FAQ section and every blog post with FAQ content should have this schema. The questions should mirror the actual informational queries your customers ask: "How much does AC replacement cost in Phoenix?", "Does my plumber need to be ROC licensed in Arizona?", "What should I do if my roof is leaking during monsoon season?"
The answer content in FAQPage schema should be specific and directly useful — not vague hedges. An answer that says "costs vary by project" provides no citation value. An answer that says "AC replacement in Phoenix metro typically costs $4,500–$8,500 depending on system size, with SRP and APS rebates potentially offsetting $200–$500 of that cost" is both useful and locally specific enough that AI systems will extract and cite it when answering related queries. Specificity is the variable that determines whether your FAQ answers get cited or skipped.
Schema for Healthcare and Professional Services in Arizona
Healthcare providers and licensed professionals in Arizona have specific schema types and credential fields that significantly outperform generic LocalBusiness implementations for AI Overview citation and E-E-A-T signals:
Physician and Dentist @types: Healthcare providers should use the specific @type (Physician, Dentist, Orthodontist, Psychologist, PhysicalTherapist) rather than MedicalBusiness or LocalBusiness. Each specialist @type unlocks additional relevant properties — medicalSpecialty for Physician, availableService for Dentist — that generic types don't support.
hasCredential for Arizona licensing: The hasCredential field linked to the relevant Arizona licensing board is what separates schema that AI systems trust from schema that provides no additional verification signal. Physicians should link to the Arizona Medical Board (azmd.gov) verification page. Dentists to the Arizona State Board of Dental Examiners (azdentalboard.gov). Therapists to the Arizona Board of Behavioral Health Examiners (azbbhe.us). Contractors to roc.az.gov. Each of these government-hosted verification pages is a high-authority source that AI systems can cross-reference, making the credential claim machine-verifiable rather than self-asserted.
HealthPlanNetwork and acceptedInsurance: For healthcare providers, listing accepted insurance plans in the schema using the healthPlanNetworkId property for major Arizona carriers (Delta Dental of Arizona, BCBS of Arizona, United Healthcare) creates machine-readable insurance eligibility signals that AI systems use when answering "dentist accepting [insurance] near me" queries.
Arizona attorneys: Use the Attorney @type with areaServed specifying Arizona and the specific practice area cities. The hasCredential field should reference the State Bar of Arizona license number (linked to azbar.org/MemberSearch for verification). specialties or knowsAbout properties listing the practice areas (Family Law, Personal Injury, Immigration, Estate Planning) create service-specific relevance signals that generic LocalBusiness doesn't provide.
Review and AggregateRating Schema
If your website displays customer reviews or aggregate star ratings, AggregateRating schema makes those ratings eligible to appear as rich snippets in organic search results — the yellow stars beneath a search result that significantly increase CTR. The implementation requires an actual rating value, review count, and that the reviews displayed on the page are genuine and not pulled from your GBP (which would violate Google's policy).
For most local service businesses, this means either implementing a reviews widget that displays Google reviews via a verified API integration (Podium, BirdEye, and similar platforms provide these) or manually maintaining a testimonials section with proper schema markup. The CTR lift from rich snippet star ratings can be 15–30% compared to non-starred results at the same position.
Article Schema for Blog Posts
Every blog post on a local service business website should have Article (or more specifically, BlogPosting) schema. Article schema signals to Google that the page is authored editorial content, which improves eligibility for Discover, Google News surfaces (where applicable), and AI Overview citation. The most important fields: headline (matching the H1 title), author with a Person @type referencing the author's name and identifier, datePublished, dateModified, and publisher referencing the LocalBusiness or Organization entity.
The author field is a direct E-E-A-T signal. An Article schema with a named, credentialed author — rather than an anonymous "admin" — signals that the content was written by an identifiable expert. For a plumbing blog post authored by a licensed master plumber with a verified ROC license, the author schema should reflect those credentials explicitly. Connect the author @id to an About page or author profile that lists the same credentials.
For Webflow CMS sites, Article schema can be added to the blog collection template page with dynamic CMS field bindings populating the headline, datePublished, and dateModified values from the post's CMS fields automatically. This makes Article schema scale across your entire blog collection without requiring manual updates per post.
BreadcrumbList, Organization, and WebSite Schema
BreadcrumbList schema on interior pages tells Google exactly where each page sits in your site hierarchy. For a plumbing company, a water heater service page with BreadcrumbList schema showing Home → Services → Water Heater Repair gives Google explicit structural context that reinforces the page's topical relationship to the rest of the site.
Organization schema establishes your business as a recognized entity with social media profiles, contact information, and a logo. The sameAs property is particularly valuable — it lists the external URLs that represent the same business entity (your GBP URL, Yelp page, Facebook page, LinkedIn page, BBB listing). These sameAs references are how Google's Knowledge Graph connects your website entity to your listings across the web, strengthening overall entity authority and making your business Knowledge Panel more likely to appear for branded searches.
WebSite schema with a SearchAction property enables Sitelinks Search Box in Google's results — the search input that appears beneath your homepage result for branded queries. It also establishes a machine-readable connection between your domain and your business entity, which contributes to Knowledge Panel recognition.
Schema's Role in AI Search Citation
In 2026, schema markup has taken on a second strategic role beyond traditional search: AI citation eligibility. Google's AI Overviews, AI Mode, and ChatGPT Search all use structured data as a signal of content trustworthiness and precision. Schema-marked content is cited more reliably than equivalent unstructured content because the machine-readable format reduces the inference work required of the AI system.
The specific schema types that produce the highest AI citation lift in order of impact: FAQPage schema (the Q&A structure is exactly the format AI systems extract for direct answer responses), hasCredential linked to verifiable licensing boards (government-hosted credential verification pages are the highest-trust sources AI systems prefer to cite), Service schema with areaServed (geographic precision matters for local recommendation queries), and AggregateRating with review count (social proof signals in structured form are commonly cited for service recommendation queries).
The practical implication for Phoenix metro local service businesses: implementing schema with Arizona-specific credential fields (ROC license at roc.az.gov, Arizona Medical Board, Arizona State Board of Dental Examiners, AZBBHE) creates a credential verification chain that national competitors using generic schema don't have. This locally-specific verifiable credential structure is a genuine competitive advantage in AI citation frequency that compounds over time as AI systems index and trust the credential chain more deeply.
How to Implement Schema in Webflow
In Webflow, schema markup is implemented as a custom code embed in the page's head section. For site-wide LocalBusiness schema, add it to Site Settings → Custom Code → Head Code. For page-specific schema (FAQPage, Service, Article), add it in individual page settings → Custom Code → Head Code. For CMS template pages (blog posts, service pages), add schema in the CMS collection template page settings and use Webflow's field binding syntax to populate dynamic values automatically. This makes Article schema scale across your entire blog collection without per-post maintenance.
Schema Implementation Checklist
- LocalBusiness schema (site-wide): Specific @type, areaServed listing all service cities, ROC/professional license in hasCredential, GeoCoordinates, openingHoursSpecification
- Organization schema (site-wide): sameAs listing GBP URL, Yelp, Facebook, BBB, and major directory listings
- WebSite schema (site-wide): SearchAction property for Sitelinks Search Box eligibility
- FAQPage schema: Every service page FAQ section, every blog post FAQ section — top priority for AI Overview citation
- Service schema: Every service page with serviceType, provider referencing LocalBusiness @id, and areaServed
- Article/BlogPosting schema: Every blog post with named author, datePublished, dateModified, publisher
- BreadcrumbList schema: All interior pages (service pages, blog posts, location pages)
- AggregateRating schema: Any page displaying genuine verified reviews with rating and count
- Healthcare/professional credential schema: Physician, Dentist, Attorney, or Orthodontist @type with hasCredential linked to Arizona licensing board verification pages
- Validation: Google Rich Results Test on every page after implementation
- Monitoring: Search Console Enhancements report monthly; Screaming Frog structured data audit quarterly
Key Takeaway
Schema markup is a one-time implementation with compounding returns: richer search appearances, higher click-through rates, stronger entity recognition, and improved AI Overview citation frequency. The priority order for a local service business starting from zero: LocalBusiness schema on the homepage first (with ROC license in hasCredential for Arizona contractors), FAQPage schema on every Q&A page second, Service schema on each service page third, Article schema on blog posts fourth, and AggregateRating on pages with genuine reviews fifth. The AI citation opportunity from FAQPage + hasCredential + Service schema combinations is strongest for businesses with verifiable Arizona-specific credentials (ROC, AZMD, azdentalboard.gov, azbbhe.us) — these government-hosted verification pages are the highest-trust credential sources AI systems prefer. Validate everything with Google's Rich Results Test, monitor quarterly in Search Console. For the full local SEO context, see the Local SEO Ranking Factors guide.
.webp)
