Howdy!
TSF doesn’t comment on semantic web design — this should flow naturally like anyone’s been taught in school how to write papers. Moreover, search engines don’t care — as long as there’s good content. But, your visitors might appreciate a more academic approach to content. Better tools for this exist, like Grammarly and Google Search Console, each with its own focus.
TSF handles technical SEO and SSO: titles, description metadata, structured data, Open Graph, Twitter Card, oEmbed, canonical URLs, etc. All of what I listed is automatically generated from reading your content. I built bespoke HTML parsers for TSF to make processing your data as fast as possible. I added a few invisible unique technical SEO tweaks, such as Query Alteration and Advanced Query Protection — both are explained in the settings.
The “TG, DG, I, F, A, and R” symbols are from the SEO Bar. This is to quickly inform you about how TSF will act for the page (hover over it with your cursor to learn more). It will change depending on how you configured the plugin. Perhaps you have a plugin like WooCommerce active, and the SEO Bar will inform you that the checkout page won’t be indexed while other pages typically are.
So, these ratings are purely based on fact-based assertions.
If you’re interested in SEO beyond the technical, there are keywords via our Focus extension: https://tsf.fyi/e/focus. This will inform you where you should place focus keywords and their inflections and synonyms (if available). But these remain guidelines, and so you won’t get a score.
Perhaps the most important thing is reading this guide: https://developers.google.com/search/docs/fundamentals/seo-starter-guide. This is more of an accessibility handbook than SEO, but they’re interchangeable: A search engine crawler is blind, after all.
Please bear in mind that your products compete with Amazon and a few well-established vendors. They have expended tonnes on SEO.
If you have any more questions, let me know below! If it’s entirely unrelated, I suggest opening a new topic instead. Cheers!
