Public verification set
Six tools you can use before you ever talk to VERIS.
These tools are public and independent of VERIS. They are the same kinds of checks referenced inside the audit and proof package, so you can inspect the site yourself before you buy anything.
Best order
- Start with schema and discovery checks first.
- Use extraction and technical checks after that.
- Use the audit when you want the same logic applied systematically.
Foundation checks
Use these first when you want to know whether the business is structurally readable at all.
Discovery checks
Use these to confirm whether the site is at least publicly visible and findable.
Extraction checks
Use these to see how page summaries and metadata resolve when systems reuse the page.
Technical support checks
Use these when you want supporting evidence about the page’s technical quality and rendering behavior.
Google Rich Results Test
No account requiredFoundation checks
https://search.google.com/test/rich-resultsWhat it checks: Whether your website has valid schema markup and which schema types Google can detect.
How to use it
- Go to search.google.com/test/rich-results
- Paste your full website URL
- Click Test URL
- Wait for the results
What to look for
- Items detected means schema is being parsed
- No items detected means no usable schema is being found
- Warnings and errors usually point to missing or invalid properties
Why VERIS uses it: This is one of the clearest ways to confirm whether the business is machine-readable at all.
Schema Markup Validator
No account requiredFoundation checks
https://validator.schema.orgWhat it checks: Structural validity of JSON-LD schema against the schema.org specification.
How to use it
- Go to validator.schema.org
- Paste your full URL in Fetch URL
- Run the test
What to look for
- Errors point to broken schema structure
- Warnings often indicate misused properties
- Parsed items confirm the entities that are actually visible
Why VERIS uses it: A deeper structural check after the rich-results test, especially useful for confirming the JSON-LD is clean.
Google or Bing site: search
No account requiredDiscovery checks
https://www.google.comWhat it checks: Whether pages are appearing in major web indexes. This is a public proxy for discovery, not a guarantee of AI inclusion.
How to use it
- Go to Google or Bing
- Search for site:yourdomain.com
- Review which pages appear
What to look for
- Pages appearing means some public index coverage exists
- No results usually suggests a crawl or discovery problem
Why VERIS uses it: A fast check for whether the site is publicly visible before deeper verification in Search Console or Bing Webmaster Tools.
OpenGraph.to
No account requiredExtraction checks
https://www.opengraph.toWhat it checks: Open Graph and Twitter card tags. Shows how link previews resolve when the page is shared or summarized.
How to use it
- Go to opengraph.to
- Paste the full URL
- Click Check
What to look for
- The preview should show the correct image and page description
- Generic copy often signals weak extraction formatting
Why VERIS uses it: Useful when checking how well the page exposes a concise summary outside the visible page layout.
Google PageSpeed Insights
No account requiredTechnical support checks
https://pagespeed.web.devWhat it checks: Core Web Vitals and technical page health. This is not an AI-specific test, but it helps show whether the page is technically sturdy.
How to use it
- Go to pagespeed.web.dev
- Paste the full URL
- Analyze the page and review the Mobile tab
What to look for
- Large layout shifts, slow LCP, or heavy render-blocking issues
- Accessibility or technical warnings that reduce page quality
Why VERIS uses it: A support check for page quality and rendering reliability.
Lighthouse in Chrome DevTools
No account requiredTechnical support checks
https://developer.chrome.com/docs/lighthouse/overviewWhat it checks: Performance, accessibility, best practices, and mobile rendering in a first-party browser tool.
How to use it
- Open the page in Chrome
- Open DevTools and choose Lighthouse
- Select Mobile and analyze page load
What to look for
- Accessibility issues affecting headings, buttons, or contrast
- Large layout shifts or weak technical hygiene
Why VERIS uses it: Useful when the page needs a browser-level check beyond the public tools above.
Bonus manual check
You can inspect robots.txt and llms.txt without any tool at all.
Open your browser and visit `yourdomain.com/robots.txt` and `yourdomain.com/llms.txt`. If the file is missing or relevant crawlers are explicitly blocked, that usually becomes a high-priority audit finding.
ROBOTS.TXT QUICK CHECKtxt
# What you want to see: User-agent: OAI-SearchBot Allow: / User-agent: GPTBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: ClaudeBot Allow: / # What is a critical finding: User-agent: OAI-SearchBot Disallow: /