Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SEO: individualized content previews for DVC pages (and maybe /doc pages) #857

Closed
jorgeorpinel opened this issue Dec 12, 2019 · 23 comments
Closed
Labels
A: website Area: website duplicate This issue or pull request already exists. status: research Writing concrete steps for the issue type: enhancement Something is not clear, small updates, improvement suggestions

Comments

@jorgeorpinel
Copy link
Contributor

Currently preview of contents for all DVC pages has the same info:

image

Maybe it could have the actual title of each page at least? Ideally also a short excerpt of the beginning of the page contents.

@jorgeorpinel jorgeorpinel added A: docs Area: user documentation (gatsby-theme-iterative) A: website Area: website website: eng-doc DEPRECATED JS engine for /doc labels Dec 12, 2019
@shcheklein
Copy link
Member

👍 Any ideas how should we customize it depending on a link? The most obvious one - title. Not sure about snippet and image.

@shcheklein shcheklein added the status: research Writing concrete steps for the issue label Dec 12, 2019
@jorgeorpinel
Copy link
Contributor Author

Yeah well we have a markdown parses so other than a custom title such as Data Registry | Use Cases | DVC, the text preview could be the first paragraph from the md contents (After H1), truncated to some length.

@jorgeorpinel jorgeorpinel changed the title SEO: individual content previews for DVC pages? SEO: individual content previews for DVC pages Dec 12, 2019
@shcheklein
Copy link
Member

I wonder if we can use an image to put that custom text + logo. And use generic text - so that users always see what DVC is.

@jorgeorpinel
Copy link
Contributor Author

As for research, these excerpts at least in Slack come from the <meta name="description" tag. I guess we could find out what other metadata Google, Bing, etc pay attention to. Maybe <meta name="keywords"? I understand that's mostly ignored by search engines now a days (they have algorithms to extract keywords from the actual contents instead).

@jorgeorpinel
Copy link
Contributor Author

can use an image to put that custom text + logo

This is probably possible on more advanced engines, but image rendered text wouldn't help search result ranking.

@shcheklein
Copy link
Member

Yeah, probably I don't care that much about SEO per se (they are good at extracting information), more about user experience when you send a link, share a link.

@jorgeorpinel
Copy link
Contributor Author

jorgeorpinel commented Dec 12, 2019

There's <meta name="thumbnail", or more advanced PageMaps for G we can try. Not sure this helps previews in messaging apps like Slack, etc. though. They probably only check basic meta tags.

@jorgeorpinel jorgeorpinel changed the title SEO: individual content previews for DVC pages app: individualized content previews for DVC pages (SEO) Jan 10, 2020
@shcheklein shcheklein removed the A: website Area: website label Jan 11, 2020
@jorgeorpinel jorgeorpinel added A: website Area: website type: enhancement Something is not clear, small updates, improvement suggestions and removed A: docs Area: user documentation (gatsby-theme-iterative) website: eng-doc DEPRECATED JS engine for /doc labels Jan 18, 2020
@jorgeorpinel jorgeorpinel changed the title app: individualized content previews for DVC pages (SEO) seo: individualized content previews for DVC pages (and maybe /doc pages) Jan 18, 2020
@jorgeorpinel jorgeorpinel added help wanted Contributors especially welcome and removed help wanted Contributors especially welcome labels Jan 18, 2020
@jorgeorpinel
Copy link
Contributor Author

Related: #982

@shcheklein shcheklein changed the title seo: individualized content previews for DVC pages (and maybe /doc pages) SEO: individualized content previews for DVC pages (and maybe /doc pages) Apr 6, 2020
@MerlynMShelley
Copy link

MerlynMShelley commented May 30, 2020

Hi @jorgeorpinel and @shcheklein ,
The meta tag is the most important factor for search engines to find out the core meaning if the website. For that we have to enable the open graph protocol with our customised JavaScript engine I hope. I would like to work on this issue.
Thank you.

@MerlynMShelley
Copy link

MerlynMShelley commented May 30, 2020

Maybe it could have the actual title of each page at least?

I hope <meta property="og:site_name"> is missing in the site. Adding this metatag would resolve the issue. I will raise a pull request on this.
Thank you.

@MerlynMShelley
Copy link

MerlynMShelley commented May 30, 2020

