Tell Google exactly what each page is, in code it can't misread.
Schema markup is structured data: a block of code that states, unambiguously, who you are, what each page covers, and how it all connects. It turns a page Google has to guess about into one it understands, and it's the foundation for rich results and for being cited by AI search. Most property-management sites have only the basics their CMS adds automatically, not the entity grounding and page-type markup that actually earn those results.
Get my DNA Audit →Schema markup, in one paragraph.
Schema is structured data, a block of code added to your pages that tells Google explicitly what kind of entity you are, what each page is (a service, an article, an FAQ), and how it all connects. Google already tries to infer this from your page text. Schema removes the guesswork.
When schema is in place and correct, search engines can show the enhanced results that still exist, breadcrumbs above your listing and the article treatment on your posts, and, increasingly, AI engines can extract and cite your pages accurately. That second part is now the bigger prize. None of it happens reliably when Google is left to guess what a page is.
What I add
The exact schema depends on your site, but a typical baseline:
- Entity (Organization) schema, who the business is, anchored to a single
@idso Google and AI knowledge graphs treat your pages as one coherent entity instead of guessing - Page-type schema, Service, Article, FAQPage, BreadcrumbList, so each page declares what it is. Breadcrumbs and the article treatment are the enhanced results this still earns; the question-and-answer markup is now read mainly by AI engines, which is where that value has moved
- A grounded link to your Google Business Profile, so Google and the AI engines resolve your website and your profile to one business. This is what connects your review reputation to your site. Marking up your own star rating on your own pages does the opposite: it earns no stars and carries a manual-action risk, and I remove it when I find it. Here's why
Why it pays off first
Schema is mostly a one-time deployment, hours, not weeks, and it makes everything already on your page legible to the systems that decide what to show. The enhanced results that survive (breadcrumbs, the article treatment) and the answers AI engines now give directly both depend on it. No new content, no new links, no ad spend; you're just making what's there readable to a machine that would otherwise guess.
It also compounds with the rest of on-site SEO: schema tells Google what a page is, and once it understands that, your internal linking and on-page work have something clear to reinforce.
How I deploy it
I write the JSON-LD blocks (the format Google prefers), test them in Google's Rich Results Test tool, ship them to your site through whatever CMS you're on (WordPress, Wix, Squarespace, custom, I've seen all of them), and verify rendering with Search Console. Then I monitor Search Console's enhancement reports for the next 30 days to make sure nothing breaks. Total elapsed time: 1 to 3 days for most sites.
Schema markup, answered.
My CMS already adds schema. Isn't that enough?
Plugins like Yoast and CMS defaults add basic schema, and most property-management sites I audit have it. But "present" is not "complete." What's almost always missing is the entity grounding (Organization schema with a sameAs array linking your GBP and profiles), Service schema on the landlord money-pages, and FAQPage markup, the exact types that earn rich results and AI citations. I add the layer the plugin doesn't.
How long until rich results show up after deployment?
Usually 7 to 14 days, occasionally up to 30. Google has to recrawl your pages, validate the schema, and decide whether to display the rich result. I monitor Search Console and follow up if anything is rejected.
Will schema markup work if I'm on Wix or Squarespace?
Yes. Both platforms support custom code injection. The implementation is slightly different on each, but the end result is the same.
Can I implement schema markup myself?
Technically yes, Google publishes the documentation and there are free generators. Where it usually goes wrong is completeness (partial markup that never triggers a rich result), validation errors that go unnoticed, and conflicts when multiple plugins write competing schema on the same page.
Find out what schema you're missing.
The audit tells you exactly which schema types are deployed on your site, which are missing, and what the gap is costing you in visibility.
Get my DNA Audit →