Sample Pro Audit · mantox.fi · October 2026

Sample audit: Wisuron by Mantox Solutions

A shortened, real example of a GEO Platform Pro™ audit. Mantox Solutions is the founder’s own company, so this is a first-party demonstration and not an external client case. It covers Claude only; a full Pro Audit runs the questions on every assistant agreed with the client.

Summary. Claude finds and describes Wisuron correctly when asked about it by name, in English and in Finnish. When buyers describe the problem without naming the product, Wisuron is recommended in 2 of 3 Finnish answers and in none of 6 English answers. The English category is held by tools with English pages that list-style articles cite. The technical basics are in order (100/100 on the free check), so the remaining work is content and third-party presence.

1. How the audit was run

2. Brand questions

QuestionNamedCorrect
“What is Mantox Solutions and its product Wisuron? Who is it for and what does it cost?”3/33/3
“Mikä on Wisuron ja kuka sen tekee? Kenelle se sopii ja paljonko se maksaa?”3/33/3

All six answers described the product accurately (drawings and quote requests to an Excel breakdown, Netvisor export, human review) and quoted the published prices. Claude relied mainly on mantox.fi, plus x.com and a Savonia news item.

One inconsistency repeated in all three English answers: Claude reported a Kuopio address alongside “Helsinki-based” and told the user the sources disagree. The current site states Helsinki only, so the Kuopio address comes from an older indexed version or a third-party profile. Assistants repeat such conflicts word for word, and they make a small company look less certain than it is.

3. Category questions

Question (paraphrased)Named
Finnish: software that turns a quote request with drawings into an Excel parts list for a machine shop or galvanizer in Finland2/3
English: tools that turn tender requests with drawings into a parts list or quote spreadsheet for steel fabrication and galvanizing0/3
English: best AI quoting tools for metal workshops in Finland with Netvisor integration0/3

Who is named instead

QuestionNamed in all 3 answersNamed in 1–2 answers
Finnish categoryWerk24Wisuron, Paperless Parts, Kwantflow, Offeri, JAPO Bidline
English categoryKwantflow, SteelFlo, SketchDeck, MiragetheTakeoff, Paperless Parts, DigiFabster, Quotr, Customiser
NetvisorFikuro, QuoteBuddy, Oroox, DigiFabsterPaperless Parts, Aavo, MavaSoft, Total ERP, Manu Online

Sources Claude used for the category

4. Technical audit of page templates

FindingPages
Status 200, one H1, index/follow, self-canonical, lang and Open Graph presentAll 9
Organization, WebSite, SoftwareApplication and FAQPage markupHome, Wisuron
English, German and French versions exist but are missing from sitemap.xml and have no hreflang links/en, /de, /fr
Pricing page has 127 words and no structured data, although it is the page that answers “what does it cost”/wisuron/hinnoittelu
Blog index has 64 words and a single post/blogi

5. Prioritised implementation list

  1. Get the English pages discovered. Add /en, /de and /fr pages to sitemap.xml and link the language versions to each other with hreflang. Hypothesis: this is one reason English category answers had little from Wisuron to cite. The re-test checks it. Effort: hours.
  2. Get listed where English answers come from. Pitch the comparison articles Claude cites for this category, and list Wisuron in the Netvisor marketplace so the integration appears where Claude looked for it. Effort: days, mostly outreach.
  3. Fix the location conflict. Use one location everywhere: the site, llms.txt, X, LinkedIn and business registers. Effort: an hour.
  4. Write one English page per buyer question. “Tender drawings to Excel parts list for galvanizers”, “AI quoting with Netvisor export”. Use the buyer’s words as headings and answer in the first paragraph. Effort: 1–2 days.
  5. Strengthen the pricing page. Add Product and Offer markup, a short FAQ (trial, cancellation, what counts as a run), and an English version. Effort: hours.
  6. Add a named reference. The Vihti hot-dip galvanizing collaboration already appears in Finnish answers. A short English case study with numbers gives assistants a third-party-style fact to repeat. Effort: 1–2 days.

6. Re-test plan

Re-run the same five questions five times each, four to six weeks after items 1–3 are live, so search indexes have time to pick up the changes. Report the share of answers naming Wisuron before and after, with all raw answers, and check that brand answers no longer report a location conflict. With this few runs a change is an indication, so the client sees the evidence behind every number.

Want this for your company? A Pro Audit covers all major assistants, your markets and your competitors, and includes a walkthrough with your team.

Request a Pro Audit Run the free check

Limitations: first-party example, one assistant, three runs per question, answers read and counted by hand. Findings about causes are hypotheses. Assistant answers change over time; this sample reflects 19 October 2026.