Vendix Pro Documents
Version 1.1

Meet Vendix Pro

Vendix brings Elementor components, shared company content, media workflows, and search presentation tools into one WordPress workspace.

Begin with the modules you actually need. Design, SEO, AI Media, and store controls have separate settings; installing the plugin does not require enabling all of them.

Install Vendix and activate Pro

↗ Enlarge

Pro activation and AI provider access are separate. Your license does not include provider API credentials. For a missing or altered protected-file warning, reinstall a complete official package rather than editing sealed files.

Understand the module dashboard

↗ Enlarge

The dashboard summarizes module status and provides Quick Actions such as opening Elementor pages, managing company data, uploading fonts, and configuring SEO.

Use a module’s Manage link or its navigation tab. Settings forms use Save Vendix Settings; confirm the saved state before moving to another module.

Enter company information once

Open Vendix → Company Data. Shared values can be reused in footers, contact pages, documents, and dynamic content.

↗ Enlarge

[company_name]
[company_address]
[company_phone]
[company_link type="whatsapp" label="Contact us"]
[company_value field="company_name" fallback="Our company" format="text"]

[current_date] uses the WordPress timezone and date format. Updating company data can change every page that references it, so check a representative footer and contact page after edits.

Configure the global design system

Open Smart Features → Design System. Configure typography and reusable brand colors.

↗ Enlarge

1. Enable the design system when you want Vendix to apply it.
2. Choose the application scope: Vendix widgets and layouts, or the entire site.
3. Upload your fonts where offered or choose system fonts. Assign heading and body families; RTL and LTR text can use different families.
4. Set brand color tokens and review the live font preview.
5. Save, then inspect an Elementor page on desktop and mobile.

If a font is not visible, check the uploaded source, fallback stack, and frontend cache. Use the entire-site scope deliberately because it can affect content outside Vendix widgets.

Build an Elementor page with Vendix

1. Open a page and select Edit with Elementor.
2. Search the widget panel for the relevant ARN/Vendix component and drag it into a container.
3. Complete the widget’s content controls first, then its layout and style controls.
4. Choose semantic heading tags appropriate to the page structure, rather than selecting a tag solely for its visual size.
5. Review desktop, tablet, and mobile layouts in Elementor, update the page, and check the real frontend.

Available components include hero and content blocks, FAQ, feature/list blocks, pricing and comparison components, testimonials, logo carousel, image slider, responsive images, navigation components, and table of contents. Each has its own controls; use the component that matches the content you need.

For an FAQ, enter real questions and answers. For a table of contents, check which headings are included. For a carousel or slider, verify the images, links, movement, and small-screen behavior.

Use the Icon Manager workspace to enable the icon groups you need and maintain selected icons. Confirm that the chosen icon is available in the component picker and that its meaning remains clear alongside text.

Intro video, comments, and shortcuts

The Smart Features workspace also contains optional site utilities.

↗ Enlarge

Intro Video: choose the media, skip/play text, display frequency, and transition settings. Test first-visit behavior and manual playback on mobile devices. Browser playback rules can affect autoplay; keep a clear skip or play path.

Disable Comments: apply the control to all or selected content types. It prevents new commenting without deleting existing discussion threads. Disable the module to restore normal commenting behavior.

Quick Menu: configure the available administrative shortcuts and groups. Verify destination URLs, content types, and menu visibility before relying on them.

Save the module and test the frontend behavior that changed. Do not enable an intro or global comments control simply because it is available.

Build headers and footers

Open Vendix → Header & Footer. Vendix draws its own headers and footers as plain HTML and CSS: they replace the theme's header and footer, work with classic and block themes, and do not load a page builder for visitors. Until a header or footer is published, the theme keeps showing its own.

↗ Enlarge

↗ Enlarge

↗ Enlarge

Company data and phones

Phone, email, address, company name, and social links come from Vendix → Company Data. Update a detail there and every header and footer shows the new value. Text elements accept {phone}, {email}, {address}, {company}, and {year}.

On phones the menu turns into a menu button with a side panel. Wide header elements such as buttons, contact items, and social links start hidden on mobile (an M mark appears beside them in the structure); open the element and clear Hide on → Mobile to show one again. Rows and elements can be hidden on any device.

Where a layout shows

The Display rules tab chooses where a layout appears: the entire site, the front page, the blog, search results, 404 page, single items or archives of a content type, WooCommerce pages, or specific pages and categories by ID. Exclude rules remove the layout from chosen places. When several layouts match a page, the most specific rule wins; on a tie, the layout edited last wins. Logged-in administrators see the chosen layout and rule in the admin bar.

