Open istarkov opened 10 months ago
Double checking in case it fell through the cracks, are we also including the below in the SEO update?
Re the cards behavior above, I though this is just tied to the image that's uploaded, different aspect ratios will have different previews.
@istarkov am I good to close this issue or are we still working on the cli part of header code?
UI
Site Settings
https://www.figma.com/file/xCBegXEWxROLqA1Y31z2Xo/%F0%9F%93%96-Webstudio-Design-Docs?node-id=8349%3A2962&mode=dev
Page Settings
https://www.figma.com/file/xCBegXEWxROLqA1Y31z2Xo/%F0%9F%93%96-Webstudio-Design-Docs?type=design&node-id=309-39598&mode=design&t=hy1vvaaF4qJFrVkb-0
UI Issues list
Possible problems - Custom metadata can contain not only
<meta property={a} content={b}>
for example twitter usesname
instead of property. Same for themeta name="description"
Also this not covering json+ld for pages.
CLI
robots.txt
left (twitter needs it to work) #2545excludeFromSearchResult
can be solved by adding<meta name="robots" content="noindex">
https://developers.google.com/search/docs/crawling-indexing/block-indexing #2545Testing
Devops
CLI Issues
[ ] - scripts in site settings needs serious change of sdk Root component, we can't add them using remix API from what I know, but needs investigation. Seems like somekind of our ebbed component. I think that for the future we need to investigate how to add/use react-helmet for this. Instead of making custom 1 field support solution
[ ] - discord/telegram unknown behaviour that our cards are shown like
but cards from https://www.reasonfieldlab.com/post/interior-design-with-stable-diffusion are shown like
meta noindex
which I recommend we need to allow bots to access pages see https://developers.google.com/search/docs/crawling-indexing/robots/intro , https://developers.google.com/search/docs/crawling-indexing/block-indexing and it must be compatible with twitter bots (should be something what disallow api pathes and allows everything else) #2545