Use schema to describe a page accurately
Schema markup labels information in a form software can process. It can describe the business named on a page, the service being explained or the route through a site. Its job is to describe the content a visitor can actually see. It cannot turn an unsupported service or a made-up review into a valid business fact.
For a Virginia business owner, the useful first question is practical: what information is wrong, missing or hard to understand on the current page? Fix that before adding more code. If the contact page has the wrong phone number, correct the visible number and any corresponding markup together.
Separate structured data from AI inclusion
Google's AI-features documentation says there is no special schema needed for AI Overviews or AI Mode. A page does not need FAQ markup to qualify for those experiences, and adding it does not secure a citation.
That distinction changes a proposal. Ask what the markup will describe, which documented feature it serves and how it will be checked. A line item called “AI schema” is too vague to assess. The useful deliverable is a correct implementation with a stated purpose, rather than an implied place in an answer.
Choose a type that fits the visible content
Google's structured-data introduction explains the formats and links to supported feature guidance. JSON-LD is Google's recommended format when it is suitable for the site; Microdata and RDFa are also supported. The right choice depends on the existing system and the feature's documentation.
- Business identity: check the actual name, public contact details and relevant business category. Do not create an office because a service-area page names a town.
- A service page: describe the work the business really offers. Keep prices, coverage and conditions consistent with the visible explanation.
- A guide: use truthful authorship and dates. A routine link change is not a new expert review.
- Questions and answers: publish useful answers for readers first. A question format does not establish eligibility for a particular search feature.
Review the facts before reviewing the syntax
Consider a hypothetical contractor based in Hillsville who serves several nearby counties. The website should distinguish the real business location from the places it serves. A list of served towns should not become a list of fictional branch offices in the markup.
Use a small comparison sheet: visible field, markup value, business evidence and person responsible for keeping it current. Hours, phone numbers and service boundaries are sensible starting points. If two records disagree, resolve the business fact rather than choosing whichever version looks better in a test.
Reviews deserve separate care. Genuine feedback still has to meet the relevant platform and feature rules. Do not assume that displaying a testimonial makes a self-serving star-rating block eligible for a search enhancement.
Validate the implementation and keep the limits visible
Check that each structured-data block parses, its values match the page and its intended feature meets the current documentation. Google's Rich Results Test can assess supported Google features; a broader schema validator can help inspect vocabulary and syntax. Neither is evidence of future ranking, traffic or AI citations.
Keep the checked URL, date, findings and corrected fields with the release record. Recheck affected data when the business moves, an offer changes or a redesign alters the page. Do not label an unmeasured improvement as a result.
Scope the next step around the actual problem
If the facts are clear but the code is inconsistent, a focused correction may be enough. If the page itself is confusing, improve the explanation and navigation at the same time. If the business is evaluating broader discovery work, read the AI-search visibility checklist before buying more markup.
For help assessing the current site, start a project inquiry with the page URL and the information that needs attention. The AI Search service page explains the wider work and its limits.