Industry Context — Common BS Fingerprints in Software, SaaS & Tech Products
Generic Claims:
the all-in-one platform, trusted by thousands of companies, increase productivity by X percent, save hours every week…
Red Flags:
AI claims without explaining what the AI does, customer logos without case study or testimonial evidence, no live product access or demo, SOC 2 claims without audit period or report availability…
Semantic Drift Patterns:
homepage claims AI-powered but product is rules-based, claims enterprise-grade but pricing page shows startup tiers only, homepage shows Fortune 500 logos but case studies are small businesses, claims all-in-one but integration page shows critical missing pieces…
Proof Expectations:
live product demo or free trial access, specific feature documentation with screenshots, verified customer logos with published case studies, third-party review scores on G2, Capterra, or TrustRadius…
Spatie
(https://spatie.be) 📸 Data Snapshot: May 24, 2026Analyze the raw signals below. How would a machine score this business’s credibility?
Here are the exact signals captured from up to six pages of the site — the same raw inputs the evaluation engine analyzed. They are grouped by signal type so you can weigh each the way the machine does.
🏗️ Semantic Structure — heading hierarchy & page identity (Info Density · Commodity Fingerprint)
HOMEPAGE Websites & web applications in Laravel & AI | Spatie (https://spatie.be)
Title
Websites & web applications in Laravel & AI | Spatie
Meta
Spatie builds solid websites & web applications in Laravel. With AI, we focus on solutions, not boilerplate. From Antwerp, Belgium
H1 Solid expertise in Laravel & AI
H2 Made with love
and Laravel
H2 Web development
with decades of
experience
H2 Our approach
H2 Committed
to open source
H2 Our Efforts in numbers
H2 Insights from our team and products
H2 Hire us for your next project
H2 A goodmatch?
H3 Research & Analysis
H3 Build a Strong Foundation
H3 Flexible Development
H3 Get the latest from Spatie
H3 What we do best
H3 Not our cup of tea
NAV_HEADER_HEADING_REPEATED_BODY_FOOTER Web development | Spatie (https://spatie.be/web-development/)
Title
Web development | Spatie
Meta
Tailor-made web development in Laravel for companies that value quality. Accelerated by AI, reviewed by experienced developers.
H1 Tailor-made web development
H2 Specialists who know Laravel inside out
H2 Building for
the AI era
H2 The foundations we build on
H2 A goodmatch?
H2 Hire us for your next project
H2 A goodmatch?
H3 Research & Analysis
H3 Build a Strong Foundation
H3 Flexible Development
H3 Laravel & PHP
H3 React & Livewire
H3 AI coding agents
H3 What we do best
H3 Not our cup of tea
H3 What we do best
H3 Not our cup of tea
NAV_HEADER_HEADING_REPEATED_BODY_FOOTER Committed to open source | Spatie (https://spatie.be/open-source/)
Title
Committed to open source | Spatie
Meta
At Spatie, we
H1 Committed to open source
H2 At Spatie, we're big on open source.
It's not just a way of working for us,
but part of our culture.
H2 A love story
A love story with
with laravel that
laravel that
started in 2015
H2 Our Efforts in numbers
H2 How we manage
and build open
source at spatie
H2 The balancing actof open source
H2 Contribute to
our work and
keep us going
H2 Resolve open issues
H2 Buy products & courses
H2 Get some sweet merch
H2 Hire us for your next project
H2 A goodmatch?
H3 Spatie in the wild
H3 We can't stop making them
H3 01
Make it easy to use
H3 02
Write excellent documentation
H3 03
Provide an extensive test suite
H3 04
Write readable code
H3 05
Be flexible
H3 06
Keep the scope small
H3 07
Stay up to date
H3 What we do best
H3 Not our cup of tea
NAV_HEADER_HEADING_REPEATED_BODY_FOOTER Applications and digital courses built for modern developers | Spatie (https://spatie.be/products/)
Title
Applications and digital courses built for modern developers | Spatie
Meta
Welcome in our store, by artisans for artisans. Get access to our paid products, courses and ebooks
H1 Our Products & Courses
H2 Ray
H2 Media Library Pro
H2 Mailcoach Self-Hosted
H2 Laravel Package Training v2.0
H2 Laravel Comments
H2 Laravel Beyond CRUD
H2 Testing Laravel
H2 Front Line PHP
H2 Event Sourcing in Laravel
H2 Writing Readable PHP
H2 Bundle promotions
H2 Solid Applications Bundle
H2 Modern PHP Bundle
H2 Maintainable PHP bundle
H2 Large Laravel Applications Bundle
H2 Hire us for your next project
H2 A goodmatch?
H3 What we do best
H3 Not our cup of tea
📝 The Narrative — clean text per page (Info Density · Semantic Coherence)
HOMEPAGE (https://spatie.be) Websites & web applications in Laravel & AI | Spatie
[H1] Solid expertise in Laravel & AI [H2] Made with love and Laravel We use Laravel for almost all our web development projects, and it's the foundation for many of our products too. Our own products run on the same stack we build for clients, so we know firsthand what it takes to keep software running in production. Our products & courses [IMG: Mailcoach] Email marketing platform for sending campaigns, automations and transactional emails. Available as a hosted service or a self-hosted Laravel package. Try Mailcoach for free Self-hosted [IMG: Flare] Flare lets Laravel & PHP teams keep track of everything that's happening in their apps, with error tracking, performance monitoring, and logging, all in one place. Try Flare for free [IMG: There There] A helpdesk where AI surfaces context and drafts replies, so your team responds faster and every customer gets a thoughtful answer. Apply for early access [IMG: Ray] A desktop debugging app for Laravel, PHP and JavaScript. All the speed of dump() and
1083 chars
SUB-PAGE (https://spatie.be/web-development/) Web development | Spatie
[H1] Tailor-made web development [H1] Tailor-madeweb development We're not your do-it-all digital agency, but a partner focused on building web applications with a solid foundation that can grow alongside your needs. [IMG: The Spatie team] [H2] Specialists who know Laravel inside out By asking the right questions first, we make thoughtful architecture decisions, and ship clean code your team can maintain and extend long after launch. Over time, we have created a collection of open source building blocks that allow us to focus all our time and effort on making your project unique, rather than on the scaffolding. And with our experiences in building with AI, we can ship faster, iterate more quickly, and develop more prototypes that can validate your ideas. Brief us your project 01 [H3] Research & Analysis Know we dig into your domain before touching any code. We accommodate new projects and legacy applications bursting out of its seams. 02 [H3] Build a Strong Foundation A Laravel codebase built for the long haul: clear structure, automated tests, and sensible abstractions that don't fight you when requirements change. 03 [H3] Flexible Development We work in short cycles with frequent check-ins. Priorities can shift, but our process is designed for it, so you always get the most valuable thing next. [H2] Building for the AI era AI has genuinely changed how we build. Coding agents like Claude Code, Codex, and Copilot do a serious chunk of the work for us now. They scaffold features, write tests, work through refactors, and handle the kind of repetitive tasks that used to eat half a developer's week. What we used to spend on boilerplate, we now spend on architecture, edge cases, and the parts of your product that actually need careful thinking. None of it ships without a human in front of it. Every result goes through a senior Laravel developer, who reviews it as carefully as they'd review a colleague's pull request. We catch what the agent got wrong, sharpen what's clumsy, and make sure the pieces fit together. The outcome is more software, shipped faster, without the technical debt that usually comes with moving at this speed. [H2] The foundations we build on [H3] Laravel & PHP Laravel is our framework of choice for everything from marketing sites to complex platforms. It's a battle-tested foundation that keeps codebases clean, maintainable, and easy to hand off as projects grow. [H3] React & Livewire We match the frontend tool to the level of interactivity a project needs. Livewire handles reactive interfaces within Laravel, while React takes over for full SPA and mobile-first applications. [H3] AI coding agents We use AI to generate code throughout the whole development cycle: features, tests, debugging and refactoring. Our coding guidelines make sure the output matches our standards and your project. Laravel [IMG: Laravel] React [IMG: React] Livewire [IMG: Livewire] Claude Code [IMG: Claude Code] ClickHouse [IMG: ClickHouse] Statamic [IMG: Statamic] [H2] A goodmatch? [H3] What we do best All things Laravel Custom frontend components Building APIs AI-powered features Simplifying things Clean solutions Integrating services [H3] Not our cup of tea WordPress themes Cutting corners Free mockups to win a job "Just execute the briefing" In short: we'd like to be a substantial part of your project. Get in touch via email
3614 chars
SUB-PAGE (https://spatie.be/open-source/) Committed to open source | Spatie
[H1] Committed to open source spatie.be/open-source [H2] A love story A love story with with laravel that laravel that started in 2015 Back in 2015 when we first began developing open source packages and tools for Laravel and PHP, we couldn't have imagined the overwhelming support and feedback we'd receive from the community. Over the years, we've launched numerous packages and courses, and have actively engaged in delivering presentations across the globe. We have been fortunate that working with the Laravel community brought us many opportunities to collaborate with developers from around the world, and expand our own skills and services. [H2] Our Efforts in numbers 537 Packages Released& maintained 2.48B+ Total downloadson packagist 1,000+ Contributorson Github [H2] How we manage and build open source at spatie Being able to spend enough time on our open source efforts while also building applications for our clients can be challenging. Laravel is what ties everything together. We use Laravel for almost all our web development projects, and it's the foundation for many of our paid products too. We have a few rules in place to make sure our open source work meets the same high quality as our products and client work. [H2] The balancing actof open source [H3] 01 Make it easy to use We have put a lot of effort into making our packages as user-friendly as possible. Ultimately, a package should be fun to use. [H3] 02 Write excellent documentation We invest time in creating excellent documentation for each of our packages. This makes it easy to discover what a package does and what all the features are. [H3] 03 Provide an extensive test suite All of our packages have an extensive test suite. This provides you (and us) with proof that the package code behaves correctly and works under all conditions. [H3] 04 Write readable code We structure and write our code in such a way that others can easily understand what is going on. Names of variables, functions and classes are chosen with care. You should be able to understand how the package works just by reading the code. [H3] 05 Be flexible We know we can't imagine every scenario our code will be used in. That's why we make our packages as customizable and extensible as possible. We don't use the final keyword, and make everything protected by default instead of private. Our code is structured in small functions and classes that can be overwritten or extended. [H3] 06 Keep the scope small When creating a package we intentionally keep the scope small. In most cases, packages are created to be consumed in our projects. We would rather have a small package with one very polished feature, than a large package that tries to cover all possible edge cases and variations of a problem. [H3] 07 Stay up to date When a new PHP or Laravel version comes out, our team spends time to make sure the test suite is running correctly and that a new package version is tagged. Usually, all of our Laravel packages are compatible with the major releases of the Laravel framework within a few days. [H2] Contribute to our work and keep us going Community is what makes open source work worthwhile. Without the hundreds of people who use, test, and contribute to our packages, they wouldn't be as successful as they are today. If you want to get involved in our open source work or help us in other ways, here are the best ways to do that. 01 [H2] Resolve open issues Open issues across our packages and repositories are open to anyone to tackle, including you. We welcome contributions, but follow the contribution guidelines from each project on how to submit issues or pull requests correctly. 02 [H2] Buy products & courses We create paid software and courses that you can purchase to support us directly. In return, you gain access to productive tools to help you improve your workflow or learn valuable skills! 03 [H2] Get some sweet merch Show your love for Spatie with our official merchandise. T-shirts, mugs, hoodies, stickers, and more.
4196 chars
SUB-PAGE (https://spatie.be/products/) Applications and digital courses built for modern developers | Spatie
[H1] Our Products & Courses [IMG: Ray Products Teaser] [H2] Ray Debug without breaking your flow [IMG: spatie-product] [H2] Media Library Pro UI components for laravel-medialibrary [IMG: Mailcoach Teaser] [H2] Mailcoach Self-Hosted Email marketing you host yourself. Mailcoach Self-Hosted is a powerful email platform for email marketing, automations and transactional emails, seamlessly integrated into your Laravel application. [IMG: packagetraining_product_TIMG] [H2] Laravel Package Training v2.0 Learn how to create a Laravel package and become the next package maestro [IMG: laravel-comments] [H2] Laravel Comments A beautiful Livewire component to associate comments with models [IMG: laravel-beyond-crud] [H2] Laravel Beyond CRUD Learn how to build larger-than-average Laravel applications and maintain them for years to come. [IMG: product_testing_2_TIMG] [H2] Testing Laravel Learn how to automatically test your Laravel app using PHPUnit and Pest [IMG: Thumb] [H2] Front Line PHP An ebook on cutting edge tactics in PHP 8.3, accompanied by videos and practical examples. [IMG: event-sourcing] [H2] Event Sourcing in Laravel A hands-on course to start using event sourcing in large apps [IMG: writing-readable-php] [H2] Writing Readable PHP Learn how to write PHP that is a joy to read and easy to understand [H2] Bundle promotions [IMG: bundle_testing_beyond] [H2] Solid Applications Bundle Get both Testing Laravel and Laravel Beyond CRUD with a 20% discount! [IMG: Bundle] [H2] Modern PHP Bundle Get both Writing Readable PHP and Front Line PHP with a 20% discount! [IMG: bundle-testing-laravel] [H2] Maintainable PHP bundle Get both Writing Readable PHP and Testing Laravel with a 20% discount! [IMG: bundles] [H2] Large Laravel Applications Bundle Get both Laravel Beyond CRUD and Event Sourcing in Laravel with a 20% discount!
1980 chars
🛡️ Trust Signals — reviews, proof links, trust-theatre flag (Trust & Proof)
13Review mentions (all pages)
0External proof links (all pages)
| Page | Reviews | Proof links |
|---|---|---|
| / (home) | 2 | 0 |
| /web-development/ | 7 | 0 |
| /open-source/ | 2 | 0 |
| /products/ | 2 | 0 |
🔗 Identity & Technical Layer — schema JSON-LD: identity chains, entity gaps (Identity & Authority)
Homepage schema
[
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Spatie",
"url": "https://spatie.be/",
"description": "Spatie is a digital allrounder: we design solid websites & web applications using Laravel & Vue. No frills, just proven expertise. From Antwerp, Belgium",
"potentialAction": {
"@type": "SearchAction",
"target": "https://spatie.be/?s={search_term_string}",
"query-input": "required name=search_term_string"
},
"image": "https://spatie.be/images/og-image.jpg",
"sameAs": [
"https://twitter.com/spatiec",
"https://www.linkedin.com/company/spatie"
],
"publisher": {
"@type": "Organization",
"name": "Spatie",
"url": "https://spatie.be/",
"logo": {
"@type": "ImageObject",
"url": "https://spatie.be/logo.png"
}
}
},
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Spatie",
"email": "info@spatie.be",
"telephone": "+32 3 292 56 79",
"vatID": "BE0809.387.596",
"url": [
"https://spatie.be",
"https://twitter.com/spatie_be"
],
"image": "https://spatie.be/images/og-image.jpg",
"address": {
"@type": "PostalAddress",
"addressLocality": "Antwerp",
"addressRegion": "Antwerp",
"postalCode": "2060",
"streetAddress": "Kruikstraat 22 bus 12",
"addressCountry": "Belgium"
},
"founders": [
{
"@type": "Person",
"name": "Freek Van der Herten",
"jobTitle": "Backend developer",
"url": [
"https://freek.dev",
"https://twitter.com/freekmurze"
]
},
{
"@type": "Person",
"name": "Jef Van der Voort",
"jobTitle": "Account manager",
"url": [
"https://twitter.com/vdv_jef"
],
"email": "jef@spatie.be"
}
],
"employees": [
{
"@type": "Person",
"name": "Alex Vanderbist",
"jobTitle": "Backend developer",
"url": [
"https://alexvanderbist.com",
"https://twitter.com/alex_"
]
},
{
"@type": "Person",
"name": "Sebastian De Deyne",
"jobTitle": "Full stack developer",
"url": [
"https://sebastiandedeyne.com",
"https://twitter.com/sebdedeyne"
]
},
{
"@type": "Person",
"name": "Ruben Van Assche",
"jobTitle": "Backend developer",
"url": [
"https://rubenvanassche.com",
"https://twitter.com/rubenvanassche"
]
},
{
"@type": "Person",
"name": "Tim Van Dijck",
"jobTitle": "Full stack developer",
"url": [
"https://veedee.dev",
"https://twitter.com/timvandijck"
]
},
{
"@type": "Person",
"name": "Jimi Robaer",
"jobTitle": "Designer",
"url": [
"https://jimirobaer.be",
"https://twitter.com/jimirobaer"
]
},
{
"@type": "Person",
"name": "Sébastien Henau",
"jobTitle": "Frontend developer",
"url": [
"https://sebastienhenau.com"
]
},
{
"@type": "Person",
"name": "Zuzana Kunckova",
"jobTitle": "Support engineer",
"url": [
"https://www.zuzana-k.com",
"https://twitter.com/zuzana_kunckova"
]
},
{
"@type": "Person",
"name": "Nick Bevers",
"jobTitle": "Frontend developer",
"url": [
"https://nickbevers.dev"
]
},
{
"@type": "Person",
"name": "Dries Heyninck",
"jobTitle": "Frontend developer",
"url": []
},
{
"@type": "Person",
"name": "Marceli Wilczynski",
"jobTitle": "Backend developer",
"url": []
},
{
"@type": "Person",
"name": "Nick Denys",
"jobTitle": "Backend developer",
"url": [
"https://nickdenys.com"
]
}
]
}
]
/web-development/
[
{
"@context": "https://schema.org",
"@type": "WebPage",
"name": "Web development",
"url": "https://spatie.be/web-development",
"description": "Tailor-made web development is what we do best. Read about our strengths, our thoughtful process and our beloved clients.",
"image": "https://spatie.be/images/og-image.jpg",
"mainEntity": {
"@type": "Organization",
"name": "Spatie",
"sameAs": [
"https://spatie.be"
]
}
},
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Spatie",
"email": "info@spatie.be",
"telephone": "+32 3 292 56 79",
"vatID": "BE0809.387.596",
"url": [
"https://spatie.be",
"https://twitter.com/spatie_be"
],
"image": "https://spatie.be/images/og-image.jpg",
"address": {
"@type": "PostalAddress",
"addressLocality": "Antwerp",
"addressRegion": "Antwerp",
"postalCode": "2060",
"streetAddress": "Kruikstraat 22 bus 12",
"addressCountry": "Belgium"
},
"founders": [
{
"@type": "Person",
"name": "Freek Van der Herten",
"jobTitle": "Backend developer",
"url": [
"https://freek.dev",
"https://twitter.com/freekmurze"
]
},
{
"@type": "Person",
"name": "Jef Van der Voort",
"jobTitle": "Account manager",
"url": [
"https://twitter.com/vdv_jef"
],
"email": "jef@spatie.be"
}
],
"employees": [
{
"@type": "Person",
"name": "Alex Vanderbist",
"jobTitle": "Backend developer",
"url": [
"https://alexvanderbist.com",
"https://twitter.com/alex_"
]
},
{
"@type": "Person",
"name": "Sebastian De Deyne",
"jobTitle": "Full stack developer",
"url": [
"https://sebastiandedeyne.com",
"https://twitter.com/sebdedeyne"
]
},
{
"@type": "Person",
"name": "Ruben Van Assche",
"jobTitle": "Backend developer",
"url": [
"https://rubenvanassche.com",
"https://twitter.com/rubenvanassche"
]
},
{
"@type": "Person",
"name": "Tim Van Dijck",
"jobTitle": "Full stack developer",
"url": [
"https://veedee.dev",
"https://twitter.com/timvandijck"
]
},
{
"@type": "Person",
"name": "Jimi Robaer",
"jobTitle": "Designer",
"url": [
"https://jimirobaer.be",
"https://twitter.com/jimirobaer"
]
},
{
"@type": "Person",
"name": "Sébastien Henau",
"jobTitle": "Frontend developer",
"url": [
"https://sebastienhenau.com"
]
},
{
"@type": "Person",
"name": "Zuzana Kunckova",
"jobTitle": "Support engineer",
"url": [
"https://www.zuzana-k.com",
"https://twitter.com/zuzana_kunckova"
]
},
{
"@type": "Person",
"name": "Nick Bevers",
"jobTitle": "Frontend developer",
"url": [
"https://nickbevers.dev"
]
},
{
"@type": "Person",
"name": "Dries Heyninck",
"jobTitle": "Frontend developer",
"url": []
},
{
"@type": "Person",
"name": "Marceli Wilczynski",
"jobTitle": "Backend developer",
"url": []
},
{
"@type": "Person",
"name": "Nick Denys",
"jobTitle": "Backend developer",
"url": [
"https://nickdenys.com"
]
}
]
}
]
/open-source/
[
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Spatie",
"url": "https://spatie.be/open-source",
"description": "At Spatie, we’re big on open source. It’s not just a way of working for us, it's part of our culture.",
"image": "https://spatie.be/images/og-image-oss.png",
"sameAs": [
"https://cloud.typography.com",
"https://pro.fontawesome.com"
],
"potentialAction": {
"@type": "ReadAction",
"target": [
"https://spatie.be/open-source"
]
},
"alternateName": "Committed to open source"
},
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Spatie",
"email": "info@spatie.be",
"telephone": "+32 3 292 56 79",
"vatID": "BE0809.387.596",
"url": [
"https://spatie.be",
"https://twitter.com/spatie_be"
],
"image": "https://spatie.be/images/og-image.jpg",
"address": {
"@type": "PostalAddress",
"addressLocality": "Antwerp",
"addressRegion": "Antwerp",
"postalCode": "2060",
"streetAddress": "Kruikstraat 22 bus 12",
"addressCountry": "Belgium"
},
"founders": [
{
"@type": "Person",
"name": "Freek Van der Herten",
"jobTitle": "Backend developer",
"url": [
"https://freek.dev",
"https://twitter.com/freekmurze"
]
},
{
"@type": "Person",
"name": "Jef Van der Voort",
"jobTitle": "Account manager",
"url": [
"https://twitter.com/vdv_jef"
],
"email": "jef@spatie.be"
}
],
"employees": [
{
"@type": "Person",
"name": "Alex Vanderbist",
"jobTitle": "Backend developer",
"url": [
"https://alexvanderbist.com",
"https://twitter.com/alex_"
]
},
{
"@type": "Person",
"name": "Sebastian De Deyne",
"jobTitle": "Full stack developer",
"url": [
"https://sebastiandedeyne.com",
"https://twitter.com/sebdedeyne"
]
},
{
"@type": "Person",
"name": "Ruben Van Assche",
"jobTitle": "Backend developer",
"url": [
"https://rubenvanassche.com",
"https://twitter.com/rubenvanassche"
]
},
{
"@type": "Person",
"name": "Tim Van Dijck",
"jobTitle": "Full stack developer",
"url": [
"https://veedee.dev",
"https://twitter.com/timvandijck"
]
},
{
"@type": "Person",
"name": "Jimi Robaer",
"jobTitle": "Designer",
"url": [
"https://jimirobaer.be",
"https://twitter.com/jimirobaer"
]
},
{
"@type": "Person",
"name": "Sébastien Henau",
"jobTitle": "Frontend developer",
"url": [
"https://sebastienhenau.com"
]
},
{
"@type": "Person",
"name": "Zuzana Kunckova",
"jobTitle": "Support engineer",
"url": [
"https://www.zuzana-k.com",
"https://twitter.com/zuzana_kunckova"
]
},
{
"@type": "Person",
"name": "Nick Bevers",
"jobTitle": "Frontend developer",
"url": [
"https://nickbevers.dev"
]
},
{
"@type": "Person",
"name": "Dries Heyninck",
"jobTitle": "Frontend developer",
"url": []
},
{
"@type": "Person",
"name": "Marceli Wilczynski",
"jobTitle": "Backend developer",
"url": []
},
{
"@type": "Person",
"name": "Nick Denys",
"jobTitle": "Backend developer",
"url": [
"https://nickdenys.com"
]
}
]
}
]
/products/
[
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Spatie",
"url": "https://spatie.be/products",
"description": "Welcome in our store, by artisans for artisans. Get access to our paid products, courses and ebooks.",
"image": "https://spatie.be/images/og-store.png",
"potentialAction": {
"@type": "SearchAction",
"target": "https://spatie.be/products?q={search_term_string}",
"query-input": "required name=search_term_string"
},
"sameAs": [
"https://twitter.com/spatie_be",
"https://github.com/spatie"
],
"additionalType": "http://www.productontology.org/id/Software"
},
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Spatie",
"email": "info@spatie.be",
"telephone": "+32 3 292 56 79",
"vatID": "BE0809.387.596",
"url": [
"https://spatie.be",
"https://twitter.com/spatie_be"
],
"image": "https://spatie.be/images/og-image.jpg",
"address": {
"@type": "PostalAddress",
"addressLocality": "Antwerp",
"addressRegion": "Antwerp",
"postalCode": "2060",
"streetAddress": "Kruikstraat 22 bus 12",
"addressCountry": "Belgium"
},
"founders": [
{
"@type": "Person",
"name": "Freek Van der Herten",
"jobTitle": "Backend developer",
"url": [
"https://freek.dev",
"https://twitter.com/freekmurze"
]
},
{
"@type": "Person",
"name": "Jef Van der Voort",
"jobTitle": "Account manager",
"url": [
"https://twitter.com/vdv_jef"
],
"email": "jef@spatie.be"
}
],
"employees": [
{
"@type": "Person",
"name": "Alex Vanderbist",
"jobTitle": "Backend developer",
"url": [
"https://alexvanderbist.com",
"https://twitter.com/alex_"
]
},
{
"@type": "Person",
"name": "Sebastian De Deyne",
"jobTitle": "Full stack developer",
"url": [
"https://sebastiandedeyne.com",
"https://twitter.com/sebdedeyne"
]
},
{
"@type": "Person",
"name": "Ruben Van Assche",
"jobTitle": "Backend developer",
"url": [
"https://rubenvanassche.com",
"https://twitter.com/rubenvanassche"
]
},
{
"@type": "Person",
"name": "Tim Van Dijck",
"jobTitle": "Full stack developer",
"url": [
"https://veedee.dev",
"https://twitter.com/timvandijck"
]
},
{
"@type": "Person",
"name": "Jimi Robaer",
"jobTitle": "Designer",
"url": [
"https://jimirobaer.be",
"https://twitter.com/jimirobaer"
]
},
{
"@type": "Person",
"name": "Sébastien Henau",
"jobTitle": "Frontend developer",
"url": [
"https://sebastienhenau.com"
]
},
{
"@type": "Person",
"name": "Zuzana Kunckova",
"jobTitle": "Support engineer",
"url": [
"https://www.zuzana-k.com",
"https://twitter.com/zuzana_kunckova"
]
},
{
"@type": "Person",
"name": "Nick Bevers",
"jobTitle": "Frontend developer",
"url": [
"https://nickbevers.dev"
]
},
{
"@type": "Person",
"name": "Dries Heyninck",
"jobTitle": "Frontend developer",
"url": []
},
{
"@type": "Person",
"name": "Marceli Wilczynski",
"jobTitle": "Backend developer",
"url": []
},
{
"@type": "Person",
"name": "Nick Denys",
"jobTitle": "Backend developer",
"url": [
"https://nickdenys.com"
]
}
]
}
]
Your Diagnosis
Before revealing the machine’s verdict, predict the BS score for each signal. Higher = more BS (more fluff, less verifiable substance). Drag each slider, then submit to compare your judgment against the engine.
Information Density
0 / 30
Read the Narrative & headings: do hard facts (prices, dates, numbers) outweigh fluff power-words?
Semantic Coherence
0 / 20
Compare the homepage promise against the sub-page reality. Do they hold the same line?
Trust & Proof
0 / 20
Weigh review mentions against actual external proof links. Claims without verification = theatre.
Commodity Fingerprint
0 / 15
Check headings & narrative against the industry clichés in the setup above.
Identity & Authority
0 / 15
Inspect the schema: is there real Organization/Person identity with sameAs links, or gaps?
Your predicted BS score
0 / 100
Stuck? Reveal the heuristic lens — how the deterministic page-auditor reads each signal (no AI, pure pattern rules)
These are the structural rules a local, deterministic auditor applies — the same lens you can use to judge each signal. They describe what to look for, not this company’s result.
Information Density
Classify each sentence as substantive or hollow. Grounding markers — numbers, currencies, dates, technical units, named entities — outweigh marketing adjectives. When fluff sits right next to hard evidence, the fluff is forgiven.
Semantic Alignment
Pull the main entities out of the H1, then check whether they actually recur through the body. A page that announces one thing and then talks about another drifts. Headings with no real sentences underneath read as pseudo-substance.
Trust & Proof
Count trust words (review, testimonial, rating, verified) against real outbound proof links (Google, Trustpilot, Clutch, G2, Yelp). Lots of trust language with zero verification links is trust theatre. Unlinked logo galleries count against it.
Commodity Fingerprint
Look at how much sentence length varies. Natural writing varies its rhythm; templated or mass-produced copy is statistically uniform. Very low variation reads as commodity content — unless unique named entities break the pattern.
Identity & Authority
Inspect the JSON-LD. Is there an Organization or Person schema, and does it carry sameAs links to real external profiles (LinkedIn, socials)? Missing schema or no identity declaration signals an anonymous entity.
Want to apply this lens yourself? The free BS Indicator Chrome extension runs these heuristic checks live on any page. Bear in mind it is a single-page, deterministic tool — it relies only on pattern rules for the page in front of it and does not perform the cross-page semantic correlation this audit uses, so its readout is a starting lens, not the full verdict.
B
BS Level
Software, SaaS & Tech Products
33.1 Avg BS
Based on 1128 businesses audited.
✓ Less BS than average
Spatie has 20.1 points less BS than the average for Software, SaaS & Tech Products.
BS Detector
Software, SaaS & Tech Products BS: Spatie (spatie.be)
https://spatie.be
📍 Industry: Software, SaaS & Tech Products
13
BS / 100
Spatie is a high-substance anomaly that operates with maximum transparency and technical specificity. The BS score is essentially a forensic technicality due to unlinked review counts rather than actual fluff or deception. It is an industry-leading example of positioning via authority and open-source contribution.
Info Density
Power-words vs. Substance ratio.
3
10% BS
Semantic Coherence
Homepage promise vs. Sub-page reality.
0
0% BS
Trust & Proof
Verifiable evidence vs. Trust Theatre.
8
40% BS
Commodity Fingerprint
Detection of industry clichés/templates.
2
13% BS
Identity & Authority
Expert verifiability & Schema depth.
0
0% BS
To minimize the remaining BS score, the site should include direct outbound links to Packagist and GitHub within the Efforts in numbers section to convert claims into linked proof points. Testimonials should be linked to third-party platforms like G2 or Clutch to clear the trust theatre forensic flag. Finally, updating the Front Line PHP product description to reference the current PHP 9 or 10 standards as of May 2026 would eliminate the minor aging-evidence penalty for the PHP 8.3 reference.
The website perfectly aligns with the Software, SaaS & Tech Products industry. The content is deeply technical, focusing on the Laravel/PHP ecosystem, developer tools, and open-source contributions, which confirms its classification as a specialist technical agency and product house.
“The score of 13 is primarily driven by the Step 3 trust_theatre forensic trigger, where reviews are counted without direct verification links in the provided data. Minimal points were added for minor repetition of value propositions and the use of a cross-page template for the 'Good match' section. The site performed perfectly in semantic coherence and identity authority pillars.”
Verified Analysis Date: May 24, 2026
© 1EuroSEO Independent Evaluator — Non-Sponsored Result
Analysis Disclosure & Source Attribution
This training module utilizes a snapshot of public data from Spatie, captured on May 24, 2026, to demonstrate how machine logic evaluates different types of business narratives.
Purpose: This data is presented under “Fair Use” / “Educational Exception” for the purpose of forensic semantic analysis, allowing users to compare human intuition against machine-generated evaluations.
Notice to Spatie: This analysis is part of a non-adversarial audit conducted by 1 Euro SEO. The results provided by 1EuroSEO are intended as professional feedback to help improve any website’s machine-readability and authority signals. The 1EuroSEO BS Detection Tool is a free tool, and anyone can test any company to see how their content is interpreted by AI models.
Any company can use the insights for free and improve its voice by comparing it to industry clichés or competitors. When a company has updated its content, it can always submit a new audit request, which will be reflected in a new current score.
To all users: You are encouraged to visit the live site at https://spatie.be to view the most current version of its content and learn from the source what this company is about and what it offers.