Schema Markup for AI Search: Make Your Business Facts Unmistakable
Structured data won't get you into AI answers, but it gives every system reading your site less room to guess wrong.

When AI Tools Describe Your Business, Do They Get It Right?
More buyers ask ChatGPT, Perplexity, and Google AI Overviews about businesses before they ever visit a website. When the facts about your company are scattered across pages, inconsistent with your Google Business Profile, or contradicted by old directory listings, the answers those tools generate can be vague, incomplete, or flat wrong. A prospect searches for a physical therapist who treats runners, and the AI answer says you closed your second location last year. You didn't. Or it lists a phone number you haven't used in three years.
The question operators ask is whether schema markup, structured data, or some new AI-specific tag will fix this. The short answer from Google is no. Google states plainly that there are no additional requirements or special optimizations to appear in AI Overviews or AI Mode, and no special schema.org structured data you need to add. Schema markup is not a ranking hack, not an AI switch, and not a way to buy your way into answer engines.
What structured data does do, per Google, is give explicit clues about the meaning of a page, help Google understand content, and gather information about entities such as companies. Organization markup can help Google understand administrative details and disambiguate your organization. Google's AI features guidance lists making sure your structured data matches the visible text on the page among the SEO fundamentals that remain worthwhile.
So the real job is entity clarity. One consistent, accurate set of business facts, expressed in visible page text and mirrored in markup, so that any system reading your site has less room to guess or get it wrong. That includes Google Search, Google AI Overviews, and any other service, tool, or platform that crawls the public web. No AI company has published a rule that schema earns you a mention, so treat markup as a way to remove ambiguity, not as a lever. Clear, consistent, machine-readable facts reduce guessing for any system that reads the public web, and Google notes schema.org vocabulary may be useful for other search engines, services, tools, and platforms.
This guide walks through the practical steps to build that clarity. If you want the broader AEO and GEO playbook, content structure for citation, measurement routines, and the 30-day checklist, see our post on getting cited by AI answers. This post focuses on structured data, the business fact sheet, and keeping the story straight.
What Structured Data Is, in Plain Language
Structured data is a standardized format for providing information about a page and classifying the page content. Instead of a paragraph that says "We are open Monday through Friday, 9 a.m. to 6 p.m.," structured data uses a label like openingHoursSpecification with fields for dayOfWeek, opens, and closes. The words on the page are for people. The structured data is for machines.
Most structured data for search uses the schema.org vocabulary, a shared standard. Google's documentation is definitive for how Google Search behaves. schema.org itself has more attributes and types than Google requires or uses, and those additional properties may be useful for other search engines, services, tools, and platforms.
There are three formats. JSON-LD is a block of JavaScript Object Notation for Linked Data, usually placed in a script tag in the head or body of the page. Microdata and RDFa are markup embedded directly in the HTML tags. All three are equally valid if implemented correctly. Google recommends JSON-LD because it is easiest to maintain at scale, is not interleaved with the user-visible text, and can be read even when dynamically injected by JavaScript or a CMS widget. That is the format we describe in this guide.
Google's introduction to structured data and the broader documentation library are your primary reference. Read Google's introduction to structured data before you write a single line of markup. The documentation explains what Google does with the data, what it ignores, and what can trigger a manual action.
Step 1: Build the Business Fact Sheet First
Do not open a code editor or a plugin settings page until you have a single source of truth for every public fact about your business. This is the fact sheet, and it is the foundation. Every page on your site, every piece of markup, your Google Business Profile, your directory listings, and any AI agent that represents you will copy from this document.
Start with the legal name and the public name. If they differ, note both. The legal name goes in the legalName field. The public name goes in the name field. If you are known by more than one name, a nickname, an acronym, or a former name that buyers still use, list those as alternateName values. The name you use in markup must match the name you use on your site and in your profiles.
Write a one-sentence description of what you do. Not marketing copy. A factual statement. Picture a hypothetical two-location physical therapy clinic: "We provide physical therapy, sports injury rehabilitation, and wellness services to patients in the region." Picture a hypothetical residential roofing company serving three counties: "We install, repair, and replace asphalt shingle, metal, and tile roofs for homeowners in [County A], [County B], and [County C]." This sentence will become the description field and will guide how you pick your schema.org type.
Choose a primary category. If you are a local business, this is the most specific schema.org LocalBusiness subtype that fits: Dentist, Restaurant, AutoRepair, LegalService, Electrician, and so on. If you are an online-only business, a consulting firm, or an agency, you will usually start with Organization or a subtype like Corporation, depending on what schema.org defines.
For each physical location, write the full street address, city, state or province, postal code, and country. Include the phone number with country code and area code. Include the email address if you publish it. Write out the hours of operation for each day of the week, using 24-hour time or a consistent format. Note any seasonal closures, holiday hours, or temporary changes. If you serve customers at their location and do not have a public storefront, note that and define your service area by city, county, state, or postal code list.
List every service you offer that you want the public to find. Not internal project names. The names customers use. For each service, note the areas you serve if they differ from your main service area, and any audience or eligibility restrictions if relevant.
Identify the URL of your logo file. Make sure it is at least 112 pixels square, crawlable, indexable, and looks correct on a white background. Note the founding date if you want it public. List the official URLs of every profile you control: LinkedIn, Facebook, X, Instagram, Yelp, Better Business Bureau, industry directories, review sites. Only include profiles that are active, that you control, and that genuinely describe your business. Do not list competitor pages, aggregator sites that mention you, or profiles you do not own.
Who owns this fact sheet? One person. Where does it live? A shared document in Google Docs, Notion, or Confluence. A record in your CRM. A version-controlled file in your operations repository. Not in someone's head. Not in an old spreadsheet no one can find. The rule is simple: if a fact about the business changes, the fact sheet changes first, and then everything else updates from it.
Google's AI features guidance reminds you to keep your Business Profile and Merchant Center information up to date. The fact sheet is how you do that. It is also how you keep your website text, your markup, and your AI agents aligned.

