Agent view · Findings · 2026-11-18
"20 years of experience": the site's own records said 13
This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/a-site-said-20-years-of-experience-its-own-records-said-13: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.
| status | 200 |
|---|---|
| content-type | text/markdown; charset=utf-8 |
| vary | Accept |
| link | <https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/blog/a-site-said-20-years-of-experience-its-own-records-said-13>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory" |
| cache-control | public, max-age=900, stale-while-revalidate=2400 |
| bytes | 12,712 |
| words | 1,895 |
| sha-256 | ec6589295fd77c1429d79ac328becf54f05d353816b7db747a8d3c1f713fa26b |
| repr-digest | sha-256=:7GWJKV/XfBQp15rDKL7PVPBdNTgWt9t0eo08H3E/oms=: ← matches the body shown |
| signature-input | sig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795182387;expires=1795185987;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="m3hJBXRGiciSvQFZ4N8w3g";tag="crawlcheck-page" |
| signature | sig1=:k1xQ1Xal/XwU5217gEuTfyqK9/d0MfHS5UGEBpX8idpEjrURKCsQlxsWJrwCtnROBWsn0E3zOhkS/RFarmtyAA==: |
| verified | yes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba |
Findings · 2026-11-18 · By [VSNARY | Emmanuel Orta](/author)
# "20 years of experience": the site's own records said 13
A concrete contractor's site said 20 years. Its Google Business Profile said it opened in 2013. The number was in more places than anyone remembered.
A concrete contractor site we run said "20 Years of Experience". The business's own Google Business Profile gives an opening date of March 2013, which makes it 13. Fixing the home page was not enough: the same claim sat on five more pages as a sentence, as the phrase "two decades" and as a "20+" counter. All 52 pages are now checked, and the number is calculated from the opening date so it cannot go stale.
On this page
- The claim and the record
- Why a wrong number matters more now
- Fixing the home page fixed one page of six
- The fix that stays fixed
- Check your own site in ten minutes
- What this does not show
## The claim and the record #
The home page of a concrete contractor site we run carried a headline number: 20 Years of Experience. The same business has a [Google Business Profile](/glossary/google-business-profile), and that profile states the day it opened: 8 March 2013.
2013 to 2026 is 13 years. The site and the business's own public record disagreed by seven.
Nobody set out to mislead. The number came with a site template years ago and was never checked against anything. That is how most of these get there.
## Why a wrong number matters more now #
A person reading the page has no easy way to check "20 years". Software does. A search engine or an AI assistant can read the page, read the business profile, and see two different answers to the same question. When a site's facts disagree with each other, there is less reason to repeat any of them.
We have not measured a ranking change from this fix, and we are not claiming one. What changed is that the page, the profile and the site's [structured data](/glossary/structured-data) now state one fact instead of two.
## Fixing the home page fixed one page of six #
The first correction changed the home page. A check of the rest of the site the same evening found the claim was still live in five more places, and not always in the same words:
| Where | How it was written |
| --- | --- |
| Home page | "20 Years of Experience" and "has 20 years" |
| About page | 20 years |
| Three city pages | 20 years, or "two decades" |
| One service page | 20 years |
| City pages, a separate counter | "20+" above the words Years Experience |
A search for "20 years" would have missed "two decades". A search of the text would have missed the counter, which is a number in one element and a label in another. We ended up reading all 52 pages in the sitemap. None carries a 20-year claim now.
## The fix that stays fixed #
Replacing 20 with 13 would be wrong again next March. The number on the site is now calculated from the opening date, so it moves up by itself each year. The same date is published in the site's structured data as the founding date, which is where software looks for it.
| Source | Before | After |
| --- | --- | --- |
| Google Business Profile opening date | March 2013 | March 2013 |
| Pages claiming 20 years | 6 | 0 |
| Years shown on the site | 20 | 13, calculated from the date |
| Founding date in structured data | not stated | 2013-03-08 |
## Check your own site in ten minutes #
- Open your Google Business Profile and note the opening date. That is the date the public can already see.
- Search your site for every way the claim could be written: the number, the number with a plus sign, the words ("two decades"), and "since" followed by a year.
- Look at counters and badges separately. They are often images or split across elements, and a text search will not find them.
- Check city and service pages, not only the home page. Copied pages copy the claim.
- If the people doing the work have more years than the company, say whose years they are: "our lead installer has 20 years in concrete" is a different and checkable claim.
The same habit applies to a phone number or an address that appears in more than one place. We covered that in the [name, address and phone consistency guide](/guides/nap-consistency-audit-phone-address-and-coordinates).
## What this does not show #
- That the profile date is the first day anyone at the business poured concrete. It is the date the business gives for itself, and it is the one a machine can read.
- Any effect on rankings or calls. One site, one fact, corrected. No before-and-after traffic claim.
*Published by CrawlCheck. The site is run by the person who builds CrawlCheck.*
CrawlCheck’s dataset when this page loaded: 570,959 sites measured.
Written by
[Emmanuel Orta](/author) · VSNARY
I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post.
[Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta)
Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fa-site-said-20-years-of-experience-its-own-records-said-13%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fa-site-said-20-years-of-experience-its-own-records-said-13%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=%2220%20years%20of%20experience%22%3A%20the%20site)[Email](mailto:?subject=%2220%20years%20of%20experience%22%3A%20the%20site)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)
## Questions this post answers
### Where does the opening date on a Google Business Profile come from?
The business enters it. It is shown publicly on the profile, which makes it the easiest date for anyone, or any software, to compare with the website.
### Is it wrong to say 20 years if the owner has 20 years of experience?
No, if that is what the sentence says. "The owner has 20 years in the trade" is one claim; "20 years in business" is another. Say whose years they are.
### Why not just change 20 to 13?
It would be wrong again within a year. Calculating the number from the opening date keeps it right without anyone remembering to edit it.
### How did the claim survive the first fix?
It was written three ways: as a number in a sentence, as the words "two decades", and as a counter split across two elements. Only reading every page found them all.
### Did fixing it improve rankings?
We have not measured that and do not claim it. The fix removes a contradiction between the site and the business's own public record.
## Related findings
[2026-10-09 Does Data Axle feed Google? Where business data comes from Google reads your site, Business Profile, customers and its own checks. No engine documents Data Axle as a source, and its listing](/blog/where-google-and-ai-assistants-get-business-data)[2026-08-13 Email bounce case study: one typo, every address dead One typo in a contact email domain made every message to a business bounce, and nothing flagged it. The two DNS lookups that prove](/blog/one-character-of-undeliverable-email)[2026-10-14 Sitemap lastmod: 103 pages, one date, why engines skip it 103 pages in our sitemap shared one lastmod though most had been rebuilt. Why Google and Bing ignore dates like that, and how to d](/blog/sitemap-lastmod-103-pages-one-date-why-engines-ignore-it)
The main product
Found this on your own site? **We fix it for $100.**
Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.
[Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v)
[What it covers](/pricing#fix) · [scan first, it is free](/)
Free browser extension
Check this on any site you open, **without leaving the page.**
CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.
[Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post)
[What it does](/extension)
Write for the library
Measured something yourself? **Submit an article.**
Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.
[Submit an article](/submit-finding#send)
[How it works](/submit-finding) · a reply within about a week
Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections).
## Comments
Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*.
Send for review
Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan.
[All findings](/blog) · [The dataset](/data) · [How the dataset works](/policy)
We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io)
#### How we measure, and our own machine files
CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io).
**Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing.
**Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours.
**Pages:** [/](/) · [Listing check](/listing-check) · [SDK](/sdk) · [Certificates](/certificates) · [TLS posture](/data/tls-posture) | **Registry:** [wahidmart.com](/registry/wahidmart.com) · [Place: Daytona beach](/registry/place/fl/daytona-beach) | **Datasets:** [Nebraska](/datasets/state/nebraska) · [Technologies: Elementor](/datasets/technologies/elementor) | **Blog:** [AI picked a local contractor 422 times: rating decided it](/blog/ai-picked-a-local-contractor-422-times-the-rating-decided-it) | **AI crawlers:** [Cloudflare AI search external](/ai-crawlers/cloudflare-ai-search-external) | **Glossary:** [AI classifiers: Scoring](/glossary/ai-classifiers/scoring)
[Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)
Same body as a file: /blog/a-site-said-20-years-of-experience-its-own-records-said-13.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.