SEO on a public page
Title, description, canonical tag, and HTML headings on the submitted product or category page.
For e-commerce sites
A product, category, or home page can reveal visibility, loading, and trust issues. Argos measures what it can access on the submitted URL and helps prioritize fixes.
Get startedCart, ordering, and payment steps are not traversed.
Title, description, canonical tag, and HTML headings on the submitted product or category page.
Lighthouse and browser measurements on that page when the site allows analysis.
HTTPS, redirects, and HTTP headers; no transaction is made.
Detectable signals and a Lighthouse score, to be complemented by user testing.
Find technical obstacles on a page that matters in your catalog.
Share actionable findings about loading, tags, or headers.
Compare your own metrics after changes; the audit does not predict sales.
Illustrative example
A product page with a missing description, slow loading, and images without alternative text may yield issues to review. This example covers one URL and is not drawn from a client report.
Paste the address of a public page that matters to your business.
Argos runs its checks and prepares a private report, available through a link.
Review the findings and priorities, then validate the changes that make sense.
Argos brings together the HTTP response, headers, HTML tags, browser measurements and available analysis services. Findings are grouped into performance, security, SEO and accessibility. It examines one public URL: it does not crawl the whole site, test signed-in areas or certify security or accessibility. Check coverage and unavailable modules before drawing conclusions.
| Tool | Choose it to | Keep in mind |
|---|---|---|
| Argos | Get an initial cross-disciplinary diagnosis and actions to discuss with your provider: HTML, HTTP, TLS, browser and Lighthouse signals when available. | Argos uses its own score weights. Its score cannot be compared directly with Lighthouse and does not represent real visits. |
| PageSpeed Insights | Examine mobile and desktop performance using Lighthouse diagnostics and CrUX usage data when available. | Field data may be missing or apply to the origin instead of the page. Also review user journeys and server configuration. |
| Lighthouse | Investigate performance, accessibility, best practices and SEO diagnostics, then repeat measurements under controlled conditions. | Lab measurements vary and automated checks cannot validate real user journeys alone. |
References: PageSpeed Insights · Lighthouse
For a store: start with a representative product page. Manually check variant selection, adding to the cart and payment; fix blockers before optimizing images and tags. Audit key public pages separately: Argos does not simulate an order or test customer accounts.
See evidence and corrections in the public example reportSubmit a public product or category page for a concrete starting point.