Step 2: Pick the Right Schema Types
Schema.org defines hundreds of types. You need to pick the handful that describe your business and your pages accurately. Start with the difference between Organization and LocalBusiness.
Organization is the general type for any company, nonprofit, government body, or organized group. LocalBusiness is a subtype of Organization and is defined by schema.org as a particular physical business or branch of an organization. Examples include a restaurant, a particular branch of a restaurant chain, a branch of a bank, a medical practice, a club, or a bowling alley. If you have a physical location where customers or clients come to you, or if you operate from a storefront and serve a defined local area, you use LocalBusiness or one of its subtypes.
Google's local business structured data documentation tells you to use the most specific subtype that applies. The schema.org LocalBusiness type page lists dozens of subtypes: AnimalShelter, AutomotiveBusiness, ChildCare, Dentist, DryCleaningOrLaundry, EmergencyService, EmploymentAgency, EntertainmentBusiness, FinancialService, FoodEstablishment, GovernmentOffice, HealthAndBeautyBusiness, HomeAndConstructionBusiness, InternetCafe, LegalService, Library, LodgingBusiness, MedicalBusiness, ProfessionalService, RadioStation, RealEstateAgent, RecyclingCenter, SelfStorage, ShoppingCenter, SportsActivityLocation, Store, TelevisionStation, TouristInformationCenter. Many of these have further subtypes. A Dentist is more specific than a LocalBusiness. A Plumber is more specific than a HomeAndConstructionBusiness. Use the most specific type that fits.
If you have multiple locations, each location gets its own LocalBusiness block with its own address, phone, hours, and URL. If you have one headquarters and three branch offices, that is four LocalBusiness items. If you are a service-area business with a physical office but you go to the customer, you still use LocalBusiness and specify the area you serve.
If you are an online-only business, a consulting firm, a software company, or an agency with no public storefront, you typically use Organization or a relevant subtype. You do not use LocalBusiness unless you meet the schema.org definition.
You can assign multiple types to a single entity by using an array. For example, a business might be both a LocalBusiness subtype and a specific Organization subtype. Google's documentation notes that additionalType is not supported for LocalBusiness, so use an array of types in the type field if you need more than one.
For individual service pages, schema.org defines a Service type. A Service is provided by an organization and has properties like provider, serviceType, areaServed, audience, and hasOfferCatalog. Google does not list Service as a rich result feature in the search gallery, so marking up services is for clarity and disambiguation, not for a visual search feature. If you have a page that describes a specific service, you can add Service markup with a provider field that points to your business entity.
For blog posts and articles, use the Article type and include author information. For navigation breadcrumbs, use BreadcrumbList to describe the site hierarchy. For team member pages or founder bios, use ProfilePage if the page is genuinely about that person. Only use a type when the page actually is that thing. Do not mark up a service page as an Article. Do not mark up a blog post as a LocalBusiness.

