froneri.com
Evidence collected August 31, 2026 · 31 polite, robots.txt-respecting requests · every claim cites what it saw
No letter grade — withheld, not failed
No letter grade is issued because this tool could not read this site's content structure: of the 520 URLs in its sitemap, 379 (72.9%) could not be classified into content sections by the reader. That is a limit of this tool's reading, not evidence that the company lacks content — a grade computed from the readable sliver would report a gap in this tool as their failure. What could be observed is scored below at reduced confidence.
Read this before the numbers
This tool was built in a few days, on a stack of stated assumptions. I didn't have the time — or the inside knowledge of what buyers in this category actually optimize for — to be certain these are the metrics that matter most. The four categories and their weights are editorial judgment, not measurement: nobody has proven that these things cause employees to post, and I don't claim otherwise.
Where the evidence comes from: three of the four categories read only what your company has published on its own public site — the part you can fix on Monday. Half of Employee & Culture comes from somewhere else: aggregate counts of how many of your people posted in the last 90 days, from a licensed third-party index of public professional-network activity. Nothing here was scraped from LinkedIn by this tool. Those counts are records in an index, not a census — they undercount, they undercount small companies most, and you can't check them yourself — so each one says so where it appears, a zero is reported as "none in the index" and never as "nobody posts," and a company with fewer than 25 people in the index gets the number reported but not scored. No individual is named anywhere in this report.
To prioritize speed, this particular report was loaded using cached data; it was generated from evidence originally collected on August 31, 2026 rather than live. Reports are cached for 30 days. Every observation below is dated and cited.
What you can hold me to: every number cites its evidence and says where it came from, nothing unseen is guessed at, robots.txt is respected on every fetch, and when this tool can't read a site it says so instead of issuing a grade.
What was found — most fixable first
Ranked by impact × ease of fixing, not by category. Counts describe the pages actually read, and each finding cites them.
0 of 24 sampled pages carry a visible share control
None of the 24 content pages sampled (sampled from the slice of the site that could be read) carry a visible share control. Nothing on the page invites a reader — or an employee — to share it.
Evidence — content page sample
- https://www.froneri.com/en/articles/annual-report-and-financial-statements-2021/
- https://www.froneri.com/articles/annual-report-and-financial-statements-2023/
- https://www.froneri.com/en/articles/c-1/
- https://www.froneri.com/en/articles/cadbury-1/
- https://www.froneri.com/en/articles/calling-all-oreo-fans/
- https://www.froneri.com/articles/fifty-million-euros-invested-in-serbia-through-an-ice-cream-factory-in-stara-pazova/
- https://www.froneri.com/articles/france-breast-cancer-support/
- https://www.froneri.com/articles/free-the-fun-with-mango/
- … and 16 more in the sample
The fix: Add share links or buttons to the content template. Plain links to the platform share endpoints work without any tracking script.
0 of 24 sampled pages carry Article structured data
None of the 24 content pages sampled (sampled from the slice of the site that could be read) carry Article structured data. Machine readers cannot tell these pages are articles, or when they were published, or by whom.
Evidence — content page sample
- https://www.froneri.com/en/articles/annual-report-and-financial-statements-2021/
- https://www.froneri.com/articles/annual-report-and-financial-statements-2023/
- https://www.froneri.com/en/articles/c-1/
- https://www.froneri.com/en/articles/cadbury-1/
- https://www.froneri.com/en/articles/calling-all-oreo-fans/
- https://www.froneri.com/articles/fifty-million-euros-invested-in-serbia-through-an-ice-cream-factory-in-stara-pazova/
- https://www.froneri.com/articles/france-breast-cancer-support/
- https://www.froneri.com/articles/free-the-fun-with-mango/
- … and 16 more in the sample
The fix: Emit Article (or BlogPosting) JSON-LD with headline, datePublished and author in the content template.
Your careers page could not be retrieved
2 careers location(s) were tried (https://www.froneri.com/careers, https://www.froneri.com/jobs) and none returned a readable page. Candidates researching you through tools and AI assistants hit the same wall.
Evidence — careers page probes
- https://www.froneri.com/careers — HTTP 404
- https://www.froneri.com/jobs — HTTP 404
The fix: Serve a crawlable careers page at /careers and link it from the homepage.
0 of 24 sampled pages name a human author
None of the 24 sampled content pages (sampled from the slice of the site that could be read) carry a named human author — no byline, no author schema, no rel=author. Content nobody signs is content nobody feels ownership of; advocacy runs on employees being visible in the work.
Evidence: content page sample — 0 of 24 sampled pages.
The fix: Add author bylines to content pages — a name, ideally with a link or an author block in the Article schema. Start with new posts; backfilling can wait.
No structured data on your homepage
The homepage carries no JSON-LD schema.org markup. Machine readers — search engines and AI assistants alike — get no structured statement of who you are (Organization, name, logo, sameAs profiles).
Evidence: homepage HTML.
The fix: Add an Organization JSON-LD block to the homepage: name, url, logo, and sameAs links to your official social profiles.
What's already working
All tracked AI user-agents may read your site
robots.txt permits all 25 tracked AI user-agents at the site root, so AI search engines and assistants that honor robots.txt can read and cite you.
Evidence: robots.txt.
Your homepage share card is complete
The homepage carries og:title, og:description and og:image, so a shared homepage link renders a full preview card.
Evidence: homepage HTML.
What could not be seen
Anything the reader could not observe is listed here rather than guessed at or silently skipped.
The reader could not classify most of your site
Of the 520 URLs in your sitemap, 379 (72.9%) could not be sorted into content sections by the path-based classifier — the unread majority sits under paths like /mondelezicecream (232), /lotusbiscoff (75), /complaint-form (15), /complaint-form-embed (15), /brands (12), /erlenbacher-complaint-form (4). That is a limit of this tool's reading, not evidence you lack content, so no letter grade is issued and the volume-based scores below are floors, not measurements.
Evidence — sitemap URL classification
- /mondelezicecream — 232 URL(s) that could not be classified
- /lotusbiscoff — 75 URL(s) that could not be classified
- /complaint-form — 15 URL(s) that could not be classified
- /complaint-form-embed — 15 URL(s) that could not be classified
- /brands — 12 URL(s) that could not be classified
- /erlenbacher-complaint-form — 4 URL(s) that could not be classified
- /esg — 4 URL(s) that could not be classified
- /cookie-policy — 2 URL(s) that could not be classified
Content freshness is not observable here
Your sitemap carries no lastmod dates, so I cannot see how fresh your content is and have not guessed.
Evidence: sitemap lastmod analysis.
The fix: Emit real last-modified dates in the sitemap. Credible freshness data helps every machine reader — search, AI, and tools like this one — represent you accurately.
For the record
No llms.txt
No llms.txt file is served. This costs nothing today — the evidence that llms.txt affects anything is weak — so I do not count it against you.
Evidence: llms.txt fetch.
How the numbers break down
Weights: Content Supply 30% · Shareability 25% · Employee & Culture 25% (half what the site says, half what employees do) · AI Discoverability 20%. The weights are editorial judgment about what an advocacy program draws on — not the result of a study. Every row cites the observation behind it and says whether it was read from your site or from the licensed index.
Content Supply — 42.5/100 (reduced confidence)
| Signal | Points | What was observed |
|---|---|---|
| Volume floor | 18.1/40 | 105 shareable pages after collapsing localized duplicates |
| Section diversity | 14/30 | 3 shareable section(s): blog, case_study, event_webinar |
| Shareable share | 10.4/30 | 26.2% of the canonical inventory is shareable content |
Recency was not scored: this sitemap carries no lastmod dates at all. Content freshness is not observable here and has not been guessed at.
Low-coverage caveat: 379 of 520 sitemap URLs (72.9%) could not be classified, so this score describes only the 105 page(s) that could be read and section-sorted. It is a floor, not a measurement of the whole site.
Shareability — 65.6/100 (reduced confidence)
| Signal | Points | What was observed |
|---|---|---|
| Open Graph image — without one, a shared link renders as a bare grey box | 35/35 | 24 of 24 sampled pages (100%) |
| Open Graph title on the shared card | 15/15 | 24 of 24 sampled pages (100%) |
| Open Graph description on the shared card | 10.6/15 | 17 of 24 sampled pages (70.8%) |
| A visible share control on the page | 0/30 | 0 of 24 sampled pages (0%) |
| Twitter/X card tags (near-zero weight: X falls back to Open Graph) | 3/3 | 24 of 24 sampled pages (100%) |
| Canonical URL (near-zero weight: SEO hygiene, not a sharing condition) | 2/2 | 24 of 24 sampled pages (100%) |
Low-coverage caveat: 379 of 520 sitemap URLs (72.9%) could not be classified, so this score describes only the 105 page(s) that could be read and section-sorted. It is a floor, not a measurement of the whole site.
Employee & Culture — 9.9/100 (reduced confidence)
| Signal | Points | What was observed |
|---|---|---|
| What the site says (50 of 100) | ||
| Culture / life-at pages | 0/15 | 0 culture page(s) in the canonical inventory |
| Careers page reachable | 0/7.5 | No careers page could be retrieved |
| Careers depth | 5/7.5 | 5 careers URL(s) in the sitemap |
| Named authors on content | 0/12.5 | 0% of sampled pages carry a named author |
| Employee-story signals | 0/7.5 | No culture URLs existed to sample, so no employee-story signal could be checked |
| What employees do (50 of 100) | ||
| Employees posting (last 90 days) | 2.8/25 | 28 of 871 indexed employees posted in the last 90 days (3.2%). licensed third-party index (not independently verifiable); 871 of 1563 employees covered. |
| Decision-makers posting | 1.7/15 | 4 decision-makers posted in the last 90 days (0.5% of indexed employees). licensed third-party index (not independently verifiable). |
| Company page posting cadence | 0.4/10 | 5 company post(s) in the last 90 days in the index. licensed third-party index (not independently verifiable). |
A qualitative read of the careers page (boilerplate vs. real human stories) is not included in this number.
Half of this category is measured from employee posting activity in a licensed third-party index (871 of 1563 employees covered). Those counts are records in a third-party index, a lower bound the visitor cannot verify independently; the other half is what the website itself shows.
Low-coverage caveat: 379 of 520 sitemap URLs (72.9%) could not be classified, so this score describes only the 105 page(s) that could be read and section-sorted. It is a floor, not a measurement of the whole site.
AI Discoverability — 54/100
| Signal | Points | What was observed |
|---|---|---|
| AI crawler access | 45/45 | All 25 tracked AI user-agents are permitted at the site root |
| Content-Signal coherence | 9/15 | No Content-Signal declared. Neither a grant nor a restriction — scored neutrally. |
| Structured data | 0/40 | 0 schema.org type(s) on the homepage; 0% of sampled content pages carry Article schema |
| llms.txt | 0/0 | Not present. This costs nothing — the evidence that llms.txt affects anything is weak. |
robots.txt compliance is voluntary and advisory. This reports the declared policy; it is not a claim that any crawler was actually blocked.