Identify WireCat and clarify product intent in search results - #48
Merged
Merged
Conversation
leemour
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The homepage and About describe WireCat but their JSON-LD lacks an Organization or Person identity. Add a shared Organization/Project entity using the visible name, existing 512px brand icon and public email. Link WebSite.publisher to that stable identity and identify About as AboutPage with the project as mainEntity. The same identity is used across all three languages.
No personal identity, legal-company details, founder, ratings or extra social profiles are inferred. Organization/Project describes the open-source project; it does not assert registration as a company. Person remains optional for a future visible maintainer profile.
Also replace generic provider landing titles with localized Telegram/MAX CLI titles that identify the actual agent/bot use case. Keep navigation labels and visible headings unchanged. Shared guides keep their own titles.
Validation: 189 unit tests, lint/types/build/link checks and export SEO checks pass. The export guard now verifies the project identity, publisher link, logo availability and About relationship on actual generated pages. Existing CI/deployment browser gates apply. This is identity markup, not a promise of faster indexing or a knowledge panel.