Use when auditing a local business website's structured data. Applies to any business that serves customers at a physical location or specific geographic area.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
LocalBusiness schema enables Google to show your business details (hours, address, phone, rating) directly in search results and Google Maps, improving local visibility without requiring a click.
Check the page source for a JSON-LD script block with @type matching 'LocalBusiness' or a sub-type (Restaurant, Store, etc.). Verify the required properties are present: name, address with PostalAddress, telephone, and url. Validate with Google's Rich Results Test.
Add a <script type='application/ld+json'> block to the homepage with LocalBusiness schema. Include: @context, @type, name, address (with streetAddress, addressLocality, addressRegion, postalCode, addressCountry), telephone, url, openingHours, and geo. Use a specific sub-type if applicable.
LocalBusiness structured data tells Google the essential details about a physical business. This data powers the Knowledge Panel in search results, the local pack ('map pack'), and integrations with Google Maps. Without it, Google has to guess business details from unstructured page content.
Find JSON-LD script blocks with @type 'LocalBusiness' or a sub-type. Verify required fields: name, address.streetAddress, address.addressLocality, address.addressRegion, address.postalCode, address.addressCountry, telephone, url. Check that address values match the visible on-page address text. Validate with Google's Rich Results Test API.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/local-business
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when reviewing templates, rendered HTML, or shared components related to Create a custom 404 error page. Validate the final browser-facing markup, not just the source framework abstraction.
日本語の概要は準備中です。原文の説明を表示しています。
Use when auditing metadata, crawlability, structured data, or indexability related to Create a dedicated About page. Verify the rendered HTML and HTTP response rather than relying only on source files.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks. Automated testing is strongest at catching structural and attribute-level issues; it does not replace keyboard, screen reader, and manual UX testing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing sign-in, sign-up, MFA, CAPTCHA, recovery, and re-auth flows. Evaluate the full authentication path, including error handling and backup methods, not just the primary login form.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing templates, rendered HTML, or shared components related to Make notifications accessible. Validate the final browser-facing markup, not just the source framework abstraction.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use semantic table markup for screen readers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
日本語の概要は準備中です。原文の説明を表示しています。