Structured SEO schema configuration

introduction structured data integration has been implemented to improve the seo results of our sites, built with hyperbuilder adding structured data can enable search results that are more engaging to users and might encourage them to interact more with your website, which are called rich results more details on https //developers google com/search/docs/appearance/structured data/intro structured data the implementation includes three types of structured data schema configurations 1\ basic schema "website" and "organization" 2\ custom page schema 3\ generated "jobposting" schema for the "vacancy details" block configurations overview basic schema "website" and "organization" the goal of the site name in google search is to best represent and describe the source of each result to indicate your site name preference, added "website" structured data adding "organization" structured data to your website can help google better understand your organization's administrative details and disambiguate your organization in search results for these schemes to be generated on the pages, the names and descriptions must be filled in the application settings go to app settings > seo > schema configuration when part of " website" or "organization" schema is not filled in with values, the schema will not be generated fill in the corresponding name and description for "website" and "organization" should be filled for each language save changes website name the name of the website make sure the name meets the https //developers google com/search/docs/appearance/site names#choosing site name website description describes the website, not the company, legally do not copy the meta description 1 1 (you can, but it is better to summarise it slightly) organization name the name of your organization use the same name that you're using for your site name organization legal name the registered, legal name of your organization, if applicable and different from the name property when the values are filled in, a schema will be generated for the pages with the following parameters { "@context" "https //schema org", "@graph" \[ { "@type" "website", "@id" "yurii builder fpifkflmagugmtizgvnzv staging live hyperbuilder io", "url" "https //yurii builder fpifkflmagugmtizgvnzv staging live hyperbuilder io/", "name" "website name nl", "description" "website description en", "publisher" { "@id" "https //yurii builder fpifkflmagugmtizgvnzv staging live hyperbuilder io/" }, "inlanguage" "en" }, { "@type" "organization", "@id" "https //yurii builder fpifkflmagugmtizgvnzv staging live hyperbuilder io/", "name" "organization name en", "legalname" "organization legal name en", "url" "https //yurii builder fpifkflmagugmtizgvnzv staging live hyperbuilder io/", "logo" { "@type" "imageobject", "url" "https //images hyper1 net/eyjrzxkioij5dxjpas1idwlszgvyl2j4eupkzwryufftbmztu19ls1bocyisimvkaxrzijp7injlc2l6zsi6eyjmaxqioijpbnnpzguilcj3axrob3v0rw5syxjnzw1lbnqionrydwv9lcj3zwjwijp7inf1ywxpdhkiojcwlcjyzwr1y3rpb25fzmzvcnqiojusimfscghhuxvhbgl0esi6mtawfx0sim91dhb1dezvcm1hdci6indlynaifq==" } } ] } custom page schema a custom schema allows you to add appropriate structured data features for a specific page open the hyperbuilder app > click on page settings icon > in the page setting side menu placed input field "custom page schema (json ld)" via hover on the label, a tooltip is displayed with a link to the google documentation for examle you can fill in "webpage" schema should be filled for each language save changes { "@type" "webpage", "@id" "https //example com/page slug", "name" "some title", "description" "some description", "url" "https //example com/page slug", "ispartof" { "@id" "https //example com/#website" }, "primaryimageofpage" { "@id" "https //example com/sample post/#primaryimage" }, "datepublished" "2025 08 26", "inlanguage" "en us" } when custom page schema is filled in, a schema will be generated only for the current page if values for "website" and "organization" are filled , the custom schema will be added as a part of the main schema { "@context" "https //schema org", "@graph" \[ { "@type" "website", "@id" "yurii builder fpifkflmagugmtizgvnzv staging draft hyperbuilder io", "url" "https //yurii builder fpifkflmagugmtizgvnzv staging draft hyperbuilder io/", "name" "website name nl", "description" "website description en", "publisher" { "@id" "https //yurii builder fpifkflmagugmtizgvnzv staging draft hyperbuilder io/" }, "inlanguage" "en" }, { "@type" "organization", "@id" "https //yurii builder fpifkflmagugmtizgvnzv staging draft hyperbuilder io/", "name" "organization name en", "legalname" "organization legal name en", "url" "https //yurii builder fpifkflmagugmtizgvnzv staging draft hyperbuilder io/", "logo" { "@type" "imageobject", "url" "https //images hyper1 net/eyjrzxkioij5dxjpas1idwlszgvyl2j4eupkzwryufftbmztu19ls1bocyisimvkaxrzijp7injlc2l6zsi6eyjmaxqioijpbnnpzguilcj3axrob3v0rw5syxjnzw1lbnqionrydwv9lcj3zwjwijp7inf1ywxpdhkiojcwlcjyzwr1y3rpb25fzmzvcnqiojusimfscghhuxvhbgl0esi6mtawfx0sim91dhb1dezvcm1hdci6indlynaifq==" } }, { "@type" "webpage", "@id" "https //example com/page slug", "name" "some title", "description" "some description", "url" "https //example com/page slug", "ispartof" { "@id" "https //example com/#website" }, "primaryimageofpage" { "@id" "https //example com/sample post/#primaryimage" }, "datepublished" "2025 08 26", "inlanguage" "en us" } ] } block level schema in the current implementation, it was planned to add "jobposting" schema generation for the "vacancy details" block at the block level, values in the schema are filled in based on vacancy data when the page is rendered with the "vacancy details" block, the "jobposting" schema is generated with the details from the current vacancy if values for "website" and "organization" are filled , the "jobposting" schema will be added as a part of the main schema if values for "organization" are filled , the parameters for "hiringorganization" in the schema will be based on "organization" schema data { "@context" "https //schema org", "@type" "jobposting", "dateposted" "2024 11 25t12 43 46 348z", "title" "vacancy name", "description" "vacancy description", "occupationalcategory" "test category", "directapply" true, "validthrough" "2026 06 29t21 00 00 000z", "employmenttype" "manager", "hiringorganization" { "@type" "organization", "name" "organization name", "sameas" "organization legal name", "url" "https //yurii builder fpifkflmagugmtizgvnzv staging draft hyperbuilder io/" }, "joblocation" { "@type" "place", "address" { "@type" "postaladdress", "addressregion" "brugge", "addresscountry" "" } if values for "organization" are not filled , the parameters for "hiringorganization" in the schema will be based on vacancy data { "@context" "https //schema org", "@type" "jobposting", "dateposted" "2024 11 25t12 43 46 348z", "title" "vacancy name", "description" "vacancy description", "occupationalcategory" "test category", "directapply" true, "validthrough" "2026 06 29t21 00 00 000z", "employmenttype" "manager", "hiringorganization" { "@type" "organization", "name" "automobilia brugge", "sameas" "automobilia", "url" "https //yurii builder fpifkflmagugmtizgvnzv staging draft hyperbuilder io/" }, "joblocation" { "@type" "place", "address" { "@type" "postaladdress", "addressregion" "brugge", "addresscountry" "" }