Hello everyone! I want to learn how to create a website properly and according to all the standards within this fantastic program, Site Designer (SD). I noticed that there is a "structure data" option in the page manager, but I still don’t quite understand how to use it correctly. It seems directly related to building a well-structured website, and I really want to master it. However, I’m having trouble understanding how it works. Could one of the SD experts explain step by step, with examples, how to use this feature properly? Maybe make a small guide or just provide a few clear examples. I’m sure this would be useful for many!

https://www.google.com/webmasters/markup-helper/

https://developers.google.com/search/do … tured-data

Great question Juan - my business has changed a bit and I don't do as many sites as I once did but have read in the last few days that semantic data is becoming more important

Byron

Thank you, Wayan! Very useful links! Still, I want to master the built-in features of Site Designer. After working with these links, many things have become clearer.

This is true. We have to keep up with the times.

Schema markup data to assist with SEO and helping search engines better understand what that website and it's pages/content are all about has been around since 2011/2012,, and yes over those years it has been developed and improved (so they say) I would say that 14 years or so seems to me to be a reasonably long period of time for web developers to learn how to implement it best for their clients, and to have kept up with the times.


Site Designer makes it reasonably easy to add the required code and data to a website project, using both structured data and semantic named tags, you can even test the structured data with a handy link so you can see if the data you entered is valid and acceptable, you can check your HTML markup (semantics) also on W3C schools to see if that is correct too.

It is very difficult to provide more than a general 'HOW TO" other than on a general basis to these things because it is relevant to a particular website, its reason for being a website, what it's purpose id etc etc, and how important SEO is for that website owner (not all need SEO and the important thing is that id you are going to use it, then it has to be done right, or there could even be a chance that it may even damage your websites chance of even appearing on SERP's


There are hundreds of articles out there on the internet that can help a little bit with the why and wherefore, etc, The best option for me is to read as many of these articles as possible even perhaps attend a few online training courses, until the fog lifts and the understanding kicks in, that's then the time to ask the questions about the HOW TO use the tools that Site Designer has to add this essential stuff to your project.

One important thing to remember is that " etc then it HAS to be done correctly, if not then there is a greater chance that the website will suffer MORE than if you DON'T do any at all.

That's it! And that’s why I’m trying to understand this and the boundaries of SD.

My advice for what it's worth and apologies for sounding blunt
First is to forget about things like that for the moment, concentrate on getting your clients website error free (and there are a few important ones that need attention) get rid of your schema data because although in essence it's almost there it is not correct and therefore could even at this moment be too late to stop the damage being done.
You really should only put a website up live and kicking so to speak once it's ready as error free and optimised as much as possible before that it is a long and arduous task to correct any errors issues missed opportunities that may have already been indexed in search engines libraries. I know from experience where I have been tasked with finding out why sites aren't producing the results that were expected.
One extreme case in the past to almost 6 months of work error correction submitting the pages back to search engines for re indexing etc before that site started to get anywhere near the top position it deserved to be on.
It's a bit late to start wearing the SEO specialist cap once a website has been up and running for even a few days.
So yes spend some time studying reading learning about SEO then come back and discover the how to use Site Designer to add your semantic and schematic data to a project.

The other thing to consider of course is that Schema Markup can be implemented quite easily on monolingual single-domain websites; however, multilingual and multi-regional domains have special issues when it comes to maintaining Schema Markup.

One of which is that it is probably best to have different pages for each language, and the relevant links to those pages etc that allow switching between languages. This helps with Schema markup and also helps with normal SEO stuff too

There is also some theories around that you could just use English in the schema data mark up. I haven't ever needed to do this so cannot say if that would be ok or not. You may have to ask this question about language with Schema.org themselves

Thank you, Wayan! I believe I’ve fixed the mistakes you pointed out. As for SEO, I'm not really interested in it. I get aesthetic pleasure from making websites and bringing them to the level of perfection I can achieve. It’s my hobby. I earn a living in another field So the SEO expert hat isn’t something I’m interested in. I just try to make the website flawless by today's standards, which is why SEO comes up. You can’t go without it nowadays.