Published March 19, 2026
The homepage tells AI what a business is. Service pages tell AI what a business does — specifically. A business with service page schema gets matched to specific queries. A business without it gets matched to generic ones — or gets skipped.
Most service pages have no schema. The content is there for human visitors, but AI reads structured data first and page content second.
When a user asks AI for "a contractor who does kitchen remodeling," AI is not just looking for contractors. It is looking for contractors whose structured data includes kitchen remodeling as a specific service. A contractor with Service schema for kitchen remodeling, bathroom remodeling, and whole-home renovation can be matched to any of those queries individually. A contractor with only homepage schema that says "general contractor" misses the specific queries where conversion is highest.
This is where the completion gap becomes relevant. AI cites businesses when it can confidently match a specific need to a specific offering. Service page schema provides that match at the granular level.
"Kitchen remodeling" is more useful to AI than "our services." The more specific the service name and type, the more specific the queries AI can match.
What the service includes, who it is for, and what the outcome is. Not marketing copy — structured context that helps AI understand scope.
Where this specific service is available. Service-level area definitions are more precise than business-level ones and help AI match location-specific queries to the right offering.
What the service costs, even as a range or starting price. Transparent pricing lets AI pre-qualify users before sending them. The result is fewer but higher-converting sessions — consistent with findings showing AI traffic converting at 24.9%.
Which team member or provider handles this service. Particularly relevant for healthcare (which doctor handles this procedure), professional services (which attorney handles this practice area), and personal services (which stylist handles this treatment).
Service schema should reference back to the Organization schema on the homepage. This is the @graph connection that tells AI this service belongs to this specific business — not a disconnected data point.
No schema at all. Service pages have detailed content for human visitors but zero structured data for AI.
Generic service descriptions. Schema that says "professional services" gives AI nothing to work with. AI needs specificity — what kind, for whom, at what price point.
All services on one page. All services sharing one URL with one schema block makes it harder for AI to match specific queries. Individual pages with individual schema are more matchable.
No connection to the homepage organization. Service schema in isolation means AI cannot connect that offering to the business's location, contact information, or hours. The connected schema approach used in AIFDS blueprints solves this.
For service businesses — each offering needs its own page and schema. A law firm with separate pages for personal injury, estate planning, and business litigation can be matched to each individually.
For healthcare — each procedure or specialty should have its own page. A dental practice with separate pages for cosmetic dentistry, orthodontics, and emergency care gives AI three distinct matchable services.
For local businesses — services, menus, or offerings should be structured on dedicated pages.
For nonprofits — each program should have its own page with schema describing what it does and who it serves.
The principle across all industries: one service, one page, one schema block.
The AIFDS blueprint library includes service page blueprints for every industry family. Each blueprint contains the exact JSON-LD fields AI needs for that combination of industry and service type, with the @graph connection back to the homepage organization.
David Valencia writes about how AI systems find, parse, and cite websites.