The Ultimate Residence
Schema Generator
The place where a person lives.
Magic Build
Paste your URL below and our AI will automatically fill the Residence fields for you.
Configuration
Live GeneratorWhy use Residence?
Output Panel
Want to automate this?
Connect your site to SchemaGen and our AI will automatically extract and deploy schemas for you. No manual coding required.
Launch AI GeneratorWhat is Residence Schema?
The place where a person lives.
Google uses Residence structured data to understand the content and context of your pages. When correctly implemented, this schema can unlock rich results in Google Search — enhancing your listing with additional information that dramatically improves visibility and click-through rates.
Why Add Residence Structured Data?
Appear in Rich Results
Structured data helps Google show enhanced results for your pages in search — including stars, prices, FAQs, and more.
Boost Click-Through Rate
Rich snippets can increase CTR by up to 30% compared to plain search results — more clicks with the same ranking.
Feed AI Search Engines
AI answer engines like Perplexity and Google SGE use structured data to verify and cite facts from your content.
How to Implement Residence JSON-LD
Generate
Use the form above to fill in your details and generate valid Residence JSON-LD markup in seconds.
Copy
Copy the generated JSON-LD output code with one click — it's already formatted and ready to deploy.
Deploy
Paste the code into your <head> tag, or use SchemaGen's SDK to deploy without touching code.
Want to skip steps 2 & 3? Connect SchemaGen's SDK to deploy directly from the dashboard.
Properties You Can Include
Residence schema supports the following schema.org properties. Required fields are the minimum Google needs to consider your markup valid; recommended fields unlock richer search result appearances.
| Property | Description | Expected Type | Status |
|---|---|---|---|
| accommodationFloorPlan | A floorplan of some Accommodation. | FloorPlan | Optional |
| additionalProperty | A property-value pair representing an additional characteristic of the entity, e.g. a product feature or another characteristic for which there is no matching property in schema.org.\n\nNote: Publishers should be aware that applications designed to use specific schema.org properties (e.g. https://schema.org/width, https://schema.org/color, https://schema.org/gtin13, ...) will typically expect such data to be provided using those properties, rather than using the generic property/value mechanism. | PropertyValue | Optional |
| additionalType | An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. Typically the value is a URI-identified RDF class, and in this case corresponds to the use of rdf:type in RDF. Text values can be used sparingly, for cases where useful information can be added without their being an appropriate schema to reference. In the case of text values, the class label should follow the schema.org style guide. | Text, URL | Optional |
| address | Physical address of the item. | PostalAddress, Text | Optional |
| aggregateRating | The overall rating, based on a collection of reviews or ratings, of the item. | AggregateRating | Optional |
| alternateName | An alias for the item. | Text | Optional |
| amenityFeature | An amenity feature (e.g. a characteristic or service) of the Accommodation. This generic property does not make a statement about whether the feature is included in an offer for the main accommodation or available at extra costs. | LocationFeatureSpecification | Optional |
| branchCode | A short textual code (also called "store code") that uniquely identifies a place of business. The code is typically assigned by the parentOrganization and used in structured URLs.\n\nFor example, in the URL http://www.starbucks.co.uk/store-locator/etc/detail/3047 the code "3047" is a branchCode for a particular branch. | Text | Optional |
| containedIn | The basic containment relation between a place and one that contains it. | Place | Optional |
| containedInPlace | The basic containment relation between a place and one that contains it. | Place | Optional |
| containsPlace | The basic containment relation between a place and another that it contains. | Place | Optional |
| description | A description of the item. | Text, TextObject | Optional |
| disambiguatingDescription | A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation. | Text | Optional |
| event | Upcoming or past event associated with this place, organization, or action. | Event | Optional |
| events | Upcoming or past events associated with this place or organization. | Event | Optional |
| faxNumber | The fax number. | Text | Optional |
| floorLevel | The floor level for an Accommodation in a multi-storey building. Since counting systems [vary internationally](https://en.wikipedia.org/wiki/Storey#Consecutive_number_floor_designations), the local system should be used where possible. | Text | Optional |
| geo | The geo coordinates of the place. | GeoCoordinates, GeoShape | Optional |
| geoContains | Represents a relationship between two geometries (or the places they represent), relating a containing geometry to a contained geometry. "a contains b iff no points of b lie in the exterior of a, and at least one point of the interior of b lies in the interior of a". As defined in [DE-9IM](https://en.wikipedia.org/wiki/DE-9IM). | GeospatialGeometry, Place | Optional |
| geoCoveredBy | Represents a relationship between two geometries (or the places they represent), relating a geometry to another that covers it. As defined in [DE-9IM](https://en.wikipedia.org/wiki/DE-9IM). | GeospatialGeometry, Place | Optional |
Example Residence JSON-LD
Here's what valid Residence structured data looks like with sample values filled in. Use the generator above to replace these with your own data.
{
"@context": "https://schema.org",
"@type": "Residence",
"name": "Example Residence",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page",
"accommodationFloorPlan": {
"@type": "FloorPlan",
"name": "Example FloorPlan",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page"
},
"additionalProperty": {
"@type": "PropertyValue",
"name": "Example PropertyValue",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page"
},
"additionalType": "Example additionalType",
"address": {
"@type": "PostalAddress",
"name": "Example PostalAddress",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page"
},
"aggregateRating": {
"@type": "AggregateRating",
"name": "Example AggregateRating",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page"
}
}Validate Your Residence Schema
Once deployed, validate your schema is working correctly with our free audit tool. Paste your URL and we'll check for errors, missing properties, and Google Rich Result eligibility.
Check your Residence schema for errors and Rich Result eligibility