Technical eligibility comes before visibility outcomes. This report focuses on Layer 1: hard public technical checks that can expose eligibility risks before rankings, traffic or AI citation outcomes are evaluated.
What was measured
The object of the study was public websites of HVACR companies in European Union countries. HVACR includes companies connected with heating, ventilation, air conditioning and refrigeration: manufacturers, engineering firms, installers, service companies, distributors and suppliers of HVACR solutions.
The geographic scope was limited to the 27 EU countries. The United Kingdom, Norway, candidate countries and non-EU markets were not part of the core sample.
The research was designed as a technical eligibility benchmark. Every website was checked against the same set of technical rules. The study did not assign scores, create an AI readiness index or rank companies.
Methodology in brief
The final sample contained 1,353 public HVACR company websites across 27 EU countries. Country targets were assigned proportionally to population using a transparent allocation rule of three HVACR websites per one million inhabitants. This allocation rule supports EU-wide coverage, but should not be interpreted as statistical representativeness for each national HVACR market.
Each site was checked for HVACR relevance, working public web presence and company signals before inclusion. The measurement used public access only: no login, no CAPTCHA bypassing, no crawler impersonation, no private Search Console data and no private analytics data.
Methodology flow
From source discovery to aggregate analysis
- 01Source discovery→
- 02HVACR relevance validation→
- 03Company signal validation→
- 04Country allocation→
- 05Public technical checks→
- 06QC matrix→
- 07Aggregate analysis
1,353 websites · 27 EU countries · 8 technical metrics · 10,824 metric cells · 0 unknown / missing values
Public access only: no login, no CAPTCHA bypassing, no crawler impersonation, no private Search Console or analytics data.
Eligibility pipeline
Technical eligibility layers measured before visibility outcomes
- 01Discovery→
- 02Crawl access→
- 03Fetch / HTTP→
- 04Render→
- 05Indexing eligibility→
- 06Snippet preview eligibility→
- 07Language routing
This pipeline describes technical eligibility layers, not ranking or AI citation outcomes.
Key findings
The most common hard technical blocker in the measured sample was snippet preview blocking. It appeared on 117 websites, or 8.65% of the final sample.
Noindex on key pages appeared on 65 websites, or 4.80%. Language-routing risk conditions appeared on 63 of 365 applicable multilingual sites, or 17.26% of that applicable subset. Internal discoverability risk conditions appeared on 62 websites, or 4.58%.
These are eligibility risks, not visibility outcomes. The full metric-level results are shown in the table and chart below.
Overall results
Metric results across the measured sample
| Metric | Stage | Yes | No | Not applicable | No, % of total sample | Applicable subset note |
|---|---|---|---|---|---|---|
| Crawler accessHard blocker | Crawl access | 1,336 | 17 | 0 | 1.26% | - |
| HTTP successQuality gate | Fetch / HTTP | 1,353 | 0 | 0 | 0.00% | Sample quality gate. |
| Noindex on key pagesHard blocker | Indexing eligibility | 1,288 | 65 | 0 | 4.80% | - |
| Text content availabilityRisk condition | Content availability | 1,303 | 50 | 0 | 3.70% | - |
| Rendering / public-access riskRisk condition | Rendering / public access | 1,303 | 50 | 0 | 3.70% | - |
| Internal discoverabilityRisk condition | Discovery | 1,291 | 62 | 0 | 4.58% | - |
| Snippet preview eligibilityHard blocker | Snippet preview | 1,236 | 117 | 0 | 8.65% | Most common observed hard technical blocker. |
| Multilingual language routingRisk condition | Language routing | 302 | 63 | 988 | 4.66% | 17.26% of applicable multilingual sites. Applies only to multilingual sites. |
HTTP 200 success is shown for completeness but treated as a sample quality gate, not as a market finding.
Observed technical blockers and risk conditions by metric
Snippet preview eligibility
Snippet preview
8.65%
Noindex on key pages
Indexing eligibility
4.80%
Multilingual language routing
Language routing · 17.26% applicable subset
4.66%
Internal discoverability
Discovery
4.58%
Text content availability
Content availability
3.70%
Rendering / public-access risk
Rendering / public access
3.70%
Crawler access
Crawl access
1.26%
HTTP success
Quality gate
0.00%
Percentages show observed "no" results in the measured sample. The language-routing metric also has an applicable multilingual subset.
Language-routing metric
Applicable subset matters
1,353
Total sample
sites measured
988
Not applicable
monolingual sites
365
Applicable subset
multilingual sites
63
Observed risk
language-routing sites
17.26%
Share of applicable multilingual subset
Monolingual sites are not applicable, not failed.
How to read the eight metrics
The eight metrics are not SEO preferences. They are public technical eligibility, blocker or risk checks connected with crawling, fetching, indexing, rendering, discovery, snippet previews and language routing.
A failed check means that a public technical blocker or risk condition was observed. It does not prove ranking loss, traffic loss, non-indexing or non-citation by an AI system.
1. Crawler access
This metric checks whether public robots.txt rules block selected public search or AI-search crawler token groups from accessing key pages. A failed check means public robots rules block one or more selected crawler token groups.
2. HTTP success
This metric checks whether key pages return HTTP 200 after normal access and redirects. In the final sample there were no observed failures.
3. Noindex on key pages
This metric checks whether key pages contain a meta robots or X-Robots-Tag noindex directive. A failed check is one of the strongest technical blockers in the study because it asks search engines not to index the page if the directive is seen by the crawler.
4. Text content availability
This metric checks whether meaningful text content is publicly observable on key pages. A failed check means the important text layer was not observed or the page was dominated by boilerplate, challenge content or non-readable presentation.
5. Rendering and public-access risk
This metric checks whether important content is available through normal public browser rendering without login, CAPTCHA, JavaScript challenge or bot wall. A failed check means the content was not visible under honest public access.
6. Internal discoverability
This metric checks whether important pages can be found through normal internal HTML links. A failed check means key pages were not found through standard internal link discovery in the measurement.
7. Snippet preview eligibility
This metric checks whether a site uses public preview controls such as nosnippet, max-snippet:0, data-nosnippet or HTTP robots preview directives on key pages. A failed check means the site exposes a snippet preview eligibility risk condition.
8. Multilingual language routing
This metric applies only to multilingual sites. For monolingual sites the result is not applicable, not a failure. A failed check means a multilingual website showed obviously broken or inconsistent language-routing signals. In the final sample, 365 sites were applicable for this metric and 63 of them failed the check.
Reading the results
HTTP 200 success is a quality gate. Working public access was part of sample inclusion, so zero observed HTTP failures should not be read as a market finding.
The language-routing metric applies only to multilingual sites. The correct denominator for the subset result is 365 applicable multilingual sites, not the full sample of 1,353.
Country-level interpretation
Country-level findings should be read carefully. The country allocation was designed for an EU-wide benchmark, not for a national market census.
The clean way to present country-level results is descriptive variation within the measured sample: country, sample size, count and percentage by metric. It should not be presented as a ranking of countries.
Country-level results should be presented with country sample size next to every percentage. Small-country samples are especially sensitive, and percentages for small-n countries should be read as directional observations only.
Technical reference sources
This study was conducted by IndexDock Research. Google, OpenAI, Anthropic and Bing are not authors of the study and do not validate the dataset or the results.
Official documentation from search and AI platform providers is used only as technical reference material. It explains why the measured signals are relevant to crawling, indexing, rendering, snippets, crawler access and language routing. It does not validate any visibility outcome.
- Google Search technical requirements.
- Google AI features and website guidance.
- Google robots meta, X-Robots-Tag and snippet controls.
- Google JavaScript crawling and rendering basics.
- Google link best practices.
- Google localized versions and hreflang guidance.
- OpenAI crawler documentation.
- Anthropic crawler documentation.
- Bing crawler and robots documentation.
Beyond Layer 1: entity and evidence readiness
This benchmark stops at technical eligibility. Entity clarity, service clarity, geography clarity, business proof, external consistency, real-work evidence, key page depth and organization/schema signals belong to a separate Layer 2 framework and are not measured in this report.
Layer boundary
Layer 1 is measured; Layer 2 is framework-only here
Layer 1 - measured in this report
- crawling
- HTTP success
- indexing eligibility
- text availability
- rendering / public access
- internal discovery
- snippet preview
- language routing
Layer 2 - framework only, not measured here
- company identity clarity
- service/category clarity
- geography clarity
- business proof
- external consistency
- evidence of real work
- key page depth
- organization/schema signals
No combined AI readiness score is created.
Technical visibility hygiene implications
These findings have practical value for web, marketing and engineering teams, but not as an SEO checklist and not as a promise of visibility improvement.
The benchmark identifies review areas that follow directly from the measured risk conditions.
- Check whether robots.txt blocks search or AI-search crawler access to important pages.
- Check whether key pages return HTTP 200 after redirects.
- Check whether homepage, product, service, company or contact pages contain noindex.
- Check whether meaningful visible text is present, not only navigation, cookie text, image-only content or challenge pages.
- Check whether important content is accessible through normal browser rendering without login, CAPTCHA or bot wall.
- Check whether important pages are discoverable through normal internal HTML links.
- Check whether snippets or previews are not blocked accidentally.
- Check whether multilingual sites have a clear language and routing structure.
What this study does not prove
This section is part of the result, not a small disclaimer. The study deliberately avoids claims that the data cannot support.
- It does not prove rankings or traffic outcomes.
- It does not prove actual indexing status or measure Search Console data.
- It does not measure actual inclusion in AI-generated answers or predict AI citations.
- It does not evaluate SEO quality or content quality.
- It does not measure brand authority, backlinks or user behavior.
- It does not rank countries or companies, and it does not prove that fixing a blocker automatically improves rankings.
The study proves a narrower point: in the measured sample, publicly observable technical blockers and risk conditions exist at the AI/search technical eligibility layer.
Limitations
Results are time-bound because websites can change after data collection.
The sample is designed as an EU-wide technical benchmark, not a complete census of all EU HVACR companies. Country-level findings are descriptive for the measured sample.
The checker used honest public access and did not bypass access controls or impersonate official crawlers.
A no result indicates an observed technical blocker or risk condition, not guaranteed ranking loss. A yes result indicates that the checked condition was satisfied, not that the page will be crawled, indexed, ranked or cited.