Website report
Visit sitehttps://supplyzpro.com/
Discover SupplyzPro — a simple, all-in-one, AI-powered workspace to manage your business: sales and purchases, real-time inventory, invoicing, suppliers, payments, and more.
Audit Full discovery audit·Language English (en)·Response HTTP 200
Analysed Nov 7, 2026 · 15 categories · 85 passed · 34 warnings · 1 issue · 30 informational
Audit score
D60/100
Mixed
- Agentic
- 74
- SEO
- 65
What we found
1Needs a fix34Could be better85Looks good30Informational- 1.Could be better: No render-blocking head scripts: needs attention. see checkFaster pages help visitors reach your content sooner.
- 2.Could be better: Semantic HTML structure: needs attention. see checkClear, accessible information helps AI assistants understand and cite your website.
- 3.Could be better: Interactive controls have source labels: needs attention. see checkA usable mobile layout helps visitors read and act on your content.
- 4.Could be better: Share image dimensions declared: needs attention. see checkComplete link previews make your pages easier to recognize and share.
- 5.Could be better: Your headings skip levels. see checkA clear outline makes content easier to navigate, including with a screen reader.
Built with 3 technologies· detected stack
Read from the public source and response headers of the sampled pages.
FramerCMS / platform
Google AnalyticsAnalytics
- CookieYesConsent integration
A framework or CDN signal describes the public response, not the origin host or private backend.
Site checks
Every observation from the crawl, grouped by what it describes. Open a row for the evidence and the recommended fix.
Metadata1Could be better10Looks good
100/100Could be better: Meta description lengthDescription is 173 characters, over this audit's 160-character review point (a preview heuristic, not a Google limit).
Could be better · Metadata · Review suggested
Observed evidence
Description is 173 characters, over this audit's 160-character review point (a preview heuristic, not a Google limit).
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. It is there, but weaker than this check expects.
Recommended fix
Front-load the useful summary because Google may generate or truncate snippets by query and device.
Looks good: Page title exists
Looks good · Metadata · Measured on your page
Observed evidence
Title found: "SupplyzPro — Smart, Simple ERP for Your Business"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title length
Looks good · Metadata · Review suggested
Observed evidence
Title is 48 characters, inside this audit's 15–60 review range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title says what the site does
Looks good · Metadata · Measured on your page
Observed evidence
Title "SupplyzPro — Smart, Simple ERP for Your Business" says more than the site name.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description exists
Looks good · Metadata · Measured on your page
Observed evidence
Meta description found: "Discover SupplyzPro — a simple, all-in-one, AI-powered workspace to manage your business: …"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Titles unique across pages
Looks good · Metadata · Measured on your page
Observed evidence
All 3 indexable sampled pages have distinct titles.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Homepage isn't noindexed
Looks good · Metadata · Measured on your page
Observed evidence
No blocking robots meta tag on the homepage.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Character encoding declared
Looks good · Metadata · Measured on your page
Observed evidence
UTF-8 declared in a meta tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTML5 doctype
Looks good · Metadata · Measured on your page
Observed evidence
HTML5 doctype declared.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta keywords tag
Looks good · Metadata · Measured on your page
Observed evidence
No obsolete meta keywords tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Valid metadata order in <head>
Looks good · Metadata · Measured on your page
Observed evidence
No invalid element interrupts metadata in <head>.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Indexing16Looks good
100/100Looks good: Single canonical declaration
Looks good · Indexing · Measured on your page
Observed evidence
One canonical declaration found.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Noindex and canonical agree
Looks good · Indexing · Measured on your page
Observed evidence
No conflicting noindex and cross-page canonical instructions.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta-refresh redirect
Looks good · Indexing · Measured on your page
Observed evidence
No meta-refresh redirect.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No soft-404 response
Looks good · Indexing · Measured on your page
Observed evidence
No soft-404 pattern on sampled HTTP 200 pages.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical target integrity
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is a valid https URL. Its host is checked by the canonical consistency check.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled URLs have aligned indexability signals
Looks good · Indexing · Measured on your page
Observed evidence
Indexability signals align across 3 sampled URL(s).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 10 more checks
Looks good: robots.txt exists
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt responds with 200.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: robots.txt doesn't block everything
Looks good · Indexing · Measured on your page
Observed evidence
The audited URL is allowed for Googlebot. Most specific matching path; allow wins equal-length conflicts.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap exists
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap found at https://supplyzpro.com/sitemap.xml.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap parses and lists URLs
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap lists 3 same-origin URLs.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap declared in robots.txt
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt declares the sitemap.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical URL set
Looks good · Indexing · Measured on your page
Observed evidence
Canonical set: https://supplyzpro.com/
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical is absolute and self-referencing
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is absolute and points at this page.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: www vs apex consistency
Looks good · Indexing · Measured on your page
Observed evidence
Hostname is used consistently (supplyzpro.com).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: URLs are readable slugs
Looks good · Indexing · Measured on your page
Observed evidence
URL slugs are readable (3 sampled).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled pages expose search-access signals
Looks good · Indexing · Measured on your page
Observed evidence
No restrictive search-access signal on 3 sampled page(s). Actual indexing is not verified.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Content1Could be better9Looks good1Informational
100/100Could be better: Text-to-HTML ratioVisible text is 1.8% of the HTML markup (scripts and styles excluded).
Could be better · Content · Review suggested
Observed evidence
Visible text is 1.8% of the HTML markup (scripts and styles excluded).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.
Recommended fix
Text-to-HTML ratio is not a ranking factor, but a very low value often means deeply nested markup or content that only appears after JavaScript runs. Check the source-content checks before changing anything.
Not measured: ReadabilityFlesch reading ease ≈ 39.
Not measured · Content · Not established
Observed evidence
Flesch reading ease ≈ 39.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
60+ reads easily for most visitors. This is a heuristic, not a rule — technical audiences tolerate denser text.
Looks good: Crawlable content in source HTML
Looks good · Content · Measured on your page
Observed evidence
No recognized empty JavaScript application shell on 3 sampled page(s). The entered page exposes 720 publisher word(s).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage content volume
Looks good · Content · Measured on your page
Observed evidence
The audited page has about 720 words of main content.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No placeholder text
Looks good · Content · Measured on your page
Observed evidence
No placeholder text detected on crawled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No starter-template leftovers
Looks good · Content · Measured on your page
Observed evidence
No starter-template artifacts detected.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Title and H1 agree
Looks good · Content · Measured on your page
Observed evidence
Title and H1 share topic words: business.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Crawled pages aren't near-duplicates
Looks good · Content · Measured on your page
Observed evidence
No near-duplicate main content among 3 indexable sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Outbound references
Looks good · Content · Measured on your page
Observed evidence
20 outbound link(s) present.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Discovery copy is distinct across sampled pages
Looks good · Content · Measured on your page
Observed evidence
No repeated description, H1, or publisher copy across 3 sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Structured dataNot measured
Not measuredCould be better: JSON-LD presentNo JSON-LD structured data on the homepage.
Could be better · Structured data · Review suggested
Observed evidence
No JSON-LD structured data on the homepage.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.
Recommended fix
Add Organization and WebSite schema. They state who publishes the site and what it is called, which is what rich results and answer engines read first.
Could be better: Organization or WebSite schemaNo Organization, WebSite or Person schema found.
Could be better · Structured data · Review suggested
Observed evidence
No Organization, WebSite or Person schema found.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.
Recommended fix
Add an identity node so search engines and AI assistants can attribute your content to a real entity.
Not applicable: JSON-LD parsesNo JSON-LD blocks were found, so there is no syntax to validate.
Not applicable · Structured data · Measured on your page
Observed evidence
No JSON-LD blocks were found, so there is no syntax to validate.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.
Recommended fix
Add a <script type="application/ld+json"> block describing the page — Organization or WebSite is the usual starting point.
Not applicable: Content-specific schemaNo content-specific schema (Article, Product, FAQPage…) detected.
Not applicable · Structured data · Measured on your page
Observed evidence
No content-specific schema (Article, Product, FAQPage…) detected.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.
Recommended fix
If you publish articles, products or FAQs, add the matching schema type — that's what makes rich results (stars, FAQs, prices) possible.
Headings3Could be better4Looks good
83/100Could be better: Heading levels don't skip3 heading level skips: H1 → H4 "30% Fewer Errors"; H2 → H4 "Book a 30-minute call"; H2 → H4 "Start for Free".
Could be better · Headings · Review suggested
Observed evidence
3 heading level skips: H1 → H4 "30% Fewer Errors"; H2 → H4 "Book a 30-minute call"; H2 → H4 "Start for Free".
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. It is there, but weaker than this check expects.
Recommended fix
Use the next level down for each subsection (H2 under H1, H3 under H2). If a heading level was chosen for its font size, keep the level and change the styling instead.
Could be better: Element IDs are unique per document1 duplicate ID occurrence(s) across 1 document(s).
Could be better · Headings · Measured on your page
Observed evidence
1 duplicate ID occurrence(s) across 1 document(s).
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. It is there, but weaker than this check expects.
Recommended fix
Give each element a unique id and update fragment links and aria-labelledby references to point to the intended element.
Affected pages (1)
- https://supplyzpro.com/
Could be better: Single H1The homepage has 2 <h1> elements.
Could be better · Headings · Review suggested
Observed evidence
The homepage has 2 <h1> elements.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. It is there, but weaker than this check expects.
Recommended fix
Review whether one main heading and subordinate H2 sections would make the outline clearer. Multiple H1s alone do not establish a search-ranking problem.
Looks good: H1 exists
Looks good · Headings · Measured on your page
Observed evidence
H1 found: "Run your Business Directly through WhatsApp"
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: H1 has real text
Looks good · Headings · Measured on your page
Observed evidence
H1 reads "Run your Business Directly through WhatsApp".
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Headings are descriptive
Looks good · Headings · Measured on your page
Observed evidence
36 headings, averaging 4.1 words — descriptive.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is sectioned with H2s
Looks good · Headings · Measured on your page
Observed evidence
8 H2 section(s) structure the page.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Images2Could be better2Looks good
69/100Could be better: Modern image formats14 of 14 raster images are served only as PNG or JPEG: Q2fnliVJFChWjPxtrRPE2rT8cE.png, sH1F1DrNR7iaqHPP438pIhJ7krM.png, nDscEFdhlkFGaI4yvpMmUsLYO4I.png, ….
Could be better · Images · Review suggested
Observed evidence
14 of 14 raster images are served only as PNG or JPEG: Q2fnliVJFChWjPxtrRPE2rT8cE.png, sH1F1DrNR7iaqHPP438pIhJ7krM.png, nDscEFdhlkFGaI4yvpMmUsLYO4I.png, ….
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.
Recommended fix
Serve WebP or AVIF versions, which are usually 25–50% smaller at the same quality. Use <picture> with a WebP/AVIF <source> and the original as fallback, or an image CDN or framework image component that converts automatically.
Could be better: Lazy loadingNone of the 15 visible images are lazy-loaded (no loading="lazy" and no lazy-loading library markers).
Could be better · Images · Review suggested
Observed evidence
None of the 15 visible images are lazy-loaded (no loading="lazy" and no lazy-loading library markers).
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.
Recommended fix
Add loading="lazy" to below-the-fold images so the initial render doesn't wait on them. Keep the hero image eager.
Looks good: Alt text coverage
Looks good · Images · Measured on your page
Observed evidence
All 15 visible images declare alt attributes (including empty alt for decorative images). Whether each description fits its image needs a human look.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Width/height attributes
Looks good · Images · Measured on your page
Observed evidence
All 15 visible images declare dimensions or are sized by their container.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Links3Could be better2Looks good1Informational
91/100Could be better: Anchor text is meaningful9 of 28 links have unclear anchor text: 9 with no text or label (e.g.
Could be better · Links · Review suggested
Observed evidence
9 of 28 links have unclear anchor text: 9 with no text or label (e.g. ./).
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.
Recommended fix
Make each link say where it goes ("Read the pricing guide" rather than "Read more"). For icon-only links, add an aria-label. Anchor text tells crawlers and screen-reader users what the destination is about.
Affected pages (1)
- https://supplyzpro.com/
Could be better: External links use rel=noopener22 external link(s) open in a new tab without rel="noopener".
Could be better · Links · Review suggested
Observed evidence
22 external link(s) open in a new tab without rel="noopener".
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.
Recommended fix
Current browsers already treat target="_blank" as noopener, so the remaining risk is limited to older browsers. Adding rel="noopener" keeps the opened page from controlling yours there too.
Could be better: Homepage links into the siteThe homepage links to only 2 distinct internal page(s).
Could be better · Links · Review suggested
Observed evidence
The homepage links to only 2 distinct internal page(s).
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.
Recommended fix
Link generously to your key pages from the homepage — it's how crawlers discover them and how PageRank flows.
Not applicable: Same-page links have source targetsNo same-page fragment links to check.
Not applicable · Links · Measured on your page
Observed evidence
No same-page fragment links to check.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. This check does not apply to the features observed in this sample.
Recommended fix
Keep section links connected to stable IDs.
Looks good: Internal links resolve
Looks good · Links · Measured on your page
Observed evidence
All 3 sampled internal links return < 400.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No dead placeholder links
Looks good · Links · Measured on your page
Observed evidence
No placeholder links on the audited page.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Mobile1Could be better3Looks good2Informational
76/100Could be better: Interactive controls have source labels27 of 98 source controls lack a detectable name.
Could be better · Mobile · Measured on your page
Observed evidence
27 of 98 source controls lack a detectable name.
Why this matters
Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.
Recommended fix
Give each control visible text, a connected label, aria-label or aria-labelledby. Placeholder and neighboring text alone do not name an input. Verify the browser accessibility tree after fixing.
Affected pages (3)
- https://supplyzpro.com/
- https://supplyzpro.com/fr
- https://supplyzpro.com/ar
Not measured: No tiny inline font sizesNo sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Not measured · Mobile · Not established
Observed evidence
No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Check computed font sizes in a browser across mobile widths.
Not applicable: ARIA references point to source elementsNo ARIA ID references found in the sampled HTML.
Not applicable · Mobile · Measured on your page
Observed evidence
No ARIA ID references found in the sampled HTML.
Why this matters
Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.
Recommended fix
Verify rendered accessibility separately.
Looks good: Viewport meta tag
Looks good · Mobile · Measured on your page
Observed evidence
Viewport configured: "width=device-width".
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Pinch zoom not disabled
Looks good · Mobile · Measured on your page
Observed evidence
The viewport lets users zoom.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Responsive image markup
Looks good · Mobile · Measured on your page
Observed evidence
34/35 images ship responsive srcset variants.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Language2Looks good1Informational
100/100Not applicable: hreflang syntaxNo hreflang tags — fine for single-language sites.
Not applicable · Language · Measured on your page
Observed evidence
No hreflang tags — fine for single-language sites.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.
Recommended fix
Only add hreflang if you publish the same content in multiple languages/regions.
Looks good: html lang attribute
Looks good · Language · Measured on your page
Observed evidence
Language declared: lang="en".
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Declared language matches content
Looks good · Language · Measured on your page
Observed evidence
Declared language (en) matches detected content language.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Branding2Looks good2Informational
100/100Not measured: Web app manifestNo web manifest linked.
Not measured · Branding · Not established
Observed evidence
No web manifest linked.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Optional, but a manifest.json enables install prompts and better mobile integration.
Not measured: Theme colorNo theme-color meta tag.
Not measured · Branding · Not established
Observed evidence
No theme-color meta tag.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Add <meta name="theme-color"> to tint the mobile browser UI to your brand color. Small touch, feels polished.
Looks good: Favicon
Looks good · Branding · Measured on your page
Observed evidence
Favicon declared via <link rel="icon"> (https://framerusercontent.com/images/u4YeZqCwRFtXsh59xjyJDPJsIv8.png).
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Apple touch icon
Looks good · Branding · Measured on your page
Observed evidence
apple-touch-icon is declared.
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Performance
Measured from the audited response and its markup. These are source observations, not field Core Web Vitals.
| Measure | This site | Reading |
|---|---|---|
| No render-blocking head scripts | 2% | Could be better: needs attention1 synchronous script(s) in <head> block rendering: https://cdn-cookieyes.com/client_data/98a8ec297229ced46c629503/script.%E2%80%A6. |
| HTML payload size | 416 KB | Could be better: needs attentionThe page's HTML is 416 KB uncompressed. |
| Inline styles are bounded | 159 KB | Could be better: needs attention159 KB of inline <style> in the page. |
| Web fonts don't block text | — | Informational: not applicableNo Google Fonts stylesheet links detected. |
| Server response time | 215 ms | Looks good: goodThe audit received response headers after 215 ms from one test location. |
| Script/stylesheet count | — | Looks good: good4 total script/style resources — reasonable. |
| HTML served compressed | — | Looks good: goodHTML is compressed with br. |
| Iframe usage | — | Looks good: goodNo iframes. |
| Source HTML weight | 416.4 KB | Informational: measured source, not transferred bytes416.4 KB of HTML on the audited page |
From a single automated fetch of the audited page. A quick reading, not a substitute for Lighthouse or field data.
Security
HTTPS, transport security and the response headers the audited pages send.
Could be better: Frame embedding protectionNo frame-embedding restriction was observed (neither CSP frame-ancestors nor X-Frame-Options).
Could be better · Security · Review suggested
Observed evidence
No frame-embedding restriction was observed (neither CSP frame-ancestors nor X-Frame-Options).
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Send Content-Security-Policy: frame-ancestors 'self' (or 'none', or a list of partner origins), or X-Frame-Options: SAMEORIGIN. It stops other sites from framing your pages to trick visitors into clicking (clickjacking).
Could be better: Content Security PolicyNo Content-Security-Policy detected.
Could be better · Security · Review suggested
Observed evidence
No Content-Security-Policy detected.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Configure an enforced policy for script and resource origins; use report-only monitoring to prepare changes safely.
Could be better: Browser feature permissionsNo explicit restriction on sensitive browser features was observed.
Could be better · Security · Review suggested
Observed evidence
No explicit restriction on sensitive browser features was observed.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Disable unused camera, microphone, or geolocation access using Permissions-Policy.
Not applicable: Password forms avoid URL submissionNo enabled, named password inputs in sampled HTML.
Not applicable · Security · Measured on your page
Observed evidence
No enabled, named password inputs in sampled HTML.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. This check does not apply to the features observed in this sample.
Recommended fix
Review authentication forms separately when applicable.
Looks good: Site serves over HTTPS
Looks good · Security · Measured on your page
Observed evidence
Site serves over HTTPS.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTTP redirects to HTTPS
Looks good · Security · Measured on your page
Observed evidence
http:// permanently redirects to https://./
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HSTS header
Looks good · Security · Measured on your page
Observed evidence
HSTS is set: max-age=31536000.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Referrer policy
Looks good · Security · Measured on your page
Observed evidence
No Referrer-Policy is set, so browsers apply their default, strict-origin-when-cross-origin, which sends only the origin to other sites.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: X-Content-Type-Options
Looks good · Security · Measured on your page
Observed evidence
nosniff is set.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No mixed content
Looks good · Security · Measured on your page
Observed evidence
No insecure subresources detected.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Server technology disclosure
Looks good · Security · Measured on your page
Observed evidence
No X-Powered-By disclosure.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Declared form submission targets
Looks good · Security · Measured on your page
Observed evidence
3 declared form(s) submit over HTTPS to this site. Runtime submission behavior is untested.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AI answer readiness
Retrieval signals an answer engine relies on: crawler access, clear entities and answers it can quote. These checks do not measure citations or traffic.
Could be better: Semantic HTML structureSemantic landmarks exist (4) but there's no <main> or role="main".
Could be better · AI answer readiness · Review suggested
Observed evidence
Semantic landmarks exist (4) but there's no <main> or role="main".
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Wrap the primary content in one <main>. Readers, screen readers and content extractors use it to find the substance and skip the navigation and footer.
Could be better: llms.txtNo /llms.txt file.
Could be better · AI answer readiness · Review suggested
Observed evidence
No /llms.txt file.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Optional: publish an llms.txt index of useful pages. This proposal is not a requirement for Google AI features, and its absence does not reduce the core score.
Could be better: FAQ/QA schemaNo FAQPage or QAPage schema on any crawled page.
Could be better · AI answer readiness · Review suggested
Observed evidence
No FAQPage or QAPage schema on any crawled page.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
If the page answers recurring questions, use visible question-and-answer content and matching FAQPage markup. QAPage is for a single question with user-submitted answers. Google FAQ rich results are restricted to eligible authoritative government and health sites; markup does not guarantee AI citations.
Could be better: Question-style headingsOnly 1% of 68 H2/H3 headings are question-shaped.
Could be better · AI answer readiness · Review suggested
Observed evidence
Only 1% of 68 H2/H3 headings are question-shaped.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Phrase key subheadings as the questions users actually ask ("How much does X cost?"). This improves the measured question-heading signal; the audit does not guarantee citations.
Could be better: Definitional openingThe opening paragraph doesn't define what the site/topic is: "EN…"
Could be better · AI answer readiness · Review suggested
Observed evidence
The opening paragraph doesn't define what the site/topic is: "EN…"
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
"X is a Y that does Z for W" in the first paragraph gives answer engines a liftable definition of you. Write it once, benefit everywhere.
Could be better: Freshness signalsNo dateModified schema or visible 'updated' dates found.
Could be better · AI answer readiness · Review suggested
Observed evidence
No dateModified schema or visible 'updated' dates found.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
For content where dates matter, show the actual update date and mirror it in dateModified. Do not invent dates or change them without a substantive update. Missing dates alone do not prove stale content.
Could be better: Consistent brand entityThe site does not declare its name: no og:site_name and no Organization or WebSite schema.
Could be better · AI answer readiness · Review suggested
Observed evidence
The site does not declare its name: no og:site_name and no Organization or WebSite schema.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Declare the site's name once in Organization or WebSite schema and in og:site_name, using the same name as the title. Readers, search engines and AI assistants then attribute the pages to one named publisher.
Could be better: Question headings have concise answers0/1 question-shaped heading(s) have a 20–500 character paragraph immediately after them.
Could be better · AI answer readiness · Measured on your page
Observed evidence
0/1 question-shaped heading(s) have a 20–500 character paragraph immediately after them.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Put a direct 20–500 character answer paragraph immediately after each question heading so retrieval systems can quote it cleanly.
Affected pages (1)
- https://supplyzpro.com/
Could be better: Machine-readable provenance signalsOnly 2 of 4 provenance signal types were found: author, contact.
Could be better · AI answer readiness · Measured on your page
Observed evidence
Only 2 of 4 provenance signal types were found: author, contact.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Add the missing author, date, breadcrumb, or contact signal so machines can identify provenance and site structure.
Affected pages (3)
- https://supplyzpro.com/
- https://supplyzpro.com/fr
- https://supplyzpro.com/ar
Could be better: Markdown copies of pagesNo markdown copy answered at /index.md or /fr.md or /index.html.md.
Could be better · AI answer readiness · Measured on your page
Observed evidence
No markdown copy answered at /index.md or /fr.md or /index.html.md.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Publish a clean markdown copy of each key page at /page.md (or /page.html.md). It strips navigation and scripts, so a retriever spends its budget on your content.
Affected pages (2)
- https://supplyzpro.com/
- https://supplyzpro.com/fr
Not measured: llms-full.txtNo /llms-full.txt.
Not measured · AI answer readiness · Not established
Observed evidence
No /llms-full.txt.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Optional companion to llms.txt containing your full content as one markdown file — useful for sites whose pages are JS-heavy.
Not measured: Citable facts density31 concrete figures across 724 words.
Not measured · AI answer readiness · Not established
Observed evidence
31 concrete figures across 724 words.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Good — keep facts specific and current, and date-stamp them.
Not measured: llms.txt links resolve to this siteNo readable llms.txt was available to inspect for Markdown links.
Not measured · AI answer readiness · Not established
Observed evidence
No readable llms.txt was available to inspect for Markdown links.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish a readable llms.txt, then link its important pages with same-origin Markdown URLs.
Not applicable: Entity identity agrees across signalsThe page declares no site or organization name (no og:site_name and no Organization or WebSite schema name), so there is nothing to compare.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
The page declares no site or organization name (no og:site_name and no Organization or WebSite schema name), so there is nothing to compare.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
Declare the site's name once in Organization or WebSite schema and in og:site_name, and use the same name in the title.
Not measured: llms.txt follows the specNo readable /llms.txt, so its structure cannot be checked.
Not measured · AI answer readiness · Not established
Observed evidence
No readable /llms.txt, so its structure cannot be checked.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish llms.txt first — the llms.txt check covers that — then this one verifies the structure.
Not applicable: Advertised machine interfaces are inspectableNo OpenAPI interface was advertised by sampled HTML.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
No OpenAPI interface was advertised by sampled HTML.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
An API is optional. Add a service-desc link if you already publish a machine-readable API specification.
Looks good: AI crawler access
Looks good · AI answer readiness · Measured on your page
Observed evidence
The audited URL is allowed for evaluated answer-search crawlers.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Answers lead the section
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs get to the point without preamble.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is chunkable
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs average 9 words, lists present — chunk-friendly.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Cites external sources
Looks good · AI answer readiness · Measured on your page
Observed evidence
60 outbound reference(s) across crawled pages.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Description reads as a liftable summary
Looks good · AI answer readiness · Measured on your page
Observed evidence
Meta description works as a standalone summary.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Accept: text/markdown negotiation
Looks good · AI answer readiness · Measured on your page
Observed evidence
The homepage answers Accept: text/markdown with markdown.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AdSense readinessOptional
Publisher-policy signals, for sites that plan to carry ads. These checks do not affect the overall score or grade, and they do not measure or guarantee AdSense approval.
On its own, this site scores 39/100 for publisher readiness. Ignore this section if you do not run ads.
Needs a fix: Privacy policy pageNo privacy policy page is linked or crawlable.
Needs a fix · AdSense policy · Review suggestedCritical
Observed evidence
No privacy policy page is linked or crawlable.
Why this matters
A publisher review looks for this before it accepts a site. Right now the sampled pages don't provide it.
Recommended fix
Publish an accessible privacy policy that discloses cookies and data use by Google and other third-party ad vendors.
Could be better: Terms pageNo terms of use page found.
Could be better · AdSense policy · Review suggested
Observed evidence
No terms of use page found.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Consider adding terms that identify the service rules and publisher. This is a transparency heuristic, not an AdSense requirement.
Could be better: About pageNo about page found.
Could be better · AdSense policy · Review suggested
Observed evidence
No about page found.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Add an About page that identifies the publisher, site purpose, and relevant experience. This supports content transparency but is not a standalone AdSense requirement.
Could be better: Contact methodNo contact page or mailto link found.
Could be better · AdSense policy · Review suggested
Observed evidence
No contact page or mailto link found.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Add a working contact route or visible email so users can reach the publisher. This is a trust heuristic, not a published approval rule.
Not measured: Privacy policy advertising disclosuresA privacy page was not present in the crawl sample, so its disclosures could not be verified.
Not measured · AdSense policy · Not established
Observed evidence
A privacy page was not present in the crawl sample, so its disclosures could not be verified.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Confirm the policy explains cookies or similar storage, Google or advertising vendors, and third-party data use.
Not measured: ads.txtNo ads.txt yet.
Not measured · AdSense policy · Not established
Observed evidence
No ads.txt yet.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
When AdSense provides your publisher entry, publish it exactly at /ads.txt and monitor authorization status in your account.
Not applicable: Article-style content existsNo article/blog-style pages detected among crawled pages.
Not applicable · AdSense policy · Measured on your page
Observed evidence
No article/blog-style pages detected among crawled pages.
Why this matters
A publisher review looks for this before it accepts a site. This check does not apply to the features observed in this sample.
Recommended fix
No action is required solely because articles are absent. For tool or directory sites, make the unique publisher value and explanation crawlable on each relevant screen.
Not measured: Domain age & historyDomain age isn't visible from the site itself.
Not measured · AdSense policy · Not established
Observed evidence
Domain age isn't visible from the site itself.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Do not use age as a content-quality proxy. Verify ownership and account eligibility in AdSense; Google's general eligibility page publishes no domain-age threshold.
Not measured: Latest article has real depthNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then reads the newest one.
Not measured: Latest article reads as edited workNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then reviews its style signals.
Not measured: Latest article names an author and a dateNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then looks for its byline and date.
Looks good: First-party contact email
Looks good · AdSense policy · Measured on your page
Observed evidence
First-party contact email found: contact@supplyzpro.com.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled publisher-content coverage
Looks good · AdSense policy · Review suggested
Observed evidence
All 3 editorial pages expose at least 250 publisher words; those pages hold 2212 publisher words in total.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Thin page share
Looks good · AdSense policy · Review suggested
Observed evidence
3/3 editorial pages clear the audit's publisher-content triage threshold.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No ads on non-content screens
Looks good · AdSense policy · Published platform rule
Observed evidence
No Google ad code detected on sampled non-content screens.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Tool pages expose explanatory content
Looks good · AdSense policy · Review suggested
Observed evidence
All 3 sampled tool-style screens include crawlable explanation.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content differs across URLs
Looks good · AdSense policy · Review suggested
Observed evidence
No high publisher-content repetition among 2 substantial sampled page(s).
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content exists in source HTML
Looks good · AdSense policy · Measured on your page
Observed evidence
No empty client-rendered publisher shell in the crawl sample.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 4 more checks
Looks good: No "coming soon" or placeholder pages
Looks good · AdSense policy · Measured on your page
Observed evidence
No "coming soon", "under construction" or lorem-ipsum text on crawled pages.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Site language is AdSense-supported
Looks good · AdSense policy · Measured on your page
Observed evidence
Language "en" is AdSense-supported.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Policy pages linked site-wide
Looks good · AdSense policy · Measured on your page
Observed evidence
All 3 crawled pages link to the privacy policy.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Existing ad scripts
Looks good · AdSense policy · Measured on your page
Observed evidence
No competing ad scripts on the page.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Hosting and infrastructure
Public endpoint facts observed at audit time. A CDN or proxy can conceal the origin infrastructure.
| Hostname | supplyzpro.com |
|---|---|
| IP addresses | 31.43.160.6, 31.43.161.6 |
| DNS A | 31.43.160.6 · 31.43.161.6 |
| DNS NS | austin.ns.cloudflare.com · anita.ns.cloudflare.com |
| DNS MX | 0 supplyzpro-com.mail.protection.outlook.com |
| TLS | TLSv1.3TLS_AES_128_GCM_SHA256 |
| Certificate issuer | Let's Encrypt / YE1 |
| Certificate valid until | Feb 2 11:01:21 2027 GMT |
| Certificate validation | Passed |
Website anatomy and diagnostics
Explore links, resources, crawler access and site integrations.
Page architecture
Choose a page to explore its details and connections.
Page content
720 publisher words
Page structure
html content
Observed discovery
Depth 0 · 2 incoming links
HTTP 200 · 416.4 KB source
Source interactions
34 controls · 9 unnamed
4 script / 0 stylesheet references
- Canonical declaration
- https://supplyzpro.com/
- Schema types
- None observed
- Outgoing links in sampled graph
- /fr · /ar
Routes: / · /fr · /ar
Resource origins 5
Resources associated with your website. External resources may belong to the same organization.
- https://framerusercontent.com/image, script · 105 references · cross origin
- https://cdn-cookieyes.com/script · 3 references · cross origin
- https://www.googletagmanager.com/script · 3 references · cross origin
- https://events.framer.com/script · 3 references · cross origin
- https://api.producthunt.com/image · 3 references · cross origin
Crawler policy by page
Review crawler access for your pages. Search, training and user-triggered services have different purposes; declared access does not guarantee discovery.
| Crawler / purpose | Page | Policy | Matched directive |
|---|---|---|---|
| Googlebotsearch | / | allowed | allow: / |
| Googlebotsearch | /fr | allowed | allow: / |
| Googlebotsearch | /ar | allowed | allow: / |
| bingbotsearch | / | allowed | allow: / |
| bingbotsearch | /fr | allowed | allow: / |
| bingbotsearch | /ar | allowed | allow: / |
| OAI-SearchBotsearch | / | allowed | allow: / |
| OAI-SearchBotsearch | /fr | allowed | allow: / |
| OAI-SearchBotsearch | /ar | allowed | allow: / |
| PerplexityBotsearch | / | allowed | allow: / |
| PerplexityBotsearch | /fr | allowed | allow: / |
| PerplexityBotsearch | /ar | allowed | allow: / |
| Claude-SearchBotsearch | / | allowed | allow: / |
| Claude-SearchBotsearch | /fr | allowed | allow: / |
| Claude-SearchBotsearch | /ar | allowed | allow: / |
| GPTBottraining | / | allowed | allow: / |
| GPTBottraining | /fr | allowed | allow: / |
| GPTBottraining | /ar | allowed | allow: / |
| ClaudeBottraining | / | allowed | allow: / |
| ClaudeBottraining | /fr | allowed | allow: / |
| ClaudeBottraining | /ar | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | / | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /fr | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /ar | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | / | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /fr | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /ar | allowed | allow: / |
Advertised APIs and machine interfaces
No supported machine interfaces were advertised in the sampled HTML. An API or MCP server is optional; undiscovered interfaces remain unknown.
Public DNS and TLS endpoint
supplyzpro.com · observed · 31.43.160.6, 31.43.161.6
- A
- 31.43.160.6 · 31.43.161.6
- AAAA
- Unavailable for this exact hostname
- CNAME
- Unavailable for this exact hostname
- NS
- austin.ns.cloudflare.com · anita.ns.cloudflare.com
- MX
- 0 supplyzpro-com.mail.protection.outlook.com
- CAA
- Unavailable for this exact hostname
TLS: TLSv1.3
Certificate validation passed for the observed endpoint.
Issuer: Let's Encrypt / YE1
Certificate valid until: Feb 2 11:01:21 2027 GMT
PageSpeed measurement
Loading the PageSpeed panel…
Growth resources
Loading growth resources…
Where to take this site next
Follow-on work suggested by the observations above.
- 01
Your top fixes list is the priority order — clear the red items before creating more content.
- 02
Re-run the combined audit after each batch of fixes
Re-run after fixes to see which checks changed; score bands are guidance, not a guarantee of ranking, traffic, or approval.
- 03
Make policy pages, publisher disclosures and substantial content reachable before applying. This audit cannot predict approval.
Apply the recommended fixes
Hand the complete evidence to a coding agent, or take the report with you.
Report notes
- 01This report covers the sampled public pages listed above. Other pages may have different results.
- 02Browser-rendered content, private backend systems and authenticated experiences may require a separate review.
- 03Unavailable observations are identified in the report. Results do not guarantee rankings, citations, security, accessibility or advertising approval.
Pages included in this report
- https://supplyzpro.com/
- https://supplyzpro.com/fr
- https://supplyzpro.com/ar