SEO optimization #53
Merged
SEO optimization #53
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ved descriptions, structured data, and semantic HTML elements.
… enhance clarity and SEO and remove duplicate_title_tags
…o images, enhancing descriptions, and refining content structure for better readability and SEO.
…criptions, adding structured sections, and clarifying roles and processes in data science teams. Updated links and ensured consistency in formatting for better readability and SEO.
…ed clarity and SEO. Added written versions of the podcasts.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
➡️ No H1
articles.md, books.md, events.md, index.md, people.md, podcast.md, slack.md, support.mdpages andauthor.html, book.htmllayouts had no H1.I added H1 (in practice, some of the headers were H2 and I edited them to H1).
Additional changes in
author.htmlandbook.htmlI also asked Cursor to help me with SEO optimization. For
author.html, book.html, it suggested several improvements.Both files went from basic HTML to properly structured pages that search engines can understand and rank, while also being accessible to screen readers.
More about structured content JSON-LD schemas: https://docs.google.com/document/d/1xmcMOxh0glrX10Rp7vNJHXWn-ysCxISPvEEOuyUIX1k/edit?usp=sharing
author.html
Added:
<main>,<header>,<section>,<nav>) instead of generic<div>s<h1>for author name,<h2>for sectionsaria-labelon linksrel="noopener noreferrer")Impact: Search engines understand it's a person profile; screen readers navigate properly; social links are indexed.
book.html
Added:
<h1>for title (was<h2>),<h2>for authors (was<h4>)<article>,<section>,<header>,<footer><article>+ proper headings (not just bold text)Impact: Google can show rich snippets with book covers and buy buttons; better SEO rankings from proper H1/H2 structure; faster page loads from lazy loading.
Source: https://docs.google.com/spreadsheets/d/1CEgWo8nQWZrRMBQnpHe8MhNoT_mWzux7GWJlSFflEP0/edit?usp=sharing
➡️ Duplicate title tags
These pages had duplicate title tags:
I updated each of them to have unique titles.
For blog posts listed here, I also:
Source: https://docs.google.com/spreadsheets/d/13mUpkejeRKGXiydaQl7lm4O9xJOY6W4W3x-r5dTSqFk/edit?usp=sharing
➡️ Duplicate meta descriptions
These pages had duplicate meta descriptions:
I updated each of them to have unique meta descriptions.
Source: https://docs.google.com/spreadsheets/d/1y4h-i78ulL_ws_fM-XZMJbEE0KNSbcVw33AE-bYiFuk/edit?usp=sharing
➡️ Thin content
These pages had thin content, meaning less than 200 words:
For these podcasts, I added short versions of the podcasts because there were no transcripts available. To show you what short versions could look like:
For books, I expanded descriptions.