What is schema markup — and what your site adds automatically
If you've read anything about SEO, you've met the terms "schema markup" and "structured data" — usually followed by a pitch for a plugin. Here's what they actually mean, and what your website already does about them on its own.
Schema markup in plain English
A web page is written for humans: headlines, photos, styled text. A machine reading that page — a search engine crawler, an AI assistant — has to infer what it's looking at. Is this an article? Who wrote it? When was it updated? Is this a question and its answer, or just two paragraphs?
Schema markup removes the guessing. It's a set of standardized labels (from schema.org, a vocabulary the major search engines maintain together) embedded invisibly in the page's code. The visitor sees your designed page; the machine additionally reads a precise statement like: "This is an article, published on this date, last updated on that date, written by this person, who works for this organization — and here is its FAQ, question by question, answer by answer."
That's all it is: the same content, restated in a format machines can trust.
What your site emits automatically
You don't install or configure anything — every page your site serves carries the markup appropriate to what it is:
- Every page — an Organization entry identifying your community as the publisher.
- Posts (blog posts and other collection entries) — a BlogPosting entry with the headline, published and updated dates, and cover image; a BreadcrumbList showing where the post sits (home, category, post); a Person entry for the byline author; and a FAQPage entry whenever the post has an FAQ.
- Agent profile pages — a Person entry with the agent's name, title, photo, bio, and social profiles.
- Listings — property details and price in the formats real-estate search understands.
The author is a real, connected entity
When a post has a byline (set in the post editor's Details tab), the markup doesn't just state a name — if the author is listed in your agent directory, the post's author entry links to their profile page, and the profile page's own Person markup is recognizably the same person. Machines can follow that thread: this article was written by this specific human, with this role, at this organization. That connectedness is exactly what search engines and AI systems look at when they weigh how much to trust content — anonymous text is cheap; accountable authorship isn't.
The byline resolves live from the directory, so if an agent updates their title or photo, every past post's markup updates with it.
The guardrail: markup always matches the page
A rule the platform enforces everywhere: machines are only ever told what visitors can see. The FAQ markup is exactly the Q&A rendered in the post's accordion; the author markup is the byline on the page; the dates are the post's real dates. There's no way to stuff invisible content into the markup — which is good, because search engines treat mismatches between markup and visible content as spam.
Does it improve my ranking?
Not directly, and anyone promising otherwise is selling something. What it does is make your content unambiguous — eligible for richer treatments where engines offer them, and easy for AI search tools to quote accurately with attribution. Where the payoff actually lands today, especially for FAQs, has changed a lot recently — that story is in Where FAQ schema works today.
See it yourself
- Open any live, published post on your site.
- View the page source (right-click → View page source) and search for `application/ld+json` — that block is the markup, readable if you squint.
- For a friendlier view, paste the post's URL into validator.schema.org — it lists every entity the page declares.
Troubleshooting
The validator shows nothing for my post
Make sure you're testing the live URL of a published post — drafts and editor previews aren't public pages. If you published moments ago, give the site cache a few minutes and try again.
The author shows as my organization, not a person
The post has no byline. Open the post's Details tab and set the Author (byline) — the markup follows it. If the byline is set but the author isn't listed in your agent directory, the markup states their name without linking to a profile.