apache
feat: add structured data for SEO
Signed-off-by: Navendu Pottekkat [email protected]
Related to #980
Adds structured data for the homepage. This is an initial setup and in the future we can automatically generate this data on every page in the site.
Deploy Preview for apache-apisix ready!
| Name | Link |
|---|---|
| Latest commit | 3764341d9297dee91f181a3a5d6267b80b8412e8 |
| Latest deploy log | https://app.netlify.com/sites/apache-apisix/deploys/63de42b3283b720008700f61 |
| Deploy Preview | https://deploy-preview-1493--apache-apisix.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
@SkyeYoung Please let me know if I need to move the schema definition to some place else.
@SkyeYoung Please let me know if I need to move the schema definition to some place else.
No need I think. 🤔 But we need to improve some of the content.
No need I think. 🤔 But we need to improve some of the content.
Could you share what we can improve?
Could you share what we can improve?
Sorry, I'm late. My thoughts are similar to what keer said, and I think it's good now that it's been revised.
Just to confirm: this only adds Schema to the homepage?
Yes. It only does that. But AFAIK it will help with our goal to get a knowledge panel. In future, we can generate schema automatically for each page from the metadata. I have to spend more time looking into how I can achieve this or someone else can take it up.
I seem to remember Google complaining about missing field why Blog was easier to start with (cf. https://github.com/apache/apisix-website/issues/980#issuecomment-1156033243).
@nfrankel Should we add applicationCategory and operatingSystem? Another alternative is to use https://schema.org/WebSite
Which way should we go?