In 1-FIND’s audit of 75 home services contractors across Johnson City, Kingsport, and Bristol, 10 had a setting in their website files that blocks Google from crawling the entire site. Their websites appear to work. Google can’t index them.
The finding comes from the 2026 Tri-Cities Home Services Digital Visibility Study, which evaluated 75 HVAC, plumbing, electrical, roofing, and tree service companies across the Tri-Cities on five technical dimensions. Among the audit’s most actionable findings: 15 of the 75 companies (20%) had at least one configuration classified as a critical risk flag. Ten of those 15 had robots.txt files blocking all search engine crawlers. Two had noindex directives on their homepage. Three were serving pages over HTTP only.
These are not subtle ranking disadvantages. They are configurations that can prevent a website from appearing in search results at all, regardless of how well everything else is optimized. A contractor with a complete Google Business Profile, 200 reviews, and a professionally designed website is invisible in organic search if their robots.txt file is telling Google to stay out.
Table of Contents
| A robots.txt file blocking all crawlers is not a ranking disadvantage. It is the website equivalent of a closed sign on a storefront that Google cannot see past. |
What robots.txt Is and Why It Matters
Every website has (or can have) a file called robots.txt located at the root of the domain. You can view it for any site by going to the website’s address and adding /robots.txt at the end.
This file contains instructions for search engine crawlers. It tells Google’s bot and other crawlers which parts of the site they’re allowed to access and which parts they should ignore. Most businesses use robots.txt to block crawlers from administrative pages, login portals, and development environments.
The problem occurs when the robots.txt file contains an instruction that blocks all crawlers from all pages. This configuration looks like this:
| User-agent: *Disallow: / |
That two-line combination tells every search engine crawler to disallow access to every page on the site. Google reads it as an explicit instruction: do not index this website. The site remains live and accessible to human visitors. It does not exist in Google Search.
How It Happens: The Developer Mistake That Persists
This is almost never intentional. A robots.txt file blocking all crawlers is typically the result of a web development workflow that wasn’t fully reversed after the site launched.
During development, most developers set staging sites to block search engines. A staging site is a copy of the website used for building and testing before the real version goes live. Blocking crawlers from the staging site prevents Google from indexing an unfinished version. This is correct practice.
The problem is that when the finished site is deployed to the live domain, the blocking configuration sometimes comes with it. Either the staging settings were copied to production, or the developer forgot to update the robots.txt before launch, or the site was built on a WordPress template that had search engine visibility turned off and nobody turned it back on.
The website functions correctly. Visitors can access every page. No error message appears. There is no visible indicator that anything is wrong. The only way to know is to check the robots.txt file directly, or to notice that the site doesn’t appear in search results for terms it should logically rank for.
| The Three Critical Risk Flags Found in the Study Robots.txt blocking all crawlers: 10 of 75 companies (13.3%) Impact: website invisible to Google search entirely Noindex directive on homepage: 2 of 75 companies (2.7%) Impact: homepage excluded from Google’s index HTTP without HTTPS: 3 of 75 companies (4.0%) Impact: security warning in browsers; ranking disadvantage Total with at least one critical risk flag: 15 of 75 (20.0%) Source: 2026 Tri-Cities Home Services Digital Visibility Study, 1-FIND SERVICES |
Which Trades Had the Most Blocking Issues
Of the 10 companies with robots.txt files blocking all crawlers, four were classified under electrical. The electrical category also had one of the wider spreads in overall scores in the study, with the highest-performing electrical entry scoring 89.8 and one entry at 58.8. The robots.txt issue was a contributor to the category’s lower-end scores.
Across all five trade categories (HVAC, plumbing, electrical, roofing, tree service), critical risk flags appeared with enough distribution that no single trade was responsible for the majority of cases. The pattern suggests the issue is not trade-specific. It’s a web development and maintenance gap that cuts across the market.
The broader context from the study: companies with critical risk flags scored materially lower on the Combined Visibility Score. The average CVS across the full 75-entry sample was 72.0. The lowest individual score in the study was 41.6, held by a tree service company with no retrievable website health data, almost certainly a site with a complete visibility blockage rather than just a weak technical configuration.
How to Check Your Own Website Right Now
This check takes under 60 seconds:
- Go to your browser and type your website address followed by /robots.txt. For example: yourbusiness.com/robots.txt
- Look for the two lines that indicate blocking. If you see ‘User-agent: *’ followed by ‘Disallow: /’, your site is blocking all crawlers.
- Also check Google Search Console. The Coverage report (now called the Indexing report in newer versions) will show whether Google has successfully indexed your pages. If the report shows very few or zero indexed pages for a site that’s been live for more than 90 days, a robots.txt block is one of the first things to check.
- Run your domain through Google’s URL Inspection tool. In Search Console, use the URL Inspection tool on your homepage. If it returns ‘URL is not on Google’ and the reason isn’t a manual action or crawl error, check robots.txt immediately.
| What a Healthy robots.txt Looks Like A correctly configured robots.txt for most contractor websites: User-agent: *Disallow: /wp-admin/Allow: /wp-admin/admin-ajax.php Sitemap: https://yourdomain.com/sitemap.xml This allows all crawlers to access everything except the admin area, which is standard WordPress practice and exactly what you want. |
The Fix
If your robots.txt file contains the blocking configuration, the fix is simple:
- Access your website’s root directory. This is typically done through your hosting provider’s file manager, via FTP, or through the WordPress dashboard if you have a plugin that manages the robots.txt file.
- Open the robots.txt file. It’s a plain text file at the root of your domain.
- Change ‘Disallow: /’ to ‘Disallow:’ (blank). A blank Disallow means no pages are blocked. Or remove the Disallow line entirely.
- Save the file and verify. Return to yourdomain.com/robots.txt and confirm the line no longer reads ‘Disallow: /’.
- Request indexing in Search Console. Use the URL Inspection tool to request a crawl of your homepage. This speeds up the window between fixing the issue and Google processing the change.
The entire process takes 5-10 minutes. After Google recrawls the site, pages that were previously blocked will begin appearing in search results within 1-4 weeks depending on your site’s crawl frequency.
The Noindex and HTTPS Issues
Beyond the robots.txt blocking, the study found two additional critical configurations in the sample:
Noindex on the homepage
Two companies had noindex directives active on their homepage. A noindex tag is a line of code that tells Google: do not include this page in search results. It’s used legitimately on pages you don’t want indexed (thank-you pages, duplicate content pages, admin pages). When it appears on a homepage, it typically means the same kind of developer oversight as the robots.txt issue: a development or staging setting that wasn’t removed before launch. The check: view source on your homepage and search for ‘noindex’. If it appears inside a meta robots tag, it needs to be removed.
HTTP without HTTPS
Three companies in the sample were serving their sites over HTTP without TLS encryption (HTTPS). Google has marked HTTPS as a ranking signal since 2014, and modern browsers display a security warning to visitors on HTTP sites. For a contractor whose website is a trust-building tool, a security warning on page load is a conversion problem in addition to a ranking problem. SSL certificates are available free through most hosting providers and take minutes to activate.
What This Means if You’re One of the 10
If your site has a robots.txt file blocking all crawlers, the implications are straightforward: all the work that has gone into your Google Business Profile, your reviews, your website content, and your SEO is producing zero organic search visibility. Not less than it should. None.
A prospect who searches for your service in Johnson City, Kingsport, or Bristol and finds your GBP listing will be able to call you directly or click through to your website. But they will not find your website organically. Your blog posts are not indexed. Your service pages are not indexed. Your city pages are not indexed. Years of potential content authority may be sitting unindexed because of two lines of text in a file you may have never seen.
The robots.txt check is the first thing worth doing before any other SEO investment. You can review the full findings from our audit, including the methodology and per-category data, in the 2026 Tri-Cities Home Services Digital Visibility Study.
| Not sure whether your site has a crawl blocking issue? 1-FIND checks for robots.txt blocking, noindex directives, HTTPS status, and all 15 technical issues identified in the 2026 Tri-Cities study as part of our free local SEO audit for home services contractors. Takes 24 hours. No cost. |
- The Google Review Threshold: How Many Reviews You Need to Show Up in AI Search - June 3, 2026
- 10 of 75 Tri-Cities Contractors May Be Invisible to Google - June 2, 2026
- What Does a Digital Marketing Agency Actually Do? - May 30, 2026



