PUBLISHING AND TRANSPARENCY
Content, measurement, and crawler policy
This page explains how product explanations are maintained and how automated scan output is kept separate from editorial text. Visitors should be able to tell which information was measured by the tool and which information is a publisher explanation.
Publisher identity
MaxAuditor Pro is the publisher of this site. Product pages, guides, and legal notices are maintained under the same site structure, and the contact channel is published in the footer.
MaxAuditor Pro is independent. It does not represent endorsement by Google, Cloudflare, Vercel, or providers observed on a scanned website.
How is the content prepared?
Editorial pages are kept in version control as part of the product source. Research, drafting, or language-editing tools may assist the work; published wording is checked against current scan behavior so the site does not describe a check that the product does not perform.
Scan reports are different: they are generated automatically from live technical signals returned by the public URL submitted by the user. Automated scan output and publisher-maintained guidance are not presented as the same kind of content, and the source and limits of a measurement are explained separately.
Version and update dates
The application version comes from the same package value used by the health response and publication documents. Behavior changes are recorded in CHANGELOG.
The visible last-updated date on editorial pages comes from the real deployment build information. Dates are not advanced simply to make unchanged content appear fresh.
Publishing principles
Site copy describes behavior that can be demonstrated. It avoids unsupported claims of superiority, certification, guaranteed outcomes, partnership, or advertising approval.
Pages are not multiplied to capture keyword variations. Turkish and English are complete editorial versions; interface-only locale routes are kept out of search indexes instead of publishing weak duplicate content.
Advertising and measurement
When AdSense is configured, the publisher identifier is exposed in metadata and ads.txt. Actual ad serving still depends on account approval, site approval, regional consent, Google policy, and local blocking settings.
Analytics consent does not change a report score, request ad clicks, or move a visitor from a scan result into an ad placement. The publisher must not click their own ads or encourage clicks.
Search and answer-engine crawlers
robots.txt keeps public content open to major search services and known answer-engine crawlers. API routes and technical endpoints without indexing value remain excluded.
llms.txt and llms-full.txt are discovery helpers, not ranking controls. If a CDN or WAF blocks a verified crawler, robots.txt alone cannot make that request succeed.
Corrections
Use the contact channel to report inaccurate, incomplete, or stale wording. The affected page URL and observed problem are enough; do not send account passwords or secret keys.
A correction is reviewed against both the published wording and the actual technical behavior. The release notes are updated when a behavior change needs to be recorded.
Security and availability
Scan requests use target validation, private-network protection, rate limits, and human verification. API responses are kept out of search indexes and the service does not build personal report profiles.
The service does not promise uninterrupted availability. security.txt and the public contact channel are available for responsible security reports.