If another plugin also replaces headers and footers (for example Elementor Pro Theme Builder), the list screen warns you. Use one of them on the same pages. Layouts made with the former Vendix builder are listed but do not show until they are rebuilt and saved.

Change an address everywhere with Search & Replace

Open Smart Features → Search & Replace. Use it when a site moves to a new address, for example from a staging address to the live domain, or when a text must change on many pages at once. Only administrators can use it; on a multisite network only super admins, and only for the current site's tables.

↗ Enlarge

↗ Enlarge

Page builder data stays valid: escaped addresses in Elementor JSON, URL-encoded links, WPBakery raw HTML blocks, BeTheme base64 data, and serialized data such as theme options and Beaver Builder layouts are changed in their own format. Serialized data that cannot be read safely is left unchanged and reported.

Enable the SEO & Visibility Engine deliberately

Open SEO & Visibility. The master engine is an explicit switch.

↗ Enlarge

AI Media has its own switch and can run independently from the visibility engine. The engine being off means Vendix produces no SEO metadata, Schema, analysis, or sitemap changes.

Select the right sitemap and scan scope

In the visibility workspace, open Sitemap and review the deliberate list of included public content types and taxonomies.

↗ Enlarge

1. Select the public content types that should be discoverable, such as published pages or posts used on this site.
2. Exclude specific items that should not appear, and check any taxonomy choices.
3. Save and inspect the resulting sitemap from the interface’s URL when Vendix is its active owner.
4. Use the visibility report’s Rescan site action to refresh readiness results for that scope.

Site Report is a Pro feature and scans the same selected public content-type list. Header/footer builders and structural templates are not intended to be indexed independently. If a public content type is missing from the report, review its Sitemap selection first.

Excluding an item from a sitemap is different from applying a robots noindex directive. Review both decisions when keeping a page out of search results.

Review a page in the Visibility Engine

Open a WordPress post or page and find ARN Smart Visibility Engine. Vendix provides Overview, SEO, Schema, AI readiness, Search & AI, and Search Ideas views when their relevant features are available.

↗ Enlarge

1. Read the Overview and the actual detected-content/source information.
2. Review the SEO title, description, robots, and related fields exposed by the panel.
3. Choose Schema that accurately describes the visible content. Do not add unsupported entities or answers only to improve a score.
4. Read AI readiness findings such as answer clarity, structure, and trust signals.
5. Save the normal page changes and inspect the actual frontend.

Use findings as a prioritized review list. Heading hierarchy warnings should be compared with the real page. Missing image alt text should be assessed in context; decorative images may intentionally have empty alt text.

If the detected content is a fallback instead of the intended rendered source, check the actual page and rescan after correcting the underlying rendering issue. A score alone is not proof of search performance.

Connect Search Console and optional Bing

Open SEO & Visibility → Search Intelligence. This connection reads the site’s own search evidence and is separate from the AI provider connection.

↗ Enlarge

1. Expand the product’s Setup guide – step by step. Follow its service-account setup, API enablement, JSON-key creation, and Search Console property-access instructions.
2. Use a service-account JSON key containing type: service_account, client_email, and private_key. An OAuth client file with client_id/client_secret is a different credential and does not meet this field’s requirements.
3. Paste the complete JSON or choose its file in the Google connection area. Enter the Search Console property exactly as registered: a URL-prefix property such as https://example.com/, or a domain property such as sc-domain:example.com.
4. Select Save connections, then Test Google. Review the properties the key can access, correct the selection if needed, and save again.
5. Use the available synchronization action and verify its recorded result before expecting search data on individual pages.
6. For optional Bing evidence, enter its Webmaster API key and the registered site URL, save, test, and synchronize that connection separately.

These credentials belong to your site and services. The product stores the connection keys encrypted; do not paste them into support messages or public screenshots. A successfully stored key is different from successful property access or a completed synchronization.

Search evidence may be empty for a new site, an unmatched property, or a page with no relevant queries. Check the connected property, synchronization state, and actual available data before interpreting missing results.

Connect your own search data

Open Vendix → SEO & Visibility → Search Intelligence. Connections belong to your site; they do not use an ARN Google account. Search data is read-only and is not shown on the public site.

1. In your Google Cloud project, enable the Google Search Console API.
2. Open IAM & Admin → Service Accounts and create a service account. Copy its email address; no Cloud project role is needed solely to read a Search Console property.
3. Open the service account itself, then Keys → Add key → Create new key → JSON. Treat the downloaded JSON file as a credential.
4. As the Search Console property owner, open Settings → Users and permissions → Add user. Add the service-account address with the read-only Restricted permission.
5. In Vendix, supply the service-account JSON and the exact property: https://example.com/ for a URL-prefix property, or sc-domain:example.com for a domain property.
6. Save and select Test Google; verify the accessible property and synchronization result. Configure your own Bing Webmaster API key separately if required.

