Policy signal
Read the site’s robots instructions and record an approximate decision for each named profile.
Private release preview
See what a crawler-style request actually meets.
Turn authorized website checks into a request matrix, prioritized findings, and portable evidence — without sharing CMS or server credentials.
- 25
- public HTTPS URLs per job
- 3
- checks per 24 hours*
- 3
- private export formats
*Proposed production limit. Final commercial terms will match the verified release.
AUTHORIZED CHECK
docs.example.com
Pages08
Profiles12
Responses96
Priority02
PRIORITY FINDINGP1
Request behavior differs from the baseline
One profile received an access response that does not match the standard request.
/knowledgeBaseline 200Profile 403ProfilePolicyHTTPResult
BaselineN/A200Reached
GPTBotAllowed403Different
Google-ExtendedPolicy only—Not probed
Illustrative data shown in the release interface. It does not represent a customer site or an indexing guarantee.
No CMS loginNo hosting password or plugin install.
Permission firstOnly sites you own or may assess.
Evidence you can movePrivate JSON, CSV and TXT exports.
The evidence workspace
A technical result designed to be handed off.
The release interface keeps the authorization, request evidence, limits and exports visible in one workspace.
One diagnostic record
Three layers. One defensible next step.
The service separates policy signals from the response actually returned and the raw HTML signals available at that URL.
Allowed / Disallowed / Unresolved
Request response
Compare bounded HTTPS requests without following profile redirects or bypassing access controls.
Page evidence
Record selected raw-HTML signals, including title, H1, canonical, indexing directives and structured data count.
Evidence workbench
Move from a vague block to a reproducible handoff.
Switch between the same evidence views a buyer uses after an authorized check.
Prioritized observations connect a difference to the evidence and a practical next check.
CHECK / 7F2ACompleted 14:32 UTC
P1
Access response differs
Baseline reached the page. One named profile received 403.
Next: review edge security rules for requester-label handling.P2
Policy and response disagree
The approximate robots decision permits the profile, while the HTTP layer rejects it.
Next: compare robots policy with CDN and WAF behavior.INFO
Canonical is present
The raw HTML declares a canonical URL on the inspected page.
Reached Different Policy only
URLBaselineGPTBotGoogle-Ext.
/200200Policy
/knowledge200403Policy
/pricing200200Policy
JSONStructured evidence for workflows
PRIVATECSVRequest rows for spreadsheet review
PRIVATETXTReadable handoff for a developer
PRIVATEDownloads require the same verified purchase entitlement as the result.
Designed for authorized work
Bounded by design. Clear about what it cannot prove.
Public HTTPS only
No login pages, query strings, private networks, CAPTCHA bypass or credentialed access.
Controlled transport
Same-host redirects, validated public addresses, TLS hostname checks and bounded jobs.
Private entitlement
The raw license key is checked with Gumroad and is not stored with results.
Honest interpretation
No claim of indexing, citation, model training, provider affiliation or verified provider IP access.
Built for the handoff
Useful where screenshots stop being enough.
FOR DEVELOPERS
Reproduce the difference
Give an engineer the URL, profile, policy signal, response and observed evidence in one record.FOR AGENCIES
Standardize pre-audit evidence
Use the same bounded workflow before recommending changes to a client’s stack.FOR SITE OWNERS
Ask a better technical question
Separate a robots instruction from a CDN response or raw-page signal before escalating.Scope before certainty
A diagnostic, not a guarantee.
The service records what bounded requests and a raw-HTML inspection observe. It does not reproduce a provider’s infrastructure or prove what a search engine, AI product or model will do.
It checksApproximate robots policy, HTTPS response behavior and selected raw-HTML signals.
It does notRender JavaScript, inspect CSS visibility, bypass controls or establish indexing and citation.
It requiresOwnership of the target website or explicit permission to run the requests.
Founding release
Premium access begins only when the evidence chain is complete.
The public offer is intentionally closed while production entitlement, restart recovery, browser exports and the real purchase journey complete final verification.
Private QA in progressNot currently offered for purchase.
PLANNED FOUNDING ACCESS
US$49
Proposed launch price. Final access term and limits will be shown before checkout.
- Hosted diagnostic workspace
- Up to 25 authorized URLs per job
- Private result history and exports
- Transparent limits and retention
Before release
Questions worth answering first.
Does this prove that a crawler can index or cite my page?
No. It records bounded request behavior and selected raw-HTML signals. Provider-side discovery, indexing, citation and model use are outside the diagnostic.
Do I need to share a CMS or hosting password?
No. The proposed service works only with public HTTPS URLs. It does not require a CMS login, server credential or installed plugin.
Can I check a client website?
Only when you have explicit permission from the owner to run the submitted requests. Authorization is required for every job.
When can I purchase access?
After the production service, license lifecycle, retention terms, exports and real checkout journey pass the final release gates. This preview does not accept payment.