NetoTraffic Content Suite

No. The audit — all nine checks, the Health score, the corpus report, the Link health tab (including the broken link checker), the drill-down lists, the settings — works completely on its own and always will. An account is only needed if you want the plugin to write meta descriptions, title tags or alt text for you, suggest links, or draft an article.

Three, all optional, none of them on by default:

• netotraffic.com — only if you paste an API key and click a generate or fix button. Endpoint: https://api.netotraffic.com/v1/plugin. Terms: https://netotraffic.com/terms-of-service/ Privacy: https://netotraffic.com/privacy-policy/
• Google Search Console — only if you paste your own Google Cloud Client ID and Client Secret and click Connect. This is your own Google Cloud project; netotraffic.com is never involved and never sees that data. Terms: https://policies.google.com/terms Privacy: https://policies.google.com/privacy
• Check links (Link health tab) — only when you click that button. It requests the link and image addresses found in your content to see whether each one still responds. No account and no API key. What is sent is an ordinary HTTP request (a HEAD, or a small ranged GET if a server refuses HEAD).

Nothing, unless you have pasted an API key and clicked a button that generates something. New accounts include a number of free credits; the plugin shows every price before you click. You can revoke a key from your netotraffic.com account at any time.

• Connect: your API key and site URL, to check the key and read your credit balance.
• Fix with AI (description or title): API key, site URL, plugin version, that post's title, URL, current title tag when rewriting a title, and up to 6,000 characters of its text.
• Suggest links: the same, plus titles, URLs and excerpts of other published posts to choose targets from — never their full text.
• Write alt text: the same, plus the web addresses of up to 20 images with no alt text. The image files themselves are not uploaded.
• Draft with AI: the same, plus site language, target length, focus keyword if you typed one, and — on the second call — the outline as you edited it.
• Generate with AI on a Content Block: API key, site URL, plugin version, that post's title and up to 6,000 characters of its text.
• Generate site summary on llms.txt: API key, site URL, plugin version, site name and tagline, site language, and titles of up to eight recent published pages.

Nothing, unless you have created your own Google Cloud project, pasted its Client ID and Client Secret, and clicked Connect.

• Connect: your browser goes to Google's consent screen (accounts.google.com) using your Client ID. After you grant access, this site's server exchanges the code for tokens at oauth2.googleapis.com using your Client ID and Secret. That exchange never passes through netotraffic.com.
• During a scan while connected: one request to Google's Search Console API (www.googleapis.com/webmasters/v3) for this site's click and impression counts per page over roughly the last six months. Only aggregate counts, not individual visitors.

Only when you are connected to the AI service, and only on the post you clicked a button on. Nothing happens on its own, and every change has an Undo button next to it because the previous value is always saved first. Four things can be changed, and they are separate:

• The meta description — its own field, never your post content.
• The title tag — your SEO plugin's title field. Your post's actual name is never changed, so nothing is renamed anywhere else on your site.
• Image alt text — this does edit your post content, but only by adding an alt to images that had none. Nothing else in the post is touched.
• A drafted article on a thin post — this replaces (or adds to) the post's content, and it is the only feature that does. You read the whole draft in the plugin and click Save before anything reaches the page. WordPress also keeps its own revision.

No, and that is deliberate. It suggests them: an anchor phrase that already appears in your post, the post it should link to, and the finished HTML on a Copy button. You decide where it goes and paste it in yourself. Automatically inserting a link means editing your stored post content, and one bad edit on a live page is a much bigger problem than a meta description you can undo. Every suggested anchor phrase is also checked against your actual post text before you see it, so you will never be handed a phrase you cannot find.

Yoast SEO, Rank Math and SEOPress are fully supported for both reading and writing. All in One SEO is read-only in this version: it stores descriptions in its own database table with its own cache, and writing there directly could leave AIOSEO showing stale values. On an AIOSEO site the audit works normally and AI fixes hand you the finished description to paste in. If you have no SEO plugin at all, the plugin stores descriptions itself, and there is a setting to output them as a description tag. That setting turns itself off automatically if you later install an SEO plugin, so you can never end up with two description tags.

Nothing else on your site links to it. Search engines find pages by following links, so a page nothing points at is harder to discover and gets no ranking strength passed to it. This check needs the whole site read before it can answer, so it only appears once a scan finishes — a half-finished scan would report most of your site as orphaned. Links a post makes to itself do not count. Anything in one of your navigation menus is never listed, and neither are your front page and blog page — they are linked from every page on the site. One limitation to know about: only links inside your posts' content are counted. The scan reads what is stored in the database and never renders a page, which is what keeps it fast on large sites, but it means a post reachable only through a category archive or a related-posts widget can still show up here. If a listed page looks fine to you, mark it "not an issue" and it will stay off the report.

Because that is where the fix actually lives. A bio is a field on the author's profile (Users → Profile), not anything the post editor exposes, so this is the one report whose Edit link points somewhere other than the post itself. It needs the same permission WordPress already requires to edit that user's profile; if you cannot edit the author's profile, the link is left off the row instead of sending you somewhere that will just refuse you. The check itself only looks at whether the author has any bio text at all — it does not judge length or quality, and it says nothing about theme output. Whether your theme actually displays a byline or the bio on the page is a separate, theme-specific question this plugin cannot answer without rendering your posts, which is exactly what the scan is built to avoid.

One number, 100 down to 0, next to the scan button once a scan has read at least one post. It is not a new signal — it is the same weighted scoring "Fix these first" already uses (a missing description counts for more than a missing alt tag), averaged across every scanned post instead of just the top ten, and normalised so the number means the same thing on a 5-post site and a 5,000-post one. 100 means every scanned post currently has zero open issues. It deliberately ignores the cornerstone star: this is a site-wide reading, not a "what to fix first" ranking, and a handful of starred pages should not be able to swing the whole number.

A link in the post's content pointing at your own domain, either as a full URL or as a relative path. Anchors, mailto:, and tel: links do not count. Because the scan reads the stored post content rather than rendering the page, links added by your theme, by related-post widgets, or by shortcodes are not counted. Those are not really the post's own internal links, and rendering every post to find them would make scanning a large site impossibly slow.

Each post is reduced to a handful of its most distinctive words during the scan, weighted so its title counts more than its body. Posts are then compared pairwise by how much that reduced set overlaps. Two posts that share almost everything are reported as duplicates; a looser overlap is reported as "covering the same ground". A thin pair or group in either band becomes a merge candidate; an overlapping pair where neither post is linked to from anywhere else on the site becomes a "missing pillar" pair. All of this runs on your own post content already read during the scan — no extra requests, no AI.

Scan my site only ever reads your database, which is what makes it safe to run as often as you like on a site of any size. Checking whether a link still works means requesting the address itself — a fundamentally slower, external kind of check — so it stays a separate button ("Check links" on the Link health tab) rather than something the main scan does automatically. It runs in two batched passes, the same progress-bar pattern the main scan uses: first it reads every link and image address out of your content, then it requests each unique address once (so a link repeated on fifty pages is only checked once), and shows anything that no longer responds together with every page that links to it.

Block delimiters and shortcodes are stripped, HTML tags are removed, and what is left is counted. It handles non-English text correctly.

No. The scan runs in batches of 100 posts, each its own quick request, with a progress bar. You can close the tab at any point — you will just get partial results and can rescan later.

Deleting the plugin removes its settings and saved scan results automatically. There is also a setting to delete the plugin's own post data on uninstall. Descriptions that were written into your SEO plugin's field are left alone — they are your content at that point, and deleting them would remove ones this plugin never wrote.