Organizations can disable service-account key creation. Ask the Google Cloud administrator for an approved integration method instead of bypassing that restriction. Vendix also requires the PHP OpenSSL functions used by this connection.

The interface reads the most recent 90 days. Google hides some queries and API limits apply; Search Console totals do not exactly match Google Analytics. Search Ideas generated by AI are suggestions, not observed queries.

Use site profiles, page summaries, and Search Ideas

Search & AI uses the site’s context and an approved page summary to make suggestions more relevant.

↗ Enlarge

Search Console data and generated Search Ideas are different evidence sources. A page with little relevant query evidence may have few useful suggestions. Configure the available Search Console connection and synchronization controls if you want actual search evidence; verify the property and synchronization result.

Connect text and image AI

Open AI Media. Choose Vendix AI or the WordPress AI integration when it is available on your installation.

↗ Enlarge

1. Select the Text AI provider for summaries and suggestions.
2. Choose Image AI separately, or Same as Text AI only when that provider/model can read images.
3. Enter the provider key and model. Use Load models to review models available to that credential rather than copying an outdated name.
4. Select Test connection, then save the settings. Where offered, test the image model as well.
5. Enter optional token prices and a budget/usage limit appropriate to your operation.

A text-only provider cannot reliably describe an image’s visual content. The interface warns when media suggestions would be inferred from the filename; those low-confidence suggestions must remain reviewable.

WordPress AI requires WordPress 7.0 or later with a connected provider. Use directly configured Vendix AI when that integration is unavailable. Provider billing and access remain separate from your Pro license.

Review media suggestions and file changes

1. Enable Media Intelligence and open the supported attachment/media workflow.
2. Request a suggestion for a known image and inspect the filename, title, slug, and alt-text preview.
3. Check the image itself. Write a concise description of its relevant purpose, and keep decorative images appropriately empty.
4. Apply only the changes you approve. Physical filename changes use a reversible transaction; keep its result and recovery information.
5. Check the media URL and pages that use the image afterward. If a transaction reports failure, inspect its state before repeating it.

Automatic alt remains review-first: decorative images are skipped and low-confidence suggestions stay in the review queue. AI can still be wrong even when a request succeeds.

Changing an attachment title or alt attribute is different from renaming the physical file. A filename transaction can affect paths and references, so test this workflow on staging before using it for a large library.

Configure form protection

Open Form Guard. Enable the protection you need for supported form systems and configure the chosen CAPTCHA engine.

↗ Enlarge

1. Select the form systems you want protected.
2. Configure Cloudflare Turnstile with the correct site/domain credentials, or choose an available alternative such as the classic image CAPTCHA.
3. Review Spam Shield and Identity Guard settings and save.
4. Submit legitimate test messages on desktop and mobile, including logged-out users.
5. Inspect blocked events when genuine users cannot submit; adjust the specific condition that caused the block.

Form protection can reject submissions. Test the visitor experience and contact-delivery path after enabling it, rather than judging readiness only by the settings screen.

Optional WooCommerce controls

These controls are relevant when WooCommerce is installed and the store needs them.

↗ Enlarge

Enable Product Identifiers & Cost only for fields your store actually needs, such as MPN, GTIN, manufacturer, supplier, and internal costs. Review visibility settings so internal cost information is not accidentally presented as public product copy.

Test a representative new product, an existing product, and checkout behavior after changing store controls. Keep the underlying product type and shipping requirements consistent with what you sell.

A practical first-run checklist

1. Install Elementor and activate Vendix Pro.
2. Enter company information and verify one shortcode on a draft page.
3. Configure design tokens, then review a Vendix component in Elementor.
4. Choose the owner of SEO output and set the correct sitemap content scope.
5. Review one page’s content and visibility findings.
6. Configure AI only if you intend to use it; approve one page summary before generating suggestions.
7. Test optional media, form-protection, and store controls individually.
8. Build a header and footer as drafts, check them in the preview on desktop and mobile, then publish.
9. After moving the site to a new address, run the Search & Replace scan and preview before running a replacement.

Before updating, back up the site and install the verified new Pro package. After updating, check Elementor page saving, a representative frontend page, the visibility panel, and any active form protection.

Troubleshooting

Support reports should include Vendix/Elementor/WordPress/PHP versions, the module or page, reproduction steps, and sanitized errors. Exclude ARNA codes, API keys, CAPTCHA secrets, and private customer information.