When a crawler cannot find a real way to reach the people behind a site, it flags "No Contact Info." Google's human quality raters treat easy-to-find contact details as a baseline sign that a real organization stands behind the page. Add a reachable channel (email at minimum), a contact page, and ContactPoint schema. Solo operators can stay private and still pass.
This check looks for clear, reachable contact information and reports a problem when it finds none. It is one of the cheaper trust signals to fix, and one of the most common to skip. I have audited plenty of sites that ranked fine on paper but had no visible way to reach a human.
What this check flags
The crawler scans your pages, footer, header, and common locations for contact markers: a visible email, a phone number, an address, a working contact form, or a dedicated contact page. When none turn up, or the only thing present is a dead link or a form that goes nowhere, the issue fires. It is not penalizing you for missing a phone number specifically. It is reporting that a visitor (or a rater) landing on your site would struggle to figure out who you are and how to reach you.
Why contact info is a baseline trust signal
Google's Search Quality Rater Guidelines give human raters a handbook for judging page quality, and Trust is the most important piece of the E-E-A-T framework (Experience, Expertise, Authoritativeness, Trust). One of the practical things raters look for is whether a site makes it easy to learn who is responsible for the content and how to contact them. A missing or hidden contact path lowers their read on Trust.
This matters more on YMYL pages, the topics that can affect someone's money, health, safety, or civic life. For those pages, raters apply stricter scrutiny and expect satisfying contact and customer-service information, especially on stores and sites that handle transactions. The logic is simple: a real organization that stands behind its work gives people a way to reach it. A site that hides leaves the rater guessing whether anyone is accountable.
There is a search-engine side too. Consistent name, address, and phone (NAP) data acts as a confidence signal for entity resolution. When your contact details line up across your site, your schema, and your business listings, engines confirm you are a real, single entity more easily. Discrepancies, even small ones like "Street" versus "St.", muddy that picture.
What to include
Use real, working channels. The goal is reachability, not a wall of fields:
A live email address. A monitored inbox is the floor. A contact form that actually delivers, with a confirmation message so people know it sent. A phone number if you take calls. A physical or mailing address if you have a registered business location, which carries extra weight for local and ecommerce sites. A dedicated contact page linked from your global footer so it appears on every page. Round it out with ContactPoint schema inside your Organization markup, which lets you declare support and sales contact details in structured form that engines can read directly.
Privacy-conscious options for solo operators
You do not have to publish your home address to pass this check. If you run a one-person operation from home, a contact form plus a monitored email is enough to clear the flag and satisfy a rater. Keep the home address off the page; use a virtual mailbox, a registered agent address, or a PO box if you want a postal option on record. A business phone routed through a forwarding service keeps your personal cell private. The point a rater is checking for is that a real person can be reached, not that your private life is on display.
How to fix it
Work through this in order. First, create or repair a dedicated contact page at a clean URL like /contact/. Second, add at least one live channel to it, an email or a working form, and test that a submission actually arrives. Third, link the contact page from your site-wide footer so it shows on every page. Fourth, add ContactPoint schema to your Organization markup. Fifth, make your NAP match exactly across the site, your schema, and any business listings you maintain. Then recrawl and confirm the issue clears.
Common mistakes
A contact form that silently fails is worse than none, because you lose real messages and never know. Test it from outside your own network. Burying contact details so deep that nobody finds them defeats the purpose; the footer link is what makes it discoverable. Image-only contact details (an email baked into a graphic to dodge spam) cannot be read by the crawler and may not register. Listing a different address in your schema than the one shown on the page creates the exact NAP discrepancy that weakens entity trust. And a contact page with a form but no other identifying detail, no business name, no description of who you are, still reads as thin to a rater.
FAQ
A: No. A monitored email or a working contact form is enough to clear the flag. A phone number helps on local and transactional sites but is not required for every site.
A: It can be, as long as it actually delivers and is paired with at least your business name and a brief sense of who you are. Add a confirmation message so submitters know it sent.
A: No. Use a virtual mailbox, PO box, or registered agent address if you want a postal option, or skip the address entirely and rely on a form and email. Reachability is what matters.
Need a full technical audit?
SEO ProCheck runs deep crawls that catch issues like this across your whole site.
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.








