Audit and add structured organization data on a business or brand homepage. Check machine-readable details such as the official name, logo, contact information, and social profiles to help Google understand the organization and its search information panel.
Use when auditing structured data on a business or brand website homepage. Applies to organisations, companies, non-profits, and publishers that want accurate Knowledge Panel information in Google Search.
Audit and add structured data that tells Google about the organization behind a business or brand homepage. The skill checks JSON-LD, a format designed for machines to read, and reviews the name, URL, logo, and official social profile links in Organization or Corporation data. This work organizes information related to the Knowledge Panel, the organization information box in search results.
Use it to review brand information on websites for businesses, nonprofits, publishers, and similar organizations. It checks whether the data matches the official name and canonical homepage URL, and reviews the logo image URL and official profiles listed in sameAs.
This skill places organization data on the homepage and avoids duplicating it on interior pages. Use a persistent logo URL and check that it is an absolute HTTPS URL pointing to an actual image. Validation uses Google's Rich Results Test.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Organization schema helps Google understand your brand, populate your Knowledge Panel with accurate information (logo, social links, contact details), and improve brand-related search appearance.
Check the homepage for a JSON-LD script block with @type 'Organization' or 'Corporation'. Verify it includes: name, url, logo (with @type ImageObject), and sameAs array with social profile URLs. Validate with Google's Rich Results Test.
Add an Organization schema JSON-LD block to the homepage <head>. Include name, url, logo (ImageObject with url, width, height), contactPoint, and sameAs array pointing to your official social media profiles and Wikipedia/Wikidata entries if available.
Organization structured data tells Google who you are as a brand. Google uses it to populate the Knowledge Panel in search results—the box showing your logo, social profiles, and contact info that appears for branded queries. Without it, Google has to guess this information from unstructured content.
Check the homepage for a JSON-LD script with @type 'Organization' or 'Corporation'. Verify: name matches the site's official brand name, url matches the site's canonical-url homepage URL, logo.url is an absolute HTTPS URL pointing to an actual image, sameAs array contains at least 2 verified social profiles. Validate with Google's Rich Results Test. Confirm Organization schema is NOT duplicated on interior pages.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/organization
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.