Access Food Verification & Auditing Limited

Reporting app usage information

Effective 13 October 2026. This page explains the intended operation of AFVA SEO Reporting. It does not create a separate paid service or a general public app.

Purpose and permitted access

AFVA SEO Reporting is an own-business tool for Access Food Verification & Auditing Limited. Only the business owner and specifically authorised users should connect AFVA properties or access its reports. The connected Google account must already have permission to read the selected properties.

Search Console and Analytics access is read-only. Collection does not publish articles, edit the website, change Analytics configuration, reply to reviews or post publicly. Any implementation of a report recommendation is a separate task authorised by the business owner.

Understanding the report

The dashboard, written summary and action register should be read together. Search Console clicks are visits from search results, rather than confirmed enquiries. Contact clicks and recorded form events require interpretation and tracking validation before they can be described as received or qualified enquiries.

Data can be incomplete, delayed, privacy-limited or revised by its source. Each report identifies its periods, source dates and important limitations. Search Console and Analytics can use different reporting time zones. Missing data is not converted into zero.

Reports guide priorities and support the existing AFVA content workflow. They do not promise Google rankings, traffic, sales or regulatory conclusions.

Availability and account control

Local scheduled collection depends on the owner's computer, software, authorised connections and source availability. A failed or revoked connection should be shown as incomplete rather than replaced with guessed metrics.

The owner can stop collection or revoke Google access. Read the privacy disclosure for storage, providers and removal of saved copies.

Business Profile integration

A future Google Business Profile connection requires separate API approval and profile authorisation. API performance data would be handled in a live view and excluded from permanent API-derived archives. Owner-downloaded official exports are a distinct evidence source. No public profile changes are included in this reporting workflow.

Questions or corrections

If a report appears incorrect, provide its period and the figure or action needing review. Contact AFVA for reporting support. Check data and assumptions before acting on a recommendation.