Step 3: The Entity Graph with @id and sameAs
Structured data is not just a set of labels on one page. It is a graph. Entities reference each other. The business entity appears on the home page, on every location page, on every service page, and in the author field of every article. If you redefine the business from scratch in every block, you create ambiguity. If you give the business a stable identifier and reference it everywhere else, you create clarity.
The @id property is a stable identifier for an entity. It is a URL on your own domain that represents the thing, not necessarily a page you visit. For example, if your business operates from a domain, you might use "[your-domain]/#organization" as the @id for the business. That URL does not have to resolve to a page. It is a name in the graph.
Google's structured data guidelines note that you can use @id to link items that are more helpful together. When you define the Organization or LocalBusiness on your home page, you give it an @id. When you add markup to a service page, the provider field points to that @id instead of redefining the entire business. When you add Article markup to a blog post, the author or publisher field points to that @id. Now every piece of markup on your site agrees on what the business is, because they all point to the same identifier.
The sameAs property is different. It is a URL of a reference page that unambiguously indicates the item's identity. That is the schema.org definition. Google's Organization documentation describes it as a URL of a page on another website with additional information about your organization, such as a social media profile or a review site profile. You can list multiple sameAs URLs.
Only list profiles you control or that genuinely describe you. Your LinkedIn company page, your Facebook page, your Yelp listing, your Better Business Bureau profile. Do not list a competitor's page. Do not list a Wikipedia page unless you have one and it is about you. Do not list an aggregator site that mentions you in passing. Keep the list current. If you close a profile or rebrand, update the sameAs list.
The name in your markup must match the name you use on your site and in those profiles. If your website says one thing and your LinkedIn page says another, pick one and make them match. If you are known by both names, use name for the primary and alternateName for the other.
Field Maps: Three Worked Examples
The following are not code. They are field maps, written as lists, showing what goes into each property for three hypothetical businesses. Use these as templates when you build your own markup.
Example A: Home Page Organization for a Consulting Firm
Imagine a hypothetical consulting firm, online only, no physical office open to clients. The firm has a LinkedIn page, an X profile, and a profile on a professional directory. Here is what the Organization markup on the home page would include:
@context: the schema.org context value (the same on every block)
@type: "Organization" (used here because the firm operates without a storefront; if the firm later opens an office that clients visit, a LocalBusiness subtype for that location may fit)
@id: "[your-domain]/#organization"
name: "[public business name]"
url: "[your-domain]"
logo: "[your-domain]/[logo-file]"
description: "We provide strategic planning, operational improvement, and change management consulting to mid-market manufacturing and distribution companies."
foundingDate: "[founding date in YYYY-MM-DD format]"
email: "[public email from the fact sheet]"
telephone: "[phone with country and area code]"
sameAs: an array of your official profile URLs, for example your LinkedIn company page and your Google Business Profile or Yelp listing
address: a PostalAddress for the mailing address, only if you publish it on the page
This block lives on the home page or the about page, not on every page of the site.
Example B: Location Page LocalBusiness for a Physical Therapy Clinic
Imagine a hypothetical two-location physical therapy clinic. One location page would include LocalBusiness markup with these fields:
@context: the schema.org context value (the same on every block)
@type: the most specific schema.org LocalBusiness subtype that fits, for example MedicalClinic; confirm the best match on schema.org before you ship
@id: "[your-domain]/locations/[city]#location"
name: "[business name] - [city]" (required)
url: "[your-domain]/locations/[city]" (recommended, the URL of this specific location page)
telephone: "[phone with country and area code]" (recommended)
email: "[location email from the fact sheet]"
address: a PostalAddress object (required) with streetAddress "[street address]", addressLocality "[city]", addressRegion "[state or province code]", postalCode "[postal code]", addressCountry "[country code]"
geo: a GeoCoordinates object (recommended) with latitude "[latitude to at least five decimal places]" and longitude "[longitude to at least five decimal places]"
openingHoursSpecification: an array of objects, each with dayOfWeek (for example "Monday"), opens "08:00", closes "18:00"; one object per day or range of days; if the clinic has seasonal closures, add validFrom and validThrough dates to the relevant specification
image: "[your-domain]/[image-file]"
priceRange: "$$" (optional, under 100 characters, a rough indicator)
parentOrganization: an Organization object or reference to the @id of the main organization defined on the home page, "[your-domain]/#organization"
Google requires name and address for LocalBusiness. Google recommends url, telephone, geo, and openingHoursSpecification. Google recommends aggregateRating and review only for sites that capture reviews about other local businesses, so a physical therapy clinic marking up its own location should not include review markup unless it is a review platform.
Example C: Service Page Service Markup for a Roofing Company
Imagine a hypothetical residential roofing company serving three counties. The company has a service page for asphalt shingle roof installation. The Service markup on that page would include:
@context: the schema.org context value (the same on every block)
@type: "Service"
@id: "[your-domain]/services/[service-name]#service"
serviceType: "Asphalt Shingle Roof Installation"
provider: an Organization or LocalBusiness object, or a reference to the @id of the business, "[your-domain]/#organization"
areaServed: an array of Place objects or text strings, each naming a county: "[County A]", "[County B]", "[County C]"
description: "We install new asphalt shingle roofs on residential homes, including tear-off, deck inspection and repair, underlayment, shingle installation, and cleanup."
url: "[your-domain]/services/[service-name]"
audience: if relevant, a text description or Audience object, for example "Homeowners in the service area"
hasOfferCatalog: optional, an OfferCatalog object if you want to list variations or packages within the service
Service is not a Google rich result feature, so this markup will not produce a special visual element in search results. It is for clarity, so that any system reading the page understands what the service is, who provides it, and where it is available.
What NOT to Mark Up
Structured data must describe content that is visible on the page. Do not add markup for information that does not appear in the text, images, or other user-facing content. Do not create blank pages just to hold structured data. Do not mark up facts that differ from what the page says. If the page says you are open until 6 p.m. and the markup says 5 p.m., that is a violation.
Do not add self-serving review stars to your own business pages. Google's local business structured data documentation recommends aggregateRating and review only for sites that capture reviews about other local businesses. If you are a restaurant marking up your own restaurant page, do not add review markup. If you are a review platform that publishes reviews written by users about many restaurants, you may add review markup to those restaurant pages. Google's guidelines warn against marking up fake reviews, and say reviews or ratings not by actual users may result in a manual action. A manual action means the page loses eligibility for rich results and the structured data is ignored. It is not a ranking penalty in web search, but it removes any benefit the markup might have provided.
Do not stuff every page on your site with the full Organization or LocalBusiness block. Google's Organization documentation says to place Organization markup on the home page or a single page that describes the organization, such as an about page. You do not need it on every blog post, every service page, and every contact form. Use @id to reference the organization from other pages instead of redefining it everywhere.
Do not impersonate another person or organization. Do not misrepresent ownership, affiliation, or primary purpose. If you are an authorized dealer or partner, you can say that in visible text and in a relevant property, but do not claim to be the manufacturer or the brand owner if you are not.
Do not mark up content that is irrelevant or misleading. If your page is about roof repair and you add markup claiming it is a medical clinic, that is misleading. If your page lists services you do not actually offer, that is misleading. Google does not guarantee that valid structured data will show in search features, and one reason is that the data may be incorrect in ways the automated test cannot catch. Misleading markup can also be marked as spam or lead to a manual action, and a structured data manual action means the structured data on the page is ignored.
FAQ Markup Reality Check
Many guides and plugins still recommend adding FAQPage structured data to pages with frequently asked questions. As of May 7, 2026, the FAQ rich result feature no longer appears in Google Search. Google deprecated the feature and removed it from the list of supported structured data features in the search gallery. Adding FAQPage markup will not produce a rich result in Google.
That does not mean you should remove FAQ sections from your pages. A visible FAQ section that answers real questions buyers ask is still useful to readers. Clear question-and-answer text is also easy for any reader, human or machine, to quote accurately. But the FAQPage structured data itself does not trigger a special display in Google Search anymore, so do not implement it expecting a rich result.
If you already have FAQPage markup on your site and it is accurate and matches the visible content, you can leave it in place. It will not hurt anything. It may be useful to other platforms or tools. But do not spend time adding it to new pages for Google's benefit.
Step 4: Implement on Your Stack
How you add structured data depends on your website platform. If you use WordPress, many SEO plugins and themes include settings pages where you can enter business information and the plugin generates JSON-LD. Check your theme documentation and your plugin settings. If you use a different content management system like Webflow, Squarespace, Wix, or Shopify, look for structured data or schema settings in the site settings or SEO panel. Some platforms generate basic Organization or LocalBusiness markup automatically if you fill in business details in the CMS.
If your CMS does not have built-in structured data support, or if you need more control, you can hand-code JSON-LD and place it in the head or body of the page. JSON-LD is a script tag with type "application/ld+json" and a JSON object inside. You can add it to a global header template so it appears on every page, or you can add it to individual page templates. Many operators use a custom field in the CMS to hold the JSON-LD for each page and output it in the template.
Google Tag Manager and custom JavaScript are also common methods. Google can read JSON-LD that is dynamically injected by JavaScript or CMS widgets. One caution: dynamically generated Product markup can make Shopping crawls less frequent and less reliable, according to Google's documentation. If you are marking up products for Google Shopping, server-side rendering or static JSON-LD is safer.
The most common real-world problem is duplicate or conflicting structured data. A theme outputs one Organization block. A plugin outputs another. A developer added a custom block years ago and no one remembers. Conflicting blocks send mixed signals about basic facts, which is the opposite of what you want. Pick one source. Turn off the others. If you are using a plugin, disable any theme-generated schema. If you are hand-coding, disable the plugin schema for the types you are managing manually.
Step 5: Validate and Monitor
Before you deploy structured data to a live page, validate it. Google provides the Rich Results Test. Paste the URL of a staging page or paste the HTML and JSON-LD directly into the tool. The test will tell you if the markup is valid, if required properties are missing, and if the page is eligible for any rich result features. The Rich Results Test is specific to Google.
For general schema.org validity, use the Schema Markup Validator. This tool checks whether your JSON-LD conforms to the schema.org vocabulary, regardless of whether Google uses it for a rich result. It will catch syntax errors, unknown properties, and type mismatches.
Once the markup is on a live page, use the URL Inspection tool in Google Search Console. Enter the URL, and Google will show you the rendered HTML and the structured data it detected. This is what Google actually sees after JavaScript executes, after redirects, after any server-side rendering. If the structured data is missing or different from what you expected, the URL Inspection tool will show you.
Make sure the page is not blocked by robots.txt, a noindex tag, or a login wall. Structured data on a page that Google cannot crawl or index is invisible to Google. After you confirm the page is crawlable and the markup is present, request a recrawl using the URL Inspection tool. Allow several days for Google to process the page. Submit a sitemap in Search Console to keep Google informed of future changes.
After deployment, monitor the rich result status reports in Search Console. These reports show how many pages have valid structured data, how many have errors, and how many are eligible for rich results. Pages can break after deployment because of template changes, caching issues, or server configuration. A report that shows errors two weeks after launch means something changed. Check the URL Inspection tool again and compare the live page to your staging version.
Fewer, complete, accurate properties are better than many properties with incomplete or inaccurate data. Do not add every possible schema.org property just because it exists. Add the required properties for eligibility, add the recommended properties that apply to your business, and stop. Quality over quantity.
Step 6: Keep It True Over Time
Structured data is not a one-time project. Business facts change. You move an office. You change your phone number. You add a service. You close for a holiday. You rebrand. Every change must flow from the fact sheet to the website text, to the markup, to the Google Business Profile, to the directories, to the AI agents.
Attach a change log to the fact sheet. Every time a fact changes, note the date, the old value, the new value, and who made the change. This log is your audit trail. It also reminds you to update every downstream system.
Define the triggers that require an update. New phone number: update fact sheet, website contact page, footer, markup, Business Profile, directories, email signature. Moved location: update fact sheet, location page text, address markup, geo coordinates, Business Profile, directories, any printed materials. New service: update fact sheet, add or update service page, add Service markup, update service list on home page, update Business Profile services. Holiday hours: update fact sheet with validFrom and validThrough dates, update openingHoursSpecification markup, update Business Profile special hours, post a notice on the website. Rebrand or name change: update fact sheet, update name and alternateName in markup, update all profiles, update sameAs URLs if profile URLs changed, update logo file and logo URL in markup.
Run a quarterly audit. Compare the website text to the markup. Compare the markup to the Google Business Profile. Compare the Business Profile to the top five directory listings. Look for drift. A phone number that is correct on the contact page but wrong in the markup. An address that is correct in the markup but wrong on Yelp. An old service that is still listed in a directory but removed from the website. Fix the discrepancies.
Ask AI tools how they describe you. Search for your business name in ChatGPT, Perplexity, and Google AI Overviews. Read the answers. If a fact is wrong, trace it back. Check your website. Check your markup. Check your Business Profile. Check the top directories. Find the source of the wrong fact and correct it. This is part of the broader AEO measurement routine, covered in the other post, but the principle applies here: wrong facts in AI answers often come from inconsistent facts on your own properties.
Where the CRM Fits
The business fact sheet can live in a document, but for many operators the better home is the CRM. The CRM already holds customer data, service definitions, location records, and team information. If the CRM is the system of record for those facts, it can also feed the website and the AI agents, so the same facts power your public markup and your customer-facing automation.
If your business record already lives in a CRM, GoHighLevel is the place your team should maintain it. GoHighLevel holds contacts, opportunities, service definitions, location records, and team information in one system. The goal is that the facts your Conversation AI chatbot or Managed Agents give contacts should match the facts in your site text and markup, because they come from the same record.
Printable Entity Clarity Checklist
Use this checklist to audit your current state and plan your implementation.
Business fact sheet exists, is owned by one person, and lives in a shared accessible location.
Fact sheet includes legal name, public name, alternateName if applicable, one-sentence description, primary schema type.
Fact sheet includes full address for each location, phone with country and area code, email, hours for each day, seasonal closures.
Fact sheet includes service list, service area, audience or eligibility notes, logo URL, founding date if public.
Fact sheet includes official profile URLs for LinkedIn, Facebook, X, Yelp, BBB, and any other active profiles you control.
Website text matches the fact sheet for name, address, phone, email, hours, services on every relevant page.
Google Business Profile matches the fact sheet for name, address, phone, hours, services, categories.
Top five directory listings match the fact sheet for name, address, phone.
Home page or about page has Organization or LocalBusiness markup with @id, name, url, logo, description, address, telephone, sameAs.
Each location page has LocalBusiness markup with the most specific subtype, address, geo coordinates, telephone, openingHoursSpecification, url.
Service pages have Service markup with provider pointing to the business @id, serviceType, areaServed, description, url.
Blog posts have Article markup with author and publisher pointing to the business or author @id.
Breadcrumb navigation has BreadcrumbList markup if breadcrumbs are visible.
No FAQPage markup added expecting Google rich results.
No review or aggregateRating markup on your own business pages unless you are a review platform.
No structured data on pages blocked by robots.txt, noindex, or login.
No duplicate Organization or LocalBusiness blocks from multiple plugins or themes.
Markup validated with Rich Results Test and Schema Markup Validator before deployment.
Live pages checked with URL Inspection tool to confirm Google sees the markup.
Sitemap submitted in Search Console.
Rich result status reports monitored monthly for errors.
Change log attached to fact sheet, updated every time a business fact changes.
Quarterly audit scheduled to compare website text, markup, Business Profile, and directories.
AI answer engine spot checks scheduled monthly to verify correct facts.
Common Mistakes and Fixes
Mistake: Markup Does Not Match Visible Text
The markup says you are open until 6 p.m., but the page text says 5 p.m. The markup lists a service you removed last year. The markup uses the old business name. Google's AI features guidance and structured data policies both emphasize that structured data must match the visible text on the page. Fix: audit every page with markup. Compare the JSON-LD to the text. Update the markup or update the text so they agree. If they cannot agree, remove the markup.
Mistake: Using LocalBusiness for an Online-Only Business
You are a consulting firm with no physical office open to clients, but you used LocalBusiness because you wanted to appear in local search. LocalBusiness is defined by schema.org as a particular physical business or branch. If you do not have a storefront or a location where customers come to you, use Organization or a relevant subtype. Fix: change the type to Organization. Remove address and geo if there is no public location. If you serve a specific area, use areaServed to define it.
Mistake: Redefining the Business on Every Page
Every service page, every blog post, and every location page has a full Organization block with name, address, logo, and sameAs. This creates dozens of copies of the same entity, and if one copy has a typo or an old phone number, you have inconsistency. Fix: define the business once on the home page or about page with an @id. On other pages, reference that @id in the provider, publisher, or author field instead of copying the entire block.
Mistake: Adding Review Markup to Your Own Business
You added aggregateRating and review properties to your LocalBusiness markup, using reviews from your own testimonials page or made-up ratings. Google recommends review markup for LocalBusiness only on sites that capture reviews about other local businesses. Self-serving reviews can trigger a manual action. Fix: remove the aggregateRating and review properties from your own business pages. If you have genuine third-party reviews on Yelp, Google, or another platform, link to those profiles in sameAs and let the platforms display the reviews.
Mistake: Using FAQPage Markup Expecting a Rich Result
You added FAQPage markup to your FAQ page because a plugin recommended it or an old guide said it would get you a rich result. Google deprecated the FAQ rich result as of May 7, 2026. Fix: you can leave the markup in place if it is accurate, but do not expect a rich result. Focus on making the visible FAQ content clear and useful. Do not add FAQPage markup to new pages for Google's benefit.
Mistake: Blocking Structured Data Pages from Crawling
The page with your best markup is blocked by robots.txt, has a noindex tag, or is behind a login. Google cannot see it. Fix: check robots.txt and the page source. Remove any crawl blocks. Remove noindex tags unless the page truly should not be indexed. Make sure the page is publicly accessible. Use the URL Inspection tool to confirm Google can crawl and render the page.
Mistake: Ignoring Validation Errors
You deployed the markup without testing it. The Rich Results Test shows errors: missing required properties, invalid date formats, malformed URLs. You assume it is fine because the page looks normal. Fix: run every page with structured data through the Rich Results Test and the Schema Markup Validator before deployment. Fix all errors. Required properties are required. Markup with errors may not be usable, and items missing required properties are not eligible for rich results.
Mistake: Setting and Forgetting
You implemented structured data two years ago and never looked at it again. The business moved, the phone number changed, you added three new services, and none of it is reflected in the markup. Fix: treat structured data as a living system. Update it when facts change. Run quarterly audits. Check the Search Console rich result reports. Schedule it like any other maintenance task.
How SumoGrowth Labs Helps
SumoGrowth Labs is an AI implementation and consulting agency. We are the team that audits your entity facts, builds the fact sheet, implements and validates the structured data, and keeps your CRM, website, and AI agents aligned. We do entity and fact-sheet audits to find inconsistencies across your site, profiles, and directories. We implement schema markup on WordPress, custom CMS platforms, and headless architectures. We clean up duplicate or conflicting markup from multiple plugins or old custom code. We validate the markup with the Rich Results Test and Schema Markup Validator, deploy it, and monitor the Search Console reports. We set up the change log and audit schedule so your facts stay true over time. We connect your CRM business record to your public markup and your AI agents, so the same source of truth powers everything. If you need help getting your business facts unmistakable, we do the work.
by Darius Gaynor


