test: seo organization structured data #655
Closed
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
hellofanny
added a commit
to vtex/faststore
that referenced
this pull request
Feb 18, 2025
## What's the purpose of this pull request? - Adding [Organization](https://developers.google.com/search/docs/appearance/structured-data/organization) structured data in homepage > Adding organization structured data to your home page can help Google better understand your organization's administrative details and disambiguate your organization in search results. ## How it works? Allow adding the following [Organization](https://schema.org/Organization) schema proprieties: - url: the URL of the website of your organization. This helps Google uniquely identify your organization. - sameAs: The URL of a page on another website with additional information about your organization, if applicable. For example, a URL to your organization's profile page on a social media or review site. You can provide multiple sameAs URLs. - logo: A logo url that is representative of your organization, if applicable. (image [guidelines](https://developers.google.com/search/docs/appearance/structured-data/organization)) - image: An image that is representative of your organization. This could also be the same as the logo. Add a ImageObject (provide image url and caption) - name: The name of your organization. - legalName: The registered, legal name of your Organization. - email: The email address to contact your business, if applicable. - telephone: A business phone number meant to be the primary contact method for customers, if applicable. - address: The address (physical or mailing) of your organization, if applicable. > Note: Users can add Organization data through the headless CMS interface. ### Headless CMS <img width="636" alt="image" src="https://github.com/user-attachments/assets/a73765d6-2b21-4593-9d63-e684eed8285c" /> TODO: Run cms sync in default acc. ## How to test it? 1. Go to [preview](https://starter-llg52ur11-vtex.vercel.app/) link, inspect and look for `Organization` <img width="500" alt="image" src="https://github.com/user-attachments/assets/6fff3dad-6e4b-4e3d-9f45-0ad22ea7afc3" /> 2. Copy the generated script and paste [here - google rich test](https://search.google.com/test/rich-results?utm_campaign=devsite&utm_medium=jsonld&utm_source=merchant) to test the valid schema: <img width="1607" alt="image" src="https://github.com/user-attachments/assets/d9de0173-add6-4154-9746-ef50b30236ba" /> OR 1. Test in `storeframework` account, go to CMS admin, changes the fields values -> Save and Publish. 2. Wait for the new preview link and do the same process mention above (look for `organization` and validate the schema) ### Starters Deploy Preview vtex-sites/starter.store#655 ## References - [Google rich test](https://search.google.com/test/rich-results?utm_campaign=devsite&utm_medium=jsonld&utm_source=merchant) - [Schema.org](https://schema.org/Organization)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What's the purpose of this pull request?
testing vtex/faststore#2623
How does it work?
How to test it?
Faststore related PRs
References