amphtml VS next-seo

https://amp.dev/ is that. No one wants to use it because the very first line of the mandatory js file is about advertising metrics.

Google announced an open source HTML framework called AMP (Accelerated Mobile Pages) for better and faster experiences on the mobile web (Google said that) in 2015. This was created in an effort to play against Facebook Instant Articles.

Does Flutter web allow for AMP compatibility?

Without disclosing too much, I am fairly involved around this topic, and I would say it's definitely heading for deprecation this year. The key giveaway is that Google Analytics 3 will be shutting down in July[0] and AMP has made no progress towards supporting Google Analytics 4[1]. I think it'll be deprecated at first rather than shut down because there are still billions of AMP documents floating around the web.

[0] https://support.google.com/analytics/answer/11583528?hl=en

[1] https://github.com/ampproject/amphtml/issues/24621

Accelerated Mobile Page is a Google-backed open-source project that allows you to create fast-loading super mobile-friendly pages.

OK, so we've all probably heard about AMP HTML from Google by now.

No JavaScript will be allowed other than an off-the-shelf AMP library

Recently I came across the AMP website at https://amp.dev/ (after some years since first seeing it). It’s really remarkable how much Google wants to pretend this is an industry standard and not their own little fiefdom. I don’t see the word Google anywhere, not even on the About page.

More about AMP

The third one is Schema.org JSON-LD. I actually question the usefulness of this feature, but if it is relatively easy to implement without a glaring downside, just give it a shot I guess? In Next.js, there is next-seo package that greatly simplifies the implementation of Schema.org JSON-LD.

Next SEO

Next Seo GitHub Repository

I would recommend checking out https://github.com/garmeeh/next-seo. It does SEO for you. Additionally, going to recommend precisely what u/saarnav mentioned. https://vercel.com/docs/concepts/functions/edge-functions/og-image-generation

Any opinions on https://github.com/garmeeh/next-seo ?

To simplify this, we can use a package called next-seo. Next SEO makes managing SEO easier in your Next.js projects.

For SEO there is next-seo.

Meta tags exist in the head element of the page providing important information about the page that can used by search engines and social media sites. There are a variety of meta tags that represent different types of information for different search engines. A popular subset of standardized meta tags are described in the open graph protocol. Managing these tags for every page and generating them dynamically for blog pages has it’s own overhead. Thus for that reason, I have used the Next-SEO plugin. The Next-SEO plugin provides DefaultSEO component that contains tags that will be defined for all routes by default which subsequently can be overwritten at a page level by then using the NextSEO component. Below is the default SEO config used by me.

I have also used this package to make the SEO tag section easier to manage: https://github.com/garmeeh/next-seo

We will have to populate SEO-related meta tags with the relevant information for each page. To do so, we will use garmeeh/next-seo.