2026 Structured Data Blueprint

The Ultimate FloorPlan
Schema Generator

A FloorPlan is an explicit representation of a collection of similar accommodations, allowing the provision of common information (room counts, sizes, layout diagrams) and offers for rental or sale. In typical use, some ApartmentComplex has an accommodationFloorPlan which is a FloorPlan. A FloorPlan is always in the context of a particular place, either a larger ApartmentComplex or a single Apartment. The visual/spatial aspects of a floor plan (i.e. room layout, [see wikipedia](https://en.wikipedia.org/wiki/Floor_plan)) can be indicated using image.

Includes:additionalTypealternateNameamenityFeaturedescriptiondisambiguatingDescriptionfloorSizeidentifierimage+17 more
Instant JSON-LD Generation

Magic Build

Paste your URL below and our AI will automatically fill the FloorPlan fields for you.

Configuration

Live Generator

FloorPlan Schema

Fill in the fields below to generate your JSON-LD. Required fields are marked with *.

Required Fields

The name of the item. (Expects: Text)

Recommended

An image of the item. This can be a [[URL]] or a fully described [[ImageObject]]. (Expects: ImageObject, URL)

URL of the item. (Expects: URL)

Why use FloorPlan?

Structured data like FloorPlan markup helps search engines identify the most important details about your content instantly, improving your chances of earning rich results.

Output Panel

Awaiting input...

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 Generator

What is FloorPlan Schema?

A FloorPlan is an explicit representation of a collection of similar accommodations, allowing the provision of common information (room counts, sizes, layout diagrams) and offers for rental or sale. In typical use, some ApartmentComplex has an accommodationFloorPlan which is a FloorPlan. A FloorPlan is always in the context of a particular place, either a larger ApartmentComplex or a single Apartment. The visual/spatial aspects of a floor plan (i.e. room layout, [see wikipedia](https://en.wikipedia.org/wiki/Floor_plan)) can be indicated using image.

Why It Matters for SEO

Google uses FloorPlan 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 FloorPlan 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 FloorPlan JSON-LD

1

Generate

Use the form above to fill in your details and generate valid FloorPlan JSON-LD markup in seconds.

2

Copy

Copy the generated JSON-LD output code with one click β€” it's already formatted and ready to deploy.

3

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

FloorPlan 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.

PropertyDescriptionExpected TypeStatus
additionalTypeAn 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, URLOptional
alternateNameAn alias for the item.TextOptional
amenityFeatureAn 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.LocationFeatureSpecificationOptional
descriptionA description of the item.Text, TextObjectOptional
disambiguatingDescriptionA 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.TextOptional
floorSizeThe size of the accommodation, e.g. in square meter or squarefoot. Typical unit code(s): MTK for square meter, FTK for square foot, or YDK for square yard.QuantitativeValueOptional
identifierThe identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See [background notes](/docs/datamodel.html#identifierBg) for more details.PropertyValue, Text, URLOptional
imageAn image of the item. This can be a URL or a fully described ImageObject.ImageObject, URLRecommended
isPlanForApartmentIndicates some accommodation that this floor plan describes.AccommodationOptional
layoutImageA schematic image showing the floorplan layout.ImageObject, URLOptional
mainEntityOfPageIndicates a page (or other CreativeWork) for which this thing is the main entity being described. See [background notes](/docs/datamodel.html#mainEntityBackground) for details.CreativeWork, URLOptional
nameThe name of the item.TextRequired
numberOfAccommodationUnitsIndicates the total (available plus unavailable) number of accommodation units in an ApartmentComplex, or the number of accommodation units for a specific FloorPlan (within its specific ApartmentComplex). See also numberOfAvailableAccommodationUnits.QuantitativeValueOptional
numberOfAvailableAccommodationUnitsIndicates the number of available accommodation units in an ApartmentComplex, or the number of accommodation units for a specific FloorPlan (within its specific ApartmentComplex). See also numberOfAccommodationUnits.QuantitativeValueOptional
numberOfBathroomsTotalThe total integer number of bathrooms in some Accommodation, following real estate conventions as [documented in RESO](https://ddwiki.reso.org/display/DDW17/BathroomsTotalInteger+Field): "The simple sum of the number of bathrooms. For example for a property with two Full Bathrooms and one Half Bathroom, the Bathrooms Total Integer will be 3.". See also numberOfRooms.IntegerOptional
numberOfBedroomsThe total integer number of bedrooms in a some Accommodation, ApartmentComplex or FloorPlan.Number, QuantitativeValueOptional
numberOfFullBathroomsNumber of full bathrooms - The total number of full and ΒΎ bathrooms in an Accommodation. This corresponds to the [BathroomsFull field in RESO](https://ddwiki.reso.org/display/DDW17/BathroomsFull+Field).NumberOptional
numberOfPartialBathroomsNumber of partial bathrooms - The total number of half and ΒΌ bathrooms in an Accommodation. This corresponds to the [BathroomsPartial field in RESO](https://ddwiki.reso.org/display/DDW17/BathroomsPartial+Field).NumberOptional
numberOfRoomsThe number of rooms (excluding bathrooms and closets) of the accommodation or lodging business. Typical unit code(s): ROM for room or C62 for no unit. The type of room can be put in the unitText property of the QuantitativeValue.Number, QuantitativeValueOptional
ownerA person or organization who owns this Thing.Organization, PersonOptional

Example FloorPlan JSON-LD

Here's what valid FloorPlan structured data looks like with sample values filled in. Use the generator above to replace these with your own data.

Example Output
{
  "@context": "https://schema.org",
  "@type": "FloorPlan",
  "name": "Example FloorPlan",
  "image": "https://example.com/images/example.jpg",
  "url": "https://example.com/page",
  "additionalType": "Example additionalType",
  "alternateName": "Example alternateName",
  "amenityFeature": {
    "@type": "LocationFeatureSpecification",
    "name": "Example LocationFeatureSpecification",
    "image": "https://example.com/images/example.jpg",
    "url": "https://example.com/page"
  },
  "description": "A sample description for this FloorPlan.",
  "disambiguatingDescription": "Example disambiguatingDescription"
}

Validate Your FloorPlan 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.

Free Schema Audit Tool β†’

Check your FloorPlan schema for errors and Rich Result eligibility