[Registry](/registry)

# One Call Construction and Consulting

onecallconstruction.us

One Call Construction and Consulting is a consulting firm in Bellingham, WA, as its own site declares. The site lists 15 service areas, including Whatcom County, Washington, Skagit County, Washington, San Juan County, Washington, Bellingham, Washington. CrawlCheck last read onecallconstruction.us on 2026-11-16 and graded it A, 87 of 100, for how well AI agents and search crawlers can read it, with 2 findings.

llms.txt agents.md Media kit Entity graph AI access policy Agent-callable

Owner not verified. Is this your site? [Prove it is yours](/registry/onecallconstruction.us/claim) — free, by DNS TXT or a meta tag.

## Facts on record

| Fact | Value | How it is known |
| --- | --- | --- |
| **Owner** | Not verified | nobody has proved they run this site |
| **Grade** | A, 87 of 100 | measured on the last read |
| **Last read** | 2026-11-16 | the date CrawlCheck fetched the site |

## Business details

| | |
| --- | --- |
| **Name** | One Call Construction and Consulting |
| **Phone** | [(360) 362-5318](tel:+13603625318) |
| **Location** | Bellingham, WA |
| **Kind of business** | consulting firm |
| **Profiles it links** | facebook.com, houzz.com, secure.lni.wa.gov |
| **Areas served** | Whatcom County, Washington, Skagit County, Washington, San Juan County, Washington, Bellingham, Washington, Lynden, Washington, Ferndale, Washington, Blaine, Washington, Birch Bay, Washington, Mount Vernon, Washington, Anacortes, Washington, Burlington, Washington, La Conner, Washington, Orcas Island, Washington, Friday Harbor, Washington, San Juan Island, Washington |
| **Website** | [onecallconstruction.us](https://onecallconstruction.us/) |

As the site declares them for its own business, read on 2026-11-16. A street line is never republished here, even where the site’s markup carries one.

[Consulting firms in Bellingham, WA](/registry/trade/consulting/wa/bellingham) · [Every business on record in Bellingham, WA](/registry/place/wa/bellingham)

Get these 2 findings fixed

Every defect this row counts, corrected on the site itself and then re-measured from the outside — done is measured, not asserted. One-time, $100 for one small-business site, thirty days of monitoring included.
[Get this fixed — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v)
[What that covers](/pricing#fix)

Claiming is free and changes nothing but the owner mark. What a licence adds is the record behind this entry: re-measured twice a day, finding age on every defect, change receipts between any two dates. [Keep it on the daily record](/pricing?domain=onecallconstruction.us#trial).

## What the fetch found

| Finding | Severity |
| --- | --- |
| No llms.txt | 1 of 5 |
| HTTPS is served without a Strict-Transport-Security header | 1 of 5 |

## Section scores on this fetch

Weakest first. 16 of 26 scored sections at 90 or above.

| Section | Score |
| --- | --- |
| Authorship and trust signals (E-E-A-T proxies) | 29 |
| Server and hosting | 50 |
| Entity corroboration | 50 |
| Schema and entity graph | 60 |
| Local presence, citations and NAP | 75 |
| Error pages | 75 |
| Quotable content | 80 |
| Payload and render path | 80 |
| Image signals | 80 |
| Machine layer | 83 |
| Accessibility structure (from the delivered HTML) | 95 |
| RDF and linked-data surface | 100 |
| Indexability | 100 |
| Crawl waste | 100 |
| Page subject, the Webref question | 100 |
| AI and search agents | 100 |
| Speed a crawler sees, and field data where it exists | 100 |
| Machine-file trust chain | 100 |
| Claim consistency | 100 |
| Agent instruction surface | 100 |
| What each agent receives | 100 |
| Mobile surface | 100 |
| Exposed files and secrets | 100 |
| Sitemap coverage | 100 |
| Internal linking | 100 |
| Naming and case consistency | 100 |

## Shelves

| Shelf | State | Definition |
| --- | --- | --- |
| **llms.txt** | not found | [What counts, and who has it](/registry/llms) |
| **agents.md** | not found | [What counts, and who has it](/registry/agents) |
| **Media kit** | not found | [What counts, and who has it](/registry/mediakit) |
| **Entity graph** | on the shelf | [What counts, and who has it](/registry/entity) |
| **AI access policy** | not found | [What counts, and who has it](/registry/aipolicy) |
| **Agent-callable** | not found | [What counts, and who has it](/registry/agentapi) |

## Questions about One Call Construction and Consulting

### What is One Call Construction and Consulting?

One Call Construction and Consulting is a consulting firm in Bellingham, WA, according to its own website, onecallconstruction.us.

### Where does One Call Construction and Consulting work?

Its site gives Bellingham, WA as its location and lists 15 service areas: Whatcom County, Washington, Skagit County, Washington, San Juan County, Washington, Bellingham, Washington, Lynden, Washington, Ferndale, Washington, Blaine, Washington, Birch Bay, Washington, Mount Vernon, Washington, Anacortes, Washington, Burlington, Washington, La Conner, Washington, and 3 more.

### How do I contact One Call Construction and Consulting?

The phone number its site publishes is (360) 362-5318. Its website is onecallconstruction.us.

### Has the owner of onecallconstruction.us been verified?

Owner not verified. Nobody has proved to CrawlCheck that they run this site. Proving it is free and takes one DNS record or one meta tag.

### Can AI assistants read onecallconstruction.us?

On 2026-11-16 it was graded A, 87 of 100, with 2 findings. It serves 1 of the 6 things the registry looks for: entity.

### How current is this page?

CrawlCheck last read onecallconstruction.us on 2026-11-16. The page changes only when a new read does.

[The full report for this fetch](/r/a6wtuep7rf)

Machine-readable: [/api/registry?host=onecallconstruction.us](/api/registry?host=onecallconstruction.us). This row states what was served to CrawlCheck at that time. It is not an endorsement, and it says nothing this scan did not measure.

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:** [SDK](/sdk) · [Certificates](/certificates) · [Failure policy](/spec/failure-policy) · [Conduct: Google agent](/agents/conduct/google-agent) | **Registry:** [MCP: Operator](/registry/mcp/operator) · [MCP](/registry/mcp) · [stripe.dev](/registry/capabilities/stripe.dev) | **Datasets:** [Technologies: Calendly](/datasets/technologies/calendly) · [Problems: Image format mismatch](/datasets/problems/image-format-mismatch) | **Blog:** [One Cloudflare setting is behind most of the new AI training blocks on top sites](/blog/one-cloudflare-setting-behind-most-new-ai-training-blocks-november-2026) | **Glossary:** [NAP](/glossary/nap) · [Mean reciprocal rank](/glossary/mean-reciprocal-rank)

[Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)
