Schema markup is usually discussed as a way to earn enhanced Google search results.
Businesses add structured data for products, articles, events, frequently asked questions and local organisations in the hope of securing ratings, prices, breadcrumbs or other additional features in the search results.
However, schema can serve a much wider purpose.
It can help you examine whether your website clearly explains:
- Who your business is.
- What products or services it provides.
- Where it operates.
- Who works for the organisation.
- What qualifications, experience and evidence support its claims.
- How all these pieces of information relate to one another.
This becomes increasingly important as Google and AI search platforms attempt to understand businesses as connected collections of entities rather than pages containing particular keywords.
Used properly, schema markup can become more than technical code. It can provide a framework for finding gaps in your website’s content and identifying information that search engines, AI platforms and potential customers may struggle to understand.
What is an entity?
An entity is a distinct person, place, organisation, product, service, event or concept that can be identified and described.
For a local plumbing company, important entities might include:
- The plumbing business.
- The owner and individual engineers.
- Boiler installation.
- Boiler servicing.
- Emergency plumbing.
- Gas Safe registration.
- The towns and postcodes served.
- The boiler manufacturers the engineers work with.
- Completed projects and customer reviews.
These are not simply keywords to include on a page. They are identifiable elements of the business with relationships between them.
For example:
- The plumbing company provides boiler installation.
- The engineer works for the plumbing company.
- The engineer holds a relevant qualification.
- The business serves Preston and the surrounding area.
- A case study demonstrates a completed boiler installation.
- A customer review describes the service received.
When these connections are clear, a search or AI system has more context with which to understand the business.
What is a website knowledge graph?
A knowledge graph connects entities through defined relationships.
The entities can be imagined as individual points, while the relationships form the connections between them.
A business website already contains the beginnings of a knowledge graph. Its homepage, service pages, team profiles, location pages, case studies and contact information all describe different aspects of the same organisation.
The problem is that these details are often fragmented.
A website might claim to serve Lancashire on its homepage, list a Preston address on its contact page and mention boiler installations in an old blog post. If the information is inconsistent, poorly linked or not explained properly, machines may struggle to establish how everything fits together.
A well-organised website creates a more coherent picture:
- The organisation has a consistent name and identity.
- Its services have dedicated, informative pages.
- Its service areas are accurately defined.
- Its team members are associated with the business.
- Qualifications and accreditations can be verified.
- Case studies demonstrate relevant experience.
- Internal links connect related information.
Schema can explicitly describe some of these entities and relationships, while the visible content provides the detail and evidence behind them.
How schema markup helps machines understand a website
Schema markup is structured information added to a webpage, commonly using JSON-LD.
Instead of requiring a search engine to infer every detail from the visible copy, the markup can explicitly identify that something is an organisation, person, service, product, article, location or event.
Google explains that structured data provides explicit clues about the meaning of a page and can be used to understand people, companies and other information described on the web.
A basic piece of LocalBusiness schema might identify:
- The business name.
- The website address.
- The logo.
- The telephone number.
- The physical address.
- The geographic area served.
- Relevant social and business profiles.
Other markup can describe an article and its author, a product and its manufacturer, or an event and its location.
The value is not simply the individual facts. It comes from joining those facts into a consistent representation of the business.
Schema is not a shortcut to AI recommendations
It is important not to overstate what structured data can achieve.
Adding schema does not guarantee that a website will:
- Rank more highly in Google.
- Appear in an AI Overview.
- Be cited by ChatGPT.
- Become a recommended local provider.
- Receive a rich result.
Schema can help systems interpret information, but it cannot make unsupported claims true or compensate for weak content.
There is also mixed evidence about how individual AI platforms process on-page JSON-LD. Some systems may use search indexes or other intermediaries rather than reading the markup directly from every webpage.
The sensible approach is therefore to treat schema as part of your website infrastructure—not as an AI visibility trick.
Visibility may improve when a business becomes easier to understand, verify and associate with relevant subjects. Schema is only one part of achieving that.
Use schema as a website audit framework
Before writing any code, list the entities an ideal customer would need to understand before choosing your business.
For a plumber, this might include:
- The company.
- Its engineers.
- Gas Safe registration.
- Emergency plumbing.
- Boiler repairs, servicing and installations.
- Domestic and commercial customers.
- Boiler brands supported.
- Service locations.
- Opening and emergency call-out hours.
- Guarantees and warranties.
- Prices or the factors affecting cost.
- Customer reviews.
- Completed projects.
Now examine whether each entity is properly represented on the website.
Ask:
- Is it mentioned at all?
- Does it have enough visible information?
- Is there a dedicated page where one is justified?
- Is the information current and accurate?
- Is it connected to the appropriate service, person or location?
- Is there evidence supporting the claim?
- Can it be represented using an established Schema.org type or property?
This process turns schema planning into a practical content audit.
How to identify entity gaps
An entity gap exists when important information is missing, incomplete, inconsistent or poorly connected.
Imagine a plumbing company that wants to be considered for the question:
“Which Gas Safe registered plumber in Preston can install a new combi boiler and provide a warranty?”
The website might have a boiler installation page but still contain several gaps:
- The page does not clearly state that the company serves Preston.
- Gas Safe registration is mentioned but no registration details are provided.
- No engineers or their qualifications are identified.
- The types of boilers installed are unclear.
- There is no information about warranties.
- No completed boiler installation is shown.
- The boiler page is not linked from the Preston service-area page.
- The structured data only identifies the page as a generic WebPage.
Adding a large schema snippet would not solve all these problems.
The business first needs stronger visible content, clearer supporting evidence and better connections between its pages. Structured data can then describe information that genuinely exists.
Not every entity gap requires a new page
Finding a missing entity does not automatically mean publishing another blog post.
The appropriate action depends on the importance and complexity of the information.
A gap might be resolved by:
- Adding an engineer’s qualifications to a team profile.
- Expanding a service page to explain warranties.
- Adding a genuine project case study.
- Clarifying service areas on the contact page.
- Linking a location page to the relevant service.
- Correcting inconsistent business details.
- Adding or improving accurate structured data.
Create a new page only when the subject deserves a useful standalone resource and meets a genuine customer need.
Publishing thin pages for every service and town can create duplication without improving understanding.
Prioritise the gaps that influence customer decisions
A comprehensive entity map can become very large, so not every gap should receive equal attention.
Start with entities that affect whether a prospective customer can find, trust and choose the business.
A useful prioritisation order is:
- Business identity: name, address, contact information, ownership and official profiles.
- Core services or products: what the business actually provides and who each offering is for.
- Locations: where the business is based, where customers can visit and which areas it serves.
- Trust and eligibility: qualifications, registrations, accreditations, experience and guarantees.
- Commercial details: prices, availability, delivery, timescales and the process of becoming a customer.
- Supporting evidence: case studies, reviews, photographs and demonstrable results.
- Additional subjects: supporting guides, definitions and related informational content.
A missing service description or professional registration is normally more important than adding markup for a minor subject mentioned in one blog post.
Connect entities through website content and internal links
Schema should support the relationships already demonstrated by the website.
Internal links are one of the most practical ways to establish those relationships.
For example, a boiler installation page could link to:
- The engineer responsible for installations.
- The company’s Preston service-area page.
- A guide explaining boiler installation costs.
- A recent boiler replacement case study.
- The contact or quotation page.
Each destination contributes a different piece of context.
Descriptive anchor text is particularly useful because it explains the relationship between the current page and its destination.
This is why a planned group of connected pages is generally more useful than a collection of isolated posts.
Learn more about writing and structuring website content for AI search.
Connect your website with reliable external identities
Search engines do not have to rely solely on what a business says about itself.
Organisation and LocalBusiness schema can use the sameAs property to reference genuine external profiles representing the same business.
Depending on the organisation, these could include:
- An official Google Business Profile.
- Established social media profiles.
- A recognised professional or regulatory listing.
- An official industry membership profile.
- A relevant company or charity register.
Only include profiles that genuinely represent the same organisation. Do not use sameAs to link to every directory mentioning the business.
Consistent external information can reinforce business identity, particularly for local companies. This is also why an accurate and well-maintained profile matters when considering how Google Business Profile helps AI understand and recommend a business.
Should you create custom schema entities?
Schema.org provides a large vocabulary, but it will not perfectly represent every concept within every industry.
It is possible to develop a custom internal entity model to describe the information that matters to your business. This can be extremely useful for content planning, databases and knowledge-graph analysis.
However, that does not mean you should invent unsupported Schema.org types and add them to a website in the expectation that Google will understand them.
For most small and medium-sized businesses, the safer approach is to:
- Use the most accurate established Schema.org types available.
- Use recognised properties to connect relevant entities.
- Keep more specialised concepts within clearly written visible content.
- Use an internal entity map to record additional relationships and content requirements.
The purpose is accurate communication, not maximum markup volume.
Avoid common schema mistakes
Structured data can create confusion when it is incomplete, duplicated or inaccurate.
Common problems include:
- Several plugins generating conflicting Organisation markup.
- Using LocalBusiness markup for a business without checking its actual details.
- Marking up services, prices or reviews that are not visible on the page.
- Applying the same schema indiscriminately across every URL.
- Using an inaccurate business type simply because it appears more specific.
- Creating separate disconnected entities for the same organisation.
- Adding FAQ markup when no corresponding FAQs are displayed.
- Assuming valid code means the information itself is correct.
WordPress SEO plugins such as Rank Math may already generate basic WebSite, Organisation, Article and Breadcrumb markup. Check the existing output before adding a separate custom snippet.
More code is not necessarily better. Google advises providing fewer complete and accurate properties rather than a larger quantity of incomplete or unreliable information.
How to carry out a practical entity audit
A small business can begin without specialist knowledge-graph software.
1. List the important entities
Record the organisation, services, products, locations, people, qualifications, customer groups, common problems and supporting evidence that matter commercially.
2. Map each entity to the website
Identify which page contains the primary information about each entity. Record entities that have no suitable page or are mentioned only briefly.
3. Examine the relationships
Check whether services connect to appropriate locations, team members, qualifications, case studies and conversion pages.
4. Compare the website with customer questions
Review enquiries, sales conversations, Google Search Console queries, reviews and competitor content. These can expose details customers expect but the website does not answer.
5. Assess existing structured data
Identify what the website already generates before adding more. Check for duplicate or contradictory entities.
6. Improve the visible content
Fill important factual and evidential gaps on the page itself. Structured data should reflect this information, not replace it.
7. Add appropriate schema
Use established Schema.org types and properties to describe the entities and relationships accurately.
8. Validate and monitor
Test eligible markup using Google’s Rich Results Test and broader vocabulary using the Schema.org validator. Continue checking the site following plugin, theme and template changes.
Measure understanding alongside visibility
Rich-result reports are useful, but they do not provide a complete picture of whether search and AI systems understand your organisation.
Monitoring can also include:
- Whether your brand appears for relevant AI prompts.
- Whether services and locations are described accurately.
- Which competitors are recommended instead.
- Whether incorrect or outdated information appears.
- Branded and non-branded impressions in Search Console.
- Traffic and enquiries reaching important service pages.
- Changes in lead relevance and conversion quality.
AI visibility should still be connected to commercial performance. More mentions have limited value if they do not produce relevant visitors, stronger brand recognition or suitable enquiries.
Schema is infrastructure, not decoration
Schema markup should not be added simply because a plugin offers another box to complete.
Its wider value comes from encouraging businesses to think clearly about their entities, relationships and missing information.
Which services matter most? Who provides them? Where are they available? What evidence supports the company’s claims? Which pages explain these facts, and how are those pages connected?
Answering these questions can expose weaknesses that affect traditional SEO, AI search and customer confidence at the same time.
Schema can then provide an additional machine-readable layer that reinforces a clear, accurate and well-connected website.
That is more valuable than chasing markup purely for a rich result—and far more realistic than treating schema as a guaranteed shortcut into AI-generated answers.
If search engines and AI platforms do not clearly understand your business, services and areas of expertise, Augmun can audit your website’s content, entity coverage, internal linking and structured data. Contact us to discuss an SEO and AI visibility strategy.
Frequently asked questions
Does schema markup improve AI visibility?
Schema can provide explicit information about entities and relationships, but it does not guarantee citations or recommendations from AI platforms. It should be treated as supporting infrastructure alongside authoritative content, technical SEO and consistent business information.
What is an entity gap?
An entity gap is important information about a person, organisation, service, product, location or concept that is missing, incomplete, inconsistent or poorly connected within a website.
Does every service need its own schema markup?
Not necessarily. The markup should reflect the purpose and visible content of each page. Important services should be clearly described, but adding a separate schema entity for every minor activity may provide little value.
Can schema replace website content?
No. Google requires structured data to represent information found on the page. Customers also need visible explanations and evidence. Schema clarifies content for machines; it does not replace it.
Should I use custom Schema.org types?
Most businesses should use recognised Schema.org types and properties wherever possible. A custom internal entity model may help with planning, but unsupported types should not be added on the assumption that search engines will understand them.
How do I check the schema already on my website?
Test important URLs using Google’s Rich Results Test and the Schema.org validator. You can also inspect the page source for JSON-LD scripts. Check for duplicated organisations, conflicting details and markup generated by multiple plugins.
Chris Giles Snr built his first client website in 1995 and has remained at the leading edge of web development and SEO ever since. He is a Fellow of The Chartered Institute of Marketing (FCIM).
