SEO & Visibility

Configure supported SEO titles, descriptions, robots settings, social metadata, JSON-LD and sitemap output. Review which installed product owns those outputs before enabling another metadata layer.

The engine is off until you turn it on under Vendix → SEO & Visibility. Each page and post then gets a Visibility Engine box for its own title, description, canonical URL, robots, social fields and schema type.

Robots. Vendix adds its directives to the one robots tag WordPress prints, so directives from WordPress and other plugins stay and a noindex from any source wins. Search results and 404 pages are never indexed. While "Discourage search engines from indexing this site" is checked in Settings → Reading, every page gets noindex, nofollow and the SEO & Visibility screen shows a warning.

Schema. One connected JSON-LD graph holds WebSite, the organization and the page type chosen in the box: WebPage, AboutPage, ContactPage, CollectionPage, Service, Product, SoftwareApplication, Article, BlogPosting or NewsArticle. BreadcrumbList follows the trail of the ARN Breadcrumbs widget, or Vendix Theme's trail where the page has no widget; shop and product category archives get one, a product search ends at the address of the search, and a page that shows no breadcrumbs gets none. The FAQ widgets of a page share one FAQPage. Organization details fall back to Company Data, including country-specific tax and registry numbers.

XML sitemap. Choose the content types, taxonomy archives and, if wanted, author archives deliberately, leave out noindex content and specific IDs, and set the URLs per sitemap part (100–2,000). Password-protected content and builder templates are always left out.

News articles. While the Newspaper module is on, posts without a chosen type use NewsArticle schema with the post author and category, and NewsArticle can also be picked in the box. An optional Google News sitemap lists the posts of the last two days. Both are explained under News Schema & Sitemap.

Output ownership. When Yoast SEO, Rank Math, SEOPress, All in One SEO or The SEO Framework is active, Vendix leaves metadata, schema, robots and sitemap output to that plugin and keeps its analysis available. On pages ARN Contix publishes, Contix owns the schema and Vendix prints the title, description and social tags Contix writes into the Vendix fields: one description, one schema graph.

A field can be valid without being useful. Keep descriptions specific to the page, ensure the chosen image exists and review the resulting output rather than relying only on a saved settings screen.

Metadata and schema provide structured information; they do not guarantee ranking or eligibility for a particular search presentation.

SEO, GEO, AEO and E-E-A-T-related evaluations organize supported content checks into a readable review. Heading hierarchy, descriptive fields, links and other signals can point to the next editorial action.

Multilingual checks handle documented language and keyword variants, including relevant Turkish and Arabic text differences. Review language-mismatch signals alongside the actual content.

Answer and entity data (Pro). Pages can carry a concise answer summary, primary entity, supporting topics and author and reviewer details that feed the JSON-LD output; speakable selectors are opt-in. A page can also list its authoritative source URLs and a first-hand experience note, and the [arn_sources] shortcode prints the source list where you place it. The readiness score is also in the Free edition.

A readiness or content score is not a promise of search traffic, authority or AI-system inclusion. Use it to investigate the page, not as a substitute for the page itself.

List entries that have not been updated within the selected period. Optional AI suggestions can provide a refreshed title/description and a checklist of facts such as dates, prices or versions to verify.

This Pro tool is off by default; set the age limit (30 to 1,460 days) and the content types in its tab. An entry can also be marked as reviewed.

Compare current and proposed values side by side. Apply approved changes through the supported workflow and retain the available undo path.

An older page is a review candidate, not automatically an inaccurate page. Verify the facts rather than changing its date simply to appear current.

The Pro Site Report summarizes supported findings for the selected public content types. Use the report to identify pages needing attention, then return to the relevant page-level evidence.

The report compares pages with each other, which a single-page review cannot do:

• Pages that share the same title or meta description.
• Pages without an H1.
• Pages that no menu and no other page links to.
• Pages left on the automatic schema type instead of a deliberate one.

The scope is selected published content, not a guarantee that every URL and private record on the site has been assessed. The scan uses the content types selected for the sitemap.

Review report configuration and content ownership when comparing results from different runs.