Quick answer:
Schema markup is a small piece of code added to your page that labels your content in a format search engines and AI systems can read directly — instead of them guessing what your business does from plain text. A visa consultancy page that just says "98% success rate" in a paragraph means nothing to a machine. The same fact wrapped in schema tells Google explicitly: this is a business, this is its rating claim, this is its service list.
The Real Client: A Visa Consultancy Site
Our client is a tourist and student visa consultancy based in Delhi, offering services across the USA, UK, Canada, Australia, and Schengen countries. Before we touched anything, we ran their homepage through Google's Rich Results Test to see what was actually already machine-readable — and the result surprised us: it wasn't a blank slate.
Real Rich Results Test output for their homepage:
✅ Organization schema — 1 valid item detected
✅ LocalBusiness schema — 1 valid item detected, but flagged with non-critical issues
❌ FAQ schema — not detected at all, despite having a full FAQ section on the page
❌ Review/AggregateRating schema — not detected, despite real testimonials on the page
This is actually the more common real-world starting point than "zero schema everywhere." Most small business sites have some basic structured data — often added automatically by a website builder or theme — while the content that would drive AI visibility (FAQs, reviews, service details) is sitting there in plain text, completely unmarked.
What We're Fixing (and Why Each One Matters)
1. Resolving the LocalBusiness "Non-Critical Issue"
Clicking into the flagged item showed exactly one thing missing: the optional priceRange field. Everything else — business type (TravelAgency), name, address, phone, email, logo, service area, and description — was already correctly filled in. This is a good example of why you should always click into a "non-critical issue" instead of ignoring it: sometimes it's a single missing field away from being fully clean, and it takes two minutes to fix.
2. Adding FAQ Schema
Every question in their FAQ block ("What documents are required for a US tourist visa?", "How long does tourist visa processing take?") gets wrapped in FAQPage schema. This is the single highest-impact addition here — it's the exact format AI Overviews and Google's "People Also Ask" boxes pull directly from, and right now none of it exists on the page.
3. Adding Review/AggregateRating Schema
The testimonials on the page are real client feedback, but as plain text they carry no ranking weight and weren't picked up by the test at all. Marking them up as Review schema (tied to AggregateRating) is what allows star ratings to potentially appear directly in search results.
4. Service Schema
Each visa category (tourist, student, PR) gets marked as a distinct Service under the business — so a search for "student visa consultant Delhi" and "tourist visa consultant Delhi" can both map to the correct, specific service instead of one generic homepage.
How to Check If a Site Has Schema (Do This on Your Own Site Right Now)
- Go to Google's Rich Results Test tool
- Paste in your homepage or FAQ page URL
- If it comes back empty or shows errors, you have the exact same starting point as this client did
What "Before" Actually Looked Like vs. What We Expect After
Before (real, tested) After (target)
- Organization schema ✅ Valid ✅ Valid (unchanged)
- LocalBusiness schema ✅ Valid, but non-critical issues flagged ✅ Valid, issues resolved
- FAQ schema ❌ Not detected ✅ Valid, eligible for AI Overview / "People Also Ask"
- Review schema ❌ Not detected ✅ Valid, eligible for star-rating rich results
(This table reflects an actual Rich Results Test run on the live site. We'll update the "After" column with the real re-test screenshot once the FAQ and Review schema are implemented — no assumed results, only what the tool confirms.)
Why We're Publishing This Before the Results Are In
Most schema articles show you a polished "after" with no proof of the "before," or worse, invent numbers to sound impressive. We'd rather show you the real, tested starting point — including the parts that were already working — and update this post honestly once the fixes are live. A genuine in-progress example, warts and all, is more useful than a manufactured success story.
What You Can Do on Your Own Site Today
- Run your homepage through the Rich Results Test — don't assume you have zero schema; you might have partial coverage like this client did
- Check specifically for FAQ and Review schema — these are the two most commonly missing, even on sites that already show "valid items detected"
- If any existing item shows "non-critical issues," click into it to see exactly what's incomplete
- Re-test after implementing — the tool will confirm whether it's valid
One More Real Finding (This Time, On Our Own Site)
While putting this checklist together, we ran our own site — nexoper.in — through the same Rich Results Test. The result: 4 valid items detected, but with something worth flagging — 2 valid Organization entries and 2 valid LocalBusiness entries, both labeled "Nexoper," instead of one of each.
Both pass as "valid," so the test doesn't throw an error. But having duplicate entities on one page usually means two different sources are generating schema at once — commonly a website theme/builder auto-adding one, and a manual or plugin-based one added on top. We're investigating which is the duplicate before deciding which to remove, and we'll update this post once it's resolved.
We're including this specifically because it's the same lesson from the LocalBusiness section above, applied to ourselves: "valid" on the test doesn't automatically mean "clean." Always click into the detected items, even when everything shows a green checkmark.
Following along or want us to audit your site's schema gaps? [Reach out to NexOper-6299317083] and we'll show you exactly what's missing — using the same checklist above.