Aomark Suite 2.0.0 · Updated September 26, 2026
Set accurate organization details and choose which Suite metadata and schema outputs belong on your site.
Enter the site's identity
Open Aomark Suite → Settings → Site identity. Enter the public organization or person name, canonical website URL, logo, and the entity type that best represents the site. Use a logo URL that loads publicly and depicts the same entity named in the fields.
- Open Site identity and review the site category/setup prompts.
- Enter the public name and canonical site URL.
- Choose a matching entity type and provide a publicly accessible logo for that same entity.
Choose schema behavior
Save the identity settings, then review schema controls for the content types where Suite should output its saved JSON-LD. Generate or save schema for a page through its WordPress editor, or use Content bulk tools for sitewide missing values. Automatic FAQPage data is derived from recognizable visible questions and answers in the rendered page; there is no separate FAQ generator or FAQ sync step.
- Review which content types use Suite's automatic schema output.
- Generate and review schema in an individual editor, or use Content only when a sitewide missing-field action is intended.
- Maintain FAQ questions and answers in the visible page content.
Set social metadata
Use the Open Graph and social card controls on Site identity to choose the default sharing image and card type. Page-level values can be reviewed alongside the page's other metadata. Use an image with a clear subject and adequate dimensions, then check the public page preview after saving.
- Open Open Graph & Social Sharing.
- Choose a representative default image and card type.
- Check a page-level value and its public social preview where available.
Check the result
Open a representative public page and inspect its source or a structured-data validator to confirm the intended Suite output appears once. If another SEO plugin already emits the same schema or social tags, resolve ownership before leaving both active. FAQ additions depend on server-rendered, recognizable content and may not be detected from client-only or ambiguous markup.
- Open a representative public page and inspect its source or use a structured-data validator.
- Check for one intended schema owner and correct site identity.
- If FAQ content is client-only or not clearly identifiable in rendered HTML, do not assume it will be detected.



