How Client Finch DiscoversWebsite Opportunities

Client Finch uses public company information from Companies House, including official bulk data and API synchronisation. Only companies whose legal status is exactly Active qualify for the eligible dataset. A company record provides supporting business context; the product’s main value is the website evidence available alongside it.

Active is a legal status, not proof of current trading. A registered office may differ from a trading address, SIC classifications may be broad or outdated, and incorporation date does not establish commercial experience. Sole traders and some partnerships are not covered in the same way as registered companies.

Company data contains public sector information licensed under the Open Government Licence v3.0. The underlying official record remains the source for legal registration facts.

Matched Websites are high-confidence company-to-website matches accepted under strict identity and location criteria. The existing process compares company information with Overture-related website-discovery data and checks the relationship between the business identity, location and website. Ambiguous, conflicting or insufficiently supported matches are excluded.

A match helps you connect a website observation with an eligible company. It does not constitute formal certification, government verification or legal proof of domain ownership or administrative control. Matching evidence and source information are available with the company profile where supplied.

Not every imported company qualifies. A website that later appears parked, for sale or inconsistent with the company identity may be withdrawn. Research should still include checking the current website and the business context before relying on an earlier match.

Client Finch automatically analyses 1,000 new websites daily across shared platform coverage. This is not a promise of 1,000 new opportunities every day, a per-subscriber scan allowance or a claim that all matched websites have completed analysis. Opening a company profile reads existing results; it does not request a new scan.

The existing checker examines the homepage and a bounded selection of public pages and links. It respects applicable automated-access restrictions. It does not execute the website’s JavaScript, perform an unrestricted crawl, authenticate to private areas or submit forms.

Matching and analysis are separate stages. Awaiting Analysis indicates that a completed result is not available. Opportunities Found indicates a completed analysis with published supported opportunities. No supported opportunities is a valid completed result; recorded technical observations may still exist.

The categories below describe the existing checker, rather than an exhaustive SEO audit. Observations are recorded against checked URLs and need interpretation in context. An intentionally configured noindex directive or an appropriate off-site canonical is not automatically a problem that needs changing.

Use separate, appropriate tools for browser lab measurements, authorised private analytics, keyword ranking histories and comprehensive accessibility investigations. Client Finch does not infer those measurements from an HTML response.

Where available, users can review an issue title, category, severity, affected or evidence URL, recorded observation and analysis timestamp. Read the source detail before relying on a suggested service. Severity helps with triage; it is not a numerical opportunity score, a forecast of financial impact or a measure of purchasing intent.

Evidence detail depends on the check. An ordinary broken-link observation may identify a failing destination without supplying a complete map of every referring page. Revenue Path evidence includes the source page, visible action text, destination, final response, confirmation attempts and time.

The opportunity examples show how to read an observation and scope a possible investigation. They are examples, not the source of the aggregate research report. The technical SEO prospecting guide provides a more detailed interpretation checklist.

Supported website observations can indicate a possible professional service: a metadata review, internal-link maintenance, responsive implementation review or a repair to an enquiry destination. The opportunity explanation connects an observed condition with work an agency could investigate.

A raw finding and a published opportunity are different units. An observation can be recorded without producing a service opportunity, and a completed analysis can publish no opportunities. Do not treat a count of opportunities as a count of every technical issue, or a count of issues as evidence of commercial demand.

The public research resource will use reviewed, anonymised aggregates from completed check records. It will state its sample and denominators when verified data is available. Read the UK Website Issues Report scope for its publication criteria.

My Agency Profile, For You and Opportunity Alerts are existing Pro features. Your profile records supported service preferences, available sector choices and target areas. For You applies those preferences to existing completed opportunities and explains the available match reasons.

Opportunity Alerts can notify you about qualifying newly available findings after activation. In-app alerts and optional daily or weekly account-email summaries are off until you choose them. The system reuses the existing matching and completed analysis; changing preferences does not commission new website scans or send a historical backlog.

These are subscriber research tools. They do not send messages to prospects, collect prospect email addresses or establish that a company has expressed interest in your services. Free and Pro retain their existing detail-view and export permissions.

Revenue Path checks focus on meaningful customer actions, such as requesting a quote, making an enquiry or reaching a booking destination. Confirmation requires two distinct GET observations of the same HTTP 404 or 410 at the same final destination. Relevant public external booking destinations can be checked where permitted.

Repeated links to the same underlying failed customer-action destination are consolidated. Redirects are evaluated as part of the observed journey. A transient timeout, temporary server response, bot challenge, login requirement or untested JavaScript behaviour does not become a confirmed Revenue Path opportunity.

The checker does not submit contact forms, create bookings, place orders, initiate payments or submit applications. It does not assume a missing contact form, absent booking button or design preference is a technical failure.

A confirmed broken quotation link may interrupt that path for someone using it. The observation does not measure how many people tried, whether another route worked, conversion loss or revenue. The enquiry-path example shows how to keep that distinction clear.

Website conditions and company circumstances can change after a check. Review the recorded time and inspect the current page before recommending work. Findings reflect selected checks and available evidence; no finding is a substitute for understanding the page’s purpose.

Some websites have no detected issues within the performed checks. Some completed checks have no published opportunities. Some matches are awaiting analysis or could not be checked reliably. These states remain separate, and none establishes that the entire website is free of possible problems.

Client Finch does not guarantee leads, customers, rankings or revenue. It does not provide private Search Console data, full website crawls, comprehensive browser performance measurements or buying-intent evidence. Users decide which companies to save and whether to take any independent next step.

Client Finch does not automatically contact businesses or provide prospect email addresses. You remain responsible for lawful outreach through your own channels. Account verification, password reset, support communication and subscriber alerts are separate email functions.