XeroWP
Traffalyzer
Traffalyzer

Traffalyzer

0/5 (0 ratings) — active installs Updated Sep 23, 2026
content refreshllms.txtSearch Consoleseosite audit
Download v1.0.0 Plugin Website
Block editor sidebar: clicks and position, the real search queries checked live against your text, and the search performance chart with a verdict on your last change.

Block editor sidebar: clicks and position, the real search queries checked live against your text, and the search performance chart with a verdict on your last change.

Traffalyzer connects this website with its account on traffalyzer.com and brings the outside view into WordPress. Other SEO plugins check what is in the form. This plugin shows what actually happens out there.

Reports in the admin area (menu Traffalyzer):

  • Overview: site score, last scan, what comes next and a technical quick check of robots.txt, the sitemap and llms.txt.
  • Findings: everything the crawler found, with an edit link for every affected page.
  • Growth plan: the steps Traffalyzer suggests; tick them off on paid plans.
  • Search queries: strongest queries, opportunities (position 5–20), winners and losers.
  • Pages: clicks, impressions, position and open findings for every page, plus the view Needs a refresh: pages that lost at least 20 % of their clicks and have not been changed for twelve months.
  • Broken addresses: addresses that returned an error in the last scan, with the pages that link to them and a suggested redirect. With the Redirection plugin or the Rank Math redirections module the redirect is created right there.

In the editor (block editor sidebar, or a meta box in the classic editor): findings for this page, clicks and position, the real search queries, live-checked against your text as you type, pages worth linking to, pages that compete for the same query, the search performance chart with your revisions as markers, and a verdict whether your last change made a difference. The sidebar loads in the background; nobody waits for Traffalyzer when opening the editor.

Also: Traffalyzer columns in the post lists (sortable), a dashboard widget, an admin bar item with the number of important findings, checks in Tools Site Health, WP-CLI commands and an optional /llms.txt generated from your published content.

The inventory. WordPress tells Traffalyzer which addresses exist, whether they are published and indexable (including noindex from Yoast SEO, Rank Math, SEOPress and All in One SEO), which canonical you set deliberately, the content type and when a page was changed. Traffalyzer uses this for findings no crawler can make on its own: unpublished content that is still reachable or still in Google, published pages nothing links to, and canonicals that differ from what WordPress intends. Changes are collected when you save and sent in the background; a complete sync runs once a week.

What the plugin deliberately does not do: start a scan when you save. A crawl takes minutes and uses quota. There is a button for that.

Staging and local copies

Reports and the editor sidebar work on staging and local copies too: addresses are rewritten to the domain Traffalyzer knows. The inventory, however, is only sent from the live site, because a copy would report content the live site does not have.

Free and paid

The Traffalyzer service can be used for free. Some functions depend on the paid Traffalyzer plan (the details of the growth plan steps and ticking them off); the plugin itself locks nothing.

External services

This plugin connects to Traffalyzer (traffalyzer.com), a service run by kommune3 (Germany) that analyses the search performance of websites. It is used to show the reports, the editor sidebar and the metrics of this website in WordPress. Nothing is sent before you connect the website.

What is sent, and when:

  • When connecting (your browser, on traffalyzer.com): the address of the homepage, the return address in the admin area and one-time values of the connection. You sign in on traffalyzer.com yourself.
  • When connecting (this server, to traffalyzer.com/api/v1): a one-time code and its verifier, in exchange for the key.
  • Every request to traffalyzer.com/api/v1 carries the key of this website, the language of the current user (lang=de or en, so texts come back in that language) and a User-Agent with the plugin version and the address of the homepage.
  • Reports, editor sidebar, dashboard widget (when someone opens them): the address or path of the requested page and the time window.
  • Daily background task: the domain profile and the metrics of all pages are fetched (no data is sent apart from the key).
  • Site Health (Tools Site Health, and WordPress’ own weekly background check): the key is checked with one request for the domain profile.
  • Inventory (background task, button or WP-CLI, only from the live site): per post the address, a deliberately set canonical, published/indexable, the content type, the internal ID (e.g. post/12) and the date of the last change.
  • Edit dates (background task, can be switched off): the page address, the time of the edit and the revision ID.
  • Scan button: only the request to start a scan.
  • Growth plan, ticking off a step (paid plan): the key of the step and whether it is done or open again.
  • Disconnecting, reconnecting and uninstalling: the stored key (on reconnecting: the previous key) is sent to Traffalyzer to revoke it.

Not sent: content, titles, names, e-mail addresses or IDs of editors, anything about visitors. The plugin sets no cookies and adds no scripts to the public website.

Source code and build

The admin and editor scripts in build/ are compiled from the readable sources in src/, which ship with the plugin together with package.json, package-lock.json and webpack.config.js. To build them yourself you need Node.js 20.19 or newer (22 recommended):

npm ci && npm run build

PHP needs no build step. Translations: npm run i18n:pot creates languages/traffalyzer.pot.