-
Notifications
You must be signed in to change notification settings - Fork 118
Fix: Updated and improved SEO #946
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
base: main
Are you sure you want to change the base?
Conversation
The previous version of the introduction article had an illogical flow for new learners, jumping between concepts without building a proper foundation. SEO elements were also minimal. This commit completely restructures the content to be more beginner-friendly and impactful: - Introduces the concept of Version Control first to establish the "why". - Clearly distinguishes between Git (the tool) and GitHub (the platform). - Improves SEO with a keyword-rich title, meta description, and tags. - Rewrites core concepts like 'Repository' and 'Pull Request' for better clarity. - Organizes the content with a logical heading structure.
The previous version of the introduction article had an illogical flow for new learners, jumping between concepts without building a proper foundation. SEO elements were also minimal. This commit completely restructures the content to be more beginner-friendly and impactful: - Introduces the concept of Version Control first to establish the "why". - Clearly distinguishes between Git (the tool) and GitHub (the platform). - Improves SEO with a keyword-rich title, meta description, and tags. - Rewrites core concepts like 'Repository' and 'Pull Request' for better clarity. - Organizes the content with a logical heading structure.
1.The entire meta block was commented out and has been fixed and enabled. 2.The og:url, og:image, and og:description tags were pointing to an incorrect article about the MERN stack. They now correctly point to the DeepMind article's assets and have an accurate, well-written description. 3.The primary description field was rewritten to be grammatically correct and more compelling.
Updated content to improve clarity and consistency throughout the article, including sections on energy efficiency, healthcare applications, and AI technology.
Fix: Proofread and Correct Metadata in DeepMind Article
1.Frontmatter and Naming Standardization: Consistent Naming: Standardized the program name to "Google Student Ambassador" throughout the article, removing confusion from variations like "Campus Ambassador" and "Gemini Ambassador." Synced Metadata: Updated the title, slug, and id in the frontmatter to be consistent with the main <h1> heading and article content. The new slug is /google-student-ambassador-program-2025. 2. Content and Factual Accuracy: Corrected Time Commitment: Resolved the contradiction in the FAQ. Both Q2 and Q3 now correctly state the time commitment as "5–7 hours per week." Removed Empty Section: Deleted the "Got Questions & What Happens Next?" section, as it contained no actionable information and detracted from the article's professional tone. 3.Accessibility and Code Quality: Added Alt Text: Provided descriptive alt text for both images, ensuring the article is accessible to screen readers. Removed Unused Import: Deleted an unused Layout component import to clean up the code.
1.Frontmatter and Naming Standardization: Consistent Naming: Standardized the program name to "Google Student Ambassador" throughout the article, removing confusion from variations like "Campus Ambassador" and "Gemini Ambassador." Synced Metadata: Updated the title, slug, and id in the frontmatter to be consistent with the main <h1> heading and article content. The new slug is /google-student-ambassador-program-2025. 2. Content and Factual Accuracy: Corrected Time Commitment: Resolved the contradiction in the FAQ. Both Q2 and Q3 now correctly state the time commitment as "5–7 hours per week." Removed Empty Section: Deleted the "Got Questions & What Happens Next?" section, as it contained no actionable information and detracted from the article's professional tone. 3. Accessibility and Code Quality: Added Alt Text: Provided descriptive alt text for both images, ensuring the article is accessible to screen readers. Removed Unused Import: Deleted an unused Layout component import to clean up the code.
1.Activated Social Media Metadata: The entire meta block containing Open Graph and Twitter card information was commented out. This has been uncommented, enabling rich previews when the article is shared on social platforms. 2.Added Canonical URL: Populated the empty canonical_url field to prevent duplicate content issues and improve search engine indexing. 3.Aligned Page Titles: The frontmatter title has been updated to match the on-page <h1> heading for better SEO alignment and user experience. The sidebar_label was also shortened for better UI fit. 4.Improved Image Accessibility: Enhanced the alt text for the architecture diagram to be more descriptive for users with screen readers.
1.The entire meta block containing Open Graph and Twitter card information was commented out. This has been uncommented, enabling rich previews when the article is shared on social platforms. 2.Populated the empty canonical_url field to prevent duplicate content issues and improve search engine indexing. 3.The frontmatter title has been updated to match the on-page <h1> heading for better SEO alignment and user experience. The sidebar_label was also shortened for better UI fit. 4.Enhanced the alt text for the architecture diagram to be more descriptive for users with screen readers.
@DIYA-bot is attempting to deploy a commit to the recode Team on Vercel. A member of the Team first needs to authorize it. |
Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs. In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊 Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv. We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰 🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨ 📚Your perks for contribution to this community 👇🏻
If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊 |
The latest updates on your projects. Learn more about Vercel for GitHub.
|
04:27:30.415 Running build in Washington, D.C., USA (East) – iad1 |
Description
Fixes # (issue)
Type of Change
Changes Made
Dependencies
Checklist
npm run build
and attached screenshot(s) in this PR.