Description

Sugata (姿, meaning “figure” or “presence”) helps WordPress company sites output their organization information as accurate JSON-LD structured data (Schema.org) — content that search engines and AI search / LLM systems can read.

Many SEO plugins are either too complex or rely on automatic generation, which makes it surprisingly hard to express your own, company-specific information correctly. Sugata focuses on “learn less, set up faster”, so that even small businesses without a dedicated web person can configure the Organization schema without getting lost.

The result is a clear “presence” for your company in digital space — a form that search engines and AI can correctly understand as who this company is.

Structured data is infrastructure: it helps machines understand your site, but whether and how it appears in search results or AI answers is decided by Google and other services. Sugata’s job is to express your information correctly — what happens next is up to them.

Note: The plugin’s admin interface is currently in Japanese, as it is aimed at companies in Japan.

Free features

Settings page for company information (Organization) — a single admin menu screen
Company name / legal name / alternate name / description / site URL / logo / founding date / email / phone
Japanese Corporate Number (法人番号, 13 digits) output as Organization identifier — a strong signal for uniquely identifying the company
Multiple official social/related URLs (sameAs) — signals that help search engines and AI identify your company
Address (PostalAddress) and contact point (ContactPoint)
WebSite schema (site name & URL) output on the front page, for the “site name” feature in search results
Output written to the front page <head> as application/ld+json (Organization is front-page only, following Google’s recommendation)
Empty fields are excluded — clean JSON-LD
Live preview of the generated JSON-LD
One-click “Import from WordPress” (site title, tagline, logo) into empty fields
Each entity gets an @id (#organization / #website) and WebSite references Organization as its publisher

Roadmap

Multiple locations / departments (branches, sales offices)
Product / Service schema with repeatable “specification” fields
Automatic structuring of category pages (CollectionPage)
Input assistance and validation
Full localization of the admin UI (e.g. an English locale) — the plugin is already translation-ready (text domain sugata, bundled .pot)

Screenshots

The company information (Organization) settings page: input status at the top, per-field help, and the "Import from WordPress" button. — The company information (Organization) settings page: input status at the top, per-field help, and the “Import from WordPress” button.

Live preview of the generated JSON-LD (Organization and WebSite). — The company information (Organization) settings page: input status at the top, per-field help, and the “Import from WordPress” button.

Installation

Upload and activate the plugin.
Open the “Sugata” menu in the admin.
Enter your company name (required) and any other information you know, then save.
View your site source and check the <script type="application/ld+json"> in the <head>.
Validate with Google’s Rich Results Test or the Schema Markup Validator.

FAQ

Can I leave fields other than the company name empty?: Yes. Only the company name (name) is required; everything else is optional. Empty fields are not included in the JSON-LD output.
On which pages is the data output?: Organization and WebSite are output in the <head> of the front page. Google recommends placing company information on the homepage (or a single page that describes the organization), so there is no need to include it on every page.
Is the admin interface available in English?: Not yet. The interface is currently Japanese only. The plugin is fully translation-ready (text domain sugata), so other languages can be added later.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Sugata（姿）” is open source software. The following people have contributed to this plugin.

mukuro696

Translate “Sugata（姿）” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.0.1

Admin styles are now loaded as a proper stylesheet via wp_enqueue_style (assets/admin.css) instead of an inline block, following the WordPress.org plugin guidelines.

1.0.0

First public release. Organization & WebSite JSON-LD with a friendly Japanese settings screen (corporate number, multiple social URLs, overseas-friendly address, @id linking, import from WordPress, honest copy, AI search / LLM positioning).

0.1.20

The “Pro” overview is now visually muted and shows “coming soon” until a Pro page exists. A sugata_pro_url filter is in place so the upgrade link can be enabled later (once the sales plan is decided) without editing the free plugin.

0.1.19

Carried the “AI search / LLM” positioning through the settings-page tagline and the English readme (short description and description), worded as compatibility rather than a guarantee.

0.1.18

Added an “AI search / LLM ready” lead to the Japanese plugin description, to highlight that structured data also helps AI/LLM systems read your company info (worded as compatibility, not a guarantee).

0.1.17

Added a discreet copyright notice (© Mukuro-696) at the bottom of the settings page.

0.1.16

Warmed the tone of the Japanese plugin description and the settings-page tagline (friendlier for non-technical users), without over-promising.
Removed the “Visit plugin site” link, which pointed to an unprepared URL. Everything you need is inside WordPress (the settings page overview).

0.1.15

The plugin name and description shown in the WordPress plugins list are now fixed in Japanese (the same regardless of the site’s language setting). The readme description text remains English as required by WordPress.org.

0.1.14

Added a branded header and a “Free / Pro” overview at the top of the settings page, so you can understand the plugin and its plans inside WordPress without visiting an external site.

0.1.13

The region field now supports overseas addresses too. It is a text field with autocomplete suggestions of Japan’s 47 prefectures, so Japanese sites can pick from the list while sites abroad can type any state/region freely.

0.1.12

The prefecture (都道府県) field briefly became a dropdown of the 47 prefectures; superseded by 0.1.13 (autocomplete) to also support overseas regions.

0.1.11

The contact type is now a dropdown (customer service / sales / technical support / billing / emergency, or “unspecified”), with guidance for when you are unsure. The submitted value is validated against the allowed list.

0.1.10

Added support for an optional always-visible sub-description under an input (in addition to the hover “i” tooltip), for fields that benefit from a visible hint.

0.1.9

Reworded help text and descriptions to avoid implying any guarantee about what Google or AI will do. Sugata’s role is to express your information correctly; how it appears in search results or AI answers is up to those services.

0.1.8

Added support for the Japanese Corporate Number (法人番号, 13 digits), output as the Organization identifier (PropertyValue). Hyphens and spaces are stripped automatically and the value is validated to 13 digits.
Security review pass (escaping, capabilities, nonce via Settings API, direct-access guards); minor hardening of the logo preview markup.

0.1.7

Rewrote readme in English (WordPress.org requirement) and made plugin headers English; admin UI remains Japanese.
Removed the manual load_plugin_textdomain() call (translations load automatically on WordPress.org).

0.1.6

Internationalization (i18n): all strings are translatable; bundled translation template languages/sugata.pot.

0.1.5

Output Organization on the front page only, following Google’s recommendation to place company info on the homepage.

0.1.4

Added @id to Organization and WebSite, with WebSite referencing Organization as its publisher, so search engines and AI can treat them as one entity.

0.1.3

Added an “Import from WordPress” button (site title, tagline, URL, logo) that fills empty fields without overwriting existing input.

0.1.2

WebSite schema support (site name & URL on the front page; opt-in). The sitelinks search box (SearchAction) is not supported, as Google retired it in 2024.
Logo can be selected from the media library (direct URL input still works), with preview.
Input-status panel on the settings page (required = red, recommended missing = yellow, complete = green).

0.1.1

Added Organization fields: legal name, alternate name, description, founding date, email, and official social/related URLs (sameAs, multiple).
Added “i” tooltips for each field and changed placeholders to generic guidance.
Founding date accepts year / year-month / year-month-day (Schema.org compliant; slashes and single digits are normalized).

0.1.0

Initial release. Organization JSON-LD output and settings page.