WEBVTT

1
00:00:00.000 --> 00:00:07.467
Schema markup is code you add to your
website that tells AI systems exactly what your content means.

2
00:00:07.467 --> 00:00:10.945
Without schema, AI has to guess.

3
00:00:10.945 --> 00:00:29.047
With schema, you explicitly tell it: •
'This is a local business' • 'This is our address' • 'These are our hours' • 'This is a FAQ section' Think of it as providing AI with a clearly labeled data sheet about your business.

4
00:00:29.047 --> 00:00:37.677
Schema is typically added as
JSON-LD—JavaScript Object Notation for Linked Data.

5
00:00:37.677 --> 00:00:39.950
Don't worry if that sounds technical.

6
00:00:39.950 --> 00:00:43.663
Many website platforms have plugins that
handle this for you.

7
00:00:43.663 --> 00:00:47.087
LocalBusiness schema is your digital
business card.

8
00:00:47.087 --> 00:01:14.661
Required properties: • @type:
'LocalBusiness' or a specific type like 'Restaurant' or 'Dentist' • name: Your official business name • address: Street, city, state, postal code • telephone: Primary phone number Recommended properties: • openingHours • geo: Latitude and longitude • areaServed • priceRange • image • description • sameAs: Links to social profiles IMPLEMENTATION OPTIONS: • WordPress plugins: Yoast, Rank Math, Schema Pro • Website builder tools: Wix and Squarespace have built-in options • Manual JSON-LD code • Google Tag Manager FAQPage schema is powerful for AI visibility.

9
00:01:14.661 --> 00:01:19.249
It marks up question-and-answer content
that AI loves to cite.

10
00:01:19.249 --> 00:01:47.612
Create effective FAQs by thinking about
what customers actually ask: • 'What are your hours?' • 'Do you offer emergency drain cleaning?' • 'How much does plumber cost?' • 'Do you serve Metro Detroit?' Best practices: • Answer questions concisely—2-3 sentences ideal for voice • Use natural language • Include location and service specifics • Only use FAQ schema for actual Q&A content Always test before deploying: TOOLS: • Google Rich Results Test: search.google.com/test/rich-results • Schema.org Validator: validator.schema.org Common errors to avoid

11
00:01:47.612 --> 00:02:02.098
• Missing required properties • Invalid
JSON syntax • URLs that don't exist • Schema that doesn't match visible page content You now understand schema basics!

12
00:02:02.098 --> 00:02:07.613
In Module 5, we'll cover creating content
that AI can easily cite.

