Skip to content
VTEX Companion
EN PT Switch to Portuguese

VTEX Companion

A Chrome and Firefox extension that reads the stack, catalog and SEO of the open tab, calls the store’s APIs with its own session, and unlocks the FastStore CMS preview on your localhost.

Chrome Firefox · Coming soon Source on GitHub
The VTEX Companion popup open over a product page, showing name, reference, brand, category and the SKU list with EAN, seller, price and availability.

What it does

01

FastStore preview on localhost

The Preview button of the FastStore CMS — the legacy Headless CMS and Storefront > Content — opens the published store. The extension injects a Localhost button next to it that opens the same URL on your dev server: the whole query preserved, on both CMS versions, and with no cmsDevMode required. Stores on VTEX IO and on the legacy portal preview by workspace and do not use this flow.

The FastStore CMS admin with the injected Localhost button next to Preview, and the Development Mode panel showing a clickable Localhost URL beside the API URL.

02

Fetch runner

Call the store’s APIs from inside the tab itself, with the session it already has. Presets for Session, Checkout, Catalog, Intelligent Search, OMS and Master Data; the response formatted or raw; session history and copy as JSON or CSV. Any method that changes data asks for confirmation first.

The VTEX panel inside DevTools, with the request on the left and the formatted 200 response on the right, plus the history of the session’s calls.

03

Stack detection and session

IO, FastStore, legacy CMS Portal or headless — with account, workspace, binding and the signals behind every conclusion. It also reports whether store and admin sessions exist on the origin, and clones the session from {account}.myvtex.com to the store domain without the token ever touching the clipboard.

The popup on the Store tab over a FastStore store, showing the detection signals and the session block with buttons to sign in with a token, clone from admin, and clear.

04

SEO and third-party scripts

Indexing, canonical, hreflang, JSON-LD, headings and images missing alt, with rules per page type — a PDP with no Product, a listing with no ItemList. Alongside it, the vendors loaded on the page, with the account id where there is one: GTM, GA4, Meta, TikTok, Clarity, Criteo and others.

The popup on the Page tab showing the table of SEO findings and, below it, the detected third-party scripts with Meta Pixel, Google reCAPTCHA and VTEX Pixel Manager.

And more

Page catalog
A PDP with the SKU list — EAN, refId, seller, price and availability — and a shortcut into the admin. Listings and search with category, path, term, map and sorting.
DevTools panel
The runner also lives in a VTEX tab in DevTools, with the whole window, on top of the popup.
Chrome and Firefox
One source tree, two MV3 builds: service_worker on Chrome, background.scripts on Firefox.
No global content script
Page reading is injected on demand when you open the popup. That is why installing it never asks to “read your data on all websites”.

It collects nothing

There is no server. The extension reads the tab on demand and discards it when the panel closes. Fixed access is only *.myvtex.com and localhost; store domains are optional, granted by you site by site.

Privacy policy

An independent project. Not an official VTEX product, and it does not use VTEX’s visual identity.