SEO Metadata

[rallisf1]

Is your feature request related to a problem? Please describe.
I know I can manually add the meta tags in the Page's but I'd prefer to do it through the gui as data is duplicated across tags.

Describe the solution you'd like
I propose a SEO button next to HTML CSS Fields buttons in Page IDE mode which would bring up a modal with the following inputs:

• Live Base URL (needed for og:url and image urls)
• Title
• Description
• Author
• Favicon (have the user upload a 512x512 pixel image and then generate the web manifest file along with the other resolutions and .ico)
• Robots (multiple select of noindex, nofollow, notranslate, noarchive ... etc)
• Page type (select from website, article, product etc, and also add their special fields e.g. publish_date, price etc.)
• Twitter Card Type
• Canonical URL (in case we use the same content in another page/website)
• Image (multiple select consisting of the images already used in the page, no need to upload them again)

And generate the appropriate html tags or JSON+LD for the published site. In multi-language sites it must also include og:locale and hreflang tags.

Describe alternatives you've considered
There are a few svelte meta tag packages, but they wouldn't help much apart from replicating how they work.

[mateomorris]

You should be able to do most of this now by creating Page Fields & connecting them via the Page HTML like so:

<title>{title}</title>
<meta name="description" content={description} />
...

[rallisf1]

You should be able to do most of this now by creating Page Fields & connecting them via the Page HTML like so:

<title>{title}</title>
<meta name="description" content={description} />
...

Yeah I know but still it's 2 steps rather than 1 and even if you use the same variables you will still have 3 description tags, 3 title tags etc...

I understand Primo is (svelte) dev oriented atm and I don't know what's your goal with the project, I just mention features that can automate much of the website building process and the average Joe will just switch to another tool if Primo doesn't have them.

[mateomorris]

What do you mean by 3 description tags? That HTML only appears once in the HTLM head tag.

[mateomorris]

I understand Primo is (svelte) dev oriented atm and I don't know what's your goal with the project, I just mention features that can automate much of the website building process and the average Joe will just switch to another tool if Primo doesn't have them.

This definitely isn't for the "average Joe" at this stage, but that's a good reminder that I should write the goal of the project somewhere. Basically, we're trying to make web development as smooth as possible without removing flexibility, with the goal being that developers can build tailored [no-code] experiences for content editors.

So although this would make it easier to add SEO data to a page,

• Not all of these options are relevant to every site or content editor. For instance, when I make a site for someone who isn't a marketer, the only options I'd want them to see are Title and Description. I'll probably have to explain what "SEO" means too. In that case, having an SEO button with an exhaustive list of fields would introduce more friction.
• HTML, CSS, and Fields are each their own domains and unlock functionality which isn't possible in the others, but SEO would just be an implementation of Fields - it wouldn't enable new functionality, just make things a little easier for users who happen to want that functionality.
• The cost to the codebase (in terms of development time and additional complexity) isn't worth the benefit.

Hopefully that's enough to show why this won't be implemented as-is.

However, I think it would be helpful to keep the conversation going to see how things could be smoothed out while holding to the project's goal, so I'm going to convert this into a discussion.

[rallisf1]

Fair enough. Based on this though maybe Primo should become extendable with plugins at some point? Heck even start a marketplace and make a buck out of it (both you and the plugin devs)

[mateomorris]

You read my mind 😅 That's the plan for sustaining development (I've been full-time for two years)

[rallisf1]

Count me in then :D

[mateomorris]

And yeah extendability is def on the roadmap; An SEO plugin would be 💯

The first version of extendability should be coming soon. I'm working on a way to write custom fields like this:

CustomFieldTypePOC.mov

So maybe I could add a json download + upload to reuse it across sites.