leclercfoods.com
Evidence collected August 31, 2026 · 43 polite, robots.txt-respecting requests · every claim cites what it saw
No letter grade — withheld, not failed
No letter grade is issued because 4 of 4 categories could not be observed. The categories that were measurable are scored below.
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.
Your homepage og:image is a relative URL
The homepage declares og:image as "/wp-content/uploads/2025/08/6jh3tnp6bz_12632_LEC_Celebration_Header_Page_USA_P1B.png". The Open Graph spec requires a full URL; platforms are not required to resolve a relative path, so shares of your homepage can render without an image.
Evidence: homepage HTML.
The fix: Fix the template variable feeding og:image and make it an absolute URL to a real 1200×630 image. This is one template attribute; every future share inherits the fix.
Your job listings are invisible without JavaScript
Your careers page (https://leclercfoods.com/careers) returns HTML, but the job listings are injected client-side — a plain reader sees a page with no roles on it. Machine readers that do not execute JavaScript (many crawlers and AI assistants) cannot see that you are hiring.
Evidence — careers page probes
- https://leclercfoods.com/careers
- https://leclercfoods.com/jobs
The fix: Server-render at least the role titles and locations, or publish jobs in structured data (schema.org JobPosting).
What could not be seen
Anything the reader could not observe is listed here rather than guessed at or silently skipped.
No sitemap returned any URLs
Sitemaps were checked at 32 location(s) (declared in robots.txt or at the conventional paths) and collected zero URLs. Your content inventory is invisible to this tool — and to anything else that discovers content this way. This means "not found where sitemaps usually live", not "no content".
Evidence: sitemap fetches.
The fix: Publish an XML sitemap of your canonical content and declare it with a Sitemap: line in robots.txt.
Your robots.txt could not be read
The robots.txt endpoint did not return a usable file (HTTP 404). Crawler and AI-agent policy for this domain is unknown — unknown is not the same as open, and I have not scored it as open.
Evidence: robots.txt fetch.
The fix: Serve a plain-text robots.txt at the domain root. Even an empty or allow-all file makes your crawl policy explicit instead of undefined.
For the record
llms.txt is present
An llms.txt file is served. Reported for completeness: Google has said it does not support llms.txt, no major AI vendor has confirmed consuming it, and large-scale studies found no correlation with AI citations. I record it and weight it at zero.
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 — not scored
No sitemap URLs were retrieved, so content volume could not be measured.
Shareability — not scored
No content pages were sampled.
Employee & Culture — not scored
No sitemap URLs were retrieved.
AI Discoverability — not scored
No usable robots.txt was retrieved, so AI-agent posture is unknown for this domain. Unknown is not the same as open, and it has not been scored as open.