A structured data audit checks whether your website’s schema markup is helping search engines understand your pages clearly. It is used to find schema that is broken, outdated, duplicated, incomplete or attached to the wrong page type before your team invests more time in implementation.
For many businesses, structured data is added once through a plugin, theme, ecommerce platform or developer task and then forgotten. The website changes, but the markup does not always change with it. Product fields move, templates are rebuilt, FAQ sections are removed, business details change, and different tools can start generating overlapping schema.
A structured data audit gives you a clear answer: what is working, what needs attention, what can wait and what should be fixed first.
What a structured data audit covers
A structured data audit reviews the schema markup on your website and checks whether it supports the actual purpose of each page.
This is more than running a URL through a testing tool. A page can pass a basic validation check and still have weak structured data. The markup might describe content that is no longer visible, use a generic schema type where a more specific one would be more useful, repeat the same business entity in conflicting ways, or miss important fields on commercial templates.
The audit looks at the relationship between page content, page templates, schema types, entity details and SEO priorities. It can review JSON-LD formatting, schema type selection, Search Console issues, rich result eligibility, template-level markup, plugin-generated schema and whether the structured data matches what users can actually see on the page.
Google supports JSON-LD, Microdata and RDFa for structured data, recommends JSON-LD where possible, and states that valid structured data can enable rich result eligibility but does not guarantee that rich results will appear. Google structured data guidelines
That is why the value of a structured data audit is not a promise of special search displays. The value is cleaner diagnosis, safer implementation decisions and a more reliable technical SEO foundation.
Who this service is for
A structured data audit is useful when your website already has schema markup, but nobody is fully confident that it is correct.
This is common on ecommerce sites, service websites, local business websites and content-heavy sites where schema is generated automatically by plugins, themes or platform settings. It is also common after a redesign, migration, CMS change, template rebuild or plugin update.
You may need a structured data audit when Google Search Console reports structured data issues, when rich result visibility has changed, when developers are unsure which schema output to trust, or when marketing needs a practical technical SEO brief before implementation work begins.
For many South African businesses, the issue is not simply “we need schema”. The more useful question is whether the schema already on the site is accurate, maintainable and connected to the pages that matter commercially.
Problems a structured data audit solves
Structured data issues are often invisible on the page itself. A product, service page or article may look correct to users while the underlying markup tells a different story.
An ecommerce product page might show the correct price on the site, while the Product schema fails to update sale pricing or stock status. A service business might have organisation, website and local business markup generated by separate tools, each using slightly different business details. A resource page might continue to output FAQ schema after the visible FAQ section has been removed.
These problems create uncertainty. Marketing teams cannot tell whether schema is helping. Developers may not know which plugin or template is responsible. SEO teams may be left with a list of warnings but no clear view of what matters.
A structured data audit turns that uncertainty into a fix order. It identifies where the issue appears, whether it affects one page or an entire template, and whether it is worth developer time now.
Google’s structured data guidelines state that markup should represent the page content, should not describe hidden or misleading content, and must include required properties to be eligible for relevant rich result features. Google structured data guidelines
Structured data audit vs schema implementation
A structured data audit is not the same as schema implementation.
Schema implementation means adding or changing markup. A structured data audit comes first. It checks what is already present, what is missing, what is being generated automatically, what is causing risk and what should be prioritised.
| Service | What it does | When it is useful |
|---|---|---|
| Structured data audit | Reviews existing markup, gaps, errors, duplication and risk | Before changing schema across important pages or templates |
| Schema implementation | Adds or updates schema on pages or templates | After the right schema plan has been defined |
| Rich results optimisation | Focuses on eligibility for specific search features | When a site is targeting a specific feature such as product, breadcrumb or article visibility |
| Technical SEO audit | Reviews broader crawl, indexation, canonical, rendering, speed and architecture issues | When schema is only one part of a wider technical SEO problem |
| Schema markup service | Usually focuses on writing or installing schema | Useful when backed by proper page-type mapping and validation |
This difference matters because many structured data problems are not solved by adding more markup. Sometimes the right fix is to remove duplicate output, correct entity relationships, simplify plugin settings, adjust template logic or align the markup with visible content.
Recommended audit approach
A structured data audit should start with the pages that matter most.
For most websites, that means grouping pages by template and commercial role. A homepage, service page, ecommerce category page, product page, article, location page and contact page do not need the same structured data decisions.
The review first identifies what schema is present and where it comes from. Some markup may be generated by the CMS. Some may come from an SEO plugin. Some may be hard-coded into the theme. Some may be injected through custom development or tag management.
Once the source is clear, the audit checks whether the markup can be read, whether it fits the page type and whether it adds useful clarity. It also separates isolated URL issues from template-level issues. A single incorrect field on one page may be a small fix. A product template outputting incomplete offer data across hundreds of URLs is a very different priority.
Google recommends using testing tools such as the Rich Results Test and URL Inspection to catch technical structured data errors and confirm whether Google can access the markup. Google structured data guidelines
What the audit checks
A structured data audit normally reviews four areas.
The first is technical validity. This checks whether the markup can be parsed, whether the format is correct, whether required properties are present and whether the page can be accessed by search engines.
The second is page-type fit. This checks whether the schema matches the purpose of the page. A product page, service page, article, local business page and breadcrumb trail each need different treatment.
The third is content accuracy. This checks whether the structured data describes information that is visible and current on the page. This is where many plugin-led implementations fail, because the markup may continue to output old FAQs, business details, ratings, product data or entity information after the page has changed.
The fourth is priority. Not every warning deserves immediate action. The audit should identify which issues affect important pages, which affect many URLs, which carry risk and which can safely wait.
This is what turns a technical check into a useful SEO decision-making document.
Common audit findings
The most common findings usually fall into three groups.
The first group is broken markup. This includes syntax errors, missing required properties, broken nesting, inaccessible image URLs or structured data that testing tools cannot parse properly.
The second group is mismatched markup. This includes FAQ schema on pages without visible FAQs, breadcrumb schema that differs from the visible breadcrumb trail, local business details that do not match the page content, or service pages marked up in a way that does not reflect the actual service.
The third group is weak markup. This is schema that may not be technically wrong, but does not add much value. Examples include generic WebPage markup on important commercial pages, duplicate organisation schema from several tools, or markup that describes the business but gives little clarity about the specific page.
The audit should not treat those findings equally. A minor issue on an old article does not carry the same weight as a recurring product schema problem across an ecommerce catalogue.
Deliverables and outcomes
A structured data audit should leave your team with clear, practical outputs.
Depending on the scope, the deliverables may include a structured data issue log, a reviewed URL sample set, a schema map by page type, notes on missing or duplicated properties, Search Console issue notes, validation findings, developer guidance and a prioritised fix list.
The output should explain what is wrong, where it appears, why it matters and what should happen next.
For example, imagine an online store where sale products display correctly on the website, but the product template does not pass the right offer details into the structured data. The audit would identify the affected template, show example URLs, explain which fields are missing or unreliable, and give the developer a focused fix rather than a vague instruction to “fix schema”.
For a service business, the audit might find that business-level markup is duplicated by several tools while the key service pages have no useful Service schema. The fix plan may recommend simplifying business entity markup and improving page-specific schema on commercial pages.
For a local business, the review may compare visible business details, location content and structured data output so that the site sends a clearer and more consistent signal.
The outcome is not just a list of errors. It is a decision-making document for what to fix, what to leave alone and what to handle as part of a wider technical SEO roadmap.
How this supports enquiries and revenue
Structured data does not create leads or sales by itself. It supports the technical conditions that help important pages become clearer, more consistent and better prepared for eligible search features.
For an ecommerce store, that may mean stronger product and offer data across revenue-driving templates. For a service business, it may mean clearer markup on pages that explain core services. For a local business, it may mean reducing inconsistency between business details, location content and technical markup.
The value is in reducing ambiguity. When page content, templates and structured data tell the same story, the site is easier to interpret. When they conflict, duplicate or fall out of date, they create avoidable technical noise.
A structured data audit helps you decide whether an issue should be fixed now, included in a broader technical SEO project, or left until higher-priority work is complete.
When a structured data audit is worth doing
A structured data audit is worth doing when schema has become important enough to affect SEO decisions, but unclear enough that your team is guessing.
It is a sensible next step after a website migration, redesign, CMS change, theme update, ecommerce rebuild or plugin change. It is also useful when Search Console reports structured data issues, when rich result appearance changes, or when developers are about to rebuild important templates.
It can also be useful before new schema implementation. Adding more markup without understanding the current setup can create duplication, conflict and maintenance problems. Auditing first gives you a cleaner foundation.
Related technical SEO support
Structured data works best when it is reviewed as part of a wider technical SEO system.
If your website also has crawlability, indexation, canonical, page-template or internal-linking issues, a broader technical SEO South Africa review may be the better starting point. Structured data can then be assessed alongside the foundations that affect how search engines access and understand the site.
For online stores, ecommerce technical SEO is closely connected to structured data. Product schema, offer data, category templates, breadcrumb markup and merchant-related information often depend on how the ecommerce platform manages product and template data.
The structured data audit is most useful when it gives your team a clear bridge between SEO requirements and practical implementation.
Next step
Book an SEO diagnostic review if you need a clear, consultant-led view of what your structured data is doing and what should happen next.
SEO Strategist can review your current schema setup, identify the issues that matter, separate quick fixes from deeper template problems and give your team or developer a practical fix order before changes are made across important pages.
Use the review to find out what is working, what is creating noise, what should be removed or improved, and which structured data fixes deserve priority in your wider technical SEO roadmap.
Book an SEO diagnostic review and get a clear fix order before your team changes schema across important templates.