Public document

Public Analysis Policy

This page explains how OverRank discovers, retrieves and analyzes public pages, especially for sitemaps and competitive comparisons.

Last update: May 3, 2026

This policy complements the conditions of use and the Privacy Policy . It describes our operational functioning and our security limits.

What we analyze

OverRank analyzes public web pages to produce SEO signals, AI visibility, web performance and visibility recommendations.
Analytics can use a user-provided URL, pages declared in a public sitemap, public search results, or public competitive pages selected for comparison.
The extracted signals are limited to what is useful for analysis: URL, retrieval status, title, description, page structure, visible content useful for diagnosis, structured data, trust signals, metrics and competitive gaps.

We must not be used to access a member area, a customer account, an administration interface, a payment tunnel, a quote tunnel, a private form or a page requiring authentication.
We block URLs containing sensitive indices, for example login, account, checkout, payment, shopping cart, app, token, session, email or similar parameters.
We do not circumvent protected access. If a page returns a clear barrier like 403, captcha, anti-bot or non-exploitable content, the analysis of that page is stopped or ignored.
We do not construct a permanent copy of a third party site and we do not offer a reproduction service for third party content.

When you add a project, you confirm that you have the necessary rights to analyze this site or act on behalf of the organization concerned.
For your own site, the analysis can be more comprehensive: recurring audit, history, target pages, reports, comparisons over time and connected data when you allow them.
You remain responsible for not submitting to the service private URLs, confidential data or pages whose analysis would be contrary to your internal or contractual obligations.

Competitive comparisons only focus on public pages accessible without an account and selected to understand why they appear in search results.
When the user adds a competitor, he only forces a comparison perimeter. This does not allow access to protected or non-public data.
Competitive reports provide gaps, scores, URLs, structures and recommendations. They must not be used to copy a third party site or reproduce its protected content.

Sitemaps are used to discover the public pages that a site exposes to crawlers and search engines.
We can read robots.txt, sitemap.xml, sitemap indexes or likely sitemap paths in order to suggest target pages to the user.
When direct reading fails, a public reader can be used to retrieve a usable representation of a sitemap. This step is limited to discovering public URLs and should not be used to scan protected areas.
Sitemap lists are processed on demand, filtered and limited. They may be cached temporarily to avoid repeat requests, but are not intended to become a permanent basis for all URLs on a third-party site.

We apply a logic of minimization: only collect data useful for the requested diagnosis and avoid unnecessary personal or sensitive data.
Technical caches, when they exist, are intended to be short and proportionate: they serve to reduce network load, speed up searches in a sitemap and avoid needlessly requesting the same site several times.
The reports kept in the user account store the results useful for the history: scores, findings, recommendations, URLs analyzed and limited technical evidence. They do not store the full HTML of a third-party site as a reusable archive.
If obviously unnecessary or sensitive data is retrieved by mistake, it must be possible to delete or ignore it during processing.

The service enforces request limits, timeouts, URL validation, private IP blocks, and deny rules on sensitive paths.
Anti-bot protection, a captcha, HTTP refusal or an empty page can make analysis impossible. In this case, the report may be incomplete or refused so as not to produce a misleading diagnosis.
We may limit, suspend or block use that appears excessive, abusive, non-compliant or likely to disrupt a third-party site.

A site editor may contact us to report a difficulty, request clarification or request the reasonable exclusion of a domain from competitive analyses.
Requests must be sent to contact@stuandco.com with the domain concerned, the identity of the requester and the elements allowing to verify his authority on the site.
We will consider requests in good faith, taking into account security, compliance, the SEO / AI visibility purpose of the service and the legitimate interests involved.

For an exclusion request, a compliance question or a report related to the analysis of a site, write to contact@stuandco.com.