As for research, these excerpts at least in Slack come from the <meta name="description" tag. I guess we could find out what other metadata Google, Bing, etc pay attention to. Maybe <meta name="keywords"? I understand that's mostly ignored by search engines now a days (they have algorithms to extract keywords from the actual contents instead).

It is, <meta property="og:site_name"> missing in the site. So we would get the individualised content on the preview.

@MerlynMShelley

This comment has been minimized.

@MerlynMShelley

This comment has been minimized.

@MerlynMShelley
Copy link

I wonder if we can use an image to put that custom text + logo. And use generic text - so that users always see what DVC is.

Yes, I understand this.

@jorgeorpinel
Copy link
Contributor Author

The meta tag is the most important factor for search engines to find out the core meaning if the website.

As noted in #1379 (comment) and #1379 (comment) that seems to relate more to #1119. Let's move the conversation there?

I have submitted a pull request to this issue. Kindly check.
I have made the pull request that could fix this issue. Please check here,

Yeah, don't worry, we get the notifications and emails from GH. No need for 2 comments about this 😋 but thanks a lot for the contribution

@MerlynMShelley
Copy link

MerlynMShelley commented Jun 7, 2020

Screenshot_20200607_161407
When I share I blog link in slack, it's displaying the page title and the image in a smaller size. If we further want to increase the size of the image, we have to work with the Twitter summary of cards with larger dimensions of the picture. So please help me in knowing the absolute requirement of this issue @jorgeorpinel also I have raised a pull request before on this issue with some additional twitter cards on #1379. Kindly help me in this regard to understand the SEO requirement. Thank you

@MerlynMShelley

This comment has been minimized.

@jorgeorpinel
Copy link
Contributor Author

jorgeorpinel commented Jun 9, 2020

Hey @MerlynMShelley thanks. TBH pasting these long vertical emails is not very easy to read so I hid you comment. Can you just copy/paste the key text from there or paste a link to the reference please? I also don't really understand what it is about or why you cant comment in #1379, which BTW is now closed. Don't you have another PR open for this?

Sorry, it's been a few really busy weeks and I'm not keeping close track of things, will need your help to make sure everything you comment is as easy to read/understand as possible (digested, not raw) and in the right context. Thanks!

@jorgeorpinel
Copy link
Contributor Author

If we further want to increase the size of the image, we have to work with the Twitter summary of cards with larger dimensions of the picture

Why is this a Twitter-specific issue? Thanks

help me in knowing the absolute requirement of this issue

The custom image idea comes from #857 (comment) but the goal is to keep both the basic description of DVC and also the excerpt from each page in these previews somehow. It's not a perfectly defined requirement, it needs a creative solution, probably. Any suggestions?

It's a good point that the blog previews already have custom excerpts, it seems cc @shcheklein @rogermparent how can we replicate that everywhere?

@jorgeorpinel
Copy link
Contributor Author

jorgeorpinel commented Jun 9, 2020

why you cant comment in #1379, which BTW is now closed. Don't you have another PR open for this?
Sorry, it's been a few really busy weeks

I see that was your only PR @MerlynMShelley, but it got complicated and was closed. Are you planning to try again with a smaller PR so it's easy to review and follow up on? Or do you prefer to work on something else? I've seen you've commented in #1119 (comment), for example. Thanks!

Again, this week will probably be a little difficult to work with you very closely so if you have a small, specific, complete contribution you'd like to make, please send a PR 🙂 otherwise let's touch base in a few days.

@rogermparent
Copy link
Contributor

rogermparent commented Jun 10, 2020

It's a good point that the blog previews already have custom excerpts, it seems [...] how can we replicate that everywhere?

Looks like only blog posts use the description prop of our SEO component, so providing that component the data we want to display in the other templates should do the trick if blog posts currently exhibit the desired behavior.

Blog posts currently have a complete separate excerpt in the description field of their frontmatter, but the description prop can be a string acquired through any method.

@jorgeorpinel
Copy link
Contributor Author

providing that component the data we want to display in the other templates should do the trick

Sounds worth a shot 🙂

@jorgeorpinel
Copy link
Contributor Author

Closing in favor of #1785

@jorgeorpinel jorgeorpinel added the duplicate This issue or pull request already exists. label Sep 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: website Area: website duplicate This issue or pull request already exists. status: research Writing concrete steps for the issue type: enhancement Something is not clear, small updates, improvement suggestions
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants