Service Page Schema for AEO: The FAQ, Organization, and SameAs Markup B2B Sites Actually Need

Seventy-three percent of B2B buyers now use AI tools like ChatGPT and Perplexity during their research process (Averi/Loganix, 2026). That stat should stop you cold, especially if your service page schema for AEO isn’t in place yet. Nearly three-quarters of your potential customers are asking AI assistants to help them evaluate vendors, compare solutions, and build shortlists. Yet most B2B service pages have either no schema markup, generic templates copied from WordPress plugins, or structured data designed for rich results that no longer exist.

This disconnect costs visibility where it matters most.

AI engines parse structured data to understand what a company does, who stands behind it, and whether it’s trustworthy enough to cite. Without proper service page schema, you’re invisible to the fastest-growing discovery channel in B2B. The data backs this up: websites with properly implemented structured data are 3.2 times more likely to be cited in Google AI Overviews (Princeton/Moz, WWW 2026 Conference). AI Overviews themselves grew from 31% to 48% of all tracked queries between February 2025 and February 2026 (BrightEdge, 2026).

The window for early-mover advantage is closing. By the end of this guide, you’ll have the exact schema structure that connects your Organization, Service pages, and FAQ content into a machine-readable entity graph that AI engines can actually cite. This isn’t about chasing rich results anymore. It’s about building the foundation for AI discoverability that compounds over time.

What You Need Before Implementing Service Page Schema

Before you write a single line of JSON-LD, get your prerequisites in order. Rushed implementations create validation errors that AI engines may penalize.

Technical requirements:
– Access to your site’s HTML or CMS with the ability to inject code
– A JSON-LD injection method: direct code access, a plugin like Yoast or RankMath, or Google Tag Manager
– A list of your core services with consistent naming across all pages

Entity inventory:
– Your Organization’s official name (exactly as it appears on legal documents)
– Founding date
– Key leadership names and titles (for Person schema)
– Any authoritative external profiles: LinkedIn Company page, Crunchbase, government business registrations

SameAs research:
– Identify which external entities link to or reference your company
– Check Wikidata for an existing entry (rare for mid-market companies, but check)
– Document your LinkedIn Company URL, Crunchbase profile, and any industry association listings

The common mistake I see? Implementing new schema without first auditing what’s already there. Conflicting schema types (like having both Organization and LocalBusiness on the same page) cause validation errors that can undermine your entire structured data strategy.

The B2B Service Page Schema Stack: What Actually Matters

Not all schema types carry equal weight for B2B service companies. Let me give you the priority order we use at NAV43:

Organization schema is foundational. Without it, AI engines have no verified entity to attribute expertise to. Without this baseline, your company doesn’t exist in the knowledge graph.

Service schema connects what you do to who you are. This is where most B2B companies drop the ball. They describe their services in marketing copy but never structure that data in a machine-parsable format. Service schema tells AI systems exactly what problems you solve and for whom.

FAQ schema remains essential for AEO, and I’ll defend this position most strongly. Google killed FAQ rich results in May 2026, and many B2B companies abandoned FAQ schema entirely. That’s exactly wrong. AI platforms like ChatGPT, Perplexity, and Google AI Overviews still parse and cite FAQ-marked content. Pages with valid FAQPage, HowTo, and QAPage schema appear 20-30% more often in AI-generated summaries (LLMReach, 2025).

Person schema for key leadership provides the E-E-A-T signals that AI systems use for trust verification. When Perplexity needs to verify that a claim comes from a legitimate expert, it uses Person schema connected to your Organization.

This stack differs from e-commerce (where Product schema dominates) and local businesses (where LocalBusiness schema is critical). B2B service companies need a different approach: one built for expertise and authority, not transactions or physical locations.

Why Organization Schema Is Your Foundation

Organization schema establishes your company as a verified entity in the Knowledge Graph. Without it, you’re asking AI systems to cite a source they can’t verify.

Core properties to include:
– name: Your official company name
– url: Your homepage URL
– logo: URL to your company logo image
– foundingDate: When your company was established
– description: A concise description of what your company does
– contactPoint: How prospects can reach you

The differentiator most B2B companies miss is the knowsAbout property. This signals topical authority and influences which query categories AI Mode selects you for. A B2B marketing agency should include knowsAbout entries for specific competencies: “search engine optimization,” “marketing automation,” “B2B lead generation,” “HubSpot implementation.”

Google’s March 2026 core update increased the importance of intent-matched schema for AI Mode citation. The companies with specific, accurate knowsAbout properties are getting cited for relevant queries. The companies with generic descriptions are getting skipped.

Service Schema for B2B Pages (Not LocalBusiness)

Here’s a confusion I constantly clear up: Service schema is distinct from LocalBusiness. B2B companies without physical customer locations should NOT use LocalBusiness schema. If your clients don’t walk into your office to receive services, LocalBusiness is wrong.

Service schema properties to include:
– name: The service name (e.g., “B2B SEO Services”)
– description: What the service delivers and for whom
– provider: Links back to your Organization using @id reference
– serviceType: Industry-standard terminology for the service category
– areaServed: Geographic regions where you offer this service

Connect each Service entity to your Organization using @id references. This relationship tells AI systems that your organization is the verified provider of this specific service.

aggregateRating and offers are optional but valuable for trust signals when you have verified reviews or transparent pricing. Most B2B service companies won’t have these, and that’s fine: focus on the core properties first.

FAQ Schema in the Post-Rich-Results Era

Let me address the May 2026 change directly: Google Search has removed FAQ rich results. Many SEO practitioners took this as a signal that FAQ schema is dead. They’re abandoning it at exactly the wrong moment.

Here’s my position: FAQ schema is MORE important now than before.

The value has shifted from SERP real estate to AI citations. AI platforms actively parse FAQPage markup to extract Q&A pairs for answer generation. When ChatGPT or Perplexity encounters a well-structured FAQ on a service page, it has ready-made content blocks designed for citation. Fifty-five percent of AI Overview citations come from the first 30% of the source page (CXL/Search Engine Land, 2025). FAQs positioned near the top of service pages get cited disproportionately.

FAQPage structure:
– Use the mainEntity property containing an array of Question/Answer pairs
– Each Question has name (the question text) and acceptedAnswer (containing the answer text)
– Keep answers concise (2-3 sentences ideal) and quotable
– AI engines lift these directly when generating responses

The companies retreating from FAQ schema are creating an opportunity for those who understand the shift. Don’t follow the crowd into that mistake.

The @graph Structure: Connecting Your Entities for Maximum AI Discoverability

This is where most competitors miss the boat entirely. They implement isolated schema types (Organization in one block, FAQ in another, maybe Service somewhere else) and wonder why AI systems don’t seem to recognize the relationships.

Isolated schema types don’t communicate relationships. AI engines need connected entities to verify expertise, authorship, and topical scope. The @graph approach solves this.

A single JSON-LD block containing multiple interconnected entity types with @id cross-references creates a machine-readable entity graph. The relationship chain works like this:

Organization → Service (provider reference) → FAQPage (about reference) → Person (author/employee reference)

Each entity gets a unique @id: typically its URL or a #fragment identifier like #organization or #service-seo. Other entities then reference that @id to establish relationships.

Here’s the structure in practice:

The provider property in the Service entity points to the Organization’s @id. This tells AI systems that the verified Organization is the source of this specific service. When Perplexity needs to cite an SEO service provider, it can trace the authority chain from the FAQ answer back through the Service to the verified Organization.

This connected structure is what separates AI-citable schema from decorative markup.

SameAs Markup: Entity Verification Without a Wikipedia Page

Here’s the B2B reality: most mid-market companies don’t have Wikipedia pages. That’s fine. SameAs is still critical for entity verification, and you have alternatives.

The sameAs property links your Organization entity to authoritative external profiles, increasing Knowledge Graph confidence scores. It tells AI systems, “This organization exists in these verified external databases.”

Priority order for B2B companies without Wikipedia:

1. Wikidata: If you can get an entry, it’s the gold standard. Wikidata entries require notability criteria, but many B2B companies qualify through industry awards, media coverage, or significant client relationships. The barrier is lower than Wikipedia.
2. LinkedIn Company page URL: Nearly every B2B company has this. Use the company page URL (linkedin.com/company/your-company), not personal LinkedIn profiles.
3. Crunchbase profile: Particularly valuable for funded companies or those with documented business milestones.
4. Government business registration: Corporate filings, business registries, and official registration databases provide hard-to-fake verification.
5. Industry association directories: If you’re a member of a recognized industry body, their member directory listing counts.
6. Official social profiles: Twitter/X, YouTube channel URLs for company accounts.

Quality matters more than quantity. Three authoritative SameAs links beat ten weak ones. A LinkedIn Company page, Crunchbase profile, and industry association listing provide more verification signal than a dozen low-authority social profiles.

The mistake I see constantly: using personal LinkedIn profiles instead of Company page URLs. AI systems need to verify the organization, not an individual employee. Get this right.

Implementation: The Step-by-Step Process

Let’s walk through the implementation systematically. Each step has a clear output you should verify before moving forward.

Step 1: Audit Your Existing Schema

Before adding anything new, document what’s already there.

Tools to use:
– Google Rich Results Test (search.google.com/test/rich-results)
– Schema Markup Validator (validator.schema.org)

Run your homepage and service pages through both tools. Document every schema type currently present. Look for:
– Conflicting types (Organization AND LocalBusiness on the same page)
– Deprecated properties that may cause validation warnings
– Errors that need fixing before new schema deployment

Output: A clean slate or a documented list of fixes needed before proceeding.

Step 2: Build Your Organization Schema First

Your Organization schema goes on your homepage and gets referenced by every other entity.

Organization Schema Checklist:

Property	Required/Recommended	Notes
@type	Required	Always “Organization”
@id	Required	Your homepage URL + #organization
name	Required	Official company name
url	Required	Homepage URL
logo	Required	Full URL to logo image
description	Recommended	1-2 sentences describing the business
foundingDate	Recommended	Year founded
contactPoint	Recommended	Sales or customer service contact
knowsAbout	Recommended	Array of expertise areas
sameAs	Recommended	Array of authoritative external profile URLs

Use the @id format: https://yoursite.com/#organization

Validate the JSON-LD before deployment. Fix any errors or warnings.

Output: Validated Organization JSON-LD ready for your homepage.

Step 3: Create Service Schema for Each Core Service Page

Build one Service entity per service page. Each connects back to your Organization.

• Use the provider property to reference your Organization @id
• Include serviceType using industry-standard terminology
• Write a clear description that explains what the service delivers
• Specify areaServed if you have geographic focus

Output: Service JSON-LD blocks for each service page, all connected to your Organization entity.

Step 4: Add FAQ Schema to Service Pages

Identify 3-5 questions per service page that buyers actually ask. Pull from:
– Sales call recordings
– Customer support tickets
– Search console query data
– Competitor FAQ sections

Structure each as an FAQPage with a Question/Answer mainEntity array. Keep answers concise and quotable (2-3 sentences ideal). AI engines lift these directly.

If applicable, link to the Service or page using the about property.

Output: FAQPage JSON-LD for each service page, with 3-5 question/answer pairs each.

Step 5: Connect Everything with @graph

Combine Organization, Service, and FAQ into a single @graph JSON-LD block on each service page.

• Organization schema (reference from homepage)
• Service schema specific to that page
• FAQPage schema for that service’s questions

Use @id cross-references to link all entities. Validate the complete @graph structure using Schema Markup Validator.

Output: Unified @graph JSON-LD for each service page.

Step 6: Deploy and Monitor

Deployment:
– Inject JSON-LD in the <head> section or before the closing </body> tag
– Re-test every page with Rich Results Test after deployment
– Verify no validation errors appeared during deployment

Monitoring:
– Check Google Search Console weekly for structured data errors
– Access the Generative AI Performance Reports in Search Console (launched June 2026) for AI Overview impression data
– Set a 30-day review checkpoint to identify any validation errors that emerge

Output: Live schema across all service pages, with a monitoring system in place.

What Good Looks Like: The Complete Service Page Schema

Let me walk you through a complete working example. This is what should appear on a B2B service page for SEO services:

Notice how each entity connects:
– The Service references the Organization via the provider property
– The FAQPage references the Service via the about property
– The Organization establishes authority through knowsAbout and sameAs

This is what AI engines can now parse. The relationships are explicit, the expertise is documented, and the answers are quotable.

Measuring Schema Effectiveness for AEO

Here’s the uncomfortable truth: traditional rich result tracking is less relevant now. The measurement challenge has shifted.

Google Search Console’s Generative AI Performance Reports (launched June 2026) provide first-party data on AI Overview and AI Mode impressions. This is your primary measurement source. The limitation: impressions only, not clicks. But impressions indicate citation and visibility, which is exactly what we’re optimizing for.

Manual brand monitoring:
– Search your brand name plus service terms in ChatGPT, Perplexity, and Google AI Mode monthly
– Document whether you appear, in what context, and what content gets cited
– Track changes after schema implementation

Third-party tools:
– Ahrefs AI Overview tracking can monitor which pages get cited in AI Overviews
– Tools like Otterly or AI visibility trackers provide additional citation monitoring

Measurement framework:
1. Establish baseline before schema implementation
2. Measure at 30 days: look for validation errors and initial impression changes
3. Measure at 60 days: look for AI citation patterns
4. Measure at 90 days: assess whether citation frequency is improving

Only 38% of AI Overview citations now come from pages ranking in Google’s top 10 (Ahrefs, 2026). Schema is a visibility lever independent of traditional rankings. You may not rank #1 for a query but still get cited in the AI Overview. That’s the measurement paradigm shift to embrace.

The Service Page Schema Quick-Reference

Schema Type	Required Properties	Recommended Properties	AEO Priority
Organization	name, url, logo	foundingDate, description, contactPoint, knowsAbout, sameAs	Critical
Service	name, provider, serviceType	description, areaServed, aggregateRating	High
FAQPage	mainEntity (Question/Answer array)	about	High
Person	name, jobTitle, worksFor	sameAs, knowsAbout	Medium

Implementation priority:
1. Organization schema on homepage (this week)
2. Service schema for each core service page (next week)
3. FAQ schema for each service page (week three)
4. Connect everything using @graph structure (week four)

What to Do Next

The B2B companies implementing a structured data strategy now are positioning themselves for the next 2-3 years of AI search evolution. The compounding advantage starts the moment your entities connect and get verified.

Key takeaways:

• Organization schema is foundational: without it, AI engines have no verified entity to cite
• FAQ schema is MORE important after Google killed rich results because AI platforms still parse and cite FAQ-marked content
• The @graph structure connecting entities is what separates AI-citable schema from decorative markup
• SameAs properties linking to LinkedIn, Crunchbase, and Wikidata establish entity verification without a Wikipedia page
• Ninety-four percent of B2B buyers used generative AI tools during their purchase process (6sense, 2025); this is the channel that matters

Your next steps:

1. Audit your existing schema this week using Google Rich Results Test
2. Build and deploy Organization schema with complete knowsAbout and sameAs properties
3. Create Service schema for your three highest-priority service pages
4. Add FAQ schema with 3-5 quotable questions per service page
5. Connect everything using the @graph structure before the end of the month

If you want expert guidance on implementing service page schema for AEO, get a free growth plan from NAV43. We’ll audit your current structured data, identify the gaps, and build the implementation roadmap that connects your expertise to AI discoverability.

The companies with the cleanest entity data will compound their visibility advantage. Start building yours now.