Current source addresses used when the Colewood Digital SEO Audit Tool retrieves a client website.
Only the services below make direct requests to the website being audited from a stable, known address. Rules should be restricted to the audited hostname and normal web ports wherever possible.
Technical crawling, page parsing and screenshot collection
94.130.93.30168.119.141.170168.119.99.190168.119.99.191168.119.99.192168.119.99.193168.119.99.19468.183.60.34134.209.42.10968.183.60.8068.183.54.13168.183.49.22268.183.149.3068.183.157.2268.183.149.129Mozilla/5.0 (compatible; RSiteAuditor)Direct page-content, media and UX evidence retrieval
82.163.176.106Mozilla/5.0 (compatible; ColewoodAudit/1.2; +https://tmc-apps.co.uk/seo-audit/)Match the client’s exact hostname and ports 80/443. Skip only the WAF, bot or rate-limit control preventing authorised retrieval.
Use the audit’s access check after the rule is active. A successful check confirms the site is returning readable pages before a paid crawl starts.
The website owner may remove a temporary exception after audit collection is complete, unless ongoing monitoring has been agreed.
Google runs Lighthouse from data-centre infrastructure that can vary. Google does not publish a supported fixed PageSpeed source-IP allowlist. The page must be publicly reachable for a fresh lab test; historical CrUX field data may still be available separately.
Used only as supplemental evidence when requested by an authorised reviewer. It does not have an app-managed fixed source address. DataForSEO and the Colewood server remain the primary retrievers.
Search Console, GA4, Semrush, DataForSEO search datasets and Apify reputation collection call their providers’ APIs or public review platforms; they do not require an IP exception on the client website.