You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a discrepancy between the SEO title set in the content and the title displayed in the metadata. The SEO title should be '⭐ TinaCMS headless CMS' but is currently showing as 'markdown CMS'. Additionally, there are error messages in the console related to images being served to the home route and issues with GraphQL requests.
Acceptance Criteria
SEO title on the homepage should display '⭐ TinaCMS headless CMS' as set in the content.
No error messages related to images or GraphQL requests should appear in the console.
Correct SEO data should be fetched from the home JSON page.
Reproduce Steps
Go to the homepage of the ⭐ Tina.io website.
Inspect the SEO title and compare it with the title set in the content.
Check the console for any error messages related to images or GraphQL requests.
Verify the data being fetched from the home JSON page.
Screenshot
Figure: SEO title mismatch; serve issue with home images affecting metadata
The text was updated successfully, but these errors were encountered:
joshbermanssw
changed the title
🐛 Investigate and Fix SEO Title Discrepancy on Homepage
🐛 Investigate and fix slug and graphql querying discrepency for home route
Jan 30, 2025
Requested by: @joshbermanssw via YakShaver.ai 🦬
cc: @tiagov8, @joshbermanssw, @adamcogan, @wicksipedia
Hi Team!
Watch the video
Pain
There is a discrepancy between the SEO title set in the content and the title displayed in the metadata. The SEO title should be '⭐ TinaCMS headless CMS' but is currently showing as 'markdown CMS'. Additionally, there are error messages in the console related to images being served to the home route and issues with GraphQL requests.
Acceptance Criteria
Reproduce Steps
Screenshot
Figure: SEO title mismatch; serve issue with home images affecting metadata
The text was updated successfully, but these errors